Collecting information on crashes
[size=14pt]Please submit .RPT (more important) and .LOG files if you got any in your Fallout folder.[/size]
- [li]Do you have the most recent Fallout 3 / Fallout: New Vegas version? (you need: Fallout 3 non-steam 1.7 uncut, Fallout: New Vegas Steam 1.4 uncut)[/li]
[li]Are the savegames in the right folder? (e.g. check if you accidently copied the Fallout: New Vegas default.fos to the Fallout 3 savegame folder)[/li]
[li]Do you run any Fallout mods? If yes, remove them and try again (mods will be supported in the future)[/li]
In case you aren't able to resolve the crashes yourself, please provide the information I listed above and point out that you aren't able to run vaultmp properly ;)
Re: Collecting information on crashes
i got it to work just fine and i roamed the mojave for a while :D
Re: Collecting information on crashes
The New Vegas server does not work for me. When i click join it goes onto the normal menu.....
Re: Collecting information on crashes
[quote author=Jeppe link=topic=24.msg73#msg73 date=1308770207]The New Vegas server does not work for me. When i click join it goes onto the normal menu.....[/quote]
You have copied the default.fos New Vegas savegame to the savegame folder? Oh and check the version ;D But those problems with wrong versions / missing files / wrong setup will be automatically detected in the next build...
Re: Collecting information on crashes
Will the log always have the same filename, or will it be dated or something? just so I know whether to copy it somewhere else after each crash or something. I'd be inclined to zip up a batch of crash logs rather than one at a time.
Re: Collecting information on crashes
Logs will be timestamped, like "vaultmp_DateTime.log" ;)
Re: Collecting information on crashes
I frequently crash within the first minute of playing. I'm on Vista 64bit playing Fallout 3 1.7, everything is in the right folder and I have no mods running. I've done everything properly but it continues to crash, sometimes it happens instantly, sometimes I can make it to springvale, but I've never lasted longer than a minute. I've tried many things such as running in windowed, compatibility mode, lowering graphics and other things I've seen in posts to no avail.
Re: Collecting information on crashes
[quote author=Jakemop link=topic=24.msg474#msg474 date=1311742097]
I frequently crash within the first minute of playing. I'm on Vista 64bit playing Fallout 3 1.7, everything is in the right folder and I have no mods running. I've done everything properly but it continues to crash, sometimes it happens instantly, sometimes I can make it to springvale, but I've never lasted longer than a minute. I've tried many things such as running in windowed, compatibility mode, lowering graphics and other things I've seen in posts to no avail.
[/quote]
Have you disabled XLive, this is the most common problem around here.
Re: Collecting information on crashes
[quote author=Recycler link=topic=24.msg91#msg91 date=1308918792]
Logs will be timestamped, like "vaultmp_DateTime.log" ;)
[/quote]
For the command system coming soon, perhaps make a client command named "/timestamp" & "/pagelines"
Would be really useful, sorry about not suggesting this in the suggestions thread.
Re: Collecting information on crashes
I think I've been a bit lazy about what I refer to when speaking of "command system". The new command system doesn't have anything to do with client-mod interaction (like entering a /command i.e.) it's an internal operating procedure which task is to deliver and receive Fallout engine commands / results to / from the game process (one of the core modules of the mod).
The actual command system similar to SA-MPs is going to be implemented in the next update, alongside scripting related stuff. Note that we'll still need a GUI to enter commands then, but luckily houtin is going to develop this part of the mod soon :D
[quote author=Lorenc link=topic=24.msg476#msg476 date=1311748775]Would be really useful, sorry about not suggesting this in the suggestions thread.[/quote]
No problem at all ;) System commands like the ones you mentioned are a good idea, I'll consider implementing those :)