Ajira Strobolizer 4000



Table of Contents

  1. Introduction
  2. User interface
  3. Installation, upgrade and removal
  4. Application log and error messages
  5. Game controllers and buttons
  6. Vehicle profiles
  7. Volume levels
  8. Hash values
  9. Version history
  10. Questions & answers
  11. Tips & tricks



1. Introduction

Ajira Strobolizer 4000 extends Studio 397's rFactor 2 racing simulation by offering several new functionalities:

System requirements and performance impact are very low. Processor load should stay under 1 % while memory usage should not rise above 30 MB. Microsoft Windows 10 operating system is preferable as it's needed for "Wake PC from Blank Screen" to work. Also .NET Framework 4.7.2 or newer is required. Only 64-bit version of rFactor 2 is supported.


Back to top


2. User interface

  1. Application log writes down all actions since the last time it was started
  2. Tick checkbox to start detecting game controller button for headlights
  3. Select rFactor 2 headlights keyboard key (same key must be defined in rFactor 2 game settings)
  4. Change pulse count for headlights strobing
  5. Tick checkbox to start detecting game controller button for "Wake PC from Blank Screen"
  6. Tick checkbox to start detecting game controller button for vehicle mode
  7. Select vehicle profile
  8. Set gear shifting points for selected vehicle
  9. Set engine overrev warning limit for selected vehicle
  10. Buttons for adding, renaming, copying and removing vehicle profiles
  11. Enable or disable connection to rFactor 2 telemetry data
  12. Set volume levels for currently selected vehicle
  13. Test volume levels
  14. Open this user manual in your favorite web browser
  15. Define monitored game controllers
  16. Import vehicle profile(s) from file
  17. Export vehicle profile(s) into file
  18. Save global settings and/or values for currently selected vehicle


Back to top


3. Installation, upgrade and removal

Installing or upgrading Strobolizer is simple:

  1. If you're upgrading from previous version back up vehicle profiles by exporting all profiles into file. Settings and vehicle profiles from previous version should stay intact but it's always good idea to back up your data before upgrading
  2. Download installer zip-file from Studio 397 forums to your PC
  3. Extract .msi file from the zip-file. If you lack archiver utility download and install for example free PeaZip
  4. Run installer by double-clicking extracted AjiraStrobolizer4000_1.1.0.msi file and follow on-screen guidance. Shortcuts for launching Strobolizer will be created on both desktop and start menu

During Strobolizer startup rFactor 2 folder will be searched for telemetry plugin installation. If this automated installation fails sound effects might not be heard while driving. If problem occurs see Q&A how to fix it.

When new Strobolizer version is available user will be notified during application startup and asked to be redirected to the download site. Upgrading to latest version is always recommended but not mandatory. Installer files (.zip and .msi) can be deleted after installation has completed.

Strobolizer can be removed by using standard Windows removal method: Start --> Add or remove programs --> Select Ajira Strobolizer 4000 --> Uninstall


Back to top


4. Application log and error messages

Application log writes down all actions this application has done since the last time it was started. Logging will be disabled when application has lost it's focus for example during driving to minimize memory footprint and possible problems caused by excessive amount of text. If for some reason logging should be done at all times, for example to troubleshoot whether application connected to rFactor 2 telemetry data, it can be enabled by checking "Force Logging". Contents can be copied into clipboard by clicking "Copy to Clipboard". Once application is closed application log will be cleared.

Lots of work and attention has been done for making Strobolizer as robust as possible but as every system is different unforeseen surprises are always possible. If unexpected error happens application sends error message to the author for review. This can be invaluable help for allowing to squish those last remaining bugs and making this product even more redundant. Error reporting can be prevented by disabling "Report Bugs". Please note Strobolizer values your privacy and sends information anonymously.


Back to top


5. Game controllers and buttons

Available game controllers are detected automatically and are listed into application log. Headlights functionality requires two things. Game controller button must be mapped by enabling button detection and then pressing desired game controller button. Secondly a keyboard key must be selected from the drop-down list and this same key must be defined in rFactor 2 in-game game controller settings for headlights. Short press switches lights on/off. Long press (over 300 milliseconds) activates strobing for a short duration; headlights will be flashed multiple times defined by the value in Pulses drop-down list.

