Trying to mod on steam deck but cpu_info.exe won’t run properly not sure if it’s a Linux/SteamOS issue or what does anyone have a recommendation for which version is best on steam deck?
Because this file needs to be installed manually in the game's root directory, the same folder with the game's executable. It can't be installed with a mod manager.
yeah, literally nothing happens, just asked me to use a app to open it with and I use it and nothing, just sends me to a white screen and then...nothing.
Do we really need the little black window? It makes it so I can't effectively alt tab out to my desk top. Really annoying. Please consider doing something about this, or tell me if there's something I can do to get rid of it myself. Good lord.
Hi, thank you so much for your work on the mod. I am trying to install this as a requirement for the FO3 HD overhaul. Like some other users, I am experiencing regular but inconsistent (i.e no discernible cause) CTDs. I'm not very technically able and new to modding. Is it possible the cpu_info.exe is giving incorrect recommendations? I am going to experiment with the other files, but please let me know if you have a fix for this crashing issue otherwise?
Quick update: I have tried all the different options and the AVX2 recommendation does seem to be the one that works best with my setup, but "best" in this case is a relative term as it is still CTD'ing, it just takes a handful of seconds longer than the other options to do so.
Please don't infer any ill will from my comments. I'm very new to modding, I'm genuinely grateful for the work you authors do, and I'm just trying to learn more. Do you have nay idea why its not working in my case?
What process? If you mean running cpu_info.exe - it just uses cmd.exe's command line environment to determine which d3dx9_38.dll version in particular suits your system best and informs you about it. You can exit it by pressing any keyboard button (as it instructs you in the command line window), then just copy the needed d3dx9_38.dll version into the game's root directory and you are ready to go.
FOr some reason, using this causes consistent yet non-persistent crashes when used alongside Feng Shui.
To reproduce, begin a Feng Shui session, and start moving items around; after about 2 to 5 minutes, the game will hard CTD, usually when bringing the pipboy up.
The CTD will come even if you end your Feng Shui session early, but if you do so and save the game you can load that save and no CTD will come (hence non-persistent).
I have no idea why.
I figured this out thanks to NVAC's shadow of a crash log, which pointed out that the CTD-causing unhandled exception was within d3dx9_38.dll, added by Heap Replacer.
When I remove d3dx9_38.dll from the Fallout 3 directory, the CTD doesn't happen anymore.
Mind you, even if using Heap Replacer and FengShui, the CTD does not happen unless one starts a Feng Shui session.
I see this is still listed as experimental, but...how experimental exactly? What specifically makes this less stable than the New Vegas one? From a technical standpoint, I am genuinely curious.
All of the research I did to implement this was done for Fallout New Vegas. I simply searched for the corresponding addresses in Fallout 3 and made another version. I tested and it seemed stable. That is why it is experimental.
Give Feedback
89 comments
Why did you allow people to install it with a Mod Manager then? You had an option to clarify it, and you did NOT.
Please don't infer any ill will from my comments. I'm very new to modding, I'm genuinely grateful for the work you authors do, and I'm just trying to learn more. Do you have nay idea why its not working in my case?
Is this normal? Or should I be concerned?
To reproduce, begin a Feng Shui session, and start moving items around; after about 2 to 5 minutes, the game will hard CTD, usually when bringing the pipboy up.
The CTD will come even if you end your Feng Shui session early, but if you do so and save the game you can load that save and no CTD will come (hence non-persistent).
I have no idea why.
I figured this out thanks to NVAC's shadow of a crash log, which pointed out that the CTD-causing unhandled exception was within d3dx9_38.dll, added by Heap Replacer.
When I remove d3dx9_38.dll from the Fallout 3 directory, the CTD doesn't happen anymore.
Mind you, even if using Heap Replacer and FengShui, the CTD does not happen unless one starts a Feng Shui session.