It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
----------------------------------------------------------------
Msg: Runtime execption code c0000005 (EXCEPTION_ACCESS_VIOLATION) at address 0019F368
File: WINRUN.CPP line 190
Time: Fri Nov 20 20:35:13 2020
errno = 17 (File exists)
Attachments:
avatar
KainXVIII: ----------------------------------------------------------------
Msg: Runtime execption code c0000005 (EXCEPTION_ACCESS_VIOLATION) at address 0019F368
File: WINRUN.CPP line 190
Time: Fri Nov 20 20:35:13 2020
errno = 17 (File exists)
Hi, Alex from Ziggurat here. We have occasionally seen this error occur at launch on some system configurations for BloodRayne 2: Terminal Cut when the game transitions from the launcher into the game itself, especially on the first time running the game. We generally find that this error only occurs at or close to launch time, and relaunching the game (even with the same settings you chose on the last attempt) will cause it to boot properly on the next run. We have made Terminal Reality aware of the issue, but for now would advise continuing to relaunch if the bug persists. If you have a system where this bug occurs frequently, please run dxdiag on your computer, then 'save all information' from the button in the dialog, then send the text file created to support@zigguratinteractive.com so we may better investigate the issue as it may pertain to your system.
avatar
KainXVIII: ----------------------------------------------------------------
Msg: Runtime execption code c0000005 (EXCEPTION_ACCESS_VIOLATION) at address 0019F368
File: WINRUN.CPP line 190
Time: Fri Nov 20 20:35:13 2020
errno = 17 (File exists)
avatar
alxltz: Hi, Alex from Ziggurat here. We have occasionally seen this error occur at launch on some system configurations for BloodRayne 2: Terminal Cut when the game transitions from the launcher into the game itself, especially on the first time running the game. We generally find that this error only occurs at or close to launch time, and relaunching the game (even with the same settings you chose on the last attempt) will cause it to boot properly on the next run. We have made Terminal Reality aware of the issue, but for now would advise continuing to relaunch if the bug persists. If you have a system where this bug occurs frequently, please run dxdiag on your computer, then 'save all information' from the button in the dialog, then send the text file created to support@zigguratinteractive.com so we may better investigate the issue as it may pertain to your system.
I managed to replicated this crash - if i disable Dualshock 4 (with DS4Windows) - game launches, still kinda unstable, but i can play it (and i can enable Dualshock 4 after game launches so i can bypass this crash). i will also send dxdiag.txt to your support team

Btw, i have same kind of issue with BR1 - if i enable Dualshock 4 (with DS4Windows) game just don't run (no error window though).
But then again if i turn on Dualshock 4 AFTER game launches - its working fine.
Post edited November 20, 2020 by KainXVIII
avatar
alxltz: Hi, Alex from Ziggurat here. We have occasionally seen this error occur at launch on some system configurations for BloodRayne 2: Terminal Cut when the game transitions from the launcher into the game itself, especially on the first time running the game. We generally find that this error only occurs at or close to launch time, and relaunching the game (even with the same settings you chose on the last attempt) will cause it to boot properly on the next run. We have made Terminal Reality aware of the issue, but for now would advise continuing to relaunch if the bug persists. If you have a system where this bug occurs frequently, please run dxdiag on your computer, then 'save all information' from the button in the dialog, then send the text file created to support@zigguratinteractive.com so we may better investigate the issue as it may pertain to your system.
avatar
KainXVIII: I managed to replicated this crash - if i disable Dualshock 4 (with DS4Windows) - game launches, still kinda unstable, but i can play it (and i can enable Dualshock 4 after game launches so i can bypass this crash). i will also send dxdiag.txt to your support team

Btw, i have same kind of issue with BR1 - if i enable Dualshock 4 (with DS4Windows) game just don't run (no error window though).
But then again if i turn on Dualshock 4 AFTER game launches - its working fine.
I get the same error box for BR2 and no-dialog crash for BR1 and I have a PS4 controller plugged in (a fightstick).

And both crashes happen before any kind of settings dialog pops up. The original version of the two games run just fine.
Thanks all for the additional info and sharing your experience. We've forwarded the issues and info you've brought up here to the developers, as they'll be best equipped to make the determination on whether this might be related to the DirectInput controllers you've mentioned and/or the input wrappers. They're already testing out a fix for the first error in this thread, and I'm sure they'll take a good look at the info shared in these last two posts as well.
avatar
KainXVIII: I managed to replicated this crash - if i disable Dualshock 4 (with DS4Windows) - game launches, still kinda unstable, but i can play it (and i can enable Dualshock 4 after game launches so i can bypass this crash). i will also send dxdiag.txt to your support team

Btw, i have same kind of issue with BR1 - if i enable Dualshock 4 (with DS4Windows) game just don't run (no error window though).
But then again if i turn on Dualshock 4 AFTER game launches - its working fine.
avatar
WingedKagouti: I get the same error box for BR2 and no-dialog crash for BR1 and I have a PS4 controller plugged in (a fightstick).

And both crashes happen before any kind of settings dialog pops up. The original version of the two games run just fine.
I have the exact same thing happen here as well with both BR and BR2. Occurs on first launch of either so never get any settings written to the documents as well. just empty folders. Relaunching BR2 as suggested above just keeps giving the same error KainXVIII reported. Any word on these issues?
avatar
alxltz: Thanks all for the additional info and sharing your experience. We've forwarded the issues and info you've brought up here to the developers, as they'll be best equipped to make the determination on whether this might be related to the DirectInput controllers you've mentioned and/or the input wrappers. They're already testing out a fix for the first error in this thread, and I'm sure they'll take a good look at the info shared in these last two posts as well.
I had the same issue, though with a different controller. BR2 gave me that error, BR1 didn't launch at all.
Yes looks like you can't play GOG versions with any controller.