DOSbox: Chasm: The Rift

[Mako Eyes]

Once again I turn to the Emuforums for my DOSbox woes. The last time I was having trouble with One Unit Whole Blood (which I got working successfully, thanks to the efforts of Jonc and others. I don't know if I mentioned this in the aforementioned thread).

Anyway, I picked Chasm: The Rift up years ago and, of course, it worked fine on my Win98 machine. For whatever reason I whipped it out and dusted it off and decided to play it again, with the intention of actually beating it this time.

Well, I've run into a problem. The game runs and works fine; full speed, sound works. It's looking great. However, there's one thing that makes the game literally unplayable: The player keeps looking to the bottom-right.

Now, this issue is a bit strange. It's a problem with mouse input, but the mouse isn't inputting anything. Disabling mouse-look causes the player to walk perpetually backwards and turning to the right, as opposed to looking down and right. So it would make sense that it's a mouse problem. However, unplugging the mouse (and even all other USB devices) still does it. So, basically, either the game is "generating" its own mouse input, or the mouse neutral position is set at some place beyond the bottom-most and right-most boundaries. Blood didn't do this, so this could be a problem with the game itself rather than DOSbox and the more I think on it the more I recall having the problem on my Win98 machine, but I can't remember for the life of me how I fixed that.

I know this is a very long-shot of a question; the game was never that popular. However, someone here has probably played it and, if so, may know what's going on. Can anyone offer some advice?

Any help is appreciated. Thanks in advance.

[jonc2006]

i think i had a similar problem with another dos game, and what i did was i created a custom profile for it using this frontend and under the input section, there was an option that you could enable/disabled called "mouse lock" or something like that which locked the mouse to the current window when clicked and it seemed to fix it for me.

[Mako Eyes]

Originally Posted by jonc2006

i think i had a similar problem with another dos game, and what i did was i created a custom profile for it using this frontend and under the input section, there was an option that you could enable/disabled called "mouse lock" or something like that which locked the mouse to the current window when clicked and it seemed to fix it for me.

I tried enabling/disabling mouselock in DOSbox's configuration file and then I tried enabling/disable both mouselock options in DOG. Neither of these worked.

This is odd.

[jonc2006]

ok well ive seen similar problems in numerous dos games ive played before, system shock 1 is the main one i remember having something like what you are describing. a while back someone actually made a port of SS1 that includes support for a program called "mouse2k" or something of the sorts that corrects the issue. what im going to do is in a while i will look around and see if i can find out if that same program can be used with applications other than the SS1 port because i believe it was just added in to the final version of it, it wasnt exclusive or anything it was originally a stand alone program so it might be able to work with dosbox or vdmsound with a certain install method.

[Squall-Leonhart]

probably a bug in that dosbox automatically assumes a gamepad is connected, disable all gamepads in DOG.

also make sure your using the latest beta of DOG since the older versions were ass.

[Mako Eyes]

Originally Posted by Squall-Leonhart

probably a bug in that dosbox automatically assumes a gamepad is connected, disable all gamepads in DOG.

also make sure your using the latest beta of DOG since the older versions were ass.

Well, I'll be damned Squall. The move to the new DOG beta did the trick. I made virtually no changes too.

Thanks for your help guys, now for a nice walk down memory lane shooting faces of LION MEN.

[Squall-Leonhart]

yeah, i need to assign a day to just play games... i've had hardly any real game time in the last few months.