An Unexpectedly Green Journey passes Quicktest but I have a big problem with it most of the time. It almost always runs out of memory, when going through my raider battles, and doesn’t complete. To test the game, I move the raider scene files to the bottom of the scene list in the startup file. Even so, it takes half an hour (or more) for the test to even get to them.
Now that I am working on a small update for Green, I have come face to face with this monster again after having a smooth run with my large, but much less complex, new WIP game.
My computer is not a potato. Not yet.
Does anyone have any tips/tricks to help me get through this?
Assuming you’re on Windows you could see if you’re not using the 32bit version of CMD instead of the 64bit. That would limit the amount of memory it can hog up by default. 32bit won’t take more than 4gb of RAM by default.
Show text? iterations? etc… maybe you can limit that. or make batches of fewer iterations. I do mine in a VM like 50k each x6 or 8 at the same time cause it only uses one process to run it, depending on how many cores you have available and how much memory it takes…
If you’re curious and willing I can run it through a quicktest on my workstation when I get home. If it runs out of memory there it’s not your computer’s issue.
Works a charm! Yeah, the html version has been torturing me for months. Literally have waited for over an hour for it to get to the radier scene and then run out of memory.
That would explain it. I honestly forgot about the possibility of you using html tests. Either way glad it’s solved now and hopefully the tests will run quicker on console as well