@ErikRobson I have a personal Jetbrains Ultimate subscription that I use for most things. VSCode is pretty good for python, and is really good for Rust.
@keescheese@ScrungusCrungus@ErikRobson Whoops, guess I haven’t checked my mentions in a while. I don’t think we had a name. The engine and game were developed together and I didn’t think of them as separate things. It was always just LuaTest :)
@ScrungusCrungus Yeah, we did soak tests where we would leave it running overnight and see if it was still running without blurry (or no) textures in the morning.
@keescheese At the time, it was just me coding, so at first, I just had a backup on the server. I don’t think it was very long before we got source safe set up though.
@ScrungusCrungus It would eventually crash, if you let it run long enough with a leak, and by that time, all textures had been reduced to pretty much a single color. @SheriffStone fun times :)
@ScrungusCrungus We had this whole thing in the dev xbox version called the Texture Scythe. Since it was a fixed amount of mem, if we had a mem leak, rather than crashing with out of mem, we would start throwing away the highest level mipmap of textures.
@keescheese It may be pre source control (ugh) since it was super early on while we were still in the clog shop and before fully signing with MS. I hope it's in there though!!
@keescheese haha, yes :) The stackless python version was pretty nice, but had a lot of overhead. I wonder if any of the old tests are still in the source depot?
@ScrungusCrungus@keescheese It was called luatest because near the beginning, once I had enough of the engine up and running, I had to choose a scripting language and I tested three of them. There was pythontest, javatest and luatest.. guess you know which one won :)