I like the auto updates thru Steam .

Now the problem : I built a small outpost with a couple of custom structures I made and also used several of 'Valuable Assets' buildings , added some grass around (very little ) put down some sand and mud ground and then ran the test . The first time it ran good ,high frame rate 150-300+
. Then I moved one building a little and the ran again and adjusted the grass so it was a little higher and also changed to a cloudy sky .Ran around to see how things looked and it looked good but , all of a sudden I got kicked back to the editor . It reloaded the level and I tried it again . It ran except the sky changed back to clear . Everybody likes clear days but I picked cloudy . So , maybe there is something wrong with the sky change setup in the editor ?
Going from moving clouds (FX effect ? ) to ones that don't move messes something up ? As usual I don't save these tests ..
This is just something I ran into . It's probably been happening before the last couple of builds and maybe before Steam launch .
Oh , on the first run thru of my level there was a second or 2 that the level froze and then continued perfectly . Just annoying in the editor. I hope it never shows up in a 'game' .

On one of my other posts on the forum I put down that I had 4mb. video memory when I only have 2mb.

Bring back segments ,bring back segments and ability to punch holes thru them .

Lance

I have found that when (for whatever reason) gguru has a problem it will run a "resuming from previous" and several of your settings revert to some kind of default setting for certain functions. The ones I have noticed are the sky selection, terrain, and entity shaders.

In my opinion this is a bug in the recovery system and I keep meaning to report it but ...

There is a bug (or several) in the recovery system. (i'm going to post this in the bug report right now)

For some time I have posted in the scripting forum, the lack of a workable script debugging system. Currently, if GG finds an error when testing a new script (in test mode), it locks-up (usually at the point where it is loading dynamic lights) and the program does not display the error message. Only after using Task Manager can I get to the error message which will not show-up above the full screen GG splash page.

Once I see the message and clear it, the system attempts to "Resume Previous Session". In the many times this has happened, only once did the system reset and allow me to continue. In ALL other cases, something goes wrong with GG, and I end-up having to either reboot the program, or in many cases I find that something has gone so wrong that I must reboot my computer before GG will work again.

For now I'm not using the resume function as I simply kill the program in Task Manager, which usually prevents me from having to reboot my computer. As LUA scripts become more extensive the GG team needs to do better with resetting and displaying scripting errors.