Game crashed twice at the most crucial moment!

1. In the final boss in the scene where they lift up to space
2. After I beat the final boss in space another crash occured during the ending cut scenes in the discussion between the vampire and the fairy. I am not going through this ordeal again. Will watch a Youtube video

There were some other crashes during warp scenes but I had a save game at least.

I am playing at 3440x1440 resolution so maybe it is one of the culprits

If anyone else is having the CTD issue with G-colosseum I found that switching to minimum graphics settings eliminated the issue. Just switch back when not in the colosseum.

I'm getting a rather strange bug where my attempts to load from saves doesn't register the newest saves, but the same four save files from back in my first three hours of play. My most current saves remain untouched in the "Saved Games" folder, and I don't even have a clue where these saves are being stored. It's quite odd.

Hi. I only see this post now.

I have crash in many moments.

The version here is "20180120".
I play with an X-Box One Controller wireless.
Windows 10 - 1809.
GeForce GTX 1080 - Driver 425.31
Resolution 1080
Using GOG Galaxy 1.2.55 Beta
My Internet go down many moments.

1. What is meant by "completing a dungeon"? For me was when I complete one level of the dungeon.

2. Which is it? Or, is it both? For me I have a crash in many situations:
--> The first time when I enter in G-Colosseum. I get the pink ticket, show to the Penguin and enter. After that have a animation, the G-Man talk and when I have the control again I enter in G-Colosseum and CRASH. I did it again, but before enter the G-Colosseum I exit and save. I go back on foot and don't crash.

--> When I teleport after ended a level of a dungeon. I save the game and them use the teleport to the G-Colosseum and CRASH.

--> One time was when I was in ARTE city and teleport to the G-Colosseum. Before I save the game.

--> One time I don't remember to where I was going. I save, use the teleport and CRASH.

--> One time, when I was in G-Colosseum. I enter to pick a fight and have the same bug that the Xelviar in Post 15. This time I chose the fighter level 7 and chose my PC from left (because don't show either). After I lose the fight (I was in level 4 or 5) the game CRASH.
----------------------------------------------------------------------------

I have a bug too with the medals from Galaxy.
When I get the first Combined Power, I gain the emblem "With Our Powers Combined!".
This emblem says that I have all the Arcanum combo skills, but I have only one.
I pick all latter in the game.

Hello. I just started playing the game, and everything was working just fine, until I got to the opening fmv, the one with vocals. It runs EXTREMELY slowly [the song even ends before the opening, leaving a video running at low fps without sound], when the game (and even the pre-rendered FMVs of the flight battle!) was running perfectly. Any fix for this?

Thanks.


UPDATE:

I found a solution! If you have installed the K-Lite Mega Codec pack, go to start->k-like->configuration->LAV video.

With the LAV Video config open, go to the FORMATS tab and uncheck anything that has to do with MPEG-4 (the codec that the videos of the game are set).

After doing that the opening played fine. I'll start the game from scratch to see if this screws up the earlier FMVs, but so far I got to fix my issue :D

Just bought the game but it crashes almost immediately on start, doesn't get past the Famicom screen and just boots me back to desktop, I've played around with the settings and graphics but I've gottne no farther with it. Anyone know of a fix or possible reason for it crashing like this? I'm on Windows 10 if thats of any help

Same problem here but I was able to work around it. Try launching the game directly from the folder instead of through Galaxy. Go to More -> Manage Installation -> Show folder and and Explorer window will pop up. Double-click the "Launch Zwei - The Ilvard Insurrection" shortcut. The game came right up for me when I did that. You can copy the shortcut to your desktop and run it from there.

It's weird though, I bought this game in 2018 and was able to boot it from the gog client, didn't play it for a year tried to paly it in 2020 and suddenly this problem appered. Am running windows 10 as well, was running the same os and computer when I bought it, no hardware changes in between either. Tried to repair the game, even did a clean install of it, but still have the same problem.

I also started getting the problems with the game no longer launching through Galaxy because it would crash before the title screen.

After I talked to GOG support about it a lot and they initially gave me many suggestions that didn't do anything (i.e. uninstalling & re-installing the game did nothing), GOG eventually told me to try disabling the Galaxy overlay.

So I did that, and that made the game work again and stop crashing before the title screen.

To disable the Overlay, in the Galaxy software you go to Settings > Features > Uncheck the Overlay box.

At least that's how it works in the pre-2.0 version, although this crashing bug also happens in the 2.0 version. I tried switching to 2.0 as a possible fix, but changing to 2.0 didn't have any effect on the problem, and the interface was much worse than the older version I used to use, so I switched back to the older version.

The thing is, if you disable the Overlay, it will also cause other problems for all your Galaxy games, such as that Achievements will no longer pop-up in-game at the time when you earn them (but they will still be recorded on your Galaxy profile, I think).

So you might want to manually turn the Overlay on and off again every time you start and exit the Zwei II program, so that disabling the Overlay just for Zwei II doesn't interfere with your other games, as it will do if you keep it disabled permanently.

The problem with that solution is: a) you lose Cloud Saves functionality and b) you also lose Achievements functionality and c) you also lose game time tracking functionality.

I confirm this, the game still only launches past the Falcom Screen if Overlay is disabled in gog galaxy settings.

Just tried to fire this up for the first time in a while (around 2 years, and on my previous PC) and experienced the same crashing issue mentioned above :(. Last time I ran it, I went through Galaxy as well so as speculated above it seems like GOG changed something with the Galaxy client that breaks this game at some point between ~2 years ago and now, and before the release of Galaxy 2.0. I don't see a changelog for this game here on the forum so I suppose it's possible that the game might have been updated since I last played, though the latest version suggests January 2018 and I'm fairly sure I played it after that...

Before checking this thread I did a little experimenting and I think I have a better workaround than universally disabling the Galaxy overlay. From what I'm seeing, something about the overlay AND the transition from the configuration program to the actual game seems to be what's really causing the crash. I went into the game settings and changed the default executable when clicking the play button (click the button to the right of the play button and select "configure" under "manage installation" then add a new executable and make ti the default) from config.exe to ZWEI2PDX9.exe (or ZWEI2P.exe, doesn't appear to be any difference between them offhand). I haven't done a lot of testing, but at first glance with this configuration it doesn't crash, and Galaxy appears to be tracking game time and syncing cloud saves like normal. The overlay doesn't appear to work, oddly enough; no idea what that's about. I also haven't met any achievement criteria since setting this up so I can't guarantee that they'll work, though they were a little buggy before if memory serves correct.

It seems like a decent enough workaround, so hopefully this will prove helpful.