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

×
Only software mode appears to work for me atm.
Not had time to try some tweaks yet (if there are any).

Be good to hear from others out there :)

[Win 7 64bit - Nvidia GPU]
Post edited December 02, 2010 by Krankor
avatar
Krankor: Only software mode appears to work for me atm.
Not had time to try some tweaks yet (if there are any).

Be good to hear from others out there :)
Heck I could not get D3D to work on the first one.
avatar
Krankor: Be good to hear from others out there :)
So far I've had no luck whatsoever, on two different PCs even.
When it bugs out, it creates a data\delphine.err log file which I'm currently studying. Will report any findings :)
avatar
Krankor: Be good to hear from others out there :)
avatar
81RED: So far I've had no luck whatsoever, on two different PCs even.
When it bugs out, it creates a data\delphine.err log file which I'm currently studying. Will report any findings :)
I would also be curious to know if anyone that runs Wine under Linux to see if the application has the same behavior?
From running moto.exe -h

Screen mode
-DrawMouse : Draw mouse if card doesn't do it
(3dFx Voodoo's for example)
-FullScreen : Start game in fullscreen mode
-Height<h> : Start game with a screen height of <h> pixels
(only if -Width is used too)
-Width<w> : Start game with a screen width of <w> pixels
-Windowed : Start game in windowed mode

Language
-Fr : Force French version
-Gr : Force Deutsh version
-It : Force Italian version
-Sp : Force Spanish version
-Sw : Force Sweden version
-Us : Force English version

3D cards management
-3DFX : Declare your 3D card as a 3DFX
chip-based card
-NoPowerVr : Disable PowerVr auto-detection
-PowerVr : Declare your 3D card as a PowerVr
chip-based card if auto-detection
fails
-VideoControler<n> : Use 3D hardware number <n>
(First is 0, Second is 1, etc...)

Direct3d rendering
-D3D : Use 3D hardware acceleration
(if card supports D3D but not textures)
-MenuClipSpec : Clip specular effect in menu pages
Use it if clear rectangles appear
on menu highlighted options.
-NoD3D : Do not use 3D hardware accelerat.
-NoDither : Do not use dither capabilities
-NoFilter : Do not use filter capabilities
-NoGouraud : Disable gouraud shading
-NoZBuffer : Do not use hardware Z-Buffer (slower)
-ScanOtNormal : Scan polygons Back to Front
-TripleBuffer : Enable triple buffering
-ZBuffer32 : Use Z-buffer as a 32bits Z-Buffer

Direct3d textures management
-Alpha : Force texture format 4444
-AlphaTransparent : Use alpha channel instead of color-keying
-CorrectRatioTextures : ...If problems with fonts
-DontUseAlpha : Avoid alpha textures
-DontUseColorKey : Avoid SetColorKey() function.
Use it with -AlphaTransparent for
transparency problems in textures
if your 3D card supports Alpha textures
(RGB4444, RGB1555 etc...)
-DontUseModulateAlpha : Dont use ModulateAlpha blending mode
-MipMap : Enable MipMap
-MinTextureWidth<n> : Set minimum texture width to <n> pixels
-MaxTextureWidth<n> : Set maximum texture width to <n> pixels
-MinTextureHeight<n> : Set minimum texture height to <n> pixels
-MaxTextureHeight<n> : Set maximum texture height to <n> pixels
-NoPal16 : Disable 16 colors palettes
-NoPal256 : Disable 256 colors palettes
-NoTextureSizeMax256 : To optimize size texture in
video memory
-OpaqueBlackLevel<n> : Set <n> in the range [1..3] if
transparency bugs appear
-TextureSquareOnly : All textures must be square

Video memory management
-ForceSmallestTextures: Force bank loading strategy to use smallest
texture format (may be less beautiful).
Try it if you have video memory problems.
-InfiniteZBuffer : For special Z-buffering system
(i.e PowerVr/PowerVr2 chip)
Set by default if PowerVr mode is found or
set by -PowerVr
-KeepAvailableVram<n> : Tries to keep <n> bytes free in Vram.
-AGP : Enable AGP use

DirectDraw
-AskDirectDraw : Display DirectDraw informations
-DoRealLock : Really use DirectDraw lock/unlock
(Not recommended)
-NoDuplicateSurfaces : Disable surface duplic. of bikes
Try it if all the bikes have the
same color.

Network
-AvoidNetGroup : Forbids DirectPlay to use groups
Try this option if game is lower in network mode.
-DelayEnumSessions<n> : Set refresh delay in sec/100 for sessions
enumerating in network game.
0 (Zero) means MANUAL mode.
Default is 500, which means 5sec.
Max is 3000, which means 30sec.
-DelayConnection<n> : Set connection wait in sec/100 in network game.
0 (Zero) means AUTOMATIC mode.
It means DirectPlay
will set this delay itself
Default is 500, which means 5sec.
Max is 3000, which means 30sec.
-NbMaxLinkPlayers<n> : Max number of players in a network session.
-NoModem : Forbids MotoRacer to use modem connection.
(Unavailable in US version)

Peripherals management
-JoyDZ<N><XX> : Set joystick <N> dead zone to <XX> %
(default=0, max=90)
-JoyMax<N><XX> : Set joystick <N> max to <XX> %
(default=100, min=10)
-NoCpuDetect : Disable CPU detection.
-NoMMX : Disable MMX support
-NoSound : Disable Direct Sound
-NoMixer : Disable Mixer usage
-KeepMixerState : Don't restore mixer volumes of the previous session
-DisableCDrestart : Disable the CD track auto restart
(create pause on width some CDRoms

MotoRacer2
-DemoMode : Run not playable demo
-DemoOnce : Run not playable demo one time and quits
-DemoDelay<n> : Run demo automatically after <n> secs
Values from 0 to 300. Default is 30
-DemoTime<n> : Set demo duration to <n> secs.
Values from 20 to 180. Default is 60
-DontLimitFrameRate : Normally, MotoRacer is limited to
30 fps to optimize the size of the
replay files. This argument disables the
limitation.
-LimitFrameRate<n> : Limits frame rate to <n> fps
Use values from 15 up to 60.
Default is 30.
-SkipIntro : Start directly with menu
-SnapShot : Enable screen copy in directory
Data\Shoot when using Shift-Ins
(Create this directory before
using this option)
-ThreadHighest : Set thread to highest priority
(Use this option carefully.
Avoid it if you want to play in
network mode)
-ThreadTimeCritical : Set thread to time critical mode
(Use this option carefully.
Avoid it if you want to play in
network mode)
-Disable3DNow : Do not use 3DNow instructions.
-Force3DNow : Use 3DNow instructions.

************************************************************************
Looks pretty identical to MR, so will try the parameters we discussed in the MR D3D thread and update with findings asap.

UPDATE:
No luck whatsoever. I varied the known solutions for MR1 in order to get D3D, but with MR2 diddly squat so far :(

My MR1 D3D solution being (16 bit colour depth) and the following parameters:

"C:\Program Files (x86)\GOG.com\Moto Racer\game.EXE" -D3D -CorrectRatioTextures -ZBuffer -FrameRateMax0 -nodither -TextureVideoMem268435456
Post edited December 02, 2010 by Krankor
Works fine for me, though I don't think this will be much help to you >.<
avatar
hockeycanuck: I would also be curious to know if anyone that runs Wine under Linux to see if the application has the same behavior?
See attached image for what happens with Arch Linux and wine 1.3.8
Attachments:
mr2.jpg (36 Kb)
Post edited December 02, 2010 by xyem
Software mode only works for me as well. MR1's D3D worked for me though.

Win 7 x64 with GTX 460
It works for me, with a netbook, single core, atom1.6ghz, intel 3150, 1gb ram and win7 starter 32bit edition. it also runs very smooth and supports 1024x600px.

as an off topiv tip: i found it much more enjoyable changing the collision timer in the gameplay option from, per example, 10 seconds to 4 sec. for a total crash and 4s to 1s for banding ;) :) and it is still difficult enough.
avatar
Krankor: Only software mode appears to work for me atm.
Not had time to try some tweaks yet (if there are any).

Be good to hear from others out there :)

