|
Post by steelerswit on May 17, 2020 17:55:26 GMT
Backed up my Steamapps folder to a portable hard drive and striped my desktop of all SSE files and removed vortex and all its clutter and rebuilt it with mods I know I like. Its been a few years since I did this and with trying so many mods, install, delete, try others, I knew there had to be a bunch of garbage lingering around. So, starting over and now a weak azz level 1 player.
|
|
|
Post by Sniffles on May 18, 2020 7:48:15 GMT
Now you really do have a moral obligation to catch whoever created Vortex and bury them alive under a hog pen. Just saying.
|
|
|
Post by blockhead on May 18, 2020 12:16:42 GMT
Now you really do have a moral obligation to catch whoever created Vortex and bury them alive under a hog pen. Just saying. Reminds me of a quote from Real Genius: "First thing you should do is get even with Kent. It's a moral imperative."
|
|
|
Post by steelerswit on May 19, 2020 13:37:39 GMT
I'm out to get Kent! 20 mods installed and having CTD ISSUES! nothing fancy either. Fores has a 12.9% CTD and every time I go to map crash. Random CTD. Time to purge again and learn MO2.
Yeah, I'm stupid.
|
|
|
Post by Sniffles on May 20, 2020 1:48:58 GMT
Which reminds me, a little lucidity from my techy a while back. If anyone could help me out understanding this it would be much appreciated.
"Repetitive CTDs when playing games commonly have two causes; the origin cause ->AND<-- an embedded cause in the saved games. Think about it: CTDs are perceived corruption issues. Perceived in that the OS has found an error, whether it is in fact an error in the code, or in how it happened to be mishandling the code at that particular moment. Singular CTDs are often the OS was busy masturbating to images of Hillary Clinton. Once is usually enough in it's lifetime. Repetitive CTDs are more often than not run time errors. Get a halfway decent computer with a RAID 5 of a few ultra fast SSDs and 32 GB of blitzing memory and run the program again without it ever having to cache. No CTD, run time error. If CTDS are repetitive, the cached and re-accessed code is being read wrong for any of a few million reasons. If this wrong reading is a dynamic, active code being read and written as a game changing cells, reloadings, refreshings, it gets written to the saved game. So you can correct the original issue, removing the Hillary mod, but the saved game is now corrupt. Simply take note of the circumstances where the game went CTD, revert back a few saves and enact those circumstances again. No CTD, double corruption."
|
|
|
Post by jgf on May 20, 2020 2:41:53 GMT
With many games a year or so of adding/removing/tweaking mods leaves debris strewn throughout the folders; wasted space, ini or cfg entries no longer optimal; a mixture of alternate textures...
It's often easier to just reinstall the base game and the mods you know you will use than to try cleaning out that quagmire of leftover files, especially when they, or some arcane combination/interaction of them, is causing problems. I dread the ordeal of doing this with MS FlightSim, but my current install is ten years old and has migrated across three computers; I see railroads running across airports, lakes with two different textures, a dam a half mile away from the river, flying above 1500ft in southern Germany causes a CTD (but this reinstall will entail dealing with over 120gig of original game, add-on aircraft and scenery, utilities, hd textures, etc.).
This is one reason I eschew any "kitchen sink" mods; not only do they usually include things I do not want along with the items I do want, but they are virtually impossible to remove.
|
|
|
Post by naramoore on May 30, 2020 19:56:35 GMT
Never used VORTEX, after figuring out ModOrganizer, I never saw the need. Modorgnizer isn't anywhere near as hard as people make it out.
|
|