Installation Failed, File Exists... but I can't enable or find the file

[Deleted22735209User]

Backstory:

So I recently started playing New Vegas so I decided to look at the mods I had and since it had been a little less than a year since last I played, I had the bright idea of removing the mods I had. I added mods like FCO 2.3 with TTW (Somehow it worked) along with a few other mods like animation overhauls and PN but for some reason I got this weird studder effect while trying to play. Initially, I believed that it was FCO conflicting with TTW but removing it did nothing so I continued to mess with the mods testing what caused it to no avail, so having no choice I deactivated the mods (I was using FOMM version 14), deleted the New Vegas Folder (Probably a dumb idea), deleted the managers (Full uninstall), and proceeded to reinstall the vanilla game and the managers. That's where the problem started I can install certain mods with different managers.

Dilemma:

I cannot install the Mod Configuration Menu with Vortex but I can install NVSE Extender v16, it works opposite in FOMM. It gives me the same reasoning "The File Exists" and no way to fix it. I've restarted my computer, uninstalled and reinstalled the game and the managers and nothing has worked.

 

Under details for "The File Exists" it gives me this:

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

at System.IO.Path.InternalGetTempFileName(Boolean checkHost)

at FomodInstaller.Scripting.CSharpScript.CSharpScriptCompiler.Compile(String p_strCode, Type p_tpeBaseScriptType, CompilerErrorCollection& p_cecErrors)

at FomodInstaller.Scripting.CSharpScript.CSharpScriptExecutor.Compile(String p_strCode)

at FomodInstaller.Scripting.CSharpScript.CSharpScriptExecutor.DoExecute(IScript p_scpScript, String p_strDataPath)

at FomodInstaller.Scripting.ScriptExecutorBase.<Execute>d__0.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at FomodInstaller.ModInstaller.Installer.<ScriptedModInstall>d__23.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at FomodInstaller.ModInstaller.Installer.<Install>d__a.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at FomodInstaller.ModInstaller.InstallerProxy.<Install>d__16.MoveNext()

 

So if there is any advice please tell me please and thank you, sorry if I did something really dumb.

[dubiousintent]

One thing to check when Windows starts having problems locating a file that has been installed, is that the file path doe not have any Unicode characters. Older games (and tools specific to them) often have problems with Unicode. That message is coming from the Vortex "FOMODInstaller" routine, and something to take up with them. I would read it as complaining the MCM file (MCM.dll) already exists, but it should be overwriting it or at least prompting, not aborting.

 

The statement "I cannot install the Mod Configuration Menu with Vortex but I can install NVSE Extender v16, it works opposite in FOMM" confuses me. It looks like your problem is with the installation of MCM, which puts some components into the "NVSE\Plugins" folder. But (just to be sure you know) "NVSE Extender v16" is a supplement to, and not a substitute for, NVSE (currently on version 5.1b4).

 

Re: Stuttering or "micro-stutters". All visual stuttering problems are caused by the video stream having to wait for the "art assets" required to render the display OR the game writing something to disk (such as a save game file or logging). Mostly these are due to the hard disk drive being orders of magnitude slower than VRAM, with System RAM (e.g. "ENBoost") and "solid state drives" (SSDs) being in between. Keep in mind that this game was designed for older PC and XBox console systems, and it is now possible for your new "latest and greatest" gaming machine to be faster than it can handle. There are internal design choices that cannot be overcome. The "video pipeline" has always been prone to problems. The following are "mitigations" that have been found to help some people.

Please see the following entries under the 'Solutions to Performance problems' section in the wiki Fallout NV Mod Conflict Troubleshooting" guide if you haven't already.
* 'Issue: "Full screen mode" exhibits CTDs and stutters or micro-stutters'
* 'Issue: Lag or "micro stutters" even with "New Vegas Stutter Remover" installed'
* 'Issue: Win10 Screen tearing in "Borderless Windowed Mode"'
* 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' for other settings that can indirectly affect micro-stutter.
* There are also some NVSR configuration suggestions under the 'Issue: Game in slow motion' and entries. (These will not help with the "Tick Fix" alternative mod, but the author of NVSR now has a suggested configuration for Win10 linked there.)
* The 'Issue: What's with these Solid Green billboard signs in the distance (LOD)?' entry under the 'Solutions to Mesh (Red "!" icon) or Texture (solid color) problems' section can also help if your problems started after you installed VWD/LOD texture packages.
* If you are using CASM or some similar "auto-save" mod to manage your save game files (recommended), try increasing the "time between saves" set in the "save frequency"; and reducing the number of occasions it saves to the minimum (e.g. disable most "Autosave Events" in CASM) and see how that impacts the game seeming to freeze temporarily.
* If you have "NVSE logging" enabled (see the 'Checklist Item #4' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide), disable it until actually needed.

Reading from or writing to disk for any reason is the slowest thing the game does.

The size of your image files also has an impact. Larger/higher resolution is not always "better". Please see the wiki "Display resolution versus Image Size" article.

The 'Issue: What INI edits seem to be most beneficial to performance' entry of the wiki "Fallout NV Mod Conflict Troubleshooting" guide) may also be some help. However, the above mitigations are more likely to have a fundamental beneficial effect with or without any INI adjustments, so consider them as the last resort.

As you can see, there are a number of things that can underlie your original problem. If one of these doesn't fix it, I would be interested to hear about any eventual solution that does.

-Dubious-

[Deleted22735209User]

Thanks Dubious for the fixes, hopefully that fixes some the performance issues. As it turns out after searching the forums a little longer I found a post from 2014 with the same problem (Here) that solved my File Existing problem by deleting the Temp files on my computer. Sorry about the confusing wording, I meant that a mod would be able to be installed on one manager but not the other. Again thanks for the help.

Edited April 25, 2019 by Guest

[dubiousintent]

Ah, yes. I'd forgotten about the temp files possibility. I've added it to the "Solutions to Miscellaneous problems" section of the wiki "Fallout NV Mod Conflict Troubleshooting" article.

 

Thanks for reporting back on that.

 

-Dubious-