Josh

Whoa, that is only 2 MB. I don't think the problem is memory fragmentation.

Okay, there is a timer now that fires every 30 milliseconds, checks to see if the overlay needs to be updated, and renders the first viewport, even if it is hidden.

I got it to stop during one of these episodes, and there are thousands of 5373 and 5374 messages being processed by GetMessage()...

I happened to find this: https://partner.steamgames.com/doc/api/ISteamUtils

Thanks, this is fixed for the next build.

I followed these instructions with no problems, using an AMD 6600.

I have added the size of the requested memory allocation into the error message. I believe the biggest buffer a material layer on a 4096x4096 terrain will be 256 MB.

Hi, I'm sorry but I don't think I have the FBX files for these models anywhere. I suggest you request a refund through Steam.

Hmmmm, UltraOS?

0.9.6 Changed some order-of-initialization stuff so the problem we saw in today's video, when you are creating a new project for the first time, does not occur.

I modified the coupon code so that it can be used multiple times.

I am working with the theory that some kind of event is piling up in the Steam overlay when the editor does not swap a 3D window for a long period of time, and when it resumes rendering it must evaluate a large number of events, probably some kind of timer used by Steam. I added a timer that invalidates the main view panel every ten seconds, and have not been able to produce the problem since. This will probably only work if at least one view panel is visible. If the editor is viewing the flowgraph or asset library, which do not use a 3D framebuffer, then I expect the problem would continue. So, it might be fixed now, as long as one viewport is visible, but I am not sure yet.

Okay, it's ready now. You need to sync your project in the project manager to get the updated executables.

I did something silly. Update coming in a few minutes...

During today's call, I left both the Steam and standalone version running. Steam version is now frozen, standalone is fine... After a few minutes the Steam version became responsive again. Maybe I need to render a frame every couple of minutes? It's like a bunch of events are building up and have to be dealt with when the program resumes...

Lua or C++?

This will be fixed in the next build that is uploaded. Thank you for reporting the problem.

0.9.6 Changed 2D viewport rendering to ensure compatibility with some older AMD cards.

I believe this is solved in the current build (1274). Sorry it took so long.

The current build (1274) is working now on my 580.

Okay, I can produce the error, which is the first step towards fixing it.

I have a 580 now. I figure they probably use the same driver...

Creating the fastest game engine in the world is not a job for weak men.

I'm sure it is. I just need to get a card from the same family and try it out.