Wake PC from Blank Screen requires game controller button mapping but unlike headlights it doesn't require keyboard key. If you're already running out of available steering wheel buttons it's possible to select already reserved button - just make sure to use some trivial button which doesn't interfere with driving / multiplayer game. Be careful with this functionality while driving as it probably causes black screen for a second or two. It's also very much possible it could even cause screen to freeze completely if your system isn't compatible. Always test this functionality beforehand as game and operating system updates might change behavior. This functionality is meant as last resort trying to resolve suddenly appeared graphics adapter problem such as screen freeze or drop in framerate / jerky playback. Virtual Reality glasses probably aren't compatible but you might have better luck with traditional displays. Also Windows 10 is required as what this does is echo keyboard combination Shift + Control + WinKey + B which isn't available for older Windows operating systems.

Vehicle mode button works similarly to headlights. Short press cycles next vehicle mode. Long press (over 300 milliseconds) will revert vehicle profile back to base mode. After change beep sounds are played to indicate which vehicle mode was selected.

Button mappings can be tested before entering the game by pressing buttons and watching for response in application log. After button mappings have been done remember to store changes permanently by pressing the "Save" button.

Game controllers can be set under monitoring. Application will warn if game controller has not been switched on. Game controllers which have Strobolizer buttons mapped are automatically monitored. To include other game controllers press "Monitor..." button --> tick checkboxes for game controllers which needs to be monitored --> press "Save" button. Test sound effects by pressing Play button to verify warning sound is heard as Strobolizer is using sound effect provided by Windows operating system. Even though game controller monitoring is great aid to avoid mistakes it's still good practice to always check your individual game controller operations too before entering an online event.


Back to top


6. Vehicle profiles

Default vehicle profile is always present and can't be deleted.

New vehicle profiles can be added via dialog window by pressing the "New" button. Preferable way is to use automated detection as this will read vehicle name and class from the game and later on allows Strobolizer to automatically switch vehicle profile to match vehicle selection change in rFactor 2. This can be achieved by manual addition too but you might make small mistake with name or class.

To add vehicle using automated detection in new vehicle dialog window: press "Start Detection" button and then enter the game --> Select vehicle --> Click "RACE" and wait until garage screen appears. For this to work telemetry data should be available meaning "Connect rF2" setting should be enabled (default setting). If for some reason connection to the telemetry data is not wanted it can be disabled but remember this will also disable automatic profile switching and all sound messages/warnings. Dialog window's "Use Current Settings" option does exactly what it says; it uses currently shown shift rpm, overrev warning and volume values, and stores these to the newly added vehicle. If disabled, values from default vehicle profile will be used instead.

Usually vehicle addition is done in two phases; first you add new vehicle, come back, adjust values to your liking and save changes. If desired values are known beforehand vehicle can be added in a single pass; adjust shift rpm, overrev warning and volume levels --> press "New" button --> Discard vehicle changes --> Enable "Use Current Settings" --> Add new vehicle either via automated detection or manually.

Selected vehicle profile settings can be changed by altering values in the main view. "Shift rpm" values are used to inform driver with a sound effect to upshift to the next gear. If vehicle has for example 6 gears fill values from 2nd to 6th. "Warn rpm" warns driver if engine revs rise above warning level. "Reset rpm" can be left empty but if for some reason subsequent warning sounds must be suppressed until revs fall under certain limit then this setting comes handy. After changing values remember to store changes permanently by pressing the "Save" button.

Vehicle renaming, copying or deleting are done by selecting vehicle profile and pressing "Ren", "Copy" or "Del" button accordingly. If base vehicle mode is selected action will affect all vehicle modes with same name and class.

