Dear fellog GOGers,
I have just bought Moto Racer 2 here on GOG, and it looks good. The only problem is that the steering seems highly temperamental - my choice of keys (WASD) only let me go forward and back. So I tried (ZXFC) and that worked fine. Except now I've restarted the game and it no longer likes those keys - I can only go forward and back again! Does anyone have any suggestions as to what's going on and how to fix it? I've got a standard PS/2 keyboard, and the keys all work fine in other programs in Windows & Linux.
Many thanks!

Edit - Here's my system specs, if they help:
AMD Phenom 9950 2.6GHz x4
6Gb 800MHz DDR2 RAM
Asus M2N-SLI motherboard
NVidia GeForce 9800GT PCI-E graphics
Creative Audigy X-Fi XtremeMusic PCI soundcard
Windows XP x64 Professional

hi!!

i don't jave buy the games but have you tri to uncheck the "read onlies" in the game folders properties?

do it for the folders imself and enter into it select all files and redo it...

another solution its to look for a config.ini in the games folders (i d'ont know if there a one fore this games) open it with wordpad.. or other.. and modi for your wish...

i hope i was helpefull!!

good luck

Thanks for the reply. I tried as you suggested and made the entire game directory non-"read only", and I also set the compatability mode to Windows XP, but I still can't turn the bike. It works perfectly fine on my Samsung netbook. Anyone else have any ideas?
I can't find a config file to manually edit and then set to read-only.

Edit - Hmmm, something's definitely weird with the keys. I tried changing the keys on my netbook's installation of Moto Racer 2, and it still used the Arrow (Cursor) keys even though the Controller setup clearly had the keys redefined. My desktop is even weirder - it has the acceleration and brake keys as the original Cursor keys, and the left and right steering non-existant :(

Might Windows XP x64 be the problem? I've heard that the 64-bit flavour of XP is very buggy.

What OS is your Samsung netbook?

XP x64 is a rebranded version of Server 2003, so it is very stable. The netbook is the standard (Home 32-bit) edition of XP.

Taken from Wikipedia:

Two versions of Windows XP 64-Bit Edition were released:

Windows XP 64-Bit Edition for Itanium systems, Version 2002 – Based on Windows XP codebase, was released simultaneously alongside the 32-Bit version of Windows XP on October 25, 2001.

Windows XP 64-Bit Edition, Version 2003 – Based on Windows Server 2003 codebase, which added support for the Itanium 2 processor, was released on March 28, 2003.


Known issues
There are some common issues that arise with Windows XP Professional x64 Edition.

Driver compatibility; Only 64-bit kernel mode drivers are supported. This means that devices for which there are no 64-bit Windows XP drivers available cannot be used. This includes a lot of common hardware; such as CD drives, DVD drives and USB. The amount of unsupported hardware has fallen because of the proliferation of x64 Vista and x64 Windows 7.

Any 32-bit Windows Explorer extension fails to work with 64-bit Windows Explorer. Explorer is a 64-bit program, so it cannot load a 32-bit DLL. However, Windows XP x64 Edition also ships with the 32-bit explorer.exe, which can be used as the user's default shell with a registry change.

16-bit programs will not run because of Microsoft's removal of the 16-bit subsystem. As some 32-bit software has been delivered with 16-bit installers, these software will not install.

Command prompts will not load in full-screen. This is also true of Windows Vista and Windows 7 in both 32- and 64-bit editions.

Does not contain a Web Extender Client component for Web Folders (WebDAV).

Some installers refuse to install to anything other than 32-bit XP, even though the product runs perfectly on x64.


Now, of the above, I can't see why they would be an issue if it works on 64-bit Vista, as that would share these issues, but I can honestly tell you that I've read numerous times about how to avoid XP 64-bit if you play games due to compatibility issues. Whether this is the issue, though, I cannot say. Note, however, that stability and compatibility are very different, so your OS may be very stable but if it is a compatibility issue then the stability means nothing.

Anyone else here use 64-bit XP?

Thanks for the reply. I have XP Pro x64 rather than the XP I64. The latter is for the Itanium processor which have big compatability problems as it has pretty dodgy x32 emulation. The XP Pro x64 (based on Windows Server 2003) is for the AMD x86-64 architecture that has much better backwards compatability. This was then the bedrock which led to Vista x64 and Windows 7 x64. I've got about 100 games, and the only ones that don't work are the x16 games (since Microsoft only ship one emulator, and so the x32 one is rightly considered more important!). The only issues are (a) you have to have x64 drivers (can be awkward to get for this version of Windows), and (b) the Shell requires x64 programs for integration.

Anyway, this is a moot point, as I get exactly the same issue on both computers - WinXP x32 netbook, and WinXP Pro x64 desktop. So I'm still scratching my head :)

Well, if you've tried all the standard initial fix attempts (running it using a single core of your CPU, try out various compatibility modes, etc) then I'd recommend raising a ticket to GOG support.

Many thanks, ardentlyenthused, I have a Logitech 2 Rumblepad on my Desktop, and unplugging this has made me able to steer again! Big thanks :D I don't have a gamepad on my Win32 netbook though, but maybe it's the touchpad (which has its own drivers)? I will give that a go later on and report the results.

Rather perversely after our previous (informative) discussion on Windows XP x64, it's actually working on that but not on Windows XP x32 :D

Ah ha! So it was a controller that was causing this issue for you. Glad you got it solved. I have a controller but as I only use it for a very few select games I don't keep it plugged in. Just to check, the controller is USB?

As for your touchpad, you may be able to disable it completely which, hopefully, will fix the issue if it is being picked up as a controller like your other machine was doing.

I had the same problem so I went experimenting a bit with the controls and noticed a couple of oddities.

First, it seems that in single player mode the game uses the player 2 controls as an alternative scheme. By default the P2 controls are mapped to a controller, with steering on one of the analog axes. I mapped steering to the buttons on the controller instead and my problems went away.

Second, I tried erasing all mappings for all players besides player 1 but that caused the problem to return. As soon as I mapped a single control for P2 to my joystick, it worked again. Seems if there's a controller that's not used by any of the players, it'll become an alternative controller for P1.

I set my controls like this but just removing all analog axes from the controller settings should fix the problem.

Just a quick update, setting the entire MotoRacer2 directory to be non "Read Only" fixed the problem on my netbook (i.e. where some of the controls could be remapped and some couldn't).

Thanks. I have a rog ally so I can't just disconnect the controllers. Must be mapping the controllers to player 1 even though the game lists keyboard controls for player one.