Debug globals all show as 0 and Null?

I'm pretty sure this is new to 1.93.

Entering debug mode (via the Stop) in the following program, I can see under Local variables that "b=1", but under Globals "a=0"?!

Global a = 1
b = a
Stop

This is also happening with floats (0.0), strings (""), and objects (Null).

This is weird. I tried the code and both variables showed the value 1.

But then I noticed that the version was 1.92. I had downloaded 1.93, but never installed it.

So install 1.93 and try again. Now I see b=1 and a=0.

Checking the version shows 1.93 for IDE, runtime AND linker. That's a new one.

So as a test I ran the 1.92 update and tried one more time. Now b=1 and a=0, just as with 1.93. The runtime and IDE are 1.92, but the linker still shows 1.93.

Ouch, my singletons. :(

You will require the 1.64 linker again-

Make a backup of this. I'm so glad I didnt update yet!

Update to 1.93 and downgrade the linker- what does this do?

Mark- Any idea as to whats happened?

Purely out of interest thats all!

The problem still exists, with 1.95 installed over 1.64 (Win XP SP2 x86)

I have this problem too with 1.95. So I guess I should reinstall my original install 1.84 and use the 1.91 patch? :/

Just install 1.91 or earlier, make a copy of its linker.dll, then install 1.95 and overwrite linker.dll with the old one.
(Is B3D written in C? I could bet this is one of the typical = vs == C mistakes ;))

1.96 update now available - fixes this problem.