This is Thread #2. Here is http://www.gamesas.com/index.php?/topic/1138765-relz-fallout-mod-manager/.

I'm sure many have realized that I have not been in the forums of late. I apologize for the falling off of support. I wanted to let everyone know that I won't be supporting this version of FOMM for the next while; however, I am actively working on a replacement that I hope everyone will find far superior. Rest assured that I haven't abandoned everyone, but that I am indeed working to create the best FOMM yet.

This version of FOMM is the first step in expanding the scope of the mod manager. Instead of having two different managers, one for Fallout 3 and another for Fallout: New Vegas, FOMM is able to manage mods for both games from a single install. This ensures that all new features that are added to FOMM will be available for both games. Further, the folders that FOMM uses to store install info and FOMods are now configurable, allowing you to place them wherever you have disk space, rather than wherever FOMM is insalled.

Because FOMM is no longer a mod manager for a single game, the recommendations for where to install it have changed since 0.12.x and older versions. Whereas it was usual and recommended to install FOMM in the Fallout game folder, that is no longer the case. While you are free to install FOMM wherever you like, the recommendation is to let FOM install itself in the Program Files directory. This is also true for users running Vista/Win7 with UAC.

When you run FOMM for the first time, you will be asked where you would like to store your FOMods, as well as where you would like to store FOMM mod installation information. The default locations are recommended, but you can specify alternate locations if you wish: for example, if you have a separate drive dedicated to FOMods. The only restriction is that you not set the directories to Fallout's game folder.

Finally, FOMM 0.13.x is a completely different programme from previous versions. This means that instead of replacing previous versions, it will be installed alongside them. This is so that users who like old-FOMM can continue to use it for Fallout 3, whilst enjoying new-FOMM for Fallout: New Vegas. However, this mean that if you would like to use new-FOMM for both games, it is recommended that you uninstall old-FOMM after installing new-FOMM, to minimize confusion as to which FOMM you are launching. Don't worry, however, future version of FOMM 0.13.x and newer will automatically replace older FOMM 0.13.x installs, while still leaving any 0.12.x or older installs intact.

http://sourceforge.net/projects/fomm/
http://sourceforge.net/projects/fomm/files/
http://www.newvegasnexus.com/downloads/file.php?id=36901

Lastest Version: 0.13.21

when i clicked on update, under help, fomm crashed with a script error. if i don't do the update for boss, fomm runs fine.

Wednesday, February 09, 2011 - 10:51:27 PM
Fomm 0.13.21
OS version: Microsoft Windows NT 6.1.7600.0

System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at System.Version..ctor(String version)
at Fomm.MainForm.checkForUpdateToolStripMenuItem_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.HandleMouseUp(MouseEventArgs 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.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.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 have noticed that FOMM doesn't always seem to show a progress bar when either installing, or loading a compressed file. I really liked that "feature".

Every time i try to update FOMM i get an ERROR and the program closes, here is the crash dump i get....

Wow. FNV mod section really had died.

Getting the SAME error others are getting. Looks like it's an old issue.

CRASH WHEN I CLICK ON HELP>CHECK FOR UPDATE.



There's the crash dump.

Nevermind. Pretty useless even reporting this anyways. Just had a look at the sourgeforge forums, and others where FOMM is, and no one has replied to any of the bug and crash reports in at least a month. Oh well. Kinda pitiful for a mod that EVERYONE uses and is essential to the entire modding process. Guess I'll just put off playing FNV until someone decides to fix what is wrong, because until then, it seems trying to mod FNV right now is a futile attempt doomed to end in constant CTD's.

You sound extremely entitled.

I don't see how the having the check for updates function would stop you playing New Vegas. If it is the load order you want, just use BOSS, seeing as I'm pretty sure that is the list it downloads for it anyway.

Thank you so much for FOMM.

A wonderful and elegant utility.