Page 3 of 3
Re: [Resolved] -Unable to continue GK The Beast Within chap
Posted: Thu Sep 14, 2017 10:50 pm
by Tawmis
Re: [Resolved] -Unable to continue GK The Beast Within chap
Posted: Thu Sep 14, 2017 11:04 pm
by Tawmis
Hold on... it has to be something with the way Steam and GOG have their installers?
Because with Windows XP Mode still turned off, and going the "long way" through DOSBox and not using GOG's launcher for GK2, it worked.
- 11.png (10.51 KiB) Viewed 7871 times
So... QBIX... do me a favor, since you have the GOG version of the game (based on your install location) - try using the
GOG version of the GK2 launcher like I did in the previous post. Because even when I had set the DOSBox that GK2 uses (in the G:\USB\SIERRA\GABRIEL KNIGHT 2 - THE BEAST WIN\DOSBox) to use Windows XP compat, it didn't work with the GOG GK2 launcher(when I was testing). It was only when I launched DOSBox first, independent of launching any GK2 stuff from their launcher, that it worked with Windows XP mode (I hadn't tried the normal mode, because I had assumed since it tanked with the GK2 DOSBox launcher, it must be something with the installer...) See if that works. I wonder if something in their config file is wonky (which was my thought, even when I had set Windows XP Compat mode and it worked).
Re: [Resolved] -Unable to continue GK The Beast Within chap
Posted: Fri Sep 15, 2017 10:51 am
by Collector
GOG has been known to use... less than optimal confs. They have even used confs from older versions of DOSBox.
Re: [Resolved] -Unable to continue GK The Beast Within chap
Posted: Fri Sep 15, 2017 1:50 pm
by Tawmis
Collector wrote:GOG has been known to use... less than optimal confs. They have even used confs from older versions of DOSBox.
If I uploaded the conf file - would you be able to tell? Not that it matters. But just for interest!
Re: [Resolved] -Unable to continue GK The Beast Within chap
Posted: Fri Sep 15, 2017 4:59 pm
by Qbix
Judging from your description. I think I loaded a different savefile than you. Which savefiles do I need to grab and open ?
Re: [Resolved] -Unable to continue GK The Beast Within chap
Posted: Fri Sep 15, 2017 5:48 pm
by Tawmis
Qbix wrote:Judging from your description. I think I loaded a different savefile than you. Which savefiles do I need to grab and open ?
It's the top save file... Um... Rittsberg or something (I am at work). But it's the save game file at the top of the list.
Re: [Resolved] -Unable to continue GK The Beast Within chap
Posted: Fri Sep 15, 2017 5:52 pm
by Tawmis
Tawmis wrote:Qbix wrote:Judging from your description. I think I loaded a different savefile than you. Which savefiles do I need to grab and open ?
It's the top save file... Um... Rittsberg or something (I am at work). But it's the save game file at the top of the list.
Oh! I had a screen capture in the thread! The one that's highlighted.
Re: [Resolved] -Unable to continue GK The Beast Within chap
Posted: Sat Sep 16, 2017 11:52 am
by Awesomeg
Ok. Finished the game .Thanks to everyone that helped
Re: [Resolved] -Unable to continue GK The Beast Within chap
Posted: Sat Sep 16, 2017 2:05 pm
by Tawmis
Awesomeg wrote:Ok. Finished the game .Thanks to everyone that helped
Hah! Awesome! Glad to hear it.
Re: [Resolved] -Unable to continue GK The Beast Within chap
Posted: Wed Sep 20, 2017 4:10 pm
by Qbix
I found the problem.
GOG (and I assume steam as well)
has set the memsize to 8 and that causes the the crash at that point.
With the default of 16, it works fine.
@collector, what value do you set the memsize to for this game ? Might be worth checking.
I didn't check what is actually different happening inside of DOSBox, but it can be that it just runs out of memory trying to play the movie
Re: [Resolved] -Unable to continue GK The Beast Within chap
Posted: Wed Sep 20, 2017 5:42 pm
by Collector
The DOSBox default. My confs are short and sweet,
[sdl]
output= overlay
fullresolution= 0x0
windowresolution= 800x600
fullscreen= false
autolock= false
[DOSBox]
machine= svga_s3
captures= .
[render]
scaler= normal3x
[cpu]
core= normal
cycles= 10000
[autoexec]
cls
@ECHO OFF
mount c .
c:
cd \
SIERRA.EXE RESOURCE.CFG
exit
Outside of the [sdl], [cpu], and [autoexec] sections most of the rest are just from the options from my config tool for the personal tastes of the user. So in other words DOSBox defaults for the bulk of the settings.
Re: [Resolved] -Unable to continue GK The Beast Within chap
Posted: Wed Sep 20, 2017 7:44 pm
by Tawmis
Qbix wrote:I found the problem.
GOG (and I assume steam as well)
has set the memsize to 8 and that causes the the crash at that point.
With the default of 16, it works fine.
I didn't check what is actually different happening inside of DOSBox, but it can be that it just runs out of memory trying to play the movie
Cool stuff.
Something about that particular movie too - because the other ones work fine (like when you leave that area, rather than clicking on the door, it cuts to a movie of Grace walking away). And it's odd that it works in Windows XP with their config files, but other OS' seem to have the issue.
Re: [Resolved] -Unable to continue GK The Beast Within chap
Posted: Thu Sep 21, 2017 10:51 am
by Qbix
Glad to see that your minimal version doesn't have a memsize set
And it's odd that it works in Windows XP with their config files, but other OS' seem to have the issue.
I agree, as DOSBox wise it shouldn't matter. I haven't set XP compatibility to test it out though, so will do that at a later point and see if I can find a reason for it.
Re: [Resolved] -Unable to continue GK The Beast Within chap
Posted: Thu Sep 21, 2017 1:12 pm
by Collector
Qbix wrote:Glad to see that your minimal version doesn't have a memsize set
I see no need to change anything from defaults unless there is an actual need or preference.
Re: [Resolved] -Unable to continue GK The Beast Within chap
Posted: Thu Sep 21, 2017 2:22 pm
by Tawmis
Qbix wrote:
And it's odd that it works in Windows XP with their config files, but other OS' seem to have the issue.
I agree, as DOSBox wise it shouldn't matter. I haven't set XP compatibility to test it out though, so will do that at a later point and see if I can find a reason for it.
It has to be something with maybe how Windows XP handles memory or something?