Fallout 2 Restoration Project 2.3 (Unofficial Expansion)

[RolandDeschain79]

Interesting find, RolandDeschain79. I've seen people report the same thing about the high-res patch. There shouldn't be any problems using it, though I can't say for certain...

@iLikeDirt, it might be worth reverting you changes to ddraw.ini and then downloading the high-res patch v3.06 and use that instead. I'm curious if that works for you.

Thanks for the quick replay Killap I am also very curious about whether or not this will fix issues related to the PC installs. Keep up the great work

 

[killap]

I edited my previous post with a link to old versions of the RP, so don't miss that.

Also, I do believe going back to high-res 3.06 was the solution one Mac user came up with for his black screen issue. We'll see if this is the case all around.

And lastly, keep in mind that RP 2.3.1 is just around the corner. So keep that in mind as you are making your own releases. It doesn't affect sfall/high-res patch, so it should be easy to apply the changes on your end.

 

[Darek]

And apparently this also fixed empty Kaga encounters too! At least that is what I believe one user was telling me.

I doubt that to be honest. Kagas script does not govern if he is placed on the map, only if his friends are.
Also, I have tested all the Kaga 2 encounters, at least ten times on every possible map without getting a single empty encounter. That's a total of over 110 encounters (t was with with the pre-fix scripts). I mean, if it is that hard to get the empty encounters in the first place, how would one know if it has stopped?
Feels like I'm missing something, you'd think it would have happened at least once. I was alone and had a perception of 8 if that has any effect. I also only tested with Kaga level 2, maybe that one don't have any problems. Would be interesting to know what kaga encounters can go missing (maps, level etc.).

 

[killap]

And apparently this also fixed empty Kaga encounters too! At least that is what I believe one user was telling me.

I doubt that to be honest. Kagas script does not govern if he is placed on the map, only if his friends are.

True, which is why I was a bit skeptical, but perhaps his script crashes on map load and made he disappear, etc? Seems unlikely, but who knows.

The user said it was the second encounter on mountain5.

Now I might have misunderstood his comment. We'll see if he clarifies.

 

[BrecMadak]

Killap, the game gives no actual response when typing a char name after some random number of parameters; simply you can not edit unless you re-start the whole game, and additionally it may lag mouse movement and starts to beep weirdly. This always happens on each time in this patch. Just for that reason couldn not even start my gameplay after trying for about 15 min or so.

11 characters is the max. I don't see any problem on my end. What happens if you disable the high res patch? Run f2_res_Config.exe.

Disabled, no problem. So what would you suggest me to do now ? I have 23" monitor so dont expect me to play hi-res disabled with wrong colors.

 

[killap]

Disabled, no problem. So what would you suggest me to do now ? I have 23" monitor so dont expect me to play hi-res disabled with wrong colors.

How about trying v3.06 of the high-res patch from the previous page. Look at the bottom of the thread for a big link.

And damn, if v3.06 of the high-res patch is solving problems left and right I need to verify it doesn't break some things in the game if we keep suggesting it to people...

I fear RP 2.3.1 needs to be delayed until tomorrow Dec 31st. Still before the end of the year though!

 

[iLikeDirt]

@iLikeDirt, it might be worth reverting you changes to ddraw.ini and then downloading the high-res patch v3.06 and use that instead. I'm curious if that works for you.

No dice, sadly. And without the high-res patch, the colors are all messed up again and fiddling with the options in ddraw.ini doesn't seem to help.

 

[qbadger]

Is it a good idea to start a new game on 2.3 now or should I wait a little bit longer? I assume save files will be backwards compatible?

Disabled, no problem. So what would you suggest me to do now ? I have 23" monitor so dont expect me to play hi-res disabled with wrong colors.

How about trying v3.06 of the high-res patch from the previous page. Look at the bottom of the thread for a big link.

And damn, if v3.06 of the high-res patch is solving problems left and right I need to verify it doesn't break some things in the game if we keep suggesting it to people...

I fear RP 2.3.1 needs to be delayed until tomorrow Dec 31st. Still before the end of the year though!

 

[RolandDeschain79]

I edited my previous post with a link to old versions of the RP, so don't miss that.

Also, I do believe going back to high-res 3.06 was the solution one Mac user came up with for his black screen issue. We'll see if this is the case all around.

And lastly, keep in mind that RP 2.3.1 is just around the corner. So keep that in mind as you are making your own releases. It doesn't affect sfall/high-res patch, so it should be easy to apply the changes on your end.

Thank you very much for the link to the older RP versions. I might be up all night again eating Mentats and try to find a version that will work properly with QEMU. I keep getting this "wmArealnit: error loading Cities!" error when using that version.

Screenshot_2013-12-30-11-56-37.png

I should also note that i'm using the "Windows 95-98-ME" files when running it on Android. I just swap the files back and forth if I want to play it on PC. I'm looking forward to your next release, just one more day to wait for a new year and a new Restoration Project Build

 

[RolandDeschain79]

@iLikeDirt, it might be worth reverting you changes to ddraw.ini and then downloading the high-res patch v3.06 and use that instead. I'm curious if that works for you.

No dice, sadly. And without the high-res patch, the colors are all messed up again and fiddling with the options in ddraw.ini doesn't seem to help.

The high resolution patch will still work but do you have it set to 16/32 bit colors? 8Bit will always display rainbow colors on a modern os, I'm pretty sure the default is 8bit so you'll have to change it manually. Try using the fallout 2 res config that's in the fallout 2 folder. I experienced some issues with settings not sticking when I modified the ini files.

 

[Schezza]

That should work, but only in the RP. I don't think the unofficial patch does that anymore. It's strictly bug fixes. Is the raid still happening for you in the RP?

