0.25 Bugs (VAB building missing after revert to VAB)

[MGCJerry]

I was trying to destroy a number of the buildings on KSP and ran into a huge number of problems. First, I could not click on revert flight button (it clicks but does nothing), go to space center (it clicks but does nothing), but I could revert to VAB and when I do, I get something like the attached screenshot. Once that occurs, I'm unable to take screenshots and have to do it with print-screen. The next thing I do results in a crash (save ship, launch, space center, etc). These issues have not occurred to me on other versions of KSP. This one seems unbelievably unstable for me.

* KSP 0.25 non steam (32bit, stock, clean install, no modifications, even keyboard controls, re-downloaded twice.)

* Windows XP (32 bit)

* VAB missing when reverted to VAB

* Screenshot (For Reference Only. I didn't get it for the VAB but got it for the SPH): http://2thextreme.org/forum_images/ksp/0.25_Bugs/badsph.jpg (Cant take screenshots using F1)

* My KSP_Data/output_log.txt is 18.9 MB (19,832,236 bytes), it would take me forever to upload (my upload is abysmal), and it would hammer my host if I posted it there. If there's a particular thing in there, I can look for it and post bits manually.

* AMD FX8120 8-core (4GB RAM - 8 physical), older video drivers. Updating has no effect, and causes issues in other applications when I do.

Steps I took:

1. Load KSP.

2. Create new sandbox game.

3. Go to VAB and build rocket to crash into buildings (probe core, biggest ASAS module, the 32 tank (the one half the size of the orange), mainsail, 4 winglets).

4. Destroyed launchpad by flying up, turning retrograde and burying the rocket nose first at 450 m/sec into the launchpad by turning the throttle to 11.

5. Revert to launch.

6. Crash into the tanks near the launchpad.

7. Revert launch. Fail at 3 more attempts to hit other buildings.

8. Revert to VAB. VAB missing, see screenshot above.

9. Exited.

Edited October 9, 2014 by MGCJerry

[Padishar]

Try zipping the output_log.txt (Send to compressed folder if you don't have a dedicated program). It should become very much smaller...

[Claw]

That's an epic picture.

When logs are this big, they are often full of the same error over and over.

If what Padishar suggests is still not manageable, try to recreate the problem with just the bare minimum needed to make it happen, then exit the game. This will ensure the log isn't full of extra info. Then if you can zip it up it should be even smaller.

You can also try opening the log file (which migght be a challenge given the size, and look for a spam of messages at the end. If there is a long list of the same error, you can delete all the extras. That can also trim down the size.

Cheers,

-Claw

[MGCJerry]

Thanks for the replies.

I don't know why I didn't think of that Padishar, I feel like such an idiot but my post was typed before I had to leave for awhile (while running into KSP crash after crash).

Claw, I looked toward the end, and it seems there's a lot of out of memory messages with this taking up most of the lines "d3d: VB or IB is null" (starts at line 9,137 and goes to line 852,495). I'll try to reproduce this "disappearing VAB/SPH" alone, but I'm getting all kinds of crashes at different periods.

[Claw]

Bugs like this usually start with one failure that cascades into many problems. That's why the log will be very important here. Once you run into a problem, you can stop. Because the bugs that come after are usually just the result of the earlier bug.

-Claw

[MGCJerry]

Unfortunately, I can't reliably reproduce this bug. I tried documenting my steps later that night but KSP ran wonderfully for over 3 hours. Its never run that good. So I just decided to take advantage of it running great and have fun building stuff with the new parts, which are awesome as well.

Then last night I had to start KSP 5 times before I could even see the space center. It kept crashing (Something about a non responding part, then the windows "Program has crashed" popup so I didn't get time to screenshot the error, it happens quickly). Now my log is over 343MB. During this slugfest with KSP the VAB & SPH did disappear again. I just keep running into different problems with 0.25 when doing the same things.

I'm going to hold off on my bug reports until I do a more thorough system hardware check.

* Disk defrag has already been done, its done weekly. (which I think is irrelevant to the problem)

* I've already ran memtest several times and came up clean (21 hours wall-time, 15 passes, 0 errors) (did that the last 2 days while I was not home).

* Going to run a spinrite surface scan (chkdsk comes up clean).

* Going to restore "plain os" disk image restore. I did a disk image with all my drivers installed after I setup my os.

* Another 3 day full burn-in test.

It will be a few days for any ksp.