VOGONS

Common searches


First post, by UberPrutser

User metadata
Rank Newbie
Rank
Newbie

Hello,

I'm having trouble running Grand Prix 3 (Directx7 game) with decent speed on my Windows 7 64 machine.
It should be flying just like GP4 but for some reason its very slow.
I've tried some compatibility modes and also dgvoodoo but I'm not having any luck.

Ideas?

Reply 1 of 10, by notindeed

User metadata
Rank Newbie
Rank
Newbie

Hmm could it be something to do with hyperthreading needing to be disabled?
Just a guess, could be wrong.

Your best bet is to ask at http://www.grandprixgames.org

Haven't ever tried these games on windows 7, only xp years ago. Then i discovered GPL and well they just didn't cut it anymore 🙁 Mind you a lot of it is to do with the circuits and seasons they represent. For that, GP2 is a lot better. Well, you can get traxk mods though.

Anyway i hope someone can help if disabling hyperthreading doesn't solve it. Not sure if you can do that in windows, but i know you can in the bios. Mind you, your cpu might no even have it so...

Reply 2 of 10, by UberPrutser

User metadata
Rank Newbie
Rank
Newbie

Thanks for the reply. Unfortunately the problem is not with HT.
I've been on grandprixgames.org and there are already some topics about this issue but sofar without a solution
I've uploaded a small clip to illustrate the problem. http://youtu.be/5poaTY1L-4Q

Reply 3 of 10, by notindeed

User metadata
Rank Newbie
Rank
Newbie

What's with the pink ring around your tyres? Looks like a wrong transparency or pixel centre setting in the drivers or something?

Hmm yes i had a look and couldn't really find any suggestions.

All i can think of is to try and limit the game to only using 1 CPU core. The game is very reliant on your cpu from what i remember, so this might help.

You could also try downloading microsoft's application compatibility toolkit to see if there is a profile for it in there.
I assume these profiles are only applied if you then create them yourself? Or are they by default part of windows but the ACT just shows you what they do?
I remember using one for Rally Championship 2000 anyway.

How did you record so smoothly on your XP machine? Judging from your specs it seems that your computer is about the same as my althon 64 3200+ and x1950 pro - well you have a better gpu but for recording such a game i dont think that makes a difference?
I've never really been able to record on this computer!

But yer, your CPU occupancy shouldn't be going over 100 or else the game will go into slow motion. (Obviously recording won't help matters - you could try putting the recorder set to use a different cpu core than the game, though obviously not on your single core system).

Try asking this guy as he seemed to have the same problems but judging from his videos has fixed them: https://www.youtube.com/user/ipswich1992
He originally seemed to ask here: http://www.grandprixgames.org/read.php?1,922893,925205

Or if not you could ask this guy: https://www.youtube.com/watch?v=jp3BRZTJVX8

Let us know how you get on.

I've seen a topic say to make a virtual machine and put XP on that but then if you're going to do that you might as well dual boot xp - i'm sure there will be drivers for your hardware, it's not THAT new.

Edit:
Someone says to set the rain probability above 0, basically try 50%.
http://www.grandprixgames.org/read.php?1,985205,994389

Reply 4 of 10, by UberPrutser

User metadata
Rank Newbie
Rank
Newbie

I noticed that Pink ring as well so I installed an old Nvidia FX5200 card in the XP pc and now it's gone. The game is also running a bit faster and that's not something I expected. So I just ordered a cheap Nvidia card for my Win7 pc.

I've looked into the MS ACT and there is a profile for GP3 but unfortunately it did not help. I've tried some other settings but have gotten nowhere.

The guy in your links also has the pink rings so he might not be running at optimum speed but his alienware pc is probably more powerful so he might not notice it so much.

I don't want to go the dual boot or virtualisation route but I might give wine a try on my Linux PC but that will probably come with it's own set of problems.

For now I'm playing GP3 on my old XP computer, because I just about had it with this issue 😀
If I could only get those split axis for my xbox controller to work..................

Reply 5 of 10, by VirtuaIceMan

