Visitor Comments

• 
  JimDiabolo - 1 year ago

  0liked this

  User	Date

  Liked Like

  What renderer does the widescreen version use? It looks good on original tracks, but I got some freezes on custom tracks.
  

  Reply
  • 
    pete9516 - 1 year ago

    0liked this

    User	Date

    Liked Like

    Looks like DirectX 9.0b and DGVoodoo and a ddraw compat in the main folder

    Reply
• 
  Whatscheiser - 3 months ago

  0liked this

  User	Date

  Liked Like

  Call me slow but I'm not understanding where to toggle collision back on. It's off by default and seems to stay that way. Where in the menu is this?

  Ah, I think I see where it is supposed to be. In your screenshot you have an option "Damage / Collision". I don't have that. Mine just says "Damage".

  Reply

  edited by Whatscheiser 3 months ago
  • 
    pete9516 - 3 months ago

    0liked this

    User	Date

    Liked Like

    I don't understand. I think Ravage included the necessary menu files? Did you install them?

    Reply
  • 
    Whatscheiser - 3 months ago

    1liked this

    User	Date
    pete9516	3 months ago

    Liked Like

    I would assume so... I copied my original data and savedata folders off of the CD into an empty directory and then grabbed everything that was in the 16:9 folder and copied those files to the same directory as the data folders. I overwrote everything I was prompted to, but I don't seem to have "Damage / Collision" option.

    I should note though that I did use a tool to rename all files to lower-case. I wouldn't think that should cause an issue but it is a non-standard installation step. I do that because files off of the CD are all upercase and files have a mix of upper and lower case in the download. That's a problem for me since I'm playing on Linux and the OS is case sensitive with file names. "File.exe" and "file.exe" will not overwrite each other. They'll sit along side one another.

    I suppose I'll try doing the standard setup on Windows and see if I get a different result.

    ::EDIT::

    Yeah I did the standard setup on Windows just now with the same result. I don't have the collision toggle.

    ::EDIT::

    Eh this might be much ado about nothing though. So while my menu entry doesn't say Damage / Collision as in the screen shot. I do have the option of "On" "Visual Only" "Physics Only" or "Off". If I select the "On" option I have collision. Sorry, I that's a menu I never really dove into so if those options are different I just didn't even notice. At any rate it still doesn't explicitly say whether collision is toggled. It's just the generic "Damage" descriptor.
    

    Reply

    edited by Whatscheiser 3 months ago
  • 
    pete9516 - 3 months ago

    1liked this

    User	Date
    Whatscheiser	3 months ago

    Liked Like

    Actually, it's pretty straight forward:

    Physics only = Only physical damage, no visual.

    Visual only = Visual damage, but no physical damage. Means that you will actually see the damage on your car, but it will not affect the handling of it. Like damage would be turned off

    Reply
  • 
    Whatscheiser - 3 months ago

    1liked this

    User	Date
    pete9516	2 months ago

    Liked Like

    Fair enough and it does seem to work as intended. Thanks for the response!

    Reply
• 
  eqagunn - 7 days ago

  1liked this

  User	Date
  pete9516	2 days ago

  Liked Like

  This patch is causing the polygon seams to be illuminated by headlights. Any idea what to tweak in dgVoodoo to get rid of them? See screenshot: https://i.imgur.com/mnVOTDY.png

  
  

  EDIT:
  Figured out how to make it work in widescreen with nGlide. No illuminated seams there.
  - Copy DATA folder from the CD to a game folder of your choice.
  - Create SAVEDATA folder in the game folder.
  - Copy Widescreen_Resolution_16_9/data folder to game folder and overwrite.
  - Copy Widescreen_Resolution_16_9/drivers/ws_dgvoodoo_dx9/d3da.dll file to drivers/voodoo2a-ws folder and rename it to voodoo2a.dll.
  - Copy Widescreen_Resolution_16_9/nfs4.exe, nfs4.ini, and eacsnd.dll files to game folder.
  - Set ThrashDriver to voodoo2a-ws in nfs.ini.
  - Copy Standard Resolution_4_3/drivers/nglide2/glide3x.dll file to game's folder.
  - Copy StandardResolution_4_3/drivers/nglide2/voodoo2a.dll file to drivers folder.
  - Copy StandardResolution_4_3/drivers/nglide2/thrash.ini file to drivers/voodoo2a-ws folder.
  - Set NGLIDE_RESOLUTION to 1 and NGLIDE_ASPECT to 0 in it.
  - Run nfs4.exe file.
  - Set Options/Graphics/Wide Screen to Off.
  - Set Options/Graphics/Advanced Settings/View Angle to Wide.
  - Set Options/Cameras/Camera 1 to High.
  - Play the game!

  Reply

  edited by eqagunn 6 days ago
  • 
    pete9516 - 2 days ago

    0liked this

    User	Date

    Liked Like

    Wow you really worked hard to get this running. I've never had a graphic issue like this. What i'd do instead is setup the game to Porsche Unleashed's DirectX 7 driver and install DGVoodoo2 into the game folder and use TsTg's Music&Tweaks mod to use widescreen resolutions. This way, you won't have the game lagging on highpoly cars

    Reply