eLucifer Posted August 14, 2010 Share Posted August 14, 2010 I have Fomm, Fose and Archieve Invalidated and recently downloaded a mod that changes the weather and light effects. I'm running the same on medium/low settings and when I downloaded the mod it sort of made the game look like as if I was running it on low settings. So I decided to use anti aliasing(by choosing ''Game Settings'' from the Fallout Mod manager menu) on 2 samples. The game looked awesome, but lagged a little so I decided to turn anti aliasing off. But then it looked like, well, a lot worse so I decided a little lag would be okay and tried to turn anti aliasing on the same way I did before. But when I clicked ''Game Settings'' Fallout Mod Manager just gives me an error looking like this: ''Something bad seems to have happened As long as it wasn't too bad, a crash dump will have been saved in 'fomm/crashdump.txt'Please include the contents of that file if you want to make a bug report' Well, here's the contents of that file: 14 August 2010 Saturday - 14:07:05Fomm 0.12.3OS version: Microsoft Windows NT 5.1.2600 Service Pack 2 System.ArgumentOutOfRangeException: Value of '10000000000' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.Parameter name: Value at System.Windows.Forms.NumericUpDown.set_Value(Decimal value) at Fomm.GraphicsSettings.OverrideSlider.set_Value(Decimal value) at Fomm.GraphicsSettings.GraphicsSettings.LoadDistantLODValues() at Fomm.GraphicsSettings.GraphicsSettings..ctor() at Fomm.MainForm.gameSettingsToolStripMenuItem_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) Please help me access the game settings again. I HAVE TO turn anti aliasing on. PS: When I play the game after changing anti aliasing settings from FOMM(either turning it on or off) the game's display settings get resetted( for example the brightness option is always max but when I change the settings it returns to default) and the options like actor fade, tree fade, etc. get messed up(actor fade goes above it's limit and the others are set too low) so I set them on default again(using the Default button, obviously) and set my own settings again. Link to comment Share on other sites More sharing options...
eLucifer Posted August 14, 2010 Author Share Posted August 14, 2010 Update: It seems I can't change anything from FOMM. I tried to check for updates, but it just gave me the same error message. Although things like auto sort work fine. Link to comment Share on other sites More sharing options...
eLucifer Posted August 14, 2010 Author Share Posted August 14, 2010 Problem condition: Resolved, in a really weird way. I started up regular launcher from Program Files>Bethesda Softworks>Fallout 3 and activated anti aliasing through that and closed it. Then fired up FOMM again and now Game Settings can be opened without any problems. Link to comment Share on other sites More sharing options...
Recommended Posts