User metadata
Rank Oldbie
Rank
Oldbie

You could look into some of the things I did on Win8.1 64bit here: Grand Prix 3 & GP3 2000 Season - FIXED

On my Nvidia 980 GTX I need to use dgVoodoo DirectX wrapper and recalibrate the graphics every boot up, but it's then smooth enough.

You could try software mode; the game looks worse but there's a cool sun glare/reflection effect on everything (road and scenery) that's not as obvious in 3D mode, plus the pink strips are gone!

My PC spec: Win10 64bit, i7-4970K (not overclocked), KFA2 GeForce RTX 2070 SUPER, Creative Soundblaster ZXr, 16GB RAM, Asus Z97-A motherboard, NZXT 410 case, ROG Swift GSYNC monitor

Reply 6 of 10, by UberPrutser

User metadata
Rank Newbie
Rank
Newbie

FYI: I've installed a Nvidia card on the win7 pc and the game calibration is now running below 60% at full resolution and details. The pink rings however are still there 🙁

@Virtualiceman: I've already tried dgvoodoo but it gave me an error message that there was no direct draw on my system.

Reply 7 of 10, by notindeed

User metadata
Rank Newbie
Rank
Newbie

Just to clear up confusion, i assume you mean DGVoodoo 2, not the original one which won't wrap old direct x versions?

BTW the pink lines surrounding your tyre are just a transparency issue - they won't be what's affecting the performance. You can either set a transparency setting somewhere with some tweaker tool for your card (i dunno if such a thing exists), or i think there is a setting for it in DGVoodoo 2, though i haven't tried it as my pc is too old.

The speed of the game is down to the "optimisation test" that it does not running correctly. If i remember i even had this problem on xp 10 years ago. Although maybe it was Grand Prix 4 i had the problem in? I can't remember - thinking about it maybe GP4 doesn't even have this mode.

Either way, your PCs are both well powerful enough, just try DGVoodoo 2 when calibrating.
You won't be able to do that on your XP machine, only your Windows 7 one as DGVoodoo 2 is for DX 10 and above.

Reply 8 of 10, by UberPrutser

User metadata
Rank Newbie
Rank
Newbie

Yes version 2.44 to be exact. But unfortunately it does not fix the pink rings issue. And it slows down the game considerably especially at the highest resolution. https://www.youtube.com/watch?v=S6DaypB9jcs

I've been trying all kind of settings in the ATI (XP pc) and Nvidia (win7 pc) drivers but so far without success 🙁

FYI: I did notice that the driver version can have a high impact on gameplay capture. With the standard XP driver processor utilization was above 500% and with the latest nividia driver below 100%. This was on the XP pc with the old nvida fx5200 card at 1280x1024.

Reply 9 of 10, by VirtuaIceMan

User metadata
Rank Oldbie
Rank
Oldbie

It won't help much, but the pink rings were present on my real XP PC with Nvidia 780 7800GS+ card, it's a driver issue/programming issue. There's fixes for the actual game, where people removed the pink strip by hacking files, see http://www.grandprixgames.org/read.php?1,1049385,1049390

As for speed, I could only get decent framerate on my fast PC by running the calibration each time the game started (yawn!).

My PC spec: Win10 64bit, i7-4970K (not overclocked), KFA2 GeForce RTX 2070 SUPER, Creative Soundblaster ZXr, 16GB RAM, Asus Z97-A motherboard, NZXT 410 case, ROG Swift GSYNC monitor

Reply 10 of 10, by Dege

User metadata
Rank l33t
Rank
l33t
UberPrutser wrote:

Yes version 2.44 to be exact. But unfortunately it does not fix the pink rings issue. And it slows down the game considerably especially at the highest resolution. https://www.youtube.com/watch?v=S6DaypB9jcs

It's a known issue. This game has a really bad rendering technique for ingame rendering, that's why dgVoodoo runs at low peformance.
'Fast videomemory access' helps a bit but it's not enough. This method is planned to be improved some day, I hope that will fix the issue.