No Multicore? What a joke! changed my review to negative too :)

[Dean / Noah]

rly Devs? in 2018 working on a game without Multicore support? even when the game would get a extrem huge benefit? rly?
are you aware that this is the reason why this game will fail in future?
you are trying to tell us its impossible because you would had to rewrite the whole game?
stop lying .. modders can do it too .. there is a mod wich unloads allot of stuff from the main core the game uses into an different thread .. so stop lying devs .. you just dont want to do it ..

btw, only because of the missing multicore support, i changed my review into not recommended ..

[Valkun]

I'm not sure how familiar you are with programming, but what you are asking for is not trivial in the least. Parallel processing requires a far more complicated architecture than their single threaded equivalent, as you have to ensure that the various processes stay in sync and do not access the data at the same time. This might mean the entire engine has to be rewritten from scratch to accomodate this paradigm.

Note: Adding multiplayer is also a huge undertaking requiring a fundamental restructuring of the entire architecture. It actually presents a lot of the same problems as making a program multi-threaded but at a different I/O time-scale and on more machines.

[Radiosity]

HASHTAG CURRENT YEAR ARGUMENT. Really compelling, OP. You forgot that this game started developement nearly six years ago when Unity barely even HAD multi-thread support. And you're delusional if you think a dev is going to rewrite their whole game six years later just to add it.

[ignis]

Downloaded that Tick MultiThread and poked it with disassembler. It is very primitive in design, detours destructively and lacks proper handling of race conditions or concurrent modifictions. That's not how you design multi-thread applicayions. By far.

[Dean / Noah]

ignisru님이 먼저 게시:

Downloaded that Tick MultiThread and poked it with disassembler. It is very primitive in design, detours destructively and lacks proper handling of race conditions or concurrent modifictions. That's not how you design multi-thread applicayions. By far.

then u did not read what the mod does and what not ;)

Radiosity님이 먼저 게시:

HASHTAG CURRENT YEAR ARGUMENT. Really compelling, OP. You forgot that this game started developement nearly six years ago when Unity barely even HAD multi-thread support. And you're delusional if you think a dev is going to rewrite their whole game six years later just to add it.

lets say, there was an feature .. it was in unity since launch, basicly all engines have this .. its called an update option to upgrade the engine to the new version ;) and unity supports since years multicore quite well

[ignis]

twitch.tv/BlackyGERxJahnie님이 먼저 게시:

ignisru님이 먼저 게시:

Downloaded that Tick MultiThread and poked it with disassembler. It is very primitive in design, detours destructively and lacks proper handling of race conditions or concurrent modifictions. That's not how you design multi-thread applicayions. By far.

then u did not read what the mod does and what not ;)

It's not about "what", it's about "how." You are saying that multithreading is not that difficult because mod can do that. But implementing it like that mod does would be a disaster. It only works (IF it works, I haven't actually checked) because everything else is single threaded and poorly optimized.

I'm not trying to argue about game needs multithreading. It does. But let's face it - only MMORPG developers do it in game logic. Otherwise, as best you'll have multi-threaded rendering, and only because it is handled by engine. Because multithreading is a huge can of worms that requires specific skills to handle. You can't just copy-paste multithreading from some template as you can do with most other stuff.

[Dean / Noah]

ignisru님이 먼저 게시:

twitch.tv/BlackyGERxJahnie님이 먼저 게시:

then u did not read what the mod does and what not ;)