Vehicle profiles can be imported and exported from/to file by pressing either "Import" or "Export" button. When importing be careful not to accidentally overwrite existing profiles. Volume levels can be excluded during importing if needed (default or existing vehicle's values will be used instead).


Back to top


7. Volume levels

Volume levels are bind to selected vehicle profile. Please note lap timing change warns user when lap timing has been disabled for the current lap; either caused by a track cut warning or driver entering pits. Due to limitation in current rFactor 2 telemetry data implementation it is not possible to detect multiple track cut warnings per lap. Hopefully this will change in the future. Volume levels can be tested by pressing Play button. After changing values remember to store changes permanently by pressing the "Save" button. Individual sound effect can be disabled by setting volume level down to zero.


Back to top


8. Hash values

Version 1.1.0

Version 1.0.1

Version 1.0.0


Back to top


9. Version history

Version 1.1.0 - 2020.05.07

Version 1.0.1 - 2020.03.02

Version 1.0.0 - 2020.02.28


Back to top


10. Questions & answers


Back to top


11. Tips & tricks

@echo off

echo Closing Discord...
taskkill /f /im Discord.exe

echo Starting Ajira Strobolizer 4000...
start "" /D"C:\Program Files (x86)\Ajira Racing\Ajira Strobolizer 4000\" "AjiraStrobolizer4000.exe"

echo "Changing replay recording to OFF"
powershell -Command "(gc -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\player.JSON') -replace '\"Record Hotlaps\":1', '\"Record Hotlaps\":0' | Out-File -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\player.JSON'"
powershell -Command "(gc -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\player.JSON') -replace '\"Record Replays\":1', '\"Record Replays\":0' | Out-File -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\player.JSON'"

echo Waiting 5 seconds before launching rFactor 2 via Steam
@timeout /t 5 /nobreak

echo Starting rFactor 2 via Steam...
"C:\Program Files (x86)\Steam\Steam.exe" -applaunch 365960 -nosplash

@echo off

echo Closing Discord...
taskkill /f /im Discord.exe

echo Closing OneDrive...
taskkill /f /im OneDrive.exe

echo Switching into "PC screen only" display mode...
DisplaySwitch /internal
echo Waiting 5 seconds for display mode to change...
@timeout /t 5 /nobreak

echo Starting Ajira Strobolizer 4000...
start "" /D"C:\Program Files (x86)\Ajira Racing\Ajira Strobolizer 4000\" "AjiraStrobolizer4000.exe"

echo Starting Game Controllers...
start "" /D"C:\Windows\System32" "C:\Windows\System32\joy.cpl"

echo "Changing MoTeC telemetry to OFF"
powershell -Command "(gc -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\DAMPlugin.ini') -replace 'Active on startup = 1', 'Active on startup = 2' | Out-File -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\DAMPlugin.ini'"

echo "Changing MoTeC telemetry to ON"
powershell -Command "(gc -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\DAMPlugin.ini') -replace 'Active on startup = 2', 'Active on startup = 1' | Out-File -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\DAMPlugin.ini'"

echo "Changing replay recording to OFF"
powershell -Command "(gc -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\player.JSON') -replace '\"Record Hotlaps\":1', '\"Record Hotlaps\":0' | Out-File -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\player.JSON'"
powershell -Command "(gc -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\player.JSON') -replace '\"Record Replays\":1', '\"Record Replays\":0' | Out-File -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\player.JSON'"

echo "Changing replay recording to ON"
powershell -Command "(gc -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\player.JSON') -replace '\"Record Hotlaps\":0', '\"Record Hotlaps\":1' | Out-File -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\player.JSON'"
powershell -Command "(gc -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\player.JSON') -replace '\"Record Replays\":0', '\"Record Replays\":1' | Out-File -Encoding Default 'C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\player.JSON'"

echo Starting FanaLEDs...
start "" /D"C:\Program Files (x86)\FanaLEDs" "C:\Program Files (x86)\FanaLEDs\FanaLEDs.exe"

echo Starting NVIDIA Control Panel...
start "" /D"C:\Program Files\NVIDIA Corporation\Control Panel Client" "C:\Program Files\NVIDIA Corporation\Control Panel Client\nvcplui.exe"

echo Starting CrewChief...
cd "C:\Program Files (x86)\Britton IT Ltd\CrewChiefV4"
start "" /D"C:\Program Files (x86)\Britton IT Ltd\CrewChiefV4" "C:\Program Files (x86)\Britton IT Ltd\CrewChiefV4\CrewChiefV4.exe" RF2

echo Waiting 5 seconds before launching rFactor 2 via Steam
@timeout /t 5 /nobreak

echo Starting rFactor 2 via Steam...
"C:\Program Files (x86)\Steam\Steam.exe" -applaunch 365960 -nosplash

@echo off

echo Closing Ajira Strobolizer 4000...
taskkill /im AjiraStrobolizer4000.exe

echo Closing NVIDIA Control Panel...
taskkill /im  nvcplui.exe

echo Closing FanaLEDs...
taskkill /im FanaLEDs.exe

echo Closing CrewChief...
taskkill /im CrewChiefV4.exe

echo Closing rFactor 2 Launcher...
taskkill /im "Launch rFactor.exe"

echo Switching back to cloned display mode...
DisplaySwitch /clone

echo Switching back to extended display mode...
DisplaySwitch /extend

echo Starting OneDrive...
start "" /D"C:\Users\YourUsername\AppData\Local\Microsoft\OneDrive" "C:\Users\YourUsername\AppData\Local\Microsoft\OneDrive\OneDrive.exe" /background


Back to top



© 2020 KeiKei