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

×
I have just published my 3D Vision fix: https://helixmod.blogspot.com.es/2018/05/star-wars-episode-i-racer.html

It has three hotkeys related to aspect ratio and zoom (Y axis aspect ratio) to control it in real time, but the fix will unstretch 4:3 to 16:9 by default. Be warned that what you see depends on what the game decides to draw outside the 4:3 zone.

Here is an example (stereoscopic screenshot) of a really big FOV increase in 16:9: https://u.cubeupload.com/masterotaku/SWEP1RCR013.jpg

Normal zoom level examples (they are in the blog post too):

https://u.cubeupload.com/masterotaku/SWEP1RCR005.jpg
https://u.cubeupload.com/masterotaku/SWEP1RCR014.jpg
https://u.cubeupload.com/masterotaku/SWEP1RCR016.jpg

If you don't use 3D Vision, you can ignore most of the post content (and misaligned HUD elements in the 3D screenshots), except for the need to use dgVoodoo and the aspect ratio hotkeys.

I have tested this only on Windows 10.
Post edited May 04, 2018 by masterotaku
Thanks, this is very nice. Now I can play it in 16/9 at 144 fps like I was hoping to :) The geometry culling bothers me a bit though, I may reduce the fov a bit or just end up playing in a custom 4/3 resolution.

Doing this also fixed graphical glitches I had with the vanilla gog install (my skybox was just plain green for example).
Culling in 16:9 in races isn't too bad. You can configure aspect ratio and zoom levels however you like in "d3dx.ini". Search the "w=0.75" and "y1=0.75" lines to change the default values, and "[Key5]" and "[Key7]" for hotkey values.

I don't know if you'll reach 144fps though. I'm CPU limited (i7 7700K) way before that with the resolution, AA and mods I use.
avatar
masterotaku: Culling in 16:9 in races isn't too bad. You can configure aspect ratio and zoom levels however you like in "d3dx.ini". Search the "w=0.75" and "y1=0.75" lines to change the default values, and "[Key5]" and "[Key7]" for hotkey values.

I don't know if you'll reach 144fps though. I'm CPU limited (i7 7700K) way before that with the resolution, AA and mods I use.
I'm getting 144fps with my 8700k/1080 ti. I have a g-sync monitor so I'm capping it (at 141 to be precise) but I think it would go much higher if I let it. That's with MSAA8x and AF16x (exact same settings as you showed on the blog page). In 1080p (and no 3D or any other mods).

Yeah, I'll see if I want to zoom in a bit or not. It's usually not too bad in races like you said but I find it a bit distracting sometimes still :)
Post edited May 04, 2018 by kaleena
avatar
kaleena: I'm getting 144fps with my 8700k/1080 ti. I have a g-sync monitor so I'm capping it (at 141 to be precise) but I think it would go much higher if I let it. That's with MSAA8x and AF16x (exact same settings as you showed on the blog page). In 1080p (and no 3D or any other mods).
I've just done some tests. It's very resolution dependant, it seems. For starters, this new hotfix update changed the default game resolution to 640x480 and I didn't bother to change it (dgVoodoo overrides it anyway), and I'm now getting 135fps in 2D instead of 90 something. And this was trying 8xSGSSAA at 2560x1440 instead of 4xSGSSAA. Probably dgVoodoo has an easier time overriding a lower resolution, and antialiasing doesn't count that much.

After this, I checked:

1080p with 8xSGSSAA: 200fps.
720p with no AA: 375fps.
640x480 with no AA: 420-440fps. Just a small jump from 720p.

And physics are still working as fine as always (in the minute that I tried each mode). 240Hz monitor users will be happy :p.

It looks like a CPU limitation that heavily depends on resolution.
Post edited May 04, 2018 by masterotaku