|
Проблема с FOMM |
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
© 2008—2023 Bethplanet.ru
Post copypasted from the first post bc I forgot about tags.
I am a first time modder. I have recently informed myself on FOMM’s dated system and tendency for errors. This post will detail how to fix the dreaded «something bad» error that locks you out of FOMM and FNV.
Hopefully, this will help new modders who are reluctant to install newer mod managers/want to fix before installing new managers/just want to fix the error.
-
Uninstall FOMM. Go to Local Disk (C:)/Program Files (x86)/FOMM/ and run the uninstaller.
-
Delete the FOMM file.
3 Uninstall FNV. Local Disk (C:)/GOG Games/Fallout New Vegas/ Run the uninstaller. There will be asking if you want to keep your mods. Up to you, I accidentally clicked no.
4. Reinstall both FNV and fomm.
5. If you deleted you mods like me, painstakingly add each one back into FOMM.
6. Try to avoid whatever you did that caused the error.
I got the error when I tried deactivating MCM while having Project Nevada. Apparently those 2 conflict each other in some way that deactivating MCM tickles FOMM the wrong way. So I left MCM out the next time.
A tip to first time modders is to check which mods conflict with each other and decide which one you want.
«Couldn’t inject dl»l — такая надпись в окошке вылазит,когда жму в FOMM кнопку «Laynch SOFE» .Сама игра работает,только захожу я в неё теперь через Launcher.exe или fose_loader.exe…моды тоже работают,но вот что всё же за проблема с FOMM так и не пойму…кто что посоветует?
вот порядок загрузки модов: (и отмечу,что все эти моды работают ok )
Fallout3.esm
ThePitt.esm
Anchorage.esm
BrokenSteel.esm
PointLookout.esm
Zeta.esm
RZW_Master.esm
RZW_Television.esm
Mart’s Mutant Mod.esm
CrossRepairWeapons.esp
Fellout-pipboylight.esp
MrSlackPants-DecentPipBoyLight.esp
KillableKidsNormalHealth.esp
Level 2 Some More Color.esp
Explosive Entry.esp
Stealth Kills Enabled.esp
FPS Grenade Hotkey.esp
FPS Grenade Hotkey — Zeta addon.esp
Realistic Death Physics.esp
DUIF3RUS.esp
Fellout-Full.esp
Solar’s Bottled Water v2.esp
Solar’s Bottled Water — Bottlecaps.esp
BrokenSteel1.esp
BrokenSteel2.esp
Auto Aim Fix v1.1.esp
RZW_VideoCollection01.esp
RZW_VideoCollection02.esp
RZW_SilentVideoCollection.esp
RZW_VideoCollection00.esp
RZW_VideoCollection03.esp
RZW_VideoCollection04.esp
HouseholdWaterPurifier.esp
DK_BulletTime.esp
HouseholdWaterPurifierRus.esp
Mart’s Mutant Mod.esp
Mart’s Mutant Mod — DLC Anchorage.esp
Mart’s Mutant Mod — DLC Broken Steel.esp
Mart’s Mutant Mod — DLC The Pitt.esp
Mart’s Mutant Mod — DLC Point Lookout.esp
Mart’s Mutant Mod — DLC Zeta.esp
Mart’s Mutant Mod — Natural Selection.esp
Mart’s Mutant Mod — Tougher Traders.esp
Mart’s Mutant Mod — Zones Respawn.esp
Mart’s Mutant Mod — Master Menu Module.esp
respawn.esp
richvendors.esp
VatsLongerDistance.esp
1alexscorpionFPSanimations.esp
Distributed Necklaces and Chains.esp
ModAimCamera.esp
#1
Posted 16 February 2013 — 07:12 pm
wyattfg
-
- Members
-
- 4 posts
Stranger
In my Fallout Mod Manager, I get one error when it asks me to log into my Nexus for package manager and I click «Stay Logged In» and log in. It will say «Something bad seems to have happened» and tells me where to find the crash dump. I go find the crash dump and it says:
System.NullReferenceException: Object reference not set to an instance of an object.
at WebsiteAPIs.NexusAPI.get_LoginKey()
at Fomm.PackageManager.PackageManager.WebsiteLogin()
at Fomm.PackageManager.PackageManager..ctor(MainForm mf)
at Fomm.MainForm.bPackageManager_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Alright, so that was my first problem, though it is forgivable as I am able to get in the Package Manager as long as I do not click «Stay Logged In». It doesn’t give me any errors and I’m in. But my next problem comes in now. When I click «Add FOMod», I select the .7z file that is Project Nevada or Weapon Retexture Project and click «Open» and get another «Something bad seems to have happened» error with a crash dump.txt. This crash dump says:
System.NullReferenceException: Object reference not set to an instance of an object.
at WebsiteAPIs.NexusAPI.get_LoginKey()
at Fomm.PackageManager.PackageManager.WebsiteLogin()
at Fomm.PackageManager.PackageManager..ctor(MainForm mf)
at Fomm.MainForm.bPackageManager_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Steam, FalloutNV, and GeMM are all located in C:/Games. They are the only three things in there. Anyone have any suggestions?
- Back to top
Back to top
#2
Xaranth
Posted 16 February 2013 — 08:49 pm
Xaranth
-
- Supporter
-
- 2,746 posts
Starving Artist in Training
FOMM’s networking code is basically broken; if you want to use online features, you need to use NMM.
- Back to top
#3
wyattfg
Posted 16 February 2013 — 10:23 pm
wyattfg
-
- Members
-
- 4 posts
Stranger
FOMM’s networking code is basically broken; if you want to use online features, you need to use NMM.
I read somewhere that NMM couldn’t use PN. I believed it because I couldn’t get it to work.
- Back to top
#4
Xaranth
Posted 16 February 2013 — 10:35 pm
Xaranth
-
- Supporter
-
- 2,746 posts
Starving Artist in Training
It wouldn’t surprise me; NMM and FOMM do NOT treat certain installation functions the same way. You can run them in parallel, though, using FOMM to install those mods that need a Mod Manager, and NMM for general use.
- Back to top
#5
wyattfg
Posted 16 February 2013 — 11:28 pm
wyattfg
-
- Members
-
- 4 posts
Stranger
It wouldn’t surprise me; NMM and FOMM do NOT treat certain installation functions the same way. You can run them in parallel, though, using FOMM to install those mods that need a Mod Manager, and NMM for general use.
Don’t you have to do something with the path of one if you use them both?
Edit: And how could I use FOMM to install the mods if I get error messages every time I try to?
Edited by wyattfg, 17 February 2013 — 12:17 am.
- Back to top
#6
wyattfg
Posted 17 February 2013 — 05:39 am
wyattfg
-
- Members
-
- 4 posts
Stranger
I reinstalled and tried again. When I tried to log in, it just crashed. I just clicked cancel when it prompted me to log in and got to the package manager and got a different error when I tried to install PN:
System.ArgumentException: Unrecognized file format.
Parameter name: p_strPath
at Fomm.PackageManager.FomodBuilder.FomodFromSourceBuilder.BuildFomodFromSource(String p_strPath, NexusAPI p_nxaNexus)
at Fomm.PackageManager.PackageManager.AddNewFomod(String p_strPath)
at Fomm.PackageManager.PackageManager.addFOMODToolStripMenuItem_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.PerformClick()
at Fomm.Controls.SplitButton.OnClick(EventArgs e)
at Fomm.Controls.SplitButton.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
I know this is different than I’ve been getting. Does anyone know what this means?
- Back to top
#7
luthienanarion
Posted 17 February 2013 — 03:10 pm
luthienanarion
-
- Supporter
-
- 3,797 posts
Resident poster
Navigate to the following folder and delete it. Run FOMM again afterward.
C:\Users\USERNAME\AppData\Local\FOMM
Like Xaranth said, absolutely none of the network functions work in FOMM. No logging into the Nexus, no checking for mod updates, nothing. DO NOT try to log in.
Edited by luthienanarion, 17 February 2013 — 03:11 pm.
- Back to top
#8
knovack1
Posted 14 March 2014 — 04:47 pm
knovack1
-
- Premium Member
-
- 740 posts
Anon
The problem is, (although Gopher has a video going from NMM to FOMM) you will still get this error when just running FOMM for the first time and not ever using NMM for Fallout 3, and Fallout New Vegas. The error can be bypassed, » persay» just don’t log into username and password window. Just click cancel when the window shows up, and this will open your Package Manager. However after you install a mod the error will still pop up and FOMM will shut down automaticly
Do above again and you will see your mod in the Package Manager this time. Activate the mod, and there you go. It still works, you just have to reopen FOMM for each mod you install. I just think Nexus just wants to push their NMM, as the «only mod tool» to use. Can you blame them? I went through the above process on several mods, and when I went in game my mods where working.
- Back to top
#9
lKeelo
Posted 27 May 2014 — 07:13 am
lKeelo
-
- Members
-
- 5 posts
Stranger
Mine says this:
System.NullReferenceException: Object reference not set to an instance of an object.
at Fomm.PackageManager.ModInstallLog.InstallLog.InitMods()
at Fomm.PackageManager.ModInstallLog.InstallLog.Load()
at Fomm.PackageManager.ModInstallLog.InstallLog..ctor()
at Fomm.Program.Main(String[] args)
As soon as i click on the program it displays the error message. Should i even bother with FOMM or should i just use NMM?
- Back to top
#10
Kickbutttowski
Posted 20 October 2014 — 08:24 pm
Kickbutttowski
-
- Members
-
- 2 posts
Stranger
Yea i am going to change to mod organizer because of this bug
- Back to top
Fixed it!
It appears to be a file/folder write permission error. At least that is what I can put it down to.
The fact that the error was being generated upon the ‘Update required’ dialog I posted about earlier, made me think that something wasn’t being set in the program when FOMM tried to make changes to that location.
Completely uninstalled FOMM and purged any reference from my disk or the registry to anything even remotely related to it.
That included any ‘Install Info’ or ‘mods’ folders that were generated and all FOMM registry entries.
Since I was getting errors with Fallout 3 I decided to try and install it and work with it first. All looked good until after selecting the locations for those folders. This time I was allowed, and I thought all was good, but after doing the same for FNV, I again had to recheck the «which game» selector to FO3 and bingo! the error again.
So retry number 2, complete uninstall again and this time I decided to move the ‘Install Info’ & ‘mods’ folders to completely different locations.
Previously both those locations were sub-folders to my games:
**C:\Games\Fallouts** & **C:\Program Files (x86)\Steam\SteamApps\common\Fallout New Vegas**
Now I placed those folders as sub-folders under the install directory of FOMM like this:
C:\Games\Utils\FOMM\FalloutNV\mods
C:\Games\Utils\FOMM\FalloutNV\Install Info
and
C:\Games\Utils\FOMM\Fallout3\Install Info
C:\Games\Utils\FOMM\Fallout3\mods
Success!
I don’t know why that makes a difference, no folders on my system are under UAC and at any rate I have full administrator rights. Even the user.config is in a non-system folder so I have not the foggiest what is happening.
But there you have it. When FOMM tries to install its folders under my Fallout3 game folder, it bugs out whereas they are fine under the FalloutNV folder. If anything I would’ve thought the opposite since Fallout3 is away from the Program Files folder which is usually a problem.
PS. Sorry about the slip up over your writing this fork, with so many names attached to it I wrongly assumed.