[Win 7 64bit - Nvidia GPU]
I gave in and bought this game and it works on my netbook more smoothly then MR1 did... Intel Atom N450 , Intel Media Accelerator X3150 Graphics , 1.66ghz processor 1gb ram.
avatar
Krankor: Only software mode appears to work for me atm.
Not had time to try some tweaks yet (if there are any).

Be good to hear from others out there :)

[Win 7 64bit - Nvidia GPU]
avatar
hockeycanuck: I gave in and bought this game and it works on my netbook more smoothly then MR1 did... Intel Atom N450 , Intel Media Accelerator X3150 Graphics , 1.66ghz processor 1gb ram.
The software mode runs fine (no slowdown etc). In fact other than the road markings looking 'wobbly' in the distance the entire experience is fine.

But it would be good to find a D3D fix for Win7 64bit. :)
avatar
Krankor: But it would be good to find a D3D fix for Win7 64bit. :)
I'm not able to run D3D either. I'm running Vista 64 w/9600M GS, P8400 C2D, 4GB RAM.

Software mode is fairly smooth. Is there any visual benefit from running D3D?

EDIT: never mind that comment. I could definitely do with better framerates on the motocross tracks.
Post edited December 04, 2010 by Tbone289
I found a solution (fingers crossed it may work for you too) and detailed it here
See thread :
http://www.gog.com/en/forum/moto_racer_series/d3d_solution_for_mr2