I'm on my way, but I don't wanted to spoil it by rushing there right away. If you say it works, then it works. If it doesn't, I'm gonna slam my savegame onto your head and tell you to save my dear deathclaws

I got next crashing mystery. It involves the scum son of Tandi. I always never talk to him, nothing good comes out of it.

Crash is triggered when:
1. save38 - If you stand too far away (you aren't in his aggro range)
2. save38 - If you do not attack him, crash occurs at his 2nd round.
3. however save37, apparently if you're drugged like shit crash doesn't occur in any case

Like always, have a fun figuring out that nonsense

Also for your next patch, there's random encounter with "scarred traveler".

 

[BrecMadak]

How about trying v3.06 of the high-res patch from the previous page. Look at the bottom of the thread for a big link.

And damn, if v3.06 of the high-res patch is solving problems left and right I need to verify it doesn't break some things in the game if we keep suggesting it to people...

I fear RP 2.3.1 needs to be delayed until tomorrow Dec 31st. Still before the end of the year though!

Just checked the earlier version and worked without problem. Though I'm short on time and couldn't yet try to run as administrator or giving a lower resolution from latest hi-res patch though.
So what has changed in latest hi-res patch that would cause this weird problem bear dude ?
Thanks !

 

[NovaRain]

I got next crashing mystery. It involves the scum son of Tandi. I always never talk to him, nothing good comes out of it.
Crash is triggered when:
1. save38 - If you stand too far away (you aren't in his aggro range)
2. save38 - If you do not attack him, crash occurs at his 2nd round.
3. however save37, apparently if you're drugged like shit crash doesn't occur in any case
Like always, have a fun figuring out that nonsense
Also for your next patch, there's random encounter with "scarred traveler".

With your save38, I can run far away from him (to Ranger's base) without any problem. As for the 2nd round crash for Hoss, looks like the cause is his check for your active slot. (if you take out a gun he'll back off, but the check seems not reliable enough)
If you put the ranger pin back to your inventory, you can stand there for many rounds. Your save37 drugged up character didn't help if you put any non-weapon items on your hand (like super stimpak) it will still crash at his 2nd round.

EDIT: Ok, it's not the check is unreliable. It's because for some reason it only checks your "right" slot. If you take out your .223 pistol in the left slot, he still acts like he doesn't know about it and keep beating you. Plus if you just swap your ranger pin and .223 pistol, and with ranger pin show up, the 2nd round crash won't happen.

 

[Schezza]

you got something against my pin?

I just took Lenny for the first time into my group and I have to report that, if your charisma drops to 1, he just leaves the group with a wall of text. After you recovered, he talks to you again, but no longer offers to join you. LOL this sucks cause I only have 2 charisma. LOL, I can't even take 1 mentats..

 

[NovaRain]

you got something against my pin?

Nah, it's just because it's already in your active slots. Swapping items just save me some muscle for moving other stuff from the inventory.
But seriously, his check is flawed because it doesn't check item types first and will try to get "weapon range" from protos even if it's not a weapon, thus the game crashed.

I just took Lenny for the first time into my group and I have to report that, if your charisma drops to 1, he just leaves the group with a wall of text. After you recovered, he talks to you again, but no longer offers to join you. LOL this sucks cause I only have 2 charisma. LOL, I can't even take 1 mentats..

Some NPCs will leave your permanently if some conditions are met. K-9 is another example for this. (Karma <= -101)

EDIT: I did a test for Lenny. Setting my character to CH 2 with only Lenny in my party, then take a mentats and rest for 24 hrs to get my CH dropped to 1. Lenny leaves with floating texts. I rest for a few more days to get my attributes back to normal (CH 2) and talk to him again. I can still ask him about my ancestor (Vault Dweller) to get him rejoin me with no problem. I guess you might miss the dialog option, it doesn't just show up like normal "Let's go" for rejoining.

 

[killap]

Alright, looks like we're cramming a bit more into this next hotfix release then.

@qbadger You might as well wait until RP 2.3.1 is out. Saves will be backwards compatible with RP 2.3 but might as well wait so you don't have to install multiple times.

 

[Schezza]

you got something against my pin?

Nah, it's just because it's already in your active slots. Swapping items just save me some muscle for moving other stuff from the inventory.

Ya, I love swapping too

and the star is kinda cool when you just got it, so, I'm keeping it for a bit. But this round, I failed to turn in moore since the very start, I always went ahead, drugged myself and tested her if I can turn him in. The only time I didn't have it in my inventory was when I delivered westins disk. But that's not it. Only thing left is, do I really have to deliver the case before I can turn him in? If so, it's not worth it to me, besides Bishop is a skeleton since long ago

Alright, I found out what's up with Lenny. Lenny is probably the only npc in the world that has a "hey bro, do u even have a spot for me open" check before he can offer you the line. Everyone else says "hey bro, you ain't got enuff space for me."

 

[Prosatanos]

@killap
In the link for old RP versions ,the path for v1.2 doesn't work.

 

[killap]

@killap
In the link for old RP versions ,the path for v1.2 doesn't work.

You all downloading my old files, eh? You hoarders... Permissions fixed.

@Schezza
That was a nasty vanilla crash with Hoss. I'm surprised it's been there for that long. Here's a file that should fix it: http://www.killap.net/fallout2/betas/schoss.int

@ everyone: Hopefully I'll be releasing today. It'll be a nice New Year present. Christmas and New Year gifts from the Bear Dude, what a year it's been!

It'll be a dozen new vanilla fixes and about a half dozen fixes/additions specific to the RP.

 

[phobos2077]

@killap,
Can you please make an incremental update for 2.3.1 (in addition to full version)? That would make it easier to adopt existing mods ^__^