Fixup Plugin Support

There was a problem! If you are using Version 2.1 of FixUp together with the Czech plugin track Sardian crashes to the desktop. How can I fix it?

Try this for a laugh: open fixup.ini, and change centerMenu=1 --> centerMenu=0, and see if that "fixes" it. If you're using anything other than 4:3 resolution, it'll obviously stretch the HUD.
 
Well, the crash is just by chance and not related to FixUp in any way.

Sardian does have at least one bug related to the texture index of an interactive object.
This problem has been already reported by some users and I was able to reproduce the problem in the debugger.
No easy way, if any, to fix this issue by applying a patch.
The track needs to be reworked somehow ...
 
When it comes to launching Sardian, I can say that FixUp 2.1 is "better" than 1.13 was. But that's only my experience with the settings I happen to use.

In Czech plugin I prefer using 1440x900, and with v1.13 when that resolution is combined with centerMenu=1 (basically loading _1024 textures instead of _1280 ones), launching Sardian fails every single time. However, with FixUp 2.1, I get these same settings to work BUT ONLY IF headGasketDurability is set to either 0 or 1, because anything between 2-10 causes a CTD. It sounds so amazing that it has to be true.

But again, this isn't a solution for anyone else but me. It's just a shame I use 1.13 for all the other cars than NGP ones. ;-)
 
Last edited:
Porridge, my friend, sometimes those computer thingies are really weird.
Every single patch in FixUp is absolutely independent of each other, so it is just a matter of which bytes happen to be in memory, and apparently, where in memory.

Only things not in memory happen to not cause any trouble. Maybe these are them anti-thingies I have heard of ...

When loading Sardian as sure as death and taxes an error occurs when reindexing the textures.
But, the erroneous index causes an address calculation result to point SOMEWHERE, but definitively not at the requested texture object.
So, depending on the current memory layout (loaded plugins, applied patches, ...), the address might be located in an inaccesible area and an address violation occurs, i.e. the game crashes, sooner or later.
 
Ok, finally the Sardian issue has been fixed.
And maybe some other tracks with such texure index errors.

Link in the first post updated to the new version 2.3 of the FixUp plugin.

Report any problems here, as usual.
 
New version 2.4 of the FixUp plugin available:

A new feature called adaptive force feedback (FFB) has been implemented.

The effect is noticable when vsync is on, the FFB becomes smoother and more responsive.
The more powerful your hardware, the better the FFB.


Note:
If you still prefer to run with vsync off (generally not recommended) you may switch off that new feature in the INI file with adaptiveFFB=0.
 
Later than the version published yesterday ??
Well, that was a good one.

Anyway, you can remove Z.DLL as FixUp 2.8 includes a better fix for the Z-Modeller cars.
 
LOL. Didn't realize it was released yesterday. I didn't see any info about it in the post when I downloaded it. Seems to be there now. That's quite a coincidence. First time I ever install RBR in over 7 years and this file is released same day I go to look for it.
 
FixUp plugin has been updated to version 2.9.

Excerpt from the readme:
f) V-Sync Off Sound Issues Fix
When running the game with v-sync off, especially tire sounds are not being
emitted correctly. This is best noticeable on tarmac stages where the tire
screaming sounds are more pronounced.
Actually there are two effects. One effect is that the tires seem to scream
intermittently without actually any noticeable wheel slip. The other effect is
that no noticeable tire sound is emitted when the tires actual have slip, like
when braking before entering a corner.
The patch uses a fixed sound emission rate to address these issues.

This fix may be disabled if you prefer the old, buggy behaviour (see
"Configuration", parameter "soundRefreshRate").

At first start there will be inserted a new entry into the FixUp.ini file, having a default value of 0 (zero):

; Sound refresh rate for emitting all sounds.
;
; Especially useful if playing the game with v-sync off, but applies as well
; when v-sync is active.
;
; 0 - disabled, use builtin refresh rate
; >0 - sound refresh rate in Hz
;
; Reasonable values are in the range 30 to 90.
; Recommended value: 60
;
soundRefreshRate=60


