Fallout 2 Restoration Project 2.2 - OPEN BETA (ie NOT FINAL)

[Matthews]

Patience is a virtue. There is a swedish saying that goes something like: "the ones who awaits something good, never wait too long".

Sounds silly like this, but in most cases I hold them to be true.

 

[Nibiru]

tout vient à point à qui sait attendre

 

[inpatient]

"Den som väntar på något gott väntar alltid för länge".

No need to tell me, I've waited since Fallout 1. That's right, I never played Fallout 2 so I'm going in for the first time, but not before the bear dude says so!

 

[Maxrunner]

I'm currently playing the fallout 2 RP 2.2b but im considering stopping for waiting for the final version. i wonder if the save games will work.

 

[Matthews]

Savegames will most likely not work if there has been bugfixes done after betatest is over.

 

[Muznick]

Where can I find info on the system requirements to play the game with the restoration project? I'm thinking about buying an old PC to play this (currently on mac )

 

[killap]

Where can I find info on the system requirements to play the game with the restoration project? I'm thinking about buying an old PC to play this (currently on mac )

I'm pretty certain ANY pc you buy today will be better than what was available in 1998. And even a $300 used pc.

But if you're curious, the recommended settings for the time were 120MHz and 32MB of ram. However, with sfall and wanting to play the game at > 640x480 I'd say 1Ghz. But really, I'd be baffled if you can buy a machine today with specs that can't handle this game.

Savegames will most likely not work if there has been bugfixes done after betatest is over.

Save games will work just fine but any map fixes/content changes to locations you've already been to will not work.

@everyone
I'd say this weekend (Feb 2/3) will be the end of the beta and the official release of 2.2. Some other good things things I'm squeezing into this release. All for the better, of course. For example, despite my docs saying that the automated repair system at the Sierra Army Depot was finally working, this was actually not the case. It will work in 2.2 and it's pretty awesome.

 

[AelpirT]

I'm pretty sure I originally played Fallout 2 on a 66MHz 486DX2 with 20MiBs of RAM (yeah, my PC was awesome like that )...

So, yeah, what killap said. I would even go so far as to say that anything you could possibly have bought in the last 10 years should be OK.

Without going to higher resolutions and stuff, of course!

 

[coldroll]

Even an eleven year old PC should be able to run it well.

 

[Matthews]

Savegames will most likely not work if there has been bugfixes done after betatest is over.

Save games will work just fine but any map fixes/content changes to locations you've already been to will not work.

@everyone
I'd say this weekend (Feb 2/3) will be the end of the beta and the official release of 2.2. Some other good things things I'm squeezing into this release. All for the better, of course. For example, despite my docs saying that the automated repair system at the Sierra Army Depot was finally working, this was actually not the case. It will work in 2.2 and it's pretty awesome.

Thanks for the heads up, and sweet! Can't wait to hear Cassidy's voice.

 

[pipboy-x11]

Where can I find info on the system requirements to play the game with the restoration project? I'm thinking about buying an old PC to play this (currently on mac )

Doesn't Mac OSX have Wine?

Anyway you can just install VirtualBox+Windows XP and play FO there. Even with the emulation layer the power of today's machines is by an order of magnitudes more than what FO1-2 need.

Check this thread, it contains some pointers.

 

[jirik]

However, with sfall and wanting to play the game at > 640x480 I'd say 1Ghz. But really, I'd be baffled if you can buy a machine today with specs that can't handle this game.

These requirements are sadly valid only for native running of fallout on windows platform, for linux/unix/mac via wine it's much more than that. I'm playing fallout on linux at my old notebook (1.8 Ghz, 2GB ram) and with hi-res patch it's almost unplayable.

 

[pipboy-x11]

These requirements are sadly valid only for native running of fallout on windows platform, for linux/unix/mac via wine it's much more than that. I'm playing fallout on linux at my old notebook (1.8 Ghz, 2GB ram) and with hi-res patch it's almost unplayable.

Something is clearly wrong with the HR patch then, since I remember playing Civilization 5 on Linux/Wine, full resolution (2560x1440) and it was almost as smooth as on Windows. Usually games on Wine run just a couple of percent slower compared to Windows. I bet on some GPU memory/RAM transfers, some, usually unused, DirectX calls or something like that. Doesn't the HR patch has a DirectX version switch?

 

[Animator]

Found one more strange thing.

