Fallout 2 Restoration Project 2.1 (Unofficial FO2 Expansion)

[Dravean]

Alright, here's the plan for the new default settings for the RP:

XP users: res patch set to 16bit, sfall graphics set to 0. This is what I run at and I've never had a problem. Unless someone says otherwise, this is what XP users will have as default.
Vista/7 users: res patch set to 8bit, sfall graphics set to 4. This seems to work for people so I'm going with this.

Hopefully the RP will work better for people out of the box now. If people still have problems, they can always fiddle with the settings.

I just thought I'd chime in here and say I have Windows 7 Professional 64 bit, and I've been playing with graphics set to 0 without any problems (I used the same settings on my Vista machine, also without any issues). As long as its in 16 bit mode, it works great, but if I turn it to 8, then I get the funky rainbow colors.

 

[killap]

I just thought I'd chime in here and say I have Windows 7 Professional 64 bit, and I've been playing with graphics set to 0 without any problems (I used the same settings on my Vista machine, also without any issues). As long as its in 16 bit mode, it works great, but if I turn it to 8, then I get the funky rainbow colors.

What happens if you use sfall graphics mode 4 though?

 

[Adq]

I just thought I'd chime in here and say I have Windows 7 Professional 64 bit, and I've been playing with graphics set to 0 without any problems (I used the same settings on my Vista machine, also without any issues). As long as its in 16 bit mode, it works great, but if I turn it to 8, then I get the funky rainbow colors.

Do you have setup resolution manually or by options?

 

[Dravean]

What happens if you use sfall graphics mode 4 though?

Then the game looks like shit, but it works.

Do you have setup resolution manually or by options?

I do it through the in-game Hi-Res options. I play in 1024 by 768. I always have Direct X mode off. And, of course, I play in 16 bit.

 

[Adq]

What happens if you use sfall graphics mode 4 though?

Then the game looks like shit, but it works.

Do you have setup resolution manually or by options?

I do it through the in-game Hi-Res options. I play in 1024 by 768. I always have Direct X mode off. And, of course, I play in 16 bit.

Do you have nvidia graphic card? Because on mine (ATI) FO2 crashes when in mode 0 16bit I switch resolution...

 

[Dravean]

This is weird. When I go to alter the screen resolution in-game, none of the resolution options are displayed. It's just an empty black box where they should be. I'm not sure what the deal is, because it wasn't like that when I installed the game and set everything up initially. If I try to click on the black space, nothing happens, but if I press the up or down arrow, then the game crashes.

I have an ATI card. On all my previous computers I had an Nvidia card.

 

[Adq]

Same situation as mine.

Maybe you have set initially resolution in 8bit color and then changed to 16bit ?

 

[Dravean]

I just set it to 8-bit, then restarted. The resolutions still don't show up. I know they were there when I installed the game, so this is very confusing.

Hmm, just the other day I installed the newest ATI drivers. I don't suppose that would have anything to do with it?

 

[Adq]

I have 10.6 Catalyst drivers.

 

[Ravager69]

I'm curious about one thing - if I decompile and modify RP 2.1.1 scripts, will the FSE compiler handle them? Or do I need to use the special sfall compiler? I don't have the mod downloaded yet and I plan on doing some minor modifications to it.

 

[killap]

I'm curious about one thing - if I decompile and modify RP 2.1.1 scripts, will the FSE compiler handle them? Or do I need to use the special sfall compiler? I don't have the mod downloaded yet and I plan on doing some minor modifications to it.

Any script that doesn't use sfall functions can be decompiled just fine with FSE. I do plan on releasing all the source files for the RP, but that isn't high priority for me at the moment.

@Dravean
Bah, so changing the graphics setting in sfall to 4 as default can potentially be a problem for Win 7 users? Sigh.... Does having sfall be mode 4 and high res-patch be 16bit change anything or does it revert back to 8bit like what happened to Adq.

 

[Ravager69]

Any script that doesn't use sfall functions can be decompiled just fine with FSE. I do plan on releasing all the source files for the RP, but that isn't high priority for me at the moment

