Hey man. I tried to reproduce the issue with the clutch, and couldn't. Here's a video: Am I missing something? All the other bugs are fixed for version 1.11. Thank you once again.
I'm not sure how this video proves that issue isn't there since like I said we can't see % on native input meter and the difference isn't that big to spot it via naked eye imo but it's here at least for me this video only really shows that % match on both widgets u included in the hud - not even always cause there are instances where it shows like 1% difference on the input if u will stop video like I said I did my measurement based on few different things I recently tested 2 wheels with dual clutch - CSW2.5 + McLaren rim for like 2 weeks and now Moza R12V2 + KS - in both cases this happened, I set clutch bite point and it didn't match with the hud while in Fanatec I additionally had the correct number displayed on the rim and now on KS I don't have number on the rim but bite point doesn't match with the number displayed on hud in this case too but I don't think it's dual clutch issue since I also assigned clutch to the foot pedal, opened TLCM app and then looked at input there and input on the hud, app shown 30% while hud shown like 25 or 6 this is with clutch assigned to foot pedal on TLCMs, u can see input on their app and how it's displayed on SealHUD and the % also match when I have it on dual clutch cause then I set that bite point to 29 and it also displays 25
SealHUD receives clutch, brake, and throttle data directly from RaceRoom, based on the ClutchRaw, BrakeRaw, and ThrottleRaw parameters. Your steering wheel driver sends this data to RaceRoom, and you can check the exact values RaceRoom is receiving by using the "Telemetry" widget in SealHUD. I suggest enabling "Telemetry" and checking the percentages RaceRoom is receiving. Once you activate the widget, a button will appear at the bottom left of your screen. Press this button and enable ClutchRaw, BrakeRaw, and ThrottleRaw parameters. You will see something like this: These are the values used by SealHUD and RaceRoom.
ClutchRaw shows 0.24 SealHUD Input Meter shows 25% dual clutch bite point is set at 29 in Moza App and displays proper values iRacing since I just reinstalled it and did the binds configurations like hour ago, I assume should work in other titles too then Thrustmaster TLCMs % u can see on the screen above, it's the same as on Moza dual clutch and like I said, it's only clutch issue - other pedals values match between Thrustmaster TLCM app (so external measurement), telemetry and input meter from SealHUD so idk is this some Raceroom bug? there is another clutch bug introduced recently to the game where it just cut the clutch input completely when u moving faster than 64km/h so maybe that's connected
This is because Telemetry widget is limited to 2 decimal digits. 0.xx Is not showing you 0.xxx. Just that. Look: I can't tell you exactly what's going on, man. You should check all wheel settings in RaceRoom and in Wheel's driver and ask for help on Discord if everything looks correct.
I understand how rounding works if these telemetry values really shows how the game read this input and not only how hud register it then there is some issue within Raceroom because my clutch % match the Moza App bite point numbers in other sims like I already said it's hard to really "confirm" that since they decided it's smart to not inlcude the % in both menu and their native input meter which is dumb asf for various reasons including this kind of troubleshooting or things like pedals missing that last 1% on throttle or something, if u are any hud u won't be able to figure this things out - I asked about it being added right after this "update" but knowing Raceroom it maybe will happen in 10 years or never cause they already forgot about it I know it's hard to "check" for u if it match input registered by windows or not if u don't have dual clutch because with dual clutch it's simple since it's fixed value that should be displayed the same in all sims but for some reason it isn't in Raceroom but like I said it isn't dual clutch issue though cause same disparity happens on foot pedal but obviously with foot pedal only it's much harder to figure this out the only way to check if it's happen like that for u too is using some external measurement device in the same time as u pressing and looking at these in-game numbers, not sure which gear do u have so not sure which soft u could use to see that difference I'm noticing I don't really know what I can add more since we are repeating everything at this point if u are sure that "telemetry" shows the raw Raceroom data then we need to summon someone from Raceroom here because it may be related to that clutch bug happening atm in the game - I noticed that issue with my real clutch input not matching hud numbers only recently but not because it's new but because it's first time when I have wheel with dual clutch where I can set value that should be the same everywhere and before when I only had foot pedal I never compared the hud data to data read by windows in the same time EDIT I just installed Raceroom Racing Overlay to check it and it also displays 25% in HUD when I press clutch paddle which means this probably really is Raceroom issue with how it reads the clutch I created topic about this in "HELP" on discord, maybe someone will look at it
Sorry man .... haha. No offense ... I just like to clarify everything. I don't have a dual clutch, so unfortunately I can't reproduce or validate this specific behavior on my side. In fact, I don't even know much about how dual clutch systems work. =| What I can confirm is that the values shown in Telemetry > ClutchRaw are the exact values coming from r3e.data.ClutchRaw. Those are the values provided by RaceRoom shared memory, and SealHUD does not process or modify them in any way. It simply displays whatever RaceRoom exposes through shared memory. If I'm not missing anything, this doesn't look like a SealHUD issue. SealHUD is only displaying the raw shared memory values exactly as they are received from RaceRoom, so from the HUD perspective everything is working as intended. If there is indeed a discrepancy between the values reported by Windows/Moza software and the values exposed through r3e.data.ClutchRaw, then this would probably need to be investigated by the RaceRoom developers themselves. I don't think KW developers are actively following the SealHUD thread, so it might be worth creating a separate topic on the RaceRoom Discord (Help & Support) or reporting it directly to them. Tell me if you think I am wrong about anything about this, Mike.
"Consumption" widget does that: https://forum.kw-studios.com/index.php?threads/sealhud-webhud.20675/page-18#post-260502
Hello! I've had it happen for the second time now, that I have weird 1s freeze, whereafter SealHUD partly disappears or reads nonsense values. This time luckily in a LB session, the first time was shortly after the start of this years' DTM Esports Pre-Show race, meaning I had to fuel save for ~60min without knowing how much I need. Not a great situation. But anyway, I just wanted to report this problem. In the moment the game froze, I have not done anything in particular which initiated this error. I suspect this issue is probably RaceRoom's fault for bugging out and maybe not properly feeding info to CrewChief/SealHUD. I attached 2 screenshots, one showing how my HUD looks normally when in a LB session and one of the aftermath. I know from the DTM Race, that the TV Tower forgets what player to highlight so it just shows the Top 10 drivers (I have "Show Full Driver Grid" disabled) and the relatives start showing random players, saying they are millions of seconds apart. Maybe somebody else has/will experience this too and can find this post, so they know they aren't the only ones
@Diego Junges I did Monday a race and everything looks normal and everything was on screen. tyre wear delta timing and a lot more. Then the view changes in a split second in what you see in the picture. The second picture is how my view is normaly Any idea what was happens?
Hey Jos. Tell me more about it, so I can reproduce the issue. Was it a multiplayer session with 2 races and on the second race some widgets has gone off??
It was just one race The first (i think) 2 laps the widget looks okay, and then a little (realy a very little) stuttering, and the widget changes like you can see on the picture.
Which files do I need to backup for Sealhud to remember its settings after a SimBin directory clean-up? Most RaceRoom glitches are solved by deleting the SimBin directory. I have a batch file to make a backup for some user files & directories but I have to organize Sealhud each time. For those who are interested in the batch file (just change the origin and destination to your liking in Notepad and save it as a *.bat): XCOPY /D /S "D:\Users\Eigenaar\Documents\My Games\SimBin\RaceRoom Racing Experience\UserData\CarSetups\*.*" "E:\Games\Simulation\Racing\RaceRoomRacingExperience\UserData\CarSetups" XCOPY /D /S "D:\Users\Eigenaar\Documents\My Games\SimBin\RaceRoom Racing Experience\UserData\ControlSet\*.*" "E:\Games\Simulation\Racing\RaceRoomRacingExperience\UserData\ControlSet" XCOPY /D /S "D:\Users\Eigenaar\Documents\My Games\SimBin\RaceRoom Racing Experience\UserData\MenuSettings\*.*" "E:\Games\Simulation\Racing\RaceRoomRacingExperience\UserData\MenuSettings" XCOPY /D /S "D:\Users\Eigenaar\Documents\My Games\SimBin\RaceRoom Racing Experience\UserData\*.xml" "E:\Games\Simulation\Racing\RaceRoomRacingExperience\UserData\" ECHO Hit CTRL-C to stop copying the files.
it has nothing to do with SimBin folder SHIFT+F1: Copy layout settings to the clipboard. This way you can save them as a file, send them to a friend to share your Layout, or just paste them to the other 2 layouts for reference. CTRL+V: Restore/Paste layout settings from the clipboard.
Webhuds store their settings in BrowserData, so if you wipe Simbin folder you lose your settings unless you backup the necessary files.