Racer v0.8.28 released!

Ruud

RACER Developer
Since X-mas is still so far off. ;-)

Get it at http://www.racer.nl/download/racer0.8.28.zip (83Mb)

This one does seem close to v0.9, except perhaps for some replay enhancements.

Changes (some already posted in the v0.8.27 thread):
- Minimap was painted even if no splines were present
- SMD chase cam shadow focus is now on the car, not near the camera itself
- 3rd shadow split distance reduced to 500m for detail. Last split is now faded out.
- Large car CG offset could get some 3D objects culled incorrectly.
- 'Select car' screen gave car.ini errors which were incorrect (due to fast loading of only the first part of car.ini)
- Force feedback was passed to steering wheel even if steering was not done through that wheel
- resolution.render_aspect didn't work; fixed
- Shadowmapping tweaked again for even less Z correction
- Pacejka Player tweaking lambda values wasn't correct for MF5.2 curves
- Backfire 'likeliness' removed until we get better turbo behavior (>v0.9)
- 'grip 0.5' appeared to also reduce engine torque. Fixed (doubly stored data in the code, as if grip=1).
- Only the first 2 splits are blurred
- Autoclutch RPM now slams the clutch harder around the optimal RPM. Works to get at the optimal torque rpm
when driving off, although it is a bit harsh. Seems ok when I look at g-force graphs though.
 
Back to audio pitch_scale and pitch_offset
They only seem to work outside of the sample definition.
...I'd always assumed this was for any sample or sample set, I've been struggling for about 6 years trying to get a turbo that just built up about 50% pitch over the entire engine rpm, rather than going from a dull whistle to a full-on screech :D

Sounds more like a pitch_max than per-sample pitch_offset/scale?
And there's no turbo audioset yet, and no real turbo simulation, so it would be kind of a hack... haunting us for many years. ;-)
 
!?! You dare speak of the FORBIDDEN COMMAND!!

The you-know-who command? :)
We do need it; for customers we use an auto-reset if someone steps out of the road, or rather, designated driving area. For circuits the rule of 'anything that is road is ok' was ok, but then we got to a rally gravel track... Hm. So now you can specify surfaces where autoreset would need to work. Ofcourse, for desktop use, it's not as important since you almost always have a keyboard nearby to press Shift-F.

The AI is fixed, was just a small thing due to the spline vs mesh (use_mesh_hits) fix, where the AI started tracking mesh polygons now & then instead of only splines.
 
The you-know-who command? :)
We do need it; for customers we use an auto-reset if someone steps out of the road, or rather, designated driving area. For circuits the rule of 'anything that is road is ok' was ok, but then we got to a rally gravel track... Hm. So now you can specify surfaces where autoreset would need to work. Ofcourse, for desktop use, it's not as important since you almost always have a keyboard nearby to press Shift-F.

That makes sense. It's easy for us to forget about the commercial side sometimes.

Alex Forbin
 

Latest News

Are you buying car setups?

  • Yes

  • No


Results are only viewable after voting.
Back
Top