Frozen, items still clickable

CactusLynx · October 17, 2014

What's happened is the game appears frozen, but the audio cues from clicking parts, deselecting them, deleting them, etc... can still be heard, yet the game still appears to be frozen. I did a fresh wipe and have no idea what could be causing it.

EDIT: A video showing the problem. Note that when SPH is clicked, I could hear audio cues like the music and items being clicked and removed from the SPH GUI (audio isn't present in video because of recording software)

https://www.youtube.com/watch?v=_dF6pXnAbX4&feature=youtu.be

Edited October 19, 2014 by CactusLynx
Added video

sal_vager · October 17, 2014

Is it doing this all the time CactusLynx or just the once? And did you save the logs so we can look for what went wrong?

Please see the support stickies for info on the logs

CactusLynx · October 17, 2014

It just started doing this today and i'm mystified. I did find the log though.

*Aqua* · October 17, 2014

Relevant part of the log:

------------------- initializing editor mode... ------------------
(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
editor started
(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
Untitled Space Craft - Untitled Space Craft
(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
[scenarioDestructibles]: Started. 39 objects registered
(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
mk2Cockpit.Standard(Clone) added to ship - part count: 2
(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
stage count is: 0
(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
Resetting crew assignment
(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
deleting part mk2Cockpit.Standard(Clone)
(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
deleting part mk2Cockpit.Inline(Clone)
(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
mk2FuselageLongLFO(Clone) added to ship - part count: 2
FREEZE OCCURS HERE
(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
stage count is: 0
(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
mk2FuselageShortMono(Clone) added to ship - part count: 3
(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
stage count is: 0
(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Just to make it clear:

1. You start the editor.

2. You add a MK2 Cockpit.

3. You delete it?

4. You add a LFO fuselage.

5. Game freezes.

6. You add a MonoProp fuselage.

Somehow it doesn't make sense.

CactusLynx · October 17, 2014

Relevant part of the log:
Just to make it clear:
1. You start the editor.
2. You add a MK2 Cockpit.
3. You delete it?
4. You add a LFO fuselage.
5. Game freezes.
6. You add a MonoProp fuselage.
Somehow it doesn't make sense.

Yes, there's nothing in the log that seemingly shows how or why it happens, it just happens. Like I said I can still click on things and hear the audio cues, but the game itself appears frozen.

CactusLynx · October 17, 2014

The freeze does not appear to be triggered by placing anything, it appear to occur roughly 28 seconds after entering VAB or SPH.

*Aqua* · October 18, 2014

Can you reproduce it? Is it always after 28 seconds?

Just in case check your Windows event logs if there's something happening in that time.

CactusLynx · October 18, 2014

Can you reproduce it? Is it always after 28 seconds?
Just in case check your Windows event logs if there's something happening in that time.

Nothing in logs showing up, it always occurs seemingly 20-30 seconds after starting the game itself, sitting in VAB, SPH, or just overviewing the complex.

sal_vager · October 18, 2014

There's another log called the output_log.txt that may show other stuff, the KSP.log misses some things out, look in the ksp_data folder.

CactusLynx · October 19, 2014

There's another log called the output_log.txt that may show other stuff, the KSP.log misses some things out, look in the ksp_data folder.

That was the output_log.txt I found in KSP_Data earlier, sorry for the confusion.

*Aqua* · October 19, 2014

Relevant part of the log:
Just to make it clear:
1. You start the editor.
2. You add a MK2 Cockpit.
3. You delete it?
4. You add a LFO fuselage.
5. Game freezes.
6. You add a MonoProp fuselage.
Somehow it doesn't make sense.

I'm still not sure what happened here.

You created a new craft by adding a cockpit. KSP adds 2(!) parts. You then remove the cockpit, KSP removes 2 parts. After that you add a LFO tank and KSP somehow reports that there are 2 parts?!

My calculation is + 1x cockpit - 1x cockpit + 1 LFO = 1 part in total. KSP calculates + 2 for 1x cockpit - 2 for 1x cockpit + 2 for 1x LFO = 2 parts in total. I don't get it.

Edited October 19, 2014 by *Aqua*

Kamuchi · October 19, 2014

I think that is the bug when by accident you get a pile of clipping part exactly ontop of eachother

Same when you take the "Ram intake air", stick it on a small strut and start stacking them.

After 2 to a couple of times, the clipping goes mad and breaks the editor.

I had it a few hours ago just with other dozen clipping parts where the editor went nuts, to fix it:

Find the parts that are clipping, easy to spot with massive texture flickering when moving the cam around slowly.

Move all your connecting parts (not where the stacks are attached to) so you don`t lose the entire build.

Delete the part where the stacks are connected too.

You won`t be able to link the other parts back into position, just link them to a point you can easilly detach it from later.

When all the parts are attached randomly, save the craft and exit the sph/vab!

When you enter you can load the craft again, wich is a mess, and start detaching the stacks/parts that you randomly clicked and move them out of the way.

Now you can add back the part that you had to delete (part with the messedup stack) and start attaching the rest of the craft back so that you will only have to redo a small part instead of all over again

I know it`s abit of a pita, but I`m doing this as a work around.

CactusLynx · October 19, 2014

The problem is now that the game will freeze OUTSIDE of VAB/SPH where i'm not manipulating parts. I've added a video to illustrate what's happening.

https://www.youtube.com/watch?v=_dF6pXnAbX4&feature=youtu.be

*Aqua* · October 19, 2014

I'm sorry, I don't know what's wrong with your KSP. The log is clear of errors (what's in there is unrelated) and from what you wrote, you shouldn't trigger a bug.

Did you try reinstalling the game?

Edit:

It could be a Unity error but this is just guessing.

Edited October 19, 2014 by *Aqua*

CactusLynx · October 19, 2014

I'm sorry, I don't know what's wrong with your KSP. The log is clear of errors (what's in there is unrelated) and from what you wrote, you shouldn't trigger a bug.
Did you try reinstalling the game?
Edit:
It could be a Unity error but this is just guessing.

Nope, I even installed it on my other partition to check and the same thing.

CactusLynx · October 20, 2014

I tried loading up 64 bit but upon entering a profile it just crashed. Maybe this log will help?

Just for reference, my graphics card is a GTX 670MX with 344.11 for the driver.

Edited October 20, 2014 by CactusLynx

*Aqua* · October 20, 2014

KSP x64 is offically stated as instable. It can crash anytime because of some Unity bugs nobody fixed.

Your last crash could have happend because of this, not because of the freezing bug.

One last idea: Try other hardware drivers (newer and older ones). Sometimes they are not compatible with specific games. (For example Payday 2 crashes at least once everytime I play it but KSP runs without problems for hours.)

CactusLynx · October 22, 2014

KSP x64 is offically stated as instable. It can crash anytime because of some Unity bugs nobody fixed.
Your last crash could have happend because of this, not because of the freezing bug.
One last idea: Try other hardware drivers (newer and older ones). Sometimes they are not compatible with specific games. (For example Payday 2 crashes at least once everytime I play it but KSP runs without problems for hours.)

Yep, that fixed it. I reverted to 340 and its working fine now. Awesome.

CactusLynx · November 1, 2014

Ugh, it started occuring again today, so I axed some programs in task manager and that seems to stabilize it, the search continues.

Edited November 1, 2014 by CactusLynx

vexx32 · November 1, 2014

It's possible that perhaps an antivirus application (or something similar) could cause this kind of thing -- try adding KSP to its exclusions/whitelist.

shnazgirl · December 7, 2014

My boyfriend had this same problem. Turning off EVGA precision X fixed the problem so if you have that or anything like it like a frame rate counter or temperature manager I would try closing it.

Frozen, items still clickable

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation