13-01-2020, 10:00 PM
(13-01-2020, 07:36 PM)Joeflyer Wrote: Alex, why would you want to delete the local folder?? You may be thinking about the shaders folder. With the number of issues you are having, may I suggest doing a complete uninstall of -SE (go to the FSX forum for the complete uninstall process) and then re-install OUTSIDE of the (X86) directory. Yes, you can do this via custom install. Then install FsP and test with a default aircraft.The local is the shaders folder, I deleted the roaming folder (not the actual entire roaming folder but just the fsx part) but did not delete the shader's folder, since i do not have much experience with but I reread the guide and forgot to delete it. I already did a reinstall and deleted the roaming and the main directory. Fsx is now in the backup ssd far away from program files.
Dovetail reccomened on their full uninstall guide to delete 2 folders besides the fsx main directory
• [drive]:\Users\<User Name>\AppData\Local\Microsoft\FSX
• [drive]:\Users\<User Name>\AppData\Roaming\Microsoft\FSX
The roaming has the fsx config dll.xml ect
I did run an sfc scanow in the command prompt and it did find dll errors. I also reinstalled directx 2010 as i saw someone mentioned that helps with this menu bar ctd. I also moved the uiautomationcore from the actual system 32 directly into the fsx folder. I heard that actually fixed the menu crash for some people. i'm not seeing the fspassengers module fault in the event viewer and crash app, i'm only seeing hypergauge.dll and XAudio2_6.dll, which i actually haven't gotten for a while so something definitely is different after the reinstall. Even though the ctd is the same exception code and seems to be triggered by the menu. So far i haven't gotten a crash yet but I've yet to really thoroughly test it, and the crash really seems almost random.
If that doesn't work i might have to try again on the reinstall as i don't think i really did a 100% cleaning of all previous remnants, such as the shader folder still not deleted. I'm thinking it might also be a weird system problem as i did find dll errors using the command prompt scan. Hopefully that uiautomation trick will fix it but if not besides a reinstall maybe use the tweaking windows repair tool.