why does Debug.Log repair the code? I'm going to get my Head Blown right now!!!!

Unity Engine
1

I’m going to get my HEAD BLOWN RIGHT NOW!!!

this code seems to repair my code:

	if (this == InterScript){
		Debug.Log("WTF");
	}

WTF

10 times I tried running with this uncommented code works perfectly.

20 times I tried running with commented that 3 lines code breaks every time, … WTF I’m going to get my head blown right now, …

:rage:

2

Usually this implies some sort of timing related issue. Could the time required for the code to execute affect the results of code before and after?

3

no idea, … I have some times for randomness, … curently I think I’m not using them, …

but even within randomness there are just numbers inside the what I want and I don’t get really what I’m looking for, …

4

what error do you get when it fails?

what if you use print to debug instead of debug.log?

5

What is InterScript? Is it possible, that by checking for InterScript in your if statement, InterScript is getting lazy loaded somehow?

6

the checkpoint recognizes wrong GO and sets checkpoint in wrong direction.

I managed to find that that was the correct debug after long time, …
and that I was right that that part was broken, …

but can’t understand why is it broken, …

Anyway thanks

interscript is “same script” within this GO but is a different reference to different GO.

7

I agree with Garth Smith on this. Is your snippet the exact code? If so, what happens if you change it to this:

if (this == InterScript){
    // Debug.Log("WTF");
    Application.backgroundLoadingPriority = ThreadPriority.High;
}

So it will execute the condition but not the actual call to Debug.Log. The extra line should ensure that the compiler doesn’t optimize it out; I just arbitrarily put a hopefully-innocuous line in there.

Can you post more code to put it in context?

8

No error message, no help.