Is there a way to bind the info bars(pressure,wear,temp) to a key so i can cycle through them while driving?
Not sure I understand you but if you review the overview section you'll see that it says "Besides the always visible stuff (gear, speed and rpm light), the app is divided into five sections, contents of which can be switched either by mouse or by keyboard (Alt + A to switch between sections, Alt + S to toggle available data in the selected section)."Is there a way to bind the info bars(pressure,wear,temp) to a key so i can cycle through them while driving?
I have much less hair after mmany days looking for this solution. This tip should be added to the overview / FAQ. Thank you!!I belive I've just found the solution for me. Do not use the CAPITAL letters in the folder name of your "mod". It seems that Sidekick works only when there are not capital letters used.
For example:
Folder name: porsche_911_GTE
Sidekick Compounds File: porsche_911_GTE.ini
[porsche_911_GTE_slick_supersoft_ss]
IDEAL_PRESSURE_F=26
IDEAL_PRESSURE_R=26
MAX_OPTIMAL_TEMP=80
MIN_OPTIMAL_TEMP=50
And this doesn't work but when I've delted ini file and changed the car folder name to:
porsche_911_gte, then CM auto-generated the file: porsche_911_gte.ini
[porsche_911_gte_slick_supersoft_ss]
IDEAL_PRESSURE_F=26
IDEAL_PRESSURE_R=26
MAX_OPTIMAL_TEMP=80
MIN_OPTIMAL_TEMP=50
...and it works!
So avoid capital letters in car folders and especially in sidekick componouds .ini file names, and tags inside the file.
Hope it will solve your problem also!
His last post was in 2020. It's 99.99% NOT getting an update. Although I'd love to see onewill this receive an update now that LFM has made the AC integration?
I've seen Sidekick corrupt various bits of data on many occasions (e.g. the best lap data). For me, the trigger often appeared to be me taking a screenshot right after crossing the start/finish line. Resetting the best lap data for that car/track combo was my usual fix.anyone else having the problem that sidekick changes the odometer reading for total distance driven sometimes to a completely random number? I think it happens when I use NVIDIA capture (to save video for a report for example). sometimes i can just delete sidekick and install again so fix it, sometimes it writes the wrong odometer to CM so i have to reset the stat in CM, which sucks.