And AFAIR RP 2.1.1 does use sfall so I need a sfall compiler\decompiler to modify it's scripts and be able to compile them?

 

[Adq]

From what I've read Dravean has a problem with mode 0 not 4,
4 should work like a charm.

 

[Dravean]

Does having sfall be mode 4 and high res-patch be 16bit change anything or does it revert back to 8bit like what happened to Adq.

It reverts back to 8.

From what I've read Dravean has a problem with mode 0 not 4,
4 should work like a charm.

No, mode 4 looks utterly terrible. It suffers from awful pixelation, when I have it set to 0, it looks great, but I have the issue of not seeing the resolutions.

 

[killap]

Any script that doesn't use sfall functions can be decompiled just fine with FSE. I do plan on releasing all the source files for the RP, but that isn't high priority for me at the moment

And AFAIR RP 2.1.1 does use sfall so I need a sfall compiler\decompiler to modify it's scripts and be able to compile them?

You only need the sfall compiler/decompiler for scripts that use sfall functions. This is like maybe 5 scripts out of the hundreds in the RP. There is a very low chance you will be modifying these scripts, so FSE should be all you need.

@Dravean
Alright. I'm disappointed that we don't have a default setting that can work for everyone. Sadly, it doesn't look like an Nvidia/ATI difference, as Adq has ATI and mode 4 works for him, while you also have ATI but it doesn't work for you. I still might make the change as it fixes the problem for some people. Anyone else with issues will have to just play around and see what works.

 

[Dravean]

Just to follow up, when I use mode 4, the resolutions still are invisible, but I can click the arrow up and down to change the resolution without the game crashing. So no matter what I set it to, the resolutions are invisible.

 

[Darek]

Any mode works for me - Vista 32.

Mode 0 = sfall's pixel scaling is turned off. That should work for everyone shouldn't it? Though you may get the funky colors...
I mean that is exactly the same as playing the game without sfall isn't it? If that crashes then so should playing vanilla...
Adq is the first one I have ever seen that has a problem with it and I would consider that a problem on his end and not a wide spread problem. And he knows how to change the settings himself.

On the other hand, I know there has been a lot of people with problems in regards to mode 4, even before sfall required that extra dx9 dll. I neither want to nor have the time to search for those, so I don't know if they are still relevant. Also I can't remember if it was you killap who defaulted your install to mode 4 earlier or if it was MiB88.

 

[killap]

Also I can't remember if it was you killap who defaulted your install to mode 4 earlier or if it was MiB88.

Wasn't me, or at least I don't recall doing so. I don't see any reason why I would have either.

So, what do you suggest then? You've been following all the reports more than I have. What default settings do you think will work best?

 

[Dravean]

I just totally uninstalled Fallout 2 and the RP, then reinstalled them.

By default, mode is set to 0, which works, but I get the funky colors. So I go to the screen settings menu, and, like before, the resolutions in the box are invisible (the box is just black) and the game is automatically set to 8-bit. I used the arrows to switch to my desired resolution, then turned it to 16-bit to get rid of the funky colors.

Everything looks good. The only problem is that I cant' see the resolutions in the resolution box, but that's not a big deal, since it still displays the resolution at the bottom, so when I use the arrows, I can see what I'm altering it too. The other problem is that I cannot switch resolutions when I have it set to 16-bit. If I click the arrow up or down in 16-bit mode, then the game crashes. So I simply need to do all resolution adjustments in 8-bit, then switch back to 16-bit to get rid of the funky colors.

Not sure this post is needed, and none of this is really new information, but I thought it might be helpful to have my entire situation collected into one post. So, for completeness sake, I'm using Windows 7 Professional, 64-bit, with an ATI video card.

 

[Mash]

I have the hi-res patch setup to revert to 8bit colour if sfall's MODE is set to anything other than 0. This was to avoid compatibility issues as the two don't work well together.

For those experiencing crashes using the res list:
Try setting SAFER_DISPLAY_LIST=1 in the f2_res.ini. This will hopefully stop the crashes so that you can at least set the res manually. I think the problem has more to do with monitors than video cards.