holmes323

So I am trying to open KSP 1.1.3 in 64 bit however it never gets to the regular loading screen. I opened the launcher and hit launch it asked me to allow KSP_x64.exe to run, I clicked yes and it opens to this blank window with just the word loading:http://imgur.com/PvA4gGB 32 bit KSP works fine but I want to make use of 64 bit KSP any suggestions? BTW this is the first time I have tried running 64 bit on the PC(it has a 64 bit CPU and OS)

It now appears to be a true bug as after further testing I was able to have a jet plane takeoff with zero intakes the image should be proof enough that there is a bug afoot here.

So I Have just noticed a bit of an anomaly regarding airplanes. I was testing out a airplane it had enough intakes to get to 30Km however once it reached 30km the intake air read 0.00 however the four turbojets never flamed out and continued to produce 6Kn's of thrust apiece even after shutting down the engines and restarting them in space(above 70Km) I was able to get this purely air breathing plane to achieve a 150x150km orbit and was able to deorbit from said orbit and land. has anyone else experienced this bug? I used purely stock parts to build it but have mechjeb, flight engineer and kerbal alarm clock installed none of which should modify the behavior of the stock engines.

I ended up just reinstalling ksp. the klaw was behaving strangely before the bug occurred. it would become off center of where i mounted it by a fair amount when i accelerated the pod. could then get it back to center by opening and closing the klaw. don't know if that helps on your research at all but i thought i would add that.

After Further testing I have learned that the bug is triggered in all modes including training and scenarios and that it is triggered now whenever I try to warp time on any vessel. This Bug is making the game unplayable and I would really like to know why it is happening.

I had built a ship that was designed to rescue stranded vessels and crew( out of fuel, battery.etc). it consisted of a 3 kerbal command pod a hitchhiker pod a grabbing unit and engine sas units batteries etc... it takes off with no problems, go through grav turns and all that. Right after I jettison my lower stage I will warp to where I want to cicularize the orbit at and the bug occurrs. It gives me the message cannot warp faster than 1x while the ship is accelerating at the same time I lose ability to turn the ship using the wasd keys and mechjeb SMART.A.S.S. additionally the speed on the navball gets "frozen" and the orbit changes due to the velocity being frozen (am at speeds around 1700-2500m/s when occurs). after testing I have found that this now occurs with any vessel I launch. Running 32 bit v.25(latest) on win7 Mods I have installed are: Mechjeb, kerbal engineer, remotetech2 kerbal alarm clock, and scan sat. all of the pods tested were manned so remote tech wasn't causing the loss of control. as a side note the flight computer window said n/a instead of local control like it normally does for manned pods.

I am running the 32 bit version and reinstalling did solve the problem. On a minor note the news feed on the launcher remains blanks. Any ideas there?

Ok so just got around to trying out .25 and went to try out .25 using a NEW sandbox. proceeded to load a stock Kerbal X rocket and sent it to the launchpad to launch it. it went through a normal length loading time before going to the pad, however as soon as the pad loaded my screen showed this: Which then transitioned to show as zoomed out view of Kerbin except for the ground like this: with the velocity and altitude at 0 but the atmosphere indicator showing out of atmosphere. I am then unable to zoom in turn the camera or do practically anything typically leading to having to close the game from the desktop. Have tried to launch different craft including planes all with the same result. This issue has led to .25 being unplayable on my computer. KSP version: stock .25.0642 System Specs: Dell latitude e6530 running win7 64 bit pro version. Intel i5 2.5 ghz with 4 Gb ram and Nvidia 5200 NVS GPU. Was able to run .24.2 with no problems, and was really hoping somebody on here could help me resolve this so I can get back to KSP quickly.