Conversation

Notices

1. sigmaone@toot.party's status on Thursday, 26-Jan-2023 16:13:25 JST SigmaOne

   Damn the FH5 loading times are bad

   The game is on a bloody SSD and it's still taking several minutes

   • Aral Balkan (aral@mastodon.ar.al)'s status on Thursday, 26-Jan-2023 16:13:21 JST Aral Balkan

     in reply to

     @SigmaOne Which guest OS are you running? If Windows, it has CPU limits. You should be able to configure CPUs x cores x threads to something that matches the artificial throttling built into Micro$oft’s “OS”.

   • sigmaone@toot.party's status on Thursday, 26-Jan-2023 16:13:23 JST SigmaOne

     in reply to

     Maybe it needs more than 4 threads

     The VM is supposed to have 6 but refuses to take 2 of them

   • Aral Balkan (aral@mastodon.ar.al)'s status on Thursday, 26-Jan-2023 16:17:34 JST Aral Balkan

     in reply to

     @SigmaOne Right, go into the advanced settings and configure 3 CPUs with 2 cores and 1 thread and you should get full utilisation. You’re being hit by dickhead Microsoft’s licensing limit of CPUs (because money).

   • sigmaone@toot.party's status on Thursday, 26-Jan-2023 16:17:35 JST SigmaOne

     in reply to

     • Aral Balkan

     @aral Windows 10 Enterprise, configured in virt-manager for 6 vCPUs but it only sees 4

   • Aral Balkan (aral@mastodon.ar.al)'s status on Thursday, 26-Jan-2023 16:22:17 JST Aral Balkan

     in reply to

     @SigmaOne (Or 3 CPUs x 1 core x 2 threads, I guess. I’m not sure which would give better performance, couldn’t find a good write up of whether there is a difference in this context. But the key thing is to keep the CPU count below Microsoft’s license restriction.)