Jump to content

nlight

Members
  • Posts

    160
  • Joined

  • Last visited

Posts posted by nlight

  1. Version 1.6.2 is up on KerbalStuff (and CKAN soon) and fixes the MechJeb issue. Thanks for reporting issues, I will get to everyone in time. Stay tuned.

    Quote

    That's strange because if I change the "incremental action sensitivity" and "Discrete action step" I'm not noticing much difference in sensitivity.

    I'm sorry I should have been more clear. There is a setting called "Precision mode" which allows for configurable sensitivity. You can find it by clicking the "Mod settings" button on the main AFBW screen, then turn it on via the checkbox and configure the sensitivity you want using the slider. You also have to bind a button to toggle it via "Add button" from the AFBW preset editor. At the moment this only allows you to get lower sensitivity. As an addition to that you could try to switch to using "quadratic" curves from advanced settings in the controller config window.

  2. 21 hours ago, frango9000 said:

    sorry to bother if this has been answered before, i did search but no luck for me, i have 1.0.5 with many mods, on AFBW install, mechjeb simply fails to control the vessel... any wise advice for what is probably a silly thing? i can post logs and list of mods if needed...

    I will look into this, thanks for the report.

    12 hours ago, vixr said:

    A quick question for nlight... once I use CKAN to install AFBW,(which is working flawlessly) must I continue to use CKAN? Can I just use my KSP stock desktop shortcut launcher?

    You don't have to use CKAN once you have installed the mods though you should probably open it every once in a while to check for updates.

  3. However I am having a huge issue where as soon as I start to pick up a decent amount of speed on my aircraft it starts culling the maximum joystick inputs severely.

    Are you sure that's not something NEAR is doing and not AFBW? If it's not I guess the devs implemented something in 0.90 and, again, didn't tell us.. I summon ddaf to investigate as he's dealt more lately with that part of the code :P

    It turns out the initial position of my throttle slider has an influence on that problem

    Yes, it does. When you click calibrate AFBW assumes that the controller is "at rest", meaning that all axes are at their identity values (most likely 0.0f for most controllers). The issue here is that your throttle slider doesn't return to its identity (0.0f) automatically when you release the controller - the solution is to manually put the slider at the minimum possible position before clicking Calibrate.

    As for where the settings are saved, that's in the big xml in the main folder AFBW.

    I tend to back this file up in case I start KSP without the joystick connected, which seems to make AFBW forget about the settings.

    That doesn't seem to include calibration data though, and I can't figure out where this is going....

    The whole configuration is in the single XML file. Look for the <axisConfigurations> tag.

    And I say that having played with no WSAD when no SAS and half throttle range for the past week. :wink:

    Sorry about that, I'll try to do better. Thanks for the feedback and the support, if it wasn't for you guys I would have given up on KSP/ Unity's idiosyncrasies a long time ago :)

  4. Can't get it to work. Failed to download github.com/ClawKSP/KSP-Stock-Bug-Fix-Modules/releases/download/v0.1.7e/StockBugFixModules v0.1.7e.zip -error. The file name has changed so CKAN aborts and does nothing !

    There should be an option to make in install all the other selected mods and just skip the bad one in can't find it. Letting you know which mods needed it. That way users to manually go and hunt the file.

    At present I think if this happens you need to manually install every mod because CKAN aborts install every time.

    EDIT: Creating a file in the CKAN directory still will not help. This error has totally screwed CKAN for now.

    This issue is fixed now.

  5. Do I lost my pre-sets by updating from 1.5 to 1.51? :-), not using CKAN, but I could if it's the only way (got it installed anyway)

    No, you shouldn't lose your presets. I try my best to break the config only when changing the major version and put a warning in the changelog.

    I am running Windows 8.1 and still not getting the joystick recognized. I saw the issue was closed on Github, so should that be working now?

    Windows 8.1 and AFBW have a love/ hate kind of relationship, for some people it works flawlessly, others can't ever get AFBW to recognize their controllers. I am 99% sure that x360/ ps3 controllers work fine on windows 8.1 for all users, but SDL has some issues which I can't seem to solve. I will try upgrading to the latest SDL version for next release and we'll see what happens.

    on my Logitech 3D pro the throttle outputs positive numbers for the top half and negitive numbers for the bottom. This mod only detects the top half. Thus, the throttle doesn't function below the halfway mark.

    This has been on the TODO list for a while, I'll see what I can do. Thanks for the report.

  6. The GUI is really broken on Mac. Non-retina machine, OS X 10.9.5, Mono 3.12.0, CKAN 1.6.0. Lots of repaint problems. On launch, the Manage Mods tab doesn't fully render; when you click a checkbox it switches to the Changeset tab, but doesn't render the bottom part properly, so you have to switch back to Manage Mods (which IMO it should have stayed on in the first place). Functionally it seems okay.

    I'm sorry, this is due to numerous implementation bugs in Mono, nothing we can do really except rewrite the GUI in something like GTK+. This is something that will happen only if we get twice as many contributors as we have now.

    The changelog for 1.6.2 says:

    but this doesn't seem to be working (1.6.5). No matter how I leave the window sized or positioned, the next time I open it, it's back to the default size and position. Certainly there's nothing related to size/position in GUIConfig.xml, where I'd have expected to see the setting saved.

    I've implemented a fix upstream for this, the settings should now be saved in GUIConfig.xml, try the latest nightly build or wait for 1.6.6.

  7. I don't know if it's been requested already, but is there any way CKAN can be made to check if there are updates available for CKAN itself? I installed 1.55 when it was the latest version, and only today discovered it was now up to version 1.62.

    Hey, you are the first person to request this feature (seriously!). Actually we found this idea so novel that we decided to implement it immediately.

    So.. CKAN v1.6.3 is available now with auto-updates :)

  8. This mod doesn't recognize my controller. I would fill out the report as described in the OP, but no pastebin site seems to accept a 5721KB output file. I guess I could upload it to Dropbox, but since you so specifically state you want a pastebin site, I'm just going to ask first if a controller not being recognized is what you consider a bug anyway and needs to be reported or is some no-name controller not working just not worth the trouble for you. And also, of course, if Dropbox is fine.

    Hey, are you running windows 8.1?

  9. Ok, the mod seems far from stable, it seems.

    Hey, sorry you're experiencing issues, let's see what I can do to help.

    CKAN seems the only viable way to install this on win 8.1. Found some bugs with it and Toolbar installation.

    Oops, I am pretty sure I have forgotten to update the Toolbar mod for a looong time. This has been fixed now.

    Joysticks are randomly forgotten by the plugin, only fix i found is a clean reinstall, which erases the presets built. Where are these saved?

    Are you sure you've tested with 1.5, I thought we fixed that issue. Please report back on this.

    Overrides kerbal controls, so kerbals can no longer be controlled.

    Fixed in 1.5.1 by ddaf :)

    Maybe some interaction problems with other mods? I've had to cut down to the very basics.

    No, hopefully not. AFBW doesn't really modify anything that can screw up other mods, but still I will look into this if you give me a mod list.

    Anyway, v1.5.1 is up with ddaf's fix for the broken WASD controls.

  10. Hey guys, sorry I left you in the cold like this for almost two months. Not to worry though, we're back on track with the next AFBW release :)

    v1.5

    - Re-implemented SAS override (by ddaf)

    - Fixed the disappearing SDL controller config (by DeamonSix)

    - Fixed a bug where SDL would identify the "centered" position as a button (by badpandabear)

    - A big thank you to all contributors and thanks to all users for waiting so long for this update \o/

×
×
  • Create New...