Dead on Arrival if it requires DX12 and 8GB of VRAM

[z]

Also Sims 1 still best in the series.

[z]

RedAISkye님이 먼저 게시:

SSD is a must

SSD is great for Sims 3. I can tell this much.

[Thjaffi]

RedAISkye님이 먼저 게시:

HULT님이 먼저 게시:

hdd is realy a no go for games nowadays 8 gb ram is also not enough but 4 vram is not bad not great but not bad neither

Yeah, I only use HDD for small or old games.

SSD is a must have these days, especially M2 since the performance is just significant.

M.2 is just a form factor, they can be connected via SATA or PCIe.

Honestly, i don't notice any significant difference between a halfway good SATA SSD and a PCIe SSD in gaming. theoretical peak performance doesn't seem to have a great effect here.

[RedAISkye]

Thjaffi님이 먼저 게시:

RedAISkye님이 먼저 게시:

Yeah, I only use HDD for small or old games.

SSD is a must have these days, especially M2 since the performance is just significant.

M.2 is just a form factor, they can be connected via SATA or PCIe.

Honestly, i don't notice any significant difference between a halfway good SATA SSD and a PCIe SSD in gaming. theoretical peak performance doesn't seem to have a great effect here.

Nah, M2 is a lot faster than your normal SSD.
But either one would be significantly better compared to HDD.

[Melody]

apple님이 먼저 게시:

I playied demo with rx470 with 4GB of VRAM, On lite settings it was about 45fps, on higher 15-20. Yesterday while playing I noticed that 7200rpm HDD was too slow for this game - cutscene lagged, textures took kinda long to load, and you could feel that it need stronger pc. Time to look for used pc parts, like 16GB RAM, ssd, stronger and more vram gpu.

The cutscene problem is not a storage problem, it happens on my NVMe as well, it's just random. Sometimes, it's just smooth as butter, and sometimes it just lags. Probably shader compilation or something else. Definitely not a storage issue.

[RedAISkye]

Melody님이 먼저 게시:

apple님이 먼저 게시:

I playied demo with rx470 with 4GB of VRAM, On lite settings it was about 45fps, on higher 15-20. Yesterday while playing I noticed that 7200rpm HDD was too slow for this game - cutscene lagged, textures took kinda long to load, and you could feel that it need stronger pc. Time to look for used pc parts, like 16GB RAM, ssd, stronger and more vram gpu.

The cutscene problem is not a storage problem, it happens on my NVMe as well, it's just random. Sometimes, it's just smooth as butter, and sometimes it just lags. Probably shader compilation or something else. Definitely not a storage issue.

That's weird because the cutscenes are pre-rendered.

The cutscene seamlessly ends at the actual main-menu of the game, you can notice it easily if your game is on low settings due to their significant graphical difference.

I personally had no issues with the cutscene.

[Brinkbabe91]

definitely not dead on arrival

[Melody]

RedAISkye님이 먼저 게시:

Melody님이 먼저 게시:

The cutscene problem is not a storage problem, it happens on my NVMe as well, it's just random. Sometimes, it's just smooth as butter, and sometimes it just lags. Probably shader compilation or something else. Definitely not a storage issue.

That's weird because the cutscenes are pre-rendered.

The cutscene seamlessly ends at the actual main-menu of the game, you can notice it easily if your game is on low settings due to their significant graphical difference.

I personally had no issues with the cutscene.

But whether the cutscene is prerendered or not really has no correlation especially when it comes to shader compilation which is something that, especially in UE5, happens at full CPU/GPU load.

[RedAISkye]

Melody님이 먼저 게시:

RedAISkye님이 먼저 게시:

That's weird because the cutscenes are pre-rendered.

The cutscene seamlessly ends at the actual main-menu of the game, you can notice it easily if your game is on low settings due to their significant graphical difference.

I personally had no issues with the cutscene.

But whether the cutscene is prerendered or not really has no correlation especially when it comes to shader compilation which is something that, especially in UE5, happens at full CPU/GPU load.

If shaders were being compiled, it would happen only once the first time you start the game.

[Melody]

RedAISkye님이 먼저 게시:

Melody님이 먼저 게시:

But whether the cutscene is prerendered or not really has no correlation especially when it comes to shader compilation which is something that, especially in UE5, happens at full CPU/GPU load.

If shaders were being compiled, it would happen only once the first time you start the game.

That doesn't come as granted when you speak Unreal Engine 5's language. Plus, whatever it is, it will be fixed when the game comes out.

