Game crash after start

[weezer22]

I screwed something up now my game wont start. It worked before I put FOSE in. I took out fose and it still crashes. I don't want to reinstall because I did that so many times before.

 

So can anyone tell me what is in the Data folder before any mods are put in? Or can how can I make it work again?

 

EDIT: got my game to start but on one of my saves i have no pipboy. Anyone know how to fix?

Edited October 11, 2010 by weezer22

[GrindedStone]

Groovatron has many tools built into the fun stuff it has. One of them is add remove pipboy or pipboy glove in a nice easy FOSE menu.

 

Alternatly you can find the Form ID for the pipboy or pipboy glove an Player.additem or Player.removeitem

[weezer22]

Could FOSE be the reason why my game wont start, because when i took it out my game started.

[andertox]

Sorry to post my reply here... i have a random gamecrash... updated all the components... NetFrameworks to 3.5 latest DirectX Disallowed FFDShow for fallout and viceversa to solve the issure... upgraded the latest Nvidia driver... latest gamepatch... lowered the video settings... but nothing... i get random crashes on the world map... when encountering large wilderness and walking...just like that... also crashes when i enter in hUNTER's house in Springvale...

 

here's the error crash dumpfile...

 

System.ArgumentOutOfRangeException: '7500000000' non è un valore valido per 'Value'. 'Value' deve essere compreso tra 'Minimum' e 'Maximum'.

Nome parametro: Value

in System.Windows.Forms.NumericUpDown.set_Value(Decimal value)

in Fomm.GraphicsSettings.OverrideSlider.set_Value(Decimal value)

in Fomm.GraphicsSettings.GraphicsSettings.LoadDistantLODValues()

in Fomm.GraphicsSettings.GraphicsSettings..ctor()

in Fomm.MainForm.gameSettingsToolStripMenuItem_Click(Object sender, EventArgs e)

in System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)

in System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)

in System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)

in System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)

in System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)

in System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)

in System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)

in System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)

in System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

in System.Windows.Forms.Control.WndProc(Message& m)

in System.Windows.Forms.ScrollableControl.WndProc(Message& m)

in System.Windows.Forms.ToolStrip.WndProc(Message& m)

in System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)

in System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

in System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

in System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

Also using the following mods:

 

Custom race, Dim's Custom Race v.2, calibr.esm, 20th century alive mod, Type3 Clothes, LingerFingerThings.esm. blackrock shooter.esp, 3EFdrg.esp. Tactical Weapons by gRs Frederyck.esp, DarnifiedUI.esp, Outcast Stealth Suit.esp, DN_SpiderSuit.esp. Persona_and_Secret.esp, REJillOutfit.esp and all the expansion packs excluding Vegas...

[weezer22]

Groovatron has many tools built into the fun stuff it has. One of them is add remove pipboy or pipboy glove in a nice easy FOSE menu.

 

Alternatly you can find the Form ID for the pipboy or pipboy glove an Player.additem or Player.removeitem

 

I tried the console code. It tells me the pipboy has been added but when I press tab My arm comes up then back down.

[GrindedStone]

GOTY (Game of the Year) edition of fallout 3 requires no patch, it's 1.7 already, however many of the GOTY edition players fix many issues by running the 1.7 patch after installing Fallout 3 GOTY. I only mention this because it would be quite rare to actually have a problem with FOSE (Fallout Script Extender). This current version is the 7th version of FOSE I've used along with 6 different game patches that came out. I've never had a problem besides having the wrong version. In fact the only other possible problem is for people using the Russian version of the Game. Hence how I came up with the probability of you using a unpatched GOTY editon.

 

In the case that you didn't use GOTY. I would mean either your game isn't patched to 1.7, or Somehow you messed up the install, or you grabed the wrong version of FOSE. All of these are quite easy mistakes to make. It's not like other games you actually have to read stuff to get things to work. You have to just about read every line of the read me, at least until you know enough to get by on experience alone. It's a great game an near unlimited modding potential, however there's a insane amount of work you have to do just to get anything.

 

Let's start with dispelling your fear of FOSE. A script sounds scary huh? Words an characters compiled into Hex is what I would call it, but I heard rumors comming up that it was some A++ code (computer language) pfft this is just rumor. It's not even that complex. If you asked me what it is I'd say it's nothing more than a complex macro. When you look at a script it's in words an punctuations. The computer turns that into something it can read, but we only deal with the words an punctuation, so it's not really a computer language. More like a list of commands.

 

The Fallout.exe, Gamebro engine, Havok Physics Engine, Direct X, and GFWL (Games for Windows Live) are pretty much the components of Fallout 3. For one reason or another when the Fallout.exe was created it was done so in such a way as to disable some of the things that you can do with these tools. For example while in game you can change game settings by using the console commands, however you can't put those same commands into a script an have it work.

 

FOSE comes in by enabling the use of all commands in scripts. Plus it creates some new commands. In order to do this it also has to disable GFWL (Games for Windows Live) but that's a big bonus because just about all the gamers don't really like having Microsofts finger in the pie. That's just for performance reasons though, and you can argue it's silly to worry about. I mean if I could use FOSE an GFWL I probably would. Since you have to disable GFWL to get the FOSE scripts it's a good trade off. Mostly because 90% of the reason that modders can create mods which can have near limitless possibilities is directly linked to FOSE.

 

----------------------------------SAVE GAMES----------------------------

 

Anytime you change anything about fallout 3 you run the risk of ruining a save game. So it's safe to say that anytime you do so you should start a new game. Even further anytime you have a problem you should duplicate it under the exact conditions, and then also try to duplicate it in a new game start. Which will rule out if it's a issue caused by a save game. Somewhat the same thing is installing the game an patching it then running a long test game to see how well Fallout 3 runs on your system to rule the computer system configuration an fallout 3 install as to a cause for any future problem.

 

Auto Save & Quick Save promote coruption. This is because the game isn't paused durring the creation of the save game, and any number of things like chaos can be going on in the background. Also Quick Save is only a partial save not a full save. So never Quick Save or Auto Save, yay problem fixed. Press Esc each time an create a new save game. There's still a slight chance that your game can be going corupt an you not know it until you crash an hour later. Which durring that time you could have created new save games thus locking that coruption into the save game and causing crashes next time you load it. Which is why you never delete your save games until you are ready to delete them all an start over. Also the Continue button while at the Main loading screen (Main Menu) is somewhat prone to coruption so we don't use that either.