Duck5674

Love this mod man keep up the good work! Two things to mention. 1) I had the same issue as others using the cut throttle command setting my throttle to 50% not zero. I found that the button actually resets my throttle to whatever the keyboard set the throttle to last. Because stock KSP now sets the throttle to 50% at take-off, pressing the "cut throttle" button on my controller sets it to that, 50%. I found an easy fix was simply to lower my throttle to zero using the keyboard before I took off. I simply press the "x" key on my keyboard and then the controller "cut throttle" button performs as expected. 2) This one is a little more serious. Whenever the GUI is open, my memory usage continues to increase until the game crashes. I noticed this because I flew with the presets GUI open for a while so I would not forget the controls I had mapped. The game crashed a couple of times due to over memory, and I'm fairly certain I've traced it down to the GUI being open. I re-tested it on a vanilla KSP+AFBW and got the same problem. Here are my specs: Windows 7 64-bit 8 GB of RAM KSP 0.90 -force-opengl Xbox 360 Controller AFBW v1.4 installed via CKAN Output_Log.txt Steps to recreate: Load a craft Allow memory to stabilize Open GUI interface from toolbar When I do this I can watch the memory usage for KSP increase in windows Resource Monitor. Closing the GUI immediately stops the memory increase, but it does not return it to pre-GUI memory (i.e. each time I open the GUI KSP utilizes slightly more memory). Re-opening the GUI again causes the memory to increase until it is closed again. Thus, I have a limited number of times to open the GUI before I crash KSP. Hope this helps. Let me know if you need more information.

That was my first thought as well, but it brings up the same message. I've tried completely removing KSP from my PC, re-downloading, and then re-installing FAR, but it still hasn't fixed the problem. That's why I'm here, to figure out if there is anything else I could try. Is there anything in vanilla KSP that could have been corrupted causing this or does it have to be a malfunction in one of the two mods? Also, when I use the FAR debug in the VAB it generates the drag model just fine & can even save it to a .cfg file while still yielding the error on the launchpad.

So is that a "don't worry about it, it's just outputting extra log information" or is it, "Somethings bad is definitely happening, but it's not on my end?" Thanks for the quick reply. ~Duck

KSP: 0.25 Windows 32bit Problem: Load up with FAR & debug menu spits out that it can't find the appropriate drag models Mods Installed: 1. Ferram Aerospace Research v0.14.3.2 2. Module Manager 2.5.1 Reproduction Steps: 1. Vanilla KSP 0.25 downloaded from steam 2. Copy folder "FerramAerospaceResearch" and file "ModuleManager.2.5.1.dll" to "GameData" folder. 3. Load KSP 4. New Save --> Sandbox Mode 5. Construct the following ship (or any ship really) ---Command Pod Mk1 ---RT-10 Solid Fuel Booster 6. Load craft on launch pad Log File: Here Game Data Folder Screenshot of in-game debug menu. PC Specs: Windows 7 Ultimate 64-bit Service Pack 1 8 GB RAM i5-4570 Is this an issue I should be worried about? It appears that my rockets travel significantly farther with this error than stock or my .23.5 install with FAR, but that might be apples to oranges. I appreciate any advice and help. Thanks. ~Duck