Fallout 1 mod Fallout Fixt - next release will be some time in Jan 2020

Sduibek said:
UniversalWolf said:
and if you enter combat at all, the self-destruct goes off and you die
Click to expand...
I don't think that's right... the main issue would be that each combat round equals roughly five seconds of game time. So those are being deducted from the Time Left countdown.
Click to expand...
My guess would be that the bomb automatically detonates when the player leaves the military base map via the exit grid, regardless of how much time is left on the timer, but entering combat also counts as "leaving the map," for some reason.

Combat works normally while you're still inside the base. It only makes the bomb go off once you get to the surface.
 
Combat shouldn't initiate the bomb going off, but I did make some changes so that:
1) If the timer is ever interrupted from scripts or entering dialog, it restarts once the script or dialog is finished.
2) The display at exactly five second intervals works properly during combat now, so it's -5 seconds to the timer at the end of each combat round.

So, look for that in patch 6.3, it really shouldn't ever "just go off" as you're describing. (Except for when leaving the entrance map, you're right about that)

I'm actually really proud of my "every five seconds" code, in 6.3 it's going to pretty much work perfectly 8-) :D
 
EDIT: First make sure you're using the newest version of f1_res, downloadable here.

To those of you who wouldn't mind doing some more testing: Please download the file below, place in your Fallout FIXT directly and see if it causes crashes. Specifically, patch the exe to enable it, and then try using various values on both sliders. Do this with a NEW CHARACTER just in case, because Fallout is annoying like that.

https://www.dropbox.com/s/obznwmcm2kkqdt9/FO1_encounter_tweaker.exe
_
 
Next release will change the "old version warning" to no longer be dialog, just a brief float message and a detailed system message (bottom-left message area). This is so it can display immediately upon load-game, if dialog initiates right away the game crashes so the dialog implementation kind of sucked.

Also I'm working on a fix for Look At not working intermittently. Any of you who've played Fallout a lot, you should have noticed that sometimes when you hover over something you get no "You see:" message. You'll have to click-examine something else and then hover over the original object again. I'm working on fixing that because it's annoying as hell.

Timer in Military Base works better -- "every 5 seconds" update works flawlessly in combat now too, and restarts if it's interrupted (like if you go into dialog)
 
Sduibek said:
Izo said:
The first answer to the 6.0 is a bug report. :O
Click to expand...
You mean the first post in this thread following release of alpha 6.0? Seems legit, I even said in the release details that bugs would probably exist. It was an extensive change to the mod so very difficult to test thoroughly.
Click to expand...
It isn't legit, it seems that the patch is 0.x. Again and again. It puts another bugs.
 
Izo said:
Sduibek said:
Izo said:
The first answer to the 6.0 is a bug report. :O
Click to expand...
You mean the first post in this thread following release of alpha 6.0? Seems legit, I even said in the release details that bugs would probably exist. It was an extensive change to the mod so very difficult to test thoroughly.
Click to expand...
It isn't legit, it seems that the patch is 0.x. Again and again. It puts another bugs.
Click to expand...
If you can provide a link, or savegame, or screenshot that would be helpful. I am not sure what you're referring to. Sorry.

Thanks :)
 
Wow, Junktown has 60 entries in the bugs wiki. (EDIT: No, those aren't all things I broke. I'm pretty sure the majority of these have existed since vanilla or TeamX patches)

Nevill wasn't kidding about Junktown being seriously broken.

:eek:
 
Hello I googled my error and I cannot seem to find a fix but here is my issue:

Downloaded and installed FIXT 6.1 then the 6.2 patch and everything appeared to running well. Made it through the rat cave and left the vault and began my travel and ran into the trader that offers to let you run to Shady Sands with his group and bame game crashes and I get this error: "the instruction at 0045bafc referenced memory at 000001a4." I got this same error twice in a row in the same circumstance.

I then tried to play again and just go directly to Shady Sands and again the game crashed and I got a similar error to the first with a different memory location or whatever it is listed. Here is a screenshot http://i.imgur.com/vJKgW5D.png

I am playing on STEAM and a 64 bit windows vista (!) computer, if that matters.

So I am looking to actually replay the game for the tenth time and if anyone has a suggestion I would appreciate it. Thanks! :crazy:
 
Crashing at Shady Sands? That's weird. Could you upload a savegame please? I'll take a look.

EDIT: Just tried and works fine for me. :shrug: So I will definitely need a savegame to test.

EDIT2: Are you running it through Steam? Like through the Steam interface? If so, trying just opening Falloutw.exe manually - you should be able to go to c/progam files (32)/ steam / steamapps/ common (or something similar to that). Or just do a file search for Falloutw.exe.

Another one I always try, to rule out any weirdness with the computer itself, is try disabling User Account Control (can find in control panel), and try Compatibility settings set to Windows 95 (right click on Falloutw.exe for that)
 
Thanks for the quick reply! I just read it and now I am going to try to run it outside of STEAM, disabling UAC and the compatibility setting. I'll start a new game as well if that doesn't work. If all fails I'll upload a savegame.

Keep your fingers crossed :D

EDIT: OK I even tried taking a premade guy through the rats and on to Shady Sands and crash. I entered the map for Vault 15 just fine too. I tried to upload the save game but I have no clue where it went! I searched through the file uploads and ordered them by date even and I still don't see it....let me know I Rar'ed the SLOT1 save and I can PM it to you or whatever I just gotta figure out how.

EDIT #2: Ok I emailed you the SLOT1 rar file so if you have time check that out. I might try reinstalling and repatching in the meantime. Thanks for the help!

Edit #3: Redownloaded on STEAM and repatched and I'm still having the issue. So I have no clue whats going on :crazy:
 
What folder were the savegames in? Like the entire path -- D:\blah\blahFIXT\blah\blah\SLOT01

Also if you could please try to keep playing... just pretend Shady Sands doesn't exist, and do everything else. I want to see if you're getting various crashes or it's just something on that one map.
 
Sduibek said:
What folder were the savegames in? Like the entire path -- D:\FIXT\blah\blah\SLOT01

Also if you could please try to keep playing... just pretend Shady Sands doesn't exist, and do everything else. I want to see if you're getting various crashes or it's just something on that one map.
Click to expand...

OK I'll do that and let you know.

C:\Program Files (x86)\Steam\steamapps\common\Fallout\DATA\SAVEGAME
 
There was a bunch of installer options that didn't correctly link to their global variables. [sigh] That is fixed for next version.

(Some of you noticed it, things like turning in Bob, the Brotherhood operations, etc)
 
FalloutAznBoi said:
Ok what should I do to get this working? Just use only 6.1 I guess?
Click to expand...
You could try that but honestly I'm not sure why Shady Sands is crashing. Like I said I'll look into it but it might just be your system being weird.

To see if FIXT is causing it, try just running Fallout as a fresh install, without any plugins or mods.

Then try: install FIXT 6.1, then after that, install newest f1_res available here
 
You must log in or register to reply here.
Back
Top