No return from SetTexture

[linuxgurugamer]

Hi,

I have an (for me) odd situation, which I' sure is caused by my ignorance.

I have the following code in the update() function:

                            Debug.Log ("Before MainMenuGui.AS_Button.SetTexture on");
                            MainMenuGui.AS_Button.SetTexture (MainMenuGui.AS_button_alert);
                            Debug.Log ("After MainMenuGui.AS_Button.SetTexture");

This is called when the F6 key is pressed. The SetTexture call works, I see the button change.

My problem is that it never returns from the SetTexture call, so that the flag which gets set after it isn't set and the rest of the mod doesn't work.

I added a logging statement at the beginning of the update function to display the flag, and I see that it is never set.

When the game is exited, then it returns and I get the messages in the log file.

What would prevent Unity from returning from the SetTexture call?

Thanks in advance

LGG

Edited August 8, 2015 by linuxgurugamer

[sarbian]

KSP.log is buffered. The game write it when it has more than a set size to write. If you want to see a real time log you have to open the KSP_Data\output_log.txt

[linuxgurugamer]

KSP.log is buffered. The game write it when it has more than a set size to write. If you want to see a real time log you have to open the KSP_Data\output_log.txt

OK. But when I put a debug statement at the beginning of Update(), it shows that the flag which is set immediately following the SetTexture is not set, and that shows up in the log very quickly.

When I exit the game, then I see the SetTexture message in the log.

How do I write to the output_log.txt? If it shows the same thing as the KSP.log, then why are there two log files?

Edited August 8, 2015 by linuxgurugamer

[Gaalidas]

KSP has two logs because it's weird that way. There's really no other explanation than that.

[linuxgurugamer]

Thanks.

Once I was able to see it real-time, the bug became obvious.

LGG