I have a 32 bit win 10 and mostly i got crash at autosaves in Ck 2 and im really afraid that Stellaris could have this aswell. It can't have, right?
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
They made a 32-bit Win 10? I'm hoping that they drop 32-bit compatibility starting with this game. That compatibility is holding back the potential of the engine imho.
- 3
Am honestly expecting a 64 bit only announcement here soon. No WAY can they have all the content they say they can with only 32 bit. CK2 is stretching it and often crashes, but 1000+ systems each with their own planets, and each planet having multiple areas? No way man.
- 2
I also hope it's 64 bit only. Sorry. The people using 32 bit on CK2 is a small minority. And the 32 bit-support in CK2 is one reason for some of the performance and engine problems of the game.
- 1
- 1
Well actually i can handle 64 bit. I just installed 32 bit because i have only 2,5 gb of ram. but then i upgrade to 64 bit
They probably will build it to 64 bit but that does not improve performance unless the game requires lots of memory. So far in my experience none of the paradox games comes even close to reaching the limits of 32bit address space. So in what way is it holding back the engine?
Everyone is "using 32bit on CK2". I am not aware of 64bit version of the game. The fact that the OS does support 64bit memory addresses does not really affect the game at all.
Everyone is "using 32bit on CK2". I am not aware of 64bit version of the game. The fact that the OS does support 64bit memory addresses does not really affect the game at all.
Last edited:
Games that run on 32 but would not use a full computers 64 bit processor. It's leaving a lot of the computer's processing power on the table.
According to the Wiki it is built on the Clausewitz engine, meaning it will be 32 bit. Games crashing on you have nothing to do with it being 32 bit. It will be a while before they release a 64 bit game, as they will have to build a new engine from scratch, and that is a LOT of work that they prefer spending developing games.
Is that so? My, very limited, knowledge of computer architecture indicates the most substantial difference is having more addressable stuff. Any hypothetical performance gains are fairly marginal even in theory and there's some pesky details, mostly about hauling double the data, that more or less even it out.
All in all I really don't get why people get all their pitchforks and torches up with software compiled for 32 bits.
Essentially, it puts a cap on how much memory games can use, which influences the game design significantly. Do we see the games that hit this limit and implode? No, because they either were pruned back, or labelled 64bit only.
For an example of memory limitation from another genre - the core hub zone of Mass Effect, the Citadel, was originally planned to be much more extensive than what was eventually shipped - they found that to fit within the limited RAM available to the 360, they had to do a substantial amount of cutting and trimming to get the most value out of that limited resource. Indeed, I recall reading that the reason behind one of their races having a conspicuous lack of women was that having an additional model in the mix would have taken memory budget they couldn't afford, though I can't find that cite offhand so grains of salt.
That's the problem. The >90% of the people who use 64bit can't use t6he whole power of the system. Because Paradox makes the game workable on 32bit means that the game can't be as fast as possible for people with 64bit.
Unless the program uses so much memory (>4G) that it has to use memory swapping on 32bit but not on 64bit, the actual performance difference is usually less than 5%, which is in the hardly noticeable territory.