Cool.but they tend to take up a lot of dev time to trawl through them
Cool.but they tend to take up a lot of dev time to trawl through them
I only post crash reports here that were generated by the game after it has crashed to the desktop.the in game crash reporter is much better for this.
Heck naw. There are a bunch of bugs that we need to keep on top of on console for the next update.Cool.So do you QA guys have a bit more breathing room, currently?
So, the team (in general) is not being allocated (significant) time to deal with legacy bugs? Only to make and fix new content? (Even though TerraTech's at 1.0 now, and an increasing number of players seem to be getting upset by the bugs because of this transition - however much you guys might like it to be 'just a line in the sand'.)Heck naw.
Finally, what I'm more perplexed about is:So where does fixing crafting come, then?We haven't explicitly listed bug fixes [...]
I'm worried that this means it would continue to be put off, while new features (and conclusion of MP work) are prioritised. Crafting is a complex system to work on, hence why it's not been possible to quickly fix it (as I've been told). The crafting AI must be at least as complex as the friendly mobile AI - not something that can be simply chipped away at piecemeal. So surely a significant amount of time must be allotted. Is it just something that wouldn't have looked attractive to admit on the plan...?
Heya Potato, a blue screen crash is normally indicative of a hardware issue or could be also attributed to driver issues.My PC had a blue-screen while I was playing Terratech in its 1.0 version...that's bad.
Try removing all Official and Unofficial Mods then re-load the game.Crash on a game start. There are no crash and saves files. Just output_log.