[REL] rF2 Shared Memory Tools for Developers

Your answer is not clear at all. So if I do a fast first full lap then I have to go even faster just for the delta to start working? I haven't seen this stated anywhere else. I also haven't seen anyone else having this problem which I thought a bit strange. I spread the message as I am not sure whether the issue is with the individual huds or the memory plugin or something else. Cheers
Yes it's a well known old bug of the HUD of rF2.
 
Amazing isnt it? I mean as new rf2 player, you are immediatly facing this bug. You buy a new sim, saying its so great, and you SEE a simple yet easy to fix malfunction right away. (Next to total messed fuel consumption values sometimes). And S397 does not care. Do they play their own game at least sometimes???
 
Hi all, I have an issue with the shared memory plugin on rf2, since I cant turn it on in game. It says "on (after restart)", but when I restart the game it appears off again.
Any help??
Thanks!
 
I don't know what's causing that but you can do it manually, edit c:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\CustomPluginVariables.JSON (or wherever you have rFactor installed) which should have an entry something like this

Code:
  "rFactor2SharedMemoryMapPlugin64.dll":{
    " Enabled":1,
    "DebugISIInternals":0,
    "DebugOutputLevel":0,
    "DedicatedServerMapGlobally":0,
    "EnableDirectMemoryAccess":1,
    "UnsubscribedBuffersMask":32
  }
Note the space in
Code:
" Enabled":1,
 
I don't know what's causing that but you can do it manually, edit c:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\CustomPluginVariables.JSON (or wherever you have rFactor installed) which should have an entry something like this

Code:
  "rFactor2SharedMemoryMapPlugin64.dll":{
    " Enabled":1,
    "DebugISIInternals":0,
    "DebugOutputLevel":0,
    "DedicatedServerMapGlobally":0,
    "EnableDirectMemoryAccess":1,
    "UnsubscribedBuffersMask":32
  }
Note the space in
Code:
" Enabled":1,
Y7kDJn0

Thats odd because I don´t have that file :/
 

Attachments

  • Capture.PNG
    Capture.PNG
    76.4 KB · Views: 419
It's a basic part of rFactor whether or not you use this plugin. If it's not there it might explain why you can't turn the plugin on! No, if it's not there there won't be anything to turn on.
 
Does anyone have a fix for that? I have the same problem.... Check files didn't helped.... And yeah you guessed right, nothing will be turned on.....
 
09/07/2020 - v3.7.14.2

This version introduces input buffers. See "Input Buffers" readme section (on Github) for more info.

Plugin:
* Expose `rF2PitInfo` and `rF2Weather` buffers. Special thanks for prototyping `AccessPitMenu` and `CheckHWControl` plugin functionality go to Seven Smiles.
* Expose `rF2HWControl` input buffer, which allows sending limited number of inputs into the game.
* Expose `rF2WeatherControl` input buffer, which allows changing weather conditions dynamically.
* Expose `rF2PluginControl` input buffer. Allows requesting additional plugin features dynamically.
* Experimental: Expose `rF2RulesControl` input buffer, which allows sending rules input into the game.
* Intenral: rework tracing and reduce code duplication.

Monitor:
* Updated to demo newly added features.

Thanks to @The Menace for helping testing and tracking down a bug in an early version
 
Last edited:
Hi Iron Wolf,
I used your rf2Monitor code, and removed almost everything, just to use it as a FFB Clipping Tool Buzzer.
Basically the only thing made was an added "if" to play the buzzer if the FFB value is 1 (using the Abs for the negative values)
Hope you don't mind, since for me it's easier to test the clipping this way.
As a Logitech user, using your code made easier to setup my wheel.
I didn't want to start a new thread, because to be honest, I don't want to "steal" you excellent work.

Thank you for your amazing tools and add-ons.
 

Attachments

Hi Iron Wolf,
I used your rf2Monitor code, and removed almost everything, just to use it as a FFB Clipping Tool Buzzer.
Basically the only thing made was an added "if" to play the buzzer if the FFB value is 1 (using the Abs for the negative values)
Hope you don't mind, since for me it's easier to test the clipping this way.
As a Logitech user, using your code made easier to setup my wheel.
I didn't want to start a new thread, because to be honest, I don't want to "steal" you excellent work.

Thank you for your amazing tools and add-ons.
Absolutely - you can use it for your uses and share it with others :) Though stuff like that better fits simhub that uses my plugin for FFB meter and would surely allow script doing what you wanted.
 
Last edited:
So a widley used tool uses, or lets say demonstrates, cheater tech, even by publishing code ?
And shows that cheating can work (and how)?
 
Back
Top