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

×
Community
Interstate seriesnGlide & Nvidia Inspector fix?(10 posts)solved(10 posts)solved
(10 posts)solved
Pages:
1
This is my favourite topic
Posted May 06, 2016
New place for this discussion: https://www.gog.com/forum/star_wars_shadows_of_the_empire/game_runs_too_fast/post46

Okay, got glide and d3d modes working right and I think I got the physics working correctly, now if I could just set a resolution higher than 640x480 in those modes.
Post edited May 07, 2016 by haydenaurion
This question / problem has been solved by korellimage
Posted May 07, 2016
avatar
haydenaurion: New place for this discussion: https://www.gog.com/forum/star_wars_shadows_of_the_empire/game_runs_too_fast/post46
To bring this thread up to date, then, we'll list what has been covered so far.

Okay, so which nGlide version does the GOG installation of Interstate '76 come with? I'm sure it uses nGlide, so there would be an nGlide configurator and DLL files within the game installation folder somewhere, probably the root of the installation alongside the game executable. If it is an old version, I'd replace it myself, though GOG sometimes provide older versions as they couldn't get it working consistently reliable with the latest version on their test rigs.

Then, as you have nGlide installed on your machine itself, change the settings for it first, and then go to the nGlide configurator within the game folder and set the settings there (older versions of nGlide have slightly different options, and as settings are stored in the registry they are shared between all nGlide versions, which has caused issues in the past due to conflicting values. But yes, vsync should be turned on in nGlide.

Personally, I don't use nGlide as an installation, I just extract the files to the games I want to use it on, as different versions with different games is then easily possible and it makes sure that you can't get conflicts between the nGlide DLLs in the Windows system folders and the nGlide DLLs in the game folder (whether they would ever conflict anyway I'm not sure, but this way they can't as there aren't any in the Windows system folders).

Next, use Nvidia Inspector to create a profile for the I76 executable, and then set the frame rate limit for that executable to something around 29-30 FPS. You can also set the vsync option here (try forced on, or 1/2 refresh if you are on a 60 Hz monitor, or 1/4 refresh if you are on a 120 Hz monitor. The Nvidia Control Panel probably sets similar options if you use adaptive v-sync, too.
Posted May 07, 2016
avatar
haydenaurion: New place for this discussion: https://www.gog.com/forum/star_wars_shadows_of_the_empire/game_runs_too_fast/post46
avatar
korell: To bring this thread up to date, then, we'll list what has been covered so far.

Okay, so which nGlide version does the GOG installation of Interstate '76 come with? I'm sure it uses nGlide, so there would be an nGlide configurator and DLL files within the game installation folder somewhere, probably the root of the installation alongside the game executable. If it is an old version, I'd replace it myself, though GOG sometimes provide older versions as they couldn't get it working consistently reliable with the latest version on their test rigs.

Then, as you have nGlide installed on your machine itself, change the settings for it first, and then go to the nGlide configurator within the game folder and set the settings there (older versions of nGlide have slightly different options, and as settings are stored in the registry they are shared between all nGlide versions, which has caused issues in the past due to conflicting values. But yes, vsync should be turned on in nGlide.

Personally, I don't use nGlide as an installation, I just extract the files to the games I want to use it on, as different versions with different games is then easily possible and it makes sure that you can't get conflicts between the nGlide DLLs in the Windows system folders and the nGlide DLLs in the game folder (whether they would ever conflict anyway I'm not sure, but this way they can't as there aren't any in the Windows system folders).

Next, use Nvidia Inspector to create a profile for the I76 executable, and then set the frame rate limit for that executable to something around 29-30 FPS. You can also set the vsync option here (try forced on, or 1/2 refresh if you are on a 60 Hz monitor, or 1/4 refresh if you are on a 120 Hz monitor. The Nvidia Control Panel probably sets similar options if you use adaptive v-sync, too.
I got it all working by removing the I'76's glide dll files and using my nglide installation I already had along with the other stuff. I think the weapon physics are working correctly too. I can now see the flamethrower coming from my car but just a tiny bit, is that how it was in the original?
Posted May 07, 2016
avatar
haydenaurion: I got it all working by removing the I'76's glide dll files and using my nglide installation I already had along with the other stuff. I think the weapon physics are working correctly too. I can now see the flamethrower coming from my car but just a tiny bit, is that how it was in the original?
Sounds like the included nGlide DLLs were over-riding your main installation of nGlide (the reason why I don't install it and instead use a separate instance for each game). I hate that it stores settings in the registry though. An ini file would be much nicer as it then becomes truly portable. Thing is, originally it did use an ini file, and he changed it to use the registry.

I don't think the flamethrower has much range, I didn't use it much myself. Check the mortars though, I did use them as they were useful as heavy hitting weaponry.

Last thing from me, then, as you seem to have it running fine now, is whilst the fix with the profile worked fine for the main game, I had slightly less success with the Nitro Riders expansion, because there is already a profile for nitro.exe (some WWE wrestling game or other). You might have to delete that profile and then create a new one for the Nitro Riders game. I think there's an option to reset the Nvidia driver profiles anyway, reset to Nvidia defaults or something, but it'd be on a profile by profile basis.
Posted May 07, 2016
avatar
haydenaurion: I got it all working by removing the I'76's glide dll files and using my nglide installation I already had along with the other stuff. I think the weapon physics are working correctly too. I can now see the flamethrower coming from my car but just a tiny bit, is that how it was in the original?
avatar
korell: Sounds like the included nGlide DLLs were over-riding your main installation of nGlide (the reason why I don't install it and instead use a separate instance for each game). I hate that it stores settings in the registry though. An ini file would be much nicer as it then becomes truly portable. Thing is, originally it did use an ini file, and he changed it to use the registry.

I don't think the flamethrower has much range, I didn't use it much myself. Check the mortars though, I did use them as they were useful as heavy hitting weaponry.

Last thing from me, then, as you seem to have it running fine now, is whilst the fix with the profile worked fine for the main game, I had slightly less success with the Nitro Riders expansion, because there is already a profile for nitro.exe (some WWE wrestling game or other). You might have to delete that profile and then create a new one for the Nitro Riders game. I think there's an option to reset the Nvidia driver profiles anyway, reset to Nvidia defaults or something, but it'd be on a profile by profile basis.
Yeah, I had to do the same for Tomb Raider 1 and the original Carmageddon installer before gog updated it.

Mortars I know are working now. I compared it with a youtube walkthrough of a working version of the game.

I'll keep that in mind for the Nitro Pack. I'll probably just delete that profile.

Nice that the issues with Shadows gave some new ideas and fixes for other games. Finally I can play the spiritual predecessor to Vigilante 8, one of my favs from the PS1.
Posted May 07, 2016
avatar
haydenaurion: Yeah, I had to do the same for Tomb Raider 1 and the original Carmageddon installer before gog updated it.

Mortars I know are working now. I compared it with a youtube walkthrough of a working version of the game.

I'll keep that in mind for the Nitro Pack. I'll probably just delete that profile.

Nice that the issues with Shadows gave some new ideas and fixes for other games. Finally I can play the spiritual predecessor to Vigilante 8, one of my favs from the PS1.
One last thing, whilst I think of it. Thiev mentioned that they implemented a 15-20 FPS limit for I'76 via some method or other. Whether this is working or not I can't say (though your experience suggests it isn't working for everyone, at least, and it wasn't present when I played the game before the installer was split up). Now if you do think that the flamethrower still doesn't have enough range, try reducing the framerate further, say by about 5 FPS each time, until you are happy with the result. Personally, though, I was happy with 30 FPS.
Posted May 07, 2016
avatar
haydenaurion: Yeah, I had to do the same for Tomb Raider 1 and the original Carmageddon installer before gog updated it.

Mortars I know are working now. I compared it with a youtube walkthrough of a working version of the game.

I'll keep that in mind for the Nitro Pack. I'll probably just delete that profile.

Nice that the issues with Shadows gave some new ideas and fixes for other games. Finally I can play the spiritual predecessor to Vigilante 8, one of my favs from the PS1.
avatar
korell: One last thing, whilst I think of it. Thiev mentioned that they implemented a 15-20 FPS limit for I'76 via some method or other. Whether this is working or not I can't say (though your experience suggests it isn't working for everyone, at least, and it wasn't present when I played the game before the installer was split up). Now if you do think that the flamethrower still doesn't have enough range, try reducing the framerate further, say by about 5 FPS each time, until you are happy with the result. Personally, though, I was happy with 30 FPS.
Yeah, setting Nvidia Inspector to 23 fps makes the flamethrower shoot much further (about 2 car lengths?), though I can't seem to set it lower as when I try to set it manually it just defaults to another setting for some odd reason. I wish I had more reliable original hardware footage of the game to compare it to so I could tell if the flamethrower is supposed shoot that far or not. Not having played or even heard of the game when it originally came out doesn't help.
Post edited May 07, 2016 by haydenaurion
Posted May 07, 2016
avatar
haydenaurion: Yeah, I had to do the same for Tomb Raider 1 and the original Carmageddon installer before gog updated it.

Mortars I know are working now. I compared it with a youtube walkthrough of a working version of the game.

I'll keep that in mind for the Nitro Pack. I'll probably just delete that profile.

Nice that the issues with Shadows gave some new ideas and fixes for other games. Finally I can play the spiritual predecessor to Vigilante 8, one of my favs from the PS1.
avatar
korell: One last thing, whilst I think of it. Thiev mentioned that they implemented a 15-20 FPS limit for I'76 via some method or other. Whether this is working or not I can't say (though your experience suggests it isn't working for everyone, at least, and it wasn't present when I played the game before the installer was split up). Now if you do think that the flamethrower still doesn't have enough range, try reducing the framerate further, say by about 5 FPS each time, until you are happy with the result. Personally, though, I was happy with 30 FPS.
Ran another test. This time instead of using the frame limiter option with hard numbers, I used the 1/3 refresh rate option. Before at 23 fps the flamethrower worked, but would stutter a bit coming out, now it comes out clean without stutter using the 1/3 refresh rate option which is about 20 fps in my case. Perfect as far as I can tell.
Posted May 07, 2016
Just another thought. If the Nitro Riders expansion executable (nitro.exe) can be renamed to the main game's executable, then it should use the same profile. However, I don't know if the Nitro Riders expansion will run if you do that. Worth a try maybe?
Posted May 08, 2016
avatar
korell: Just another thought. If the Nitro Riders expansion executable (nitro.exe) can be renamed to the main game's executable, then it should use the same profile. However, I don't know if the Nitro Riders expansion will run if you do that. Worth a try maybe?
It probably would work, something to try later. I'd still probably just delete the other nitro profile as I don't see myself ever playing WCW Nitro. I rented that god awful game long ago on PS1, once was enough for me, lol.
Pages:
1
This is my favourite topic
Community
Interstate seriesnGlide & Nvidia Inspector fix?(10 posts)solved(10 posts)solved
(10 posts)solved