Any word on fixing paragraphs for the bios of custom species? It's been broken for... years.
Because there are not magic bullets, and x64 in particular was not one?Oh my god the stuttering is even worse. How could it even be?
Oh yes, had that pretty much since the FTL rework. But it is a very rare and shortlived state and I do not think I ever reported it.Anyone else having an issue where auto-exploration just doesn't work with a mostly explored galaxy? There are a bunch of accessible unexplored systems which I can manually send my science ships to explore and yet if I just click auto-explore it tells me it can't reach any unexplored systems.
Habitats are unlocked with T3 Spaceforts, wich is a lot earlier then Megastructures.Also, is it intended that gateway construction sites and habitats count towards the megastructure build limit now? Because it's hard to see why I would ever construct a habitat if so, I guess if I didn't get Cybrex then I would build them early on before I could build better things. Squeezing in my gateways is going to be painful as well.
the libatomic that is in the game dir is obsolete and was not newked when we changed to 64bit, but since it is the wrong arch now it will not be used@Guraan will want to know about this too I think!
Are you...trying to make excuses for insane stuttering and slowdowns that plagued Stellaris for almost 2 years now? Really?Because there are not magic bullets, and x64 in particular was not one?
If only other Forum Users and the Devs have been telling you that. Oh wait, they did!
Turning x64 only means the game has slightly more memory to waste on chaching and other performance increases. But those are changes that are made long term.
Meanwhile it will show us all those bug that overflow bugs have been hiding before.
Under this 2.3.1 beta patch, launching stellaris through steam results in a CTD (somebody already reported it). However launching the game through the cli, outside of steam, works just fine. I suspect the steam runtime somehow forcing the wrong arch onto the game. CrashReporter does show the arch to be 32bit.the libatomic that is in the game dir is obsolete and was not newked when we changed to 64bit, but since it is the wrong arch now it will not be used
Oh yes, had that pretty much since the FTL rework. But it is a very rare and shortlived state and I do not think I ever reported it.
Habitats are unlocked with T3 Spaceforts, wich is a lot earlier then Megastructures.
Also it sounds like you have a case for those things that icnrease the megastructure limit.
No, Federations have nothing to do with it. This behavior is visible in every game, I guess most people don't really notice. After all, only a handful of systems remain unaccounted for.Hmm, this is the first time I’ve experienced it. It’s also the first time I’ve joined a federation so maybe that is something to do with it.
libatomic is a very close part to libstdc++, your dist or yourself can provide a better one so no need to include system libs with the game?Yeah thanks that helped. Two observations:
(1) libatomic is always put into the game folder, even if it exists on the system (that could make sense anyway)
Yeah that one has been deleted(2) the libatomic put there by Steam is of wrong architecture @Jamor