-
Notifications
You must be signed in to change notification settings - Fork 9
Frequently Asked Questions
All build files currently available from Releases page were remotely built from source code using automated github actions, which the entire build > upload > release
process is fully automated and there is no intervention. Additional SHA256
hash sum for each build file was also generated during the build process and included in release notes. Workflow configuration code is in .github/workflows
directory in repository, and build log can be viewed from Workflows
in Actions page. As long as the build files are downloaded from Releases page with matching SHA256
hash sum, those files are clean and safe to use.
Alternatively, for those still hold doubts and worried about false positive
reports, see Run from source or Build executable for windows for instructions on how to run
or build
the app from source code
.
No, TinyPedal cannot crash game or cause game to malfunction. TinyPedal only accesses (reads) shared memory data that output by shared memory plugin. TinyPedal does not directly interact with game.
It works as following:
[Game API]
<---> [Shared memory plugin]
---> [Shared memory]
<--- [TinyPedal]
- By enabling
Shared memory plugin
in game,game API
sends data toShared memory plugin
. -
Shared memory plugin
gets data fromgame API
, then outputs API data intoShared memory
blocks. - TinyPedal reads data from
Shared memory
blocks, then displays data on screen.
For windows platform, currently it is only possible to capture overlay by using Display Capture
to capture entire screen in OBS.
For Linux platform, may need to turn off Enable Bypass Window Manager
option from main menu -> Compatibility dialog.
TinyPedal does not natively support displaying overlay in VR.
However there are some VR programs capable of projecting application windows into VR. One of the known program is CrewChief
.
Game does not provide track map data. Map data has to be recorded from player's driving route, which requires at least one complete & valid lap to be done first in order to generate map. And map recording function is handled by Mapping Module, make sure it is enabled.
A common issue for using Windowed or Borderless mode is that frame rate would become unstable or stuttering. Here are a few tips that could help improve smoothness:
- Turn on and set
maximum frame rate
in graphics card control panel. Limiting maximum frame rate is usually the most effective way to stabilize FPS. All you need is to setmaximum frame rate
value slightly higher than your current monitor refresh rate. For example, if your monitor refresh rate is 60hz, then setmaximum frame rate
to70
would be enough. - Turn off
Fullscreen Optimizations
from game's executable file under windows 10 or 11. - Reduce
Post Effects
setting in game.
- Make sure The Iron Wolf’s rF2 Shared Memory Map Plugin is installed. See Requirements section for details.
- Make sure the plugin is enabled in game.
ForrFactor 2
, in gameSettings
->Gameplay
page, findPlugins
section and toggle onrFactor2SharedMemoryMapPlugin64.dll
.
ForLe Mans Ultimate
, user may have to manually enable plugin by editingCustomPluginVariables.JSON
file (set" Enabled"
value to1
) underLe Mans Ultimate\UserData\player
folder. After plugin enabled, must restart game to take effect. - Make sure
Spectate
mode is disabled in TinyPedal main config windowSpectate
tab.
Some vehicle mods have certain telemetry data output disabled in mod file, which the data is not accessible from game API, hence it is not possible to display the data.
RF2 API only provides a generic detached-parts detection boolean value, which returns True
if any parts were detached. It cannot tell which parts were lost. So in order to avoid confusion, detached parts display is not provided.
This is normal behavior, the damage values reported by RF2 API are not 100% same as in-game HUD, which they sometimes report slightly different readings.