Prasiatko

Since this is the first thread that comes up on google when searching for a solution i will post what i did to get it to work here. First install procedural parts nad your other mods and run the game once so module manager makes some cfg files. Then open "ModuleManager.ConfigCache" found in the gamedata folder with something like notepad++. search for ProceduralParts/Parts/TechTree/Upgrades.cfg, you'll get a number of results and in the sections underneath you'll find a line that reads "techRequired = ...." replace whatever is after the = sign with "start" (minus the "")

I have similar issues. The only way i've found to mitigate it is to reduce the friction on the front wheel to a bare minimum. Even this doesn't solve the issue entirely for me but it is good enough for me to take off.

What it really needs if they still wish to include is someway to override it and live with the consequences.

Thanks! This worked enough for me to take off albeit still veering off centre down the run way That explains a lot. I thought i just had really shaky hands on my joystick. Was wondering why increasing deadzone didn't do much.

Any ideas wht this plane is spinning when i try to take off as soon as i reach about 40m/s it veers off to the right and in best case scenario will continue in a clockwise spin on the spot.

Even with the second level one i've found it is far easier to simply turn your plane 90o and use the miles of flat ground surrounding it. Same goes for coming into land.

Add to this one i'm now finding even when the xbox one controller is still plugged in on start it still unbinds all axis settings. Also when trying to reassign axis to pitch it sticks the game on that screen unless i manually clear a corrupt binding in the .cfg

I agree i initially dismissed DX11 as cause as there was a configurator for it on the first post.

Any idea what could be causing concentric black circles to be appearing on the water when this is installed? Is not EVE as tried uninstalling that to no effect. I have a Radeon 7950 if it being an ati card makes any difference. Running in Dx11 too. EDIT: Nevermind Dx11 was cause, works fine in DX9

My current set up for translation involves my six axis joystick plus the pedals from my g25.

I've noticed it is near impossible to burn up heat shields too. once they reach about 1 unit left it depletes really slowly. Also the heat tolerance of the heat-shield without ablator is high enough for all but direct interplanetary re-entry.

Is there really any point to probes as it stands. There are far fewer problems to overcome simply sending a manned vessel. You get more science opportunities and with this update you won't have to worry about relays.

Looks like a mass exodus from kerbin

Yeah should be fixed in next patch. It only occurs when combined with FAR as seti overwrites some of the modules FAR included apparently.

For anyone else with problem bug i had on last page is with SETi tech tree.