I love what they have enabled here, loving using my simhub dash in-game.. but have to agree that more widgets and control over such actually "in-game" would be very beneficial and just because this 'mod-able' hud thing now exists, should not mean the in-game hud is left as is. Not everybody finds it easy/intuitive to setup the webhud It means more apps running and a process to launch the game There are conflicts (as in duplicate info between both in-game and webhud) In game hud is not as flexible and some things I want to turn off cannot be. Some things I want to move or re-scale, can't be (I know about the hud editor but you can't scale up, only down and it doesn't cover everything) There are lots of reports of performance issues Sometimes the "in game browser" can go wonky and freeze/flicker (not ideal mid race) Sometimes the "in-game browser" takes too long to load (maybe because of it being on github?) i.e no start lights because it didn't load in time after you joining the race at the last second. Personally, I don't get many issues.. but it doesn't mean they don't exist, hear a few people going on about them regularly. The in-game hud needs some TLC and the Number one priority, in my opinion, should be the chat box. Webhud/external apps are simply no good for this, since there's no guarantee everybody in a session is using the same thing. Simple fact is, what they have done is great... but for those that like to keep it simple and install a game without "modding it" then its not so great.
Ok we found the issue, he was running CrewChief and had the option turned on for the WebHud and wanted to start the dash.exe also, then this error pops up! He forgot about turning it on and that he do not need to start the dash.exe seperate anymore. Starting it twice is not worth and not working ^^
They have now @majuh , thank you for the reminder! New dash.exe is available: https://github.com/sector3studios/webhud and you'll find the .h and .cs files were also updated now. https://github.com/sector3studios/r3e-api
I changed the "SHARED_MEMORY_VERSION_MINOR": 7, to "SHARED_MEMORY_VERSION_MINOR": 8, in my files, but no matter if i run the old or the new dash.exe i get a only if i lower the number back to 7 it works
If i run the game with the original https://sector3studios.github.io/webhud/dist/ it is working fine. However when i download a fresh clone of the repo for developing, then "npm install" -> "npm start" the localhost:4000 is giving me this error Also the memoryblock readouts are: VersionMajor: 2 VersionMinor: 6 ?
Nah i used the dash.exe from the sector3 repo This is what gets reported when i run it on developing:
You probably grabbed the wrong one? Or still using the old one? If you shift+i in-game and search for "version", do you see Major 2 and Minor 8 ?
If i compile the files and run the game it loads the dash just fine and readouts are as they should be: Major: 2 - Minor: 8 However the developing page still reads: Major: 2 - Minor: 7
@J-F Chardon Here you can see both running same time Implemented the readouts of the Versionnumbers into the settings-screen top left corner
Can we ditch the mods and get back to developing the in game stuff. This is a bit aggravating, and one of the main reasons I like R3E is the lack of having to monkey around with mods downloading this, and changing that, to drive.
I get your point and i'm totally on for having more options to customize the ingame HUD! But integrating these kind of customizations, as the external WebHud offers, into the game, erm, is it even possible? And Developing the ingame HUD to fit everyones taste, will never happen. I actually like to have the ability to create my own HUD and this is the only way doing it. You dont get forced to use the external HUD.