Are you *still* here?

I can't believe you guys debated this for another page and a half.

Gotta make a few points --

1) Fallout 1 and Fallout 2 used the same engine. A bug in one game appearing in another is noteworthy, as one of you did point out -- players of both games have an interest in resolving the bug

2) Despite saying I contributed "NOTHING" to the thread, in fact I posted a detailed workaround for the problem in FO2. Apparently the only part of posts some of you guys read is the date/time signature

3) Necroing is bringing back a concluded post. This one is clearly marked at the very top with the following words: "No posts in this topic were marked as the solution yet. If you can help, add your reply."

4) For games that came out 15+ years ago, it shouldn't be a surprise many posts, bug discussions, support questions, etc. are "old." Honestly, GOG forums is the only place I've run across where anyone makes a stink about such a thing.

5) No one cares what some permarage user thinks are the "rules" for posting on the Internet. If an actual Admin here says I messed up I'll accept that.

Happy holidays, everyone :-D

I couldn't help myself from "necroing" this post after I saw how the people above reacted to the 2nd OP. I hope you all see this and get annoyed again.

On to the topic, on FO2 + Killap restoration, this issue is still present and UNSOLVED. I thought I have been managing it with doing things slightly differently every time I encounter it. But it finally caught up with me and now I have a "corrupted save". This is my probably around 10th play through of the game and first time losing significant amount of progress, I am not sure if it will happen again in this run so kinda considering ending this run here.

I tried the solution suggestions in this thread and some suggestions from steam forums: support.steampowered.com/kb_article.php?ref=1274-uohk-5653
steamcommunity.com/app/38410/discussions/0/154644349169323027/

There is no permanent fix to this, just some suggestions to try to avoid it. Any new suggestions are welcome, this game is not played much so I doubt this will ever be solved completely but I am willing to try anything new.

Oddly enough I'm getting this error in Fallout 2 but before actually getting the game running. My instance of it seems to be tied to graphical troubles.

Specifically I'm getting "Instruction at 00366fd1 referenced memory at 00000000", although I doubt the specific memory address matters.

Interestingly Fallout 2 isn't available for macOS on GOG at the time of writing. It's still available for me to download for macOS though (presumably I'm grandfathered in). The initial download runs although it's the unmodified, low resolution 1.02 version. It's packaged using Wineskin.

Install the Fallout 2 Restoration Project appears to break it. I've removed the registry entries that enforce compatibility mode to get past the "Fallout appears to be running in compatibility mode" issue and then used the resolution selection program from the bundled hi res patch to set an appropriate resolution. Launching after that gives the error.

I suspect this is an issue with the updated Wine bundle as I've had the game running happily before. However, there is also good news. I've managed to get the sneaky blighter to behave.

First off this involved going into the application (right-clicking to do "Show Package Contents") and opening up the contained Wineskin executable. From there I pressed the middle button on the bottom row, "Set Screen Options" and told it to run at my full resolution, in a 24 bit colour depth, full screen, with the Direct3D boost. I'm not sure how many of those are needed but you can always experiment.

Closing that particular menu I used another tool from the Wineskin executable - Task Manager. Browsing into the Fallout 2 directory I was able to run the high resolution patch (it'll let you launch any Windows executable really) and tinker with the settings there.

After a bit of testing it would also seem there's issues in the ddraw.ini file. At least for me if GPUBlt is set to 0 or 1 then the game will not launch. Setting it to 2 so that the CPU is used for palette conversion worked. I didn't notice any difference when it came to the Mode= parameter. Both 0 and 4 worked.

It seems like issues with graphics and Wine can cause this error in addition to other things. Yay!

Edit: It also seems that by downgrading the engine used by Wineskin to 1.7.x performance was much improved, although that did involve me creating a new instance of Wineskin and dumping the GOG files into it.

(Also reading a load of you moaning about forum etiquette was a real blast from the past. There's a time and a place for it and neither of those are in a thread dealing with complex errors in 20+ year old games. People are going to be playing these games for many years to come, they're classics. Having threads covering potential errors and solutions for them is super useful. I'm pretty much providing the info I am here so that future me can get some help from past me.)

@Flamekebab

You, my friend, are a goddamn saint. The GPUBlt thing worked out perfectly for me, and this is the only time I've seen this as a solution to this quite common problem. Thanks a lot.

Here I am in 2020, trying to solve this same issue. Hi, hi, hi.

I'm currently using Fallout Et Tu, which I think doesn't even use directdraw by default. I realize my use of what is essentially an engine port sort of invalidates any of my issues, compared to those experienced by the OP, but I still felt the need to express my appreciation for those who try to bring forward answers to still-unresolved problems. Look, because this thread got "necro'd" (such nonsense), at least one guy got the solution to his problem. Maybe this serve as a lesson to someone in the future...
...perhaps even in the *YYeeeEEARR Twwwwothousand FORRRTY...."

Did anyone ask if they backed up the save folders before messing with character stats?

Sometimes doing this causes all saved games to get corrupted, so you can no longer use them. This does, at least for me, result in fatal program errors and CTD. If I remember correctly, sometimes fixing this involves MORE than just deleting all the save files - I just restore the entire installation from a backup if it happens.

You seem like an incredibly insufferable person.
bump