I don't usually write on the forum but it is just that it seems like an incredible job, thank you very much
I tried to get it to work during replays, but I couldn't. I'm not sure if it will be possible because I depend on the RaceRoom browser running. I need to do more testing.
Sometimes when I go from on track to menu's to change ffb or something, when I return back to cockpit the sealHud layer does not go back on. Is there a quick toggle possibility for this situation?
Hey @Diego Junges , just a quick question about the yellow flag situations. I had a race tonight with 23 drivers in total. Is it correct that if drivers who fall outside my range cause a yellow flag at the top of the time list, I won't see this in the TV tower? Because there were a few yellow flag situations involving a driver whose name I saw in the bar at the top, as well as in the TV tower. But Crew Chief did occasionally give a notification of a yellow flag for someone I couldn't see at the top because they were driving too far ahead of me, so I didn't see their name turn yellow in the TV tower either.
Hey Jos! The RaceRoom API doesn't tell me who is causing a yellow flag, so I have to use deduction. In short, the logic I use is this: If there is a yellow flag, check who are the slowest drivers on the track. However, the game only activates the yellow flag state for the driver when the incident is close. Example: When I am in sector 1, and a driver causes a yellow flag in sector 3, the game does not activate the yellow flag state for me, and thus, no one is identified. I don't know exactly how CrewChief does it, but I've noticed that it reports when a driver has crashed or left the track, even if they are far away. I believe that the logic I implemented can be improved in the future.
Hey LabPong! Yes, you can try this: 1 - When you're in menus, don't open and close things too fast. Wait a little before click on "Drive" button. 2 - If you clicked "Drive" and the Hud didn't load, press SHIFT+F5. This will reload the hud. That's the reason I included this message, so you can press SHIFT+F5 in case SealHUD didn't load.
WebHud problem A couple of weeks ago, Sealhud was working perfect and without any problems. Now, after some weeks of absence, several Windows Updates and other things, I tried to start R3E with Sealhud running. - CrewChief (4.19.1.42) is running with enabled WebHud integration, enabled Websocket integration - Steam with -webHudUrl=https://sealhud.github.io/ When starting Raceroom configuration in CrewChief, I get some (for me) cryptic lines 20:19:26.070 : Using game definition RaceRoom 20:19:26.131 : Free text action macro, text = Sorry, my bad 20:19:26.131 : Found FREE_TEXT for commandSet r3e version 20:19:26.131 : Free text action macro, text = good pass 20:19:26.131 : Found FREE_TEXT for commandSet r3e version 20:19:26.172 : Loaded 173 default car class definitions and 0 user defined car class definitions 20:19:26.219 : ThreadManager: Waiting for root threads to start... 20:19:26.219 : ThreadManager: Root threads started 20:19:26.227 : No SRE key or value item for action toggle_rally_recce_mode 20:19:26.234 : Successfully started Crew Chief data WebSocket server 20:19:26.258 : EXCEPTION: Unable to start game data websocket: The underlying listener has failed to start. at WebSocketSharp.Server.WebSocketServer.startReceiving() at WebSocketSharp.Server.WebSocketServer.start(ServerSslConfiguration sslConfig) at WebSocketSharp.Server.WebSocketServer.Start() at CrewChiefV4.Utilities.startGameDataWebsocketServer(String endpoint, GameDataReader gameDataReader, GameDataSerializer serializer) in C:\CrewChiefV4\CrewChiefV4\Utilities.cs:line 223 20:19:26.266 : Cmnt: Duplicate Exception _log added to MY DOCUMENTS\CrewChiefV4\DebugLogs\ErrorLog.txt 20:19:26.268 : Sound: Starting queue monitor 20:19:26.269 : Sound: Monitor starting 20:19:26.272 : Using NumberReaderEn for soundPackLanguage en I also tried to start with dash.exe and get below window ... I have no idea why Sealhud is not visable/working in R3E. Tried Ctrl+Alt+Shift+L in game and Shift+ArrowUp as well. I've deleted the Local Storage Folder, where Sealhud saves config, done a clean CC install and a fresh R3E installation, but nothing happens ... No Sealhud in R3E Some useful hints appreciated, as I am have no idea .... Cheers Marcus
Hey Marcus. This is not a SealHUD issue. The exception "Unable to start game data websocket 'crewchief'" usually indicates that Crew Chief cannot open the network port required to communicate with RaceRoom. Make sure you've selected RACEROOM RACING EXPERIENCE from the game list. Here are the common solutions to fix this issue: 1. Run as Administrator Ensure Crew Chief is running with elevated privileges. Right-click the Crew Chief shortcut and select "Run as administrator". This allows it to bypass restrictions when opening ports. 2. Check Antivirus/Firewall Settings Security software might be blocking the WebSocket connection. Add exceptions to your antivirus and Windows Firewall for both the Crew Chief application and the specific racing game you are playing. 3. Disable "Websocket" and Enable "WebHud" If you are using OtterHud or similar custom dashboards, the error may occur because you have enabled the wrong setting. Go to the Crew Chief settings. Disable "Enable Websocket" (or similarly named web-hud options). Enable "Enable Web-Hud integration" instead. 4. Delete Configuration File (Reset Settings) A corrupted configuration file can cause startup errors. Go to your Documents folder. Locate the CrewChiefV4 folder. Delete the userSettings.json file or the entire CrewChiefV4 folder to reset it to default. 5. Check for Conflicts SimHub: If you are running SimHub, it might be trying to use the same data port. Shared Memory: Ensure the game's shared memory (used to send data) is enabled in the game’s settings. Note: If the issue persists, locate the ErrorLog.txt file in Documents\CrewChiefV4\DebugLogs\ for more specific details on why the socket failed.
Thanks Diego for fast reply. 1. With Admin Rights error still there 2. All checked and CC, R3E and Steam are open to communicate with ports 3. Websocket disabled / WebHud integration enabled 4. Deleted CrewChiefV4 folder 5. SimHub not activated ... what do you mean with shared memory is enabled in game settings? Does R3E has an option to enable/disable? ErrorLog.txt attached. I can't find any details why websocket failed.
Yeah, your log only say this: Repeat of EXCEPTION: Unable to start game data websocket: That's what's going on. Now you have to find out WHY? I suggest you temporarily disabling your firewall and antivirus if you have one. As far as I remember, RaceRoom doesn't have an option to disabling shared memory communication.
Check if the WS ports are correctly set: Also there is a ZIP file with my settings profile json. You can copy it to: Documents\CrewChiefV4\Profiles and load it on CrewChief for testing
Thanks a lot Diego, cc_settings tested ... same error. Ports 8070 and 8071 are the same in my profile. What I don't understand - in your profile your enabled websocket integration and webhud integration, but in post #409 you told me to deactivate websocket I think there is something broken in my registry, but not sure. I can't locate this error and that f*** me up. Without SealHUD there is missing a lot in R3E.
At this point, everything is experimental. You can try to change the port used by SealHUD to communicate with Shared Memory. Change this value to 8072, or any other free port available on your computer. Save settings. After that, change the RaceRoom launch parameter to: -webHudUrl=https://sealhud.github.io/?ws=localhost:8072
PROBLEM SOLVED! First I checked which ports are in use. - Opened cmd window - Entered resmon which opens the Resorcemonitor - Than goto Tab Network - Than goto Listening Ports (here you can see all ports are currently in use) There is an entry HapticService.exe which is using port 8070 (same port CC is using for Data). The Haptic Service is something Razer implemented for having haptic feedback on your mouse if mouse supports that "new" feature for example. As I have no specific haptic feedback hardware, I switched HapticService off. Now CrewChief is able to use port 8070. No more Error message in CrewChief and SealHUD is working again. Thanks Diego for your hints and help!!! Your solution to set Steam parameter and changing Game data Websocket port in CC is working as well.
Is there any chance you can fix it so the pit limiter overlay comes on when we request a pitstop,instead of when we get to pit road?
Hey Dean. Today, the pit limiter widget shows up when you're close to the pit entrance. This is the intended behaviour and it is working correctly as far as I know.
I think it's great that you're continuing the HUD. Thank you for that. And your updates are awesome! One question: would a vertical layout for the Session Info be possible? As an optional alternative.