The system is overpowered for the game in question so no problem there, did you check if there's any patch available? also try to disable audio accelleration in game.
Try also software mode, there could be some CPU incompatability.

Software rendering just crashes immediately. Sound is set to lowest possible quality.

Bubu2000 wrote on 2023-01-11, 18:51:

Software rendering just crashes immediately. Sound is set to lowest possible quality.

Ok let's start by slowing the cpu with something like cpugrab, then try again software mode.

Others have reported this issue as well: Re: Early Direct3D vs. early OpenGL

Given the power of your system, you might consider using a period Glide wrapper and see if that gives better results. Perhaps Dege's dgVoodoo (the original, not dgVoodoo2) for example. Have a look at Stilleto's The Wrapper Collection Project: The Wrapper Collection Project

dgVoodoo files are available here: http://www.vogonsdrivers.com/wrappers/files/G … gVoodoo/D3D7-9/

iraito wrote on 2023-01-11, 20:47:

Bubu2000 wrote on 2023-01-11, 18:51:

Software rendering just crashes immediately. Sound is set to lowest possible quality.

Ok let's start by slowing the cpu with something like cpugrab, then try again software mode.

I have an Athlon CPU with unlocked multiplier. 666 MHz is the slowest I can underclock it. Now it runs in software mode without stuttering, but the overall fps are low and not fun to play.

I also noticed that the joystick input is way to sensitive in this game. You can't hit an enemy because it's extremely twitchy.

akula65 wrote on 2023-01-11, 22:59:

Others have reported this issue as well: Re: Early Direct3D vs. early OpenGL
Given the power of your system, you might consider using a period Glide wrapper and see if that gives better results. Perhaps Dege's dgVoodoo (the original, not dgVoodoo2) for example.

Are those glide wrappers compatible with DX7? I didn't try dgvoodoo because I thought it needs DX9. I only have DX7 installed on my system.

Bubu2000 wrote on 2023-01-12, 10:24:

Are those glide wrappers compatible with DX7? I didn't try dgvoodoo because I thought it needs DX9. I only have DX7 installed on my system.

Why stick with DX7 in first place? DLLs are separated for each DX API version.

The GeForce4 Ti 4200 is more capable due to supporting PS 1.3 and VS 1.1, and there are software using the DX9 API working fine with that card. See here for more info: Games for GeForce 4 Ti 4200?

G-Police doesn't use Glide.

Gmlb256 wrote on 2023-01-12, 14:05:

Bubu2000 wrote on 2023-01-12, 10:24:

Are those glide wrappers compatible with DX7? I didn't try dgvoodoo because I thought it needs DX9. I only have DX7 installed on my system.

Why stick with DX7 in first place? DLLs are separated for each DX API version.

Because some games I play have problems with a higher DX Version. Need for Speed 1 SE doesn't run at all with anything above DX7 and in Motoracer the palette textures don't work, etc.

Bubu2000 wrote on 2023-01-12, 14:43:

Gmlb256 wrote on 2023-01-12, 14:05:

Bubu2000 wrote on 2023-01-12, 10:24:

Are those glide wrappers compatible with DX7? I didn't try dgvoodoo because I thought it needs DX9. I only have DX7 installed on my system.

Why stick with DX7 in first place? DLLs are separated for each DX API version.

Because some games I play have problems with a higher DX Version. Need for Speed 1 SE doesn't run at all with anything above DX7 and in Motoracer the palette textures don't work, etc.

This sort of problem happens because of the nVidia driver, considering that these games doesn't really touch later versions of the DX runtime libraries. If anything, consider dual booting with Windows XP (256MB RAM should be enough for early stuff, especially without any Service Pack installed).

Gmlb256 wrote on 2023-01-12, 15:00:

Bubu2000 wrote on 2023-01-12, 14:43:

Gmlb256 wrote on 2023-01-12, 14:05:

Why stick with DX7 in first place? DLLs are separated for each DX API version.

Because some games I play have problems with a higher DX Version. Need for Speed 1 SE doesn't run at all with anything above DX7 and in Motoracer the palette textures don't work, etc.

This sort of problem happens because of the nVidia driver, considering that these games doesn't really touch later versions of the DX runtime libraries. If anything, consider dual booting with Windows XP (256MB RAM should be enough for early stuff, especially without any Service Pack installed).

But those games run without any problems with exactly the same Nvidia driver and DX7. The problems start when I install DX8.

Sometimes newer cards show worse performances with previous APIs, also it sounds like the CPU was indeed one of the issues, try to use hardware mode while limiting the speed.

My copy of the game (v1.18) works fine on my Windows 7 64 gaming rig. I did have to use a ddraw.dll file from my GOG version of Metal Gear Solid in the G-Police main game directory to fix some missing textures. Everything works flawless.

I just tried another game, ReVolt, and it's exactly the same. I only get 20-30 fps and the game stutters like crazy. Shouldn't it run with at least 60 FPS on an Athlon XP 3000+ with GeForce 4200 Ti?

Edit: It's the joystick. If I disconnect my SideWinder, I get 144 FPS (@144 Hz vsync)

Why is the joystick tanking my fps?

Bubu2000 wrote on 2023-01-13, 17:50:

I just tried another game, ReVolt, and it's exactly the same. I only get 20-30 fps and the game stutters like crazy. Shouldn't it run with at least 60 FPS on an Athlon XP 3000+ with GeForce 4200 Ti?

Edit: It's the joystick. If I disconnect my SideWinder, I get 144 FPS (@144 Hz vsync)

Why is the joystick tanking my fps?

I see that your motherboard nor sound card have a gameport so where are you plugging this in?

I don't use USB at all. It's disabled in the BIOS.

My Mainboard has a Gameport and my Audigy 2 has a Gameport too. I'm using the Audigy one at the moment.

It seems to be a problem with the force feedback effects. In some games those effects are tanking the fps to unplayable values. Other games I can play without any problems.

Bubu2000 wrote on 2023-01-13, 18:43:

I don't use USB at all. It's disabled in the BIOS.

My Mainboard has a Gameport and my Audigy 2 has a Gameport too. I'm using the Audigy one at the moment.

It seems to be a problem with the force feedback effects. In some games those effects are tanking the fps to unplayable values. Other games I can play without any problems.

Ah... from the pics I've seen I did not see the gameports on either board. I'm assuming it's an extension port separate from the PCB connected by ribbon cable? Yeah, gameports run by I/O address which takes up CPU cycles. I wonder if the FF is taking too many CPU cycles on certain games. Odd. Have you tried the other gameport?

I tried it on the other Gameport and it has the same problem. I don't know what to do now.

Joystick port takes memory space #200 if I remember correctly... Check that there is no conflict.