It's not about "what", it's about "how." You are saying that multithreading is not that difficult because mod can do that. But implementing it like that mod does would be a disaster. It only works (IF it works, I haven't actually checked) because everything else is single threaded and poorly optimized.

I'm not trying to argue about game needs multithreading. It does. But let's face it - only MMORPG developers do it in game logic. Otherwise, as best you'll have multi-threaded rendering, and only because it is handled by engine. Because multithreading is a huge can of worms that requires specific skills to handle. You can't just copy-paste multithreading from some template as you can do with most other stuff.

well i checked, the mod works, that he is maybe bad coded, who knows ^^ maybe the mod has to be the way he is to actually work ..
but the dev told us on offical forums its not possible to go multicore and not even able with mods, this mod is the proof that the game could

[Wiawyr]

twitch.tv/BlackyGERxJahnie님이 먼저 게시:

ignisru님이 먼저 게시:

It's not about "what", it's about "how." You are saying that multithreading is not that difficult because mod can do that. But implementing it like that mod does would be a disaster. It only works (IF it works, I haven't actually checked) because everything else is single threaded and poorly optimized.

I'm not trying to argue about game needs multithreading. It does. But let's face it - only MMORPG developers do it in game logic. Otherwise, as best you'll have multi-threaded rendering, and only because it is handled by engine. Because multithreading is a huge can of worms that requires specific skills to handle. You can't just copy-paste multithreading from some template as you can do with most other stuff.

well i checked, the mod works, that he is maybe bad coded, who knows ^^ maybe the mod has to be the way he is to actually work ..
but the dev told us on offical forums its not possible to go multicore and not even able with mods, this mod is the proof that the game could

What that mod "proves" is that one part of the game can be moved to another thread without the entire thing bursting into flames. It does not support your claim that the entire game could be made as such.

[Astasia]

twitch.tv/BlackyGERxJahnie님이 먼저 게시:

Astasia님이 먼저 게시:

The game has as much multicore support as most other games these days. Which is of course not that much, and it hurts, but it's normal. Multicore CPUs were never designed for gaming, they've never been good for gaming, and they likely never will be.

wrong .. the game has only single core support. most games these days have full multicore support .. ofcourse multicore is made for gaming ... who ever gave you those informations .. you should not listen to him anymore ..
multicore on desktop was basicly created for gaming. on server side its a whole different story, but on desktop side, intel as first created the E6600 wich are basicly 2 cpus "glued" into one case and this was made for the gamers wich complaied that system + gaming software (skype, irc, teamspeak, ventrilo, mumble and so on) eat system resources while playing. so intel went in with this cpu and that was the day multicore for gaming was born.

and if u still thinking games do not use multicore, okay go test it urself, go battlefield 1, go into taskamanger and unasign all cores execpt 1 .. enjoy 0 frames

Nope. Rimworld has a main game thread that handles the simulation and AI, but then it also has other threads for the graphics and sound. It's the main game thread that bogs down because after a point there are too many AI decisions being made or too many map updates happening.

Most games work like this, there is a main game thread and then some other functions will have their own thread. Each of those sub-threads are limited to a single core, so in many cases dual core CPUs will of course have some effect on performance, but anything more than that is generally doing very little if anything. One of the threads bottlenecks on one core and it doesn't matter how many other cores you have because the other threads aren't struggling.

Trust me, going from a 3.5ghz quad core CPU to a 3.0ghz 8 core CPU is a noticeable downgrade in performance for nearly every game in existance.

[Rocky the Rock]

It's not completely about how well the game runs. On my simple computer, the game runs completely fine. A game should be more judged about how fun the game is, not about if it is multi core or not. If the game ran horribly, then yes, it'd be a problem.

[BanDHMO]

Pataur the Great님이 먼저 게시:

It's not completely about how well the game runs. On my simple computer, the game runs completely fine. A game should be more judged about how fun the game is, not about if it is multi core or not. If the game ran horribly, then yes, it'd be a problem.

Exactly. I don't know what kind of potato the OP has, but my computer is over 5 years old (it's so old I don't remember how many years exactly) and I still never had performance problems with RimWorld. Maybe he's using some bad mods and/or runs gigantic colonies, I don't know.

If OP wants to give the game a negative review, that's his choice, but it's ridiculously myopic and not very helpful for other players considering the game. Overall, this game is well worth it, IMHO, and performance is not an issue.

[Dr@g0n]

performance is always a issue but I don't believe theres anything wrong with how the game runs or will be ran with what ever threads may be(I have no programming knowledge and im running on a pos labtop with 200+mods with the new graphic mods too and graphics tuned as such that its not the best but wow it looks good.

Plus its a top down game, how much more will you ask for if they come up with the uber computer quality graphics game running incredible version anyhows. 3D, 4D, two story buildings.

Geez guys relax, let the modders do what they can and let the dev do what they can and any critizism is usually helpful no matter if its abused in a way that it sounds so negative especially when others take the original comment to new depths.

"So let the wind blow, the sails will fill and the direction we go is forward. To a new horison if we are lucky to get lost." So sayeth the guy jeff

[Dean / Noah]

Astasia님이 먼저 게시:

Trust me, going from a 3.5ghz quad core CPU to a 3.0ghz 8 core CPU is a noticeable downgrade in performance for nearly every game in existance.

who ever told you this, is dumb .. everygame expect this one and a other one wich uses the sprites are fully multicore able and i upgraded from 4C/4T to 8C/16T and i deffenitly see in every single game an improvement expect thse 2 and rimworld is one of them. rimworld has the same issue as the homeworld 2 2003 and will die exactly the same way ..
the future does not belong to single core, it belongs to multicore
(and if u still think games do not support multicore, go ahead test games and dissable your cores, enjoy 1fps ;)

[kingofkin]

Können wir nicht alle miteinander auskommen? Plus ich glaube, wir sind alle in der Lage, das Spiel richtig zu führen?

can we not all get along? plus i believe we are all able to run the game right?

[Dean / Noah]

kingofkin님이 먼저 게시:

Können wir nicht alle miteinander auskommen? Plus ich glaube, wir sind alle in der Lage, das Spiel richtig zu führen?

can we not all get along? plus i believe we are all able to run the game right?

yes we can run the game, but it gets unplayable in lategame because of the missing multicore feature ;)

[Swagmaster Love 🇪🇺]

Wiawyr님이 먼저 게시:

Anyone with twitch in their name can be pretty safely ruled out as doing everything for shock value and attention whoring. This fellow is just trying to be as obnoxious as possible to generate views.