Yeah ... I haven't tested it yet either, but based on the launch announcement for the new HUD, I'll likely switch to using the in-game HUD for MoTeC, relatives/tv tower, and tire wear. It's better to use in-game widgets for timing information—such as deltas and gaps between drivers— the accuracy tends to be higher. As for SealHUD widgets like FuelDetails, Inputs Graph, Position Bar, Clock, PitStop, RaceInfo, and others, I'll need to spend some time testing to figure out exactly which ones to use.
The way RaceRoom is now, yes. Unless they fix or change some security police on the new built in browser, it won't be possible to load a remote webhud because it can't "talk to" the local websocket to read RR data.
@Diego Junges Question If raceroom comes today with a fix, can you let us know if i dont have to update like you say it not? For now i did nothing with the update
Hey Jos... I am on my work, and I going home only in 9 hours from now. But J-F told they are going to push a hotfix today! Yes, if they fix it, then SealHUD could be launched the same way you always did (and probably your settings will be there)
Can anyone in VR test to see if sealhud works in the FRJ's ?? Could be a bug, it worked ok before the update now it just flashes up for a split second randomly.....
Hey Fogtop. There's someone on Discord with the same problem ... is that you? This started to happen AFTER the new RRs update. There's nothing on SealHUD causing this. Some other VR users reported everything is fine.
Yes that's me yes it seems to be fine in all other cars that's why I'm asking for others to test the frj's... I've spoken to JF now but it's just for my sanity that I'm not the only one with the issue
Have he answered?? Anyone else facing the same?? There was a guy in Facebook who reported issues loading new HUD, but he didn't said anything about flashing screen It's a bit drastic, but he uninstalled RaceRoom and installed it again ...
Ok so the sealhud is all good (great in fact). Except in the Formula junior class, which has known historical issues with the old hud. This why I was asking others in VR to test if they have the same issue with sealhud in the Formula junior's as I do...
Hallo @Diego Junges, Ich bekomme das SealHUD nach dem Raceroom Update einfach nicht mehr zum Laufen. Habe deine Anweisungen im Post #500 befolgt, die Startoption für Raceroom entsprechend geändert und auch die Start SealHUD.bat ausgeführt, aber SealHUD startet über den Crew Chief nicht wie gewohnt. Habe heute gelesen, dass es bei anderen Usern wieder wie vorher läuft. Was mache ich falsch? Ich möchte auf das SealHUD nicht mehr verzichten, denn du hast da hervorragende Arbeit geleistet und ich möchte es beim Fahren nicht mehr missen. Vielen Dank schon mal für deine Hilfe!
Hi mate. Thanks!!! The "Start SealHUD.bat" was a temporary solution and it's not needed anymore, since KW studios has already fixed the issue in RaceRoom built-in browser. Now, you should carefully read and follow the standard instructions available on the first page of this forum thread: https://forum.kw-studios.com/index.php?threads/sealhud-webhud.20675/ Checklist: 1 - CrewChief with webhud option activated OR dash.exe running 2 - RaceRoom's launch parameter on STEAM must be: -webHudUrl=https://sealhud.github.io And that's it. It should be working.
Hallo @Diego Junges, Vielen Dank für deine schnelle Hilfe. Ich habe die Anweisungen genau befolgt. Startoption: -webHudUrl= https://sealhud.githib.io Crew Chief: WebHud-Integration aktivieren (nur R3E) Ich starte SealHud immer über Crew Chief (Version 4.19.4.0), aber es passiert nichts. Nach dem R3E-Update hatte ich den von dir vorgeschlagenen Workaround installiert, aber wie bereits erwähnt, hat auch dieser ja nicht funktioniert. Und nun bin ich wieder auf die alte bisher erfolgreiche Variante zurück gewechselt und es passt auch nicht. Ich bin ratlos. Haben Sie vielleicht noch andere Ideen?
Did it work before the update? That’s unfortunate. Well, here are a few things you can try: 1 - Try using dash.exe instead of CrewChief; dash.exe might even display error messages that could help identify the problem. If you see any strange messages, feel free to post them here. 2 - You can back up the folder containing the SealHUD data and then delete it... it is located at: X:\Users\***USERNAME***\Documents\My Games\SimBin\RaceRoom Racing Experience\BrowserData\Default\Local Storage (Please change "X:" to your drive letter and "***USERNAME***" to your Windows username.) 3 - You can try using a different webHUD to see if it loads or not. Simply change the parameter to -webHudUrl=https://otterhud.github.io 4 - You can check if you are experiencing the TCP port 8070 usage issue reported here: VERY IMPORTANT: RaceRoom's shared memory requires local TCP port 8070 to share data. Certain third-party services (such as Razer Haptic) use this port, causing a conflict that prevents SealHUD from working. Check if TCP port 8070 is currently in use on your computer (using Windows Resource Monitor / resmon.exe). If it is, you can either disable the service using Windows Services (services.msc) or change the communication port used with RaceRoom, as described in this post: https://forum.kw-studios.com/index.php?threads/sealhud-webhud.20675/page-21#post-261276