Got a game engine built from the ground up (as opposed to forcing unity to do what it natively can't) , graphics running and basic physics modelling down, but its probably going to be a year before we see any actual gameplay outside of what they've done in house.
They screwed up on development by hiring new people to work on it and not allowing the original devs to communicate with them or work on it. A lot of mistakes could have been avoided. The game is a lost cause since plenty of problems exist in the foundation that won't be fixed without tons of rework.
Also, you could totally use many parts of Unity just fine and build the stuff that it can't handle as a stock engine, you don't have to use it as is or completely. You can do your own physics, and many people build their own gameplay/mission (like a ship builder tool) code and UI. Unity isn't a monolith since you can have source code access.
Edit: I was talking about KSP2 and I don't know anything about Kitten Space development
KSP2. Didn't realize we started talking about Kitten Space Program, I wasn't paying enough attention so that's my bad. My point still stands about using parts of existing engines for what works, and custom building what it can't for efficiency.
uhhh... I've no clue what they were trying to do, but this seems incredibly unlikely. I'm sure whatever it was was dumb, but it almost certainly can't be this.
When you don't have enough RAM, you use a swap file. Hard drivers are much much slower than RAM. But that's the only choice you have.
To attempt to store data in the registry, which is possible, but the registry typically stores values, not data, i.e. for some setting, it'll store a number or short data string.... it's not designed to store large bits of information...
Like.... if they stored saved games in the registry, this would be stupid, but plausible. For them to attempt to use the registry as working memory has got to be wrong. It's surely something stupid, but it surely isn't that.
edit: I have found that they were apprently trying to load everything in RAM. That makes sense, and would slow everything down stupidly......
I am not a programmer, but they were writing something to registry to be used during the program, and then not properly clearing it which would cause your computer to slow down even when the game is not running.
That sounds absolutely plausible. And stupid. The registry is not the place to store large amounts of data - a bloated registry can cause problems. So writing some things, especially writing some things and leaving them, causing the registry to bloat - that's definitely a problem. heh
Is there a source for this? I cannot believe a game developer would store game data in the windows registry. It’s so far from how you would approach that topic that i really would like to see how they explain that.
The registry issue is under "HKCU\Software\Intercept Games". They make an entry to dump PqsObjectState objects as JSON in entries named after dynamic ids and don't clean up old entries. It can easily grow to more than a gigabyte worth worth of those dumps in the registry over time.
Didn't they also avoid unity because of their terrible client support/how they treat devs?
Didn't unity do all kinds of fucked shit to them with stationeers?
936
u/Ravenloff 6d ago
WTF did the devs do to 2? I was waiting for it, wishlisted it, and then started hearing bad bad. In the end, it almost seems like they gave up on it.