[RedAISkye]

Melody님이 먼저 게시:

RedAISkye님이 먼저 게시:

If shaders were being compiled, it would happen only once the first time you start the game.

That doesn't come as granted when you speak Unreal Engine 5's language. Plus, whatever it is, it will be fixed when the game comes out.

That's just how shader compilation works regardless of language, they're done beforehand, so you don't face stuttering issues during gameplay.
There's only a need for recompiling them if there's a major game update or something.

And I highly doubt the demo even had shader compilation to begin with.

[Melody]

RedAISkye님이 먼저 게시:

And I highly doubt the demo even had shader compilation to begin with.

I guess they were magically summoning shaders with a magical wand then.

PS now leaving you with whatever floats your boat. Time to hit the magic button.

RedAISkye님이 먼저 게시:

I personally had no issues with the cutscene.

When a person's argument is "it works on my machine" you instantly know what you're dealing with.

[Thjaffi]

RedAISkye님이 먼저 게시:

Thjaffi님이 먼저 게시:

M.2 is just a form factor, they can be connected via SATA or PCIe.

Honestly, i don't notice any significant difference between a halfway good SATA SSD and a PCIe SSD in gaming. theoretical peak performance doesn't seem to have a great effect here.

Nah, M2 is a lot faster than your normal SSD.
But either one would be significantly better compared to HDD.

as i said - and i repeat it now - M.2 is just a form factor.
M.2 SSDs can be connected via SATA or PCIe.
A SATA connected M.2 SSD is not faster than a "normal" SATA connected SSD.

Altough PCIe SSDs technically have a significantly higher transfer rates, this doesn't provide a proportionally better loadtime in games.

Didn't found an english article, so here's a german one, but language doesn't matter, the result is the same: https://www.pcgames.de/SSD-Hardware-255552/Specials/Leistung-Ladezeiten-von-12-Games-mit-Festplatte-SATA-M2-m-2-im-Vergleich-pcie-3-4-Marktuebersicht-1412751/4/

tl,dr: 10% better loading times on average from 900% more theoretical transfer rate.

Bottleneck? CPU. It has to unpack the data the time they are read from the drive.
Thats the reason why you can often see 100% CPU usage in loadscreens while the game itself never uses all cores to full extent.

[Melody]

Thjaffi님이 먼저 게시:

RedAISkye님이 먼저 게시:

Nah, M2 is a lot faster than your normal SSD.
But either one would be significantly better compared to HDD.

as i said - and i repeat it now - M.2 is just a form factor.
M.2 SSDs can be connected via SATA or PCIe.
A SATA connected M.2 SSD is not faster than a "normal" SATA connected SSD.

Altough PCIe SSDs technically have a significantly higher transfer rates, this doesn't provide a proportionally better loadtime in games.

Didn't found an english article, so here's a german one, but language doesn't matter, the result is the same: https://www.pcgames.de/SSD-Hardware-255552/Specials/Leistung-Ladezeiten-von-12-Games-mit-Festplatte-SATA-M2-m-2-im-Vergleich-pcie-3-4-Marktuebersicht-1412751/4/

tl,dr: 10% better loading times on average from 900% more theoretical transfer rate.

Bottleneck? CPU. It has to unpack the data the time they are read from the drive.
Thats the reason why you can often see 100% CPU usage in loadscreens while the game itself never uses all cores to full extent.

That person is most likely just here to discuss pointless arguments to get the thread locked down, let's try to not feed it.

[Glenn H.]

Melody님이 먼저 게시:

apple님이 먼저 게시:

I playied demo with rx470 with 4GB of VRAM, On lite settings it was about 45fps, on higher 15-20. Yesterday while playing I noticed that 7200rpm HDD was too slow for this game - cutscene lagged, textures took kinda long to load, and you could feel that it need stronger pc. Time to look for used pc parts, like 16GB RAM, ssd, stronger and more vram gpu.

The cutscene problem is not a storage problem, it happens on my NVMe as well, it's just random. Sometimes, it's just smooth as butter, and sometimes it just lags. Probably shader compilation or something else. Definitely not a storage issue.

The cutscene only lagged on first run on my system.

[𝓒𝓱𝓮𝓻𝓻𝓲𝓢𝓽]

Bruh, go play the sims 4 then. Some of us have been waiting years for a sims game that looks nice and doesn't need to load walking across the freaking street. Can't run it? Save up, It's about time we get a big step up already.