The forum has been set to read-only mode. For community discussion and questions, head over to our Discord: https://discord.taleoftwowastelands.com

Okay, this is an SOS =P

General help and technical troubleshooting. Ask for help here if you can't find an answer in the FAQ.
User avatar
Himself
Posts: 36
Joined: Tue Aug 13, 2019 11:25 pm

Re: Okay, this is an SOS =P

Post by Himself » Mon Oct 21, 2019 5:38 am

Couple days back I wrote:
I disabled the frequency boost in BIOS, and also did all the BIOS updates available.
Dunno if it is just first impression or what, but things appear to be better, freeze still happens, but this time I had to "hunt" a bit for it.

Gonna test more this weekend, as time allows.
After all testing done (read post #20 on previous page, and disabling Core Performance Boost also didn't help), hoping something would really save my ass but failing miserably, I noticed the TTW install on a recent (non-updated & unoptimized) win10 partition was being quite the brave child! It is the one mentioned at the quote.
Heck it was running at a "kind-of" playable state, even after I throwed a gigantic textures folders inside (during my megamod install 2 months back, I made a meshes and a textures folder with just updated graphics, no plugins needed).

Something that was puzzling me from the start of this whole thing is why the heck FO3 and FNV run, but TTW freezes.
Now this TTW install on basic win10 was running while the other on fully updated win10+SSD was freezing easily.
Then it struck: There is a difference between the 2 installs! One was made fully, while the other was made in a hurry, so I didn't use the full TTW installer with sound encoding (or dunno what else).

Went to compare files, a few had different size, which is to be expected.
https://ibb.co/ZJHbMvZ

Copied the files from quick TTW install over the ones from full TTW install, and the game runs A LOT more stable. Can still freeze it (Yep, I'm a champ \o/) but it kinda looks playable, need to test with more mods.

If I'm not mistaken, TTW installer requires x86 Visual C++ Visual Studio 2015 to run. It is possible that my lib from fully updated windows is different from the basic one (there I only got directly from microsoft the c++ package installer was asking).
So I'm gonna leave the PC on fully installing TTW in the same OS that did the job nicely, but if game ends up freezing constantly, I will have to believe the fault is in TTW installer somewhere. Altough then, why would it be only me reporting this crazy freezefest issue? Lets see how it rolls before I can point fingers at either myself or the installer ^^
It is a cruel joke that man was born with more intent than life.

idmfan
Posts: 102
Joined: Mon Nov 12, 2018 9:28 am

Re: Okay, this is an SOS =P

Post by idmfan » Mon Oct 21, 2019 7:33 am

FiftyTifty wrote:
Sun Oct 20, 2019 6:56 pm
idmfan wrote:
Sun Oct 20, 2019 7:49 am

Thank you so much, will re-install TTW later and follow your advise.
As for DoW1 soulstorm, I will make it to use 0-1 ccx as it only recognizes 1 core.
Why? Assign it to the second CCX. Many programs and processes will use the earliest cores first, so assign it to the last core on your last CCX. With SMT disabled, that would be CPU 7. With SMT enabled, that would be CPU 14.
I decided to disable SMT entirely via BIOS since I hardly play modern games. After that, my process lasso interface looks like this.

https://ibb.co/6NV18qx

did I do it right? should I take another step?

User avatar
FiftyTifty
Posts: 493
Joined: Tue Apr 09, 2013 7:36 pm

Re: Okay, this is an SOS =P

Post by FiftyTifty » Mon Oct 21, 2019 7:48 am

idmfan wrote:
Mon Oct 21, 2019 7:33 am

I decided to disable SMT entirely via BIOS since I hardly play modern games. After that, my process lasso interface looks like this.

https://ibb.co/6NV18qx

did I do it right? should I take another step?
Untick cores 0, 1, 2, and 3. Also, open FalloutCustom.ini and set iNumHWThreads=4

User avatar
Himself
Posts: 36
Joined: Tue Aug 13, 2019 11:25 pm

Re: Okay, this is an SOS =P

Post by Himself » Mon Oct 21, 2019 11:02 pm

Following the logical conclusion, problem surely was on my end :oops:
Uninstalling and reinstalling all C++ Visual Studio runtimes seems to have solved it! (Hopefully the game is back to only crashing/freezing every once in a while, which is as I remember it ^^)

And just to clarify, for reference, if somebody has the same issue in the future:
You gotta reinstall TTW (and maybe possibly both games) after changing the C++ libs.

Gonna edit first post to add this.

Sorry to those I wronged and idmfan jlf65 Lyndi FiftyTifty GreyBeard00 thanks a million for the help!! ;)
It is a cruel joke that man was born with more intent than life.

Post Reply