Recommended settings for optimal perception (depending on your hardware):

fixVSync=1
vSyncActive=0
adaptiveFFB=0
soundRefreshRate=60
 
Hello all. I have problems on RBR since two years. It doesnt run smooth as in the past.... I've tried every different config on fixup, rbr.ini, graphic card software, hdmi and vga cables, changing monitor, adaptativeFFB, soundrefreshrate, vsync, processor, triplebouffers, everything... and the game always have micro stuttering in every single way. I have a GTX960. I dont know what to do more.... any ideas?
 
My problem were solved forcing vsync OFF on nvidia software. But with that, comes another problem.... my sequential gearbox (separated from wheel) is jumping gears like from 2nd to 4th, or when I down shift, from 2nd to N.... I've already activate the gear protection in game, but it still the same. In rfactor 2 or Raceroom for example we can prevent this in the menu or in read files, we can ajust time to between to gear change, but on RBR i think its not possible... maybe on next fixup?? :)
 
Last edited:
FixUp plugin is available here:

RBR FixUp plugin

Notes:
As usual, details provided in the readme.

Furthermore, I recommend to change the file
"Audio.ini"
in the RBR root directory as follows:

[OPTIONS::SOUNDS]
NumberChannels=64

This should significantly improve the quality of the sounds.
Especially you should then be able to hear the rain falling and some more gimmicks.


History
3.1 2020-02-18
New features
* fix season loading crash

3.0 2019-04-19
New features
* enhanced LBS file loader
* new tool splitlbs.exe to split LBS file into LBS+LB2 for the new loader

2.9 2017-02-14
New features
* configurable sound refresh rate to address tire sound issues

2.8 2016-12-10
New features
* Z-Modeler fix

2.7 2016-02-11
New features:
* another sound buffer fix, this time in the context of the mixer
* adaptive FFB has configurable FPS now
* added FFB steering wheel dead zone
* ten times the number of fences for add-on tracks

2.6 2015-03-01
* no calibration of FFB in replay
* adaptive FFB disabled by default

2.5 2015-01-27
New features:
* adaptive force feedback configurable

2.4 2015-01-19
New features:
* adaptive force feedback

2.3 2015-01-07
New features:
* check and fix textures indices after loading the LBS file

2.2 2014-09-21
* improved support for online plugins

2.1 2014-07-03
New feature:
* sound bug fix: fixed calculation of gravel pitch

2.00 2014-03-02
New features:
* show patch revision in dialog
* removed material maps patch, which is now part of the PhysicsNG plugin

1.13 2013-07-14
New features:
* fix sanity check of index in rally names array while loading
car flip animation

1.12 2013-04-08
New features:
* check and fix name offsets of animation ids in DLS data

1.11 2013-03-28
New features:
* material maps fix

1.10 2013-02-28
New features:
* fix collision mesh calculation

1.9.3 2012-12-31
New features:
* check and fix DLS data

1.9.2 2012-12-25
New features:
* processor of the main thread configurable

1.9.1 2012-12-21
New features:
* dropped RBRDLL support
* fixed car damage speech stuff
* set main thread affinity to first available processor
1.9
New features:
* proxy access to FixUp features
1.8
New features:
* sound distance fix
* engine sound
* check interactive object ids

Have fun!

Cheers,
Uncle G.


@WorkerBee i believe you are the best person to answer my question! ahahah

There is any fix to monitors ultrawide with the issue of "flickering textures?!"

Thanks in advance.
 

Attachments

  • 86982411_10216434115267743_1644777521507467264_o.jpg
    86982411_10216434115267743_1644777521507467264_o.jpg
    162.3 KB · Views: 139

Latest News

Are you buying car setups?

  • Yes

  • No


Results are only viewable after voting.
Back
Top