I've installed appearance mod (from the RP installer of course).
If any NPC got killed (i've tested Sulik and Vic) and you leave the map - where will be no dead body then you came back.
And even more: if you save and load game, where will be the same problem.

SAVEGAME http://speedy.sh/g4JEE/NPCBug.rar
(it's a bit cheating just to speed up things, but the problem exists in a normal game too)
In this savegame kill Sulik first. If you leave the map to just return - where will be no his dead body.

Something tells me that you've already knew about this issue, but there is nothing to do with it

Dex's base AP in final stage (00000517.pro) is 9, and base AC is 10. But all his previous stages have only 8 AP & 9 AC. So I think he'll get a similar problem like Cat Jules as in Animator's post.

Yes, I agree that Dex suffers with a same problem as Cat Jules. Though his final AP is 9.
Kitsun is ok.

 

[CommonOddity]

However, with sfall and wanting to play the game at > 640x480 I'd say 1Ghz. But really, I'd be baffled if you can buy a machine today with specs that can't handle this game.

These requirements are sadly valid only for native running of fallout on windows platform, for linux/unix/mac via wine it's much more than that. I'm playing fallout on linux at my old notebook (1.8 Ghz, 2GB ram) and with hi-res patch it's almost unplayable.

Actually, not quite sure what you're talking about. On Linux, at least, I've found with 2D games all you need is decent drivers (unfortunately in this case, binary blobs or solid open source drivers for much older/lower-end video cards) and you actually require less with wine than you did in Windows.

I am a maintainer for some wine projects and have done benchmarks before, so I would argue your claim.

 

[jirik]

Actually, not quite sure what you're talking about. On Linux, at least, I've found with 2D games all you need is decent drivers (unfortunately in this case, binary blobs or solid open source drivers for much older/lower-end video cards) and you actually require less with wine than you did in Windows.

I am a maintainer for some wine projects and have done benchmarks before, so I would argue your claim.

Quite a lot of windows games are running in wine with good performance, few even better like on windows, but fallout isn't that case. Even vanilla fallout have poor performance with wine and with high-res patch and some higher resolution is it really bad.
IRC fallout was running quite pleasantly with prehistoric wine 0.95, but then they reworked DRI engine and some these old games are running nowadays with worse performance than before.
Especially fallout is consuming always 97-100% of my CPU, but I assume that that's not problem of wine but poor fallout engine.
IMHO nowadays linux 2D Xorg drivers are in usable state and doesn't matter if user has intel/nvidia/ati graphics.

Nevertheless running fallout with wine is about patience at least for me.

 

[SCO]

Especially fallout is consuming always 97-100% of my CPU, but I assume that that's not problem of wine but poor fallout engine.
IMHO nowadays linux 2D Xorg drivers are in usable state and doesn't matter if user has intel/nvidia/ati graphics.

If you care about that (crashes by overheating?) there is always 'sudo apt-get install cpulimit' and then 'sudo cpulimit -P usr/bin/wineserver -l 40'
^ means that wineserver can only get up to 40% of processor time.

 

[CommonOddity]

Actually, not quite sure what you're talking about. On Linux, at least, I've found with 2D games all you need is decent drivers (unfortunately in this case, binary blobs or solid open source drivers for much older/lower-end video cards) and you actually require less with wine than you did in Windows.

I am a maintainer for some wine projects and have done benchmarks before, so I would argue your claim.

Quite a lot of windows games are running in wine with good performance, few even better like on windows, but fallout isn't that case. Even vanilla fallout have poor performance with wine and with high-res patch and some higher resolution is it really bad.
IRC fallout was running quite pleasantly with prehistoric wine 0.95, but then they reworked DRI engine and some these old games are running nowadays with worse performance than before.
Especially fallout is consuming always 97-100% of my CPU, but I assume that that's not problem of wine but poor fallout engine.
IMHO nowadays linux 2D Xorg drivers are in usable state and doesn't matter if user has intel/nvidia/ati graphics.

Nevertheless running fallout with wine is about patience at least for me.

I do admit, the DRI re-work definitely threw in a monkey wrench (well, ultimately it became essential). Fascinating that Fallout is so affected by it. Last I ran Fallout, it was perfectly smooth and my cpu barely touched (this is on an AMD x2 240, GTX 460 6GBs ram).

It's interesting to hear this sort of performance gap. I wonder what could be causing it. I'll fiddle around with it and post a bug on appdb should I find something of interest. I know it's no longer really looked at but it might be something simple.

Sorry Killap for hijacking this post with all this out-of-band chatter

 

[DaManKaga]

Dunton bros spawn spike knuckles each time enter combat

I believe this is a vanilla bug. while in Klamath Town (not the grazing area)

after I rustled the Brahmins,

I went to Duntons' house.

Previously I already stolen their spike knuckles in the grazing area.

When I enter/exit combat mode,

Afterwards, I would find new spike knuckles spawned in Duntons' inventory.

I enter/exit combat mode 2 times and stolen 4 spike knuckles from Duntons.

What I did to install the beta:

I had previously installed RP 2.1.2b over vanilla fallout2 install,

so I ran RP 2.1.2b uninstaller to uninstall RP

and then ran beta installer.

And the entrance to the temple I checked the rock to make sure that
it was the beta install.

Side Question: It's that an acceptable approach? or do I need to start from scratch. meaning not only uninstall RP but also uninstall Fallout 2 and THEN install vanilla fallout 2 again before beta install?

 

[jirik]

If you care about that (crashes by overheating?) there is always 'sudo apt-get install cpulimit' and then 'sudo cpulimit -P usr/bin/wineserver -l 40'
^ means that wineserver can only get up to 40% of processor time.

Nope, I don't have problem with overheating. I was trying to find best setup for quite lot of time and even renicing wineserver/fallout.exe priorities doesn't help. But I try cpulimit in my next fallout playthrough, thanks. Maybe if you have positive experience with it, you can add it to RP wiki?

I do admit, the DRI re-work definitely threw in a monkey wrench (well, ultimately it became essential). Fascinating that Fallout is so affected by it. Last I ran Fallout, it was perfectly smooth and my cpu barely touched (this is on an AMD x2 240, GTX 460 6GBs ram).

As I wrote in my first post on that topic, the linux requirements clearly don't match the windows ones, that's all. You have PC powerful enough to run fallout smoothly even through it's performance issues. But as you said, this wine related topic should be probably discussed elsewhere.