hellrazorman
First time out of the vault
Okay, I don't know if this is from my computer or the project, but I've noticed that I can't run when I'm wearing leather armor. Please help.
Fallout 2 Restoration Project 1.2 (Unofficial FO2 Expansion)
- Thread starter killap
- Start date
- Status
First time out of the vault
coliphorbs
Look, Ma! Two Heads!
Darek said:
It happens just after the movie ends.
It seems to run stable if I remove patch000.dat -- but I'm not sure that's a very healthy thing to do... Evenso, I'm not seeing any special description rock behind Klint when it does run.
I guess I'll try reinstalling completely. Are you sure I shouldn't patch to 1.02? The RP doesn't include the patch000.dat file.
Draconis said:
Have they been knocked out or lost a turn in combat? It's a known (if not understood) bug that looting unconscious NPCs will make them completely unresponsive, like what you're experiencing.
Suggestion: Make NPCs complain about being injured when they have crippled limbs.
Yeah i had that be4... i think some sequences will make em work again too.
PS: Just managed to get instant killed by an enclave guard! Never happened to me be4 Weird enough it was the "cut in two pieces by laser" animation. Only laser around would have been the technicans there and i somehow doubt they have better criticals... weird stuff
PS: Just managed to get instant killed by an enclave guard! Never happened to me be4 Weird enough it was the "cut in two pieces by laser" animation. Only laser around would have been the technicans there and i somehow doubt they have better criticals... weird stuff
Josan12 said:
Yes, it can be done. If dialog were written, I'd take on the scripting.
cluebatman
First time out of the vault
Jaesun said:
Hi!
I got it working by making the following changes to version 1.37 ddraw.ini
WorldMapSlots=21
OverrideArtCacheSize=1
CitiesLimitFix=1
DialogueFix=1
NPCAutoLevel=1
GainStatPerkFix=1
And if you like to have version info in the main menu;
VersionString=FALLOUT II 1.02.24 EXP 1.2
coffinshaker
First time out of the vault
Alright, posting in the right thread this time.
Did a brand new, clean install of Fallout 2 on my laptop and installed only the RP 1.2 mod on top of it with all the extra content. Started a new game, proceeded with the temple in Arroyo and finished it. Now, after the cinematic, I look at the Pip-Boy and several quests seem to already be finished(clearing out the mine in Redding, helping Widow Rooney, wiping out the slave camp for the Rangers, helping the orphans in the Den, 5 quests under EPA and 5 under Primitive Tribe and then some). I've uninstalled and reinstalled the game several times now, and it seems the quests finished seem to vary each time I start a new game.
I decided to keep on playing for a while but it seemed the game wouldn't let me. Every now and then when I switched scenery - entering towns, going down ladders, etc. - the game crashed with the error message that "The instruction at xxxxxxxx referenced memory at xxxxxxxx. The memory cannot be written." Anyone else who has experience with these kinds of
problems? I'm running a humongous install on Vista and installed the RP mod using the Windows installer from Killap's website.
Did a brand new, clean install of Fallout 2 on my laptop and installed only the RP 1.2 mod on top of it with all the extra content. Started a new game, proceeded with the temple in Arroyo and finished it. Now, after the cinematic, I look at the Pip-Boy and several quests seem to already be finished(clearing out the mine in Redding, helping Widow Rooney, wiping out the slave camp for the Rangers, helping the orphans in the Den, 5 quests under EPA and 5 under Primitive Tribe and then some). I've uninstalled and reinstalled the game several times now, and it seems the quests finished seem to vary each time I start a new game.
I decided to keep on playing for a while but it seemed the game wouldn't let me. Every now and then when I switched scenery - entering towns, going down ladders, etc. - the game crashed with the error message that "The instruction at xxxxxxxx referenced memory at xxxxxxxx. The memory cannot be written." Anyone else who has experience with these kinds of
problems? I'm running a humongous install on Vista and installed the RP mod using the Windows installer from Killap's website.
coffinshaker
First time out of the vault
I did reinstall the game from scratch without installing RP or any patches, offical or unofficial, and the game ran smooth and without troubles. However, when I tried installing the most recent version unofficial patch from Killap the quest issues appeared once again. So at least part of the problem seems to stem from the unofficial patch while the crashing seem to be locked down to the RP mod.
coffinshaker
First time out of the vault
Nope, couldn't find any signs of a patch000.dat file and the readme says version 1.0, so that's what I'm running, I guess.
Man, this thing is driving me nuts. You install the whole thing to get something new out of a great, old game only to find out that the new parts have already been done for you, and to top it all off the game crashes whenever it feels like it. Guess it's a good thing it's not that bad on it's own, but I really wanted to try out RP(or at least anything that's not plain old vanilla F2...)
Man, this thing is driving me nuts. You install the whole thing to get something new out of a great, old game only to find out that the new parts have already been done for you, and to top it all off the game crashes whenever it feels like it. Guess it's a good thing it's not that bad on it's own, but I really wanted to try out RP(or at least anything that's not plain old vanilla F2...)
- Status