@CrapsJarrard I found something in your logs that another user on Overtake had too which causes false data for him. You have something in use called GS - Options which is throwing errors like every 2 seconds. Check if you can reinstall or deactivate this plugin, this fixed it for this other user [2025-11-10 23:50:15,040] ERROR - System.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\Program Files (x86)\SimHub\DashTemplates\GS - Options\RaceResults\RaceResultsStandings.txt'. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) Regarding WPF vs HMTL Renderer, to my understanding WPF is run by the GPU and HTML by the CPU. I found occations where Simhub started to throttle, which bascially means it doesn't have enough ressources and in this case skipped 950 update cycles of the overlays before it ran smooth agian. Could it be that the CPU is peaking out in HTML Renderer? [2025-11-11 23:07:59,443] INFO - End of web dash data throttling on Aces AMS2 Ultimate Telemetry (v1.2.2) / 127.0.0.1 (950 packets skipped) [2025-11-11 23:07:59,443] INFO - End of web dash data throttling on Aces AMS2 Laptimer Small (v1.2.2) / 127.0.0.1 (950 packets skipped) [2025-11-11 23:07:59,443] INFO - End of web dash data throttling on Aces AMS2 Delta (v1.2.2) / 127.0.0.1 (950 packets skipped) [2025-11-11 23:07:59,443] INFO - End of web dash data throttling on Ace AMS2 Class Leaderboard (v1.2.2) / 127.0.0.1 (950 packets skipped) [2025-11-11 23:07:59,443] INFO - End of web dash data throttling on Aces AMS2 Tire Visualizer (v1.2.2) / 127.0.0.1 (949 packets skipped) For now, can you try reinstallt oder deactivate the GS Plugin and check if WPF Renderer then runs fine with 1.2.2?
Apologies again for the delayed response. I checked through my SimHub install and the only active plugin is GarySwallows (I assume GS Options is related to that). I removed this plugin and things went south when trying to use the new overlays (as I suspected since having the Swallow plugin is a prerequisite). I also gave more thought to my system just being too slow to handle any of this. After some light googling, I tried an app called Process Lasso and set it up so that SimHub process were contained to a set of 4 E-cores as opposed to just letting the Windows 11 task scheduler sort stuff out on its own. With this configuration, the stuttering did not disappear, but has been greatly mitigated when testing with the HTML renderer. As per a previous post, I was struggling to think of how my setup may run odd parameters. I remembered that I exclusively play AMS 2 with AutoHDR enabled for the visual boost. It seems like whatever the HTML renderer is doing does not like working with HDR enabled at the OS leve (maybe its a tonemapping bug?)l. WPF seems to have no issues with AutoHDR (as far as overlay or game performance go). I do recall I had lots of problems trying to use SimHub with ACC as that game client refuses to run with HDR enabled unless you use Exclusive Fullscreen mode (which SimHub does not like unless you you multiple monitors).
Actually now, I'm going to assume that my PC is broken. On another test run with WPF, I did notice my GPU usage was off the charts. I was running the game maxed out at 4K with 40 visible vehicles, so I was definitely not being cautious. I assumed that my GPU was eating **** trying to run the game and not leaving enough for SimHub. I changed all my AMS 2 settings to Low and made visible cars go down to 12. I also changed the rendering resolution to 720p and disabled all forms of AA. I relaunched the game only to find that my fps was still deadlocked to 117Hz and somehow the GPU usage was still at 100%. I alt-tabbed and killed SimHub and my GPU usage returned down to 46% and it downclocked itself to 1285MHz as it already had more than enough headroom for 720p 117Hz on all low settings with no cars visible. My aging 3080 just doesn't have the guts to push these overlays it seems. I am still eternally confused as to why any of the overlays I used previously never showed so much GPU usage. I'm also at a loss at how showing a WPF-rendered leaderboard can require 60%+ of my total GPU capability (and about 170 extra watts versus playing with no overlay at 720p). For now, I am going to run the 1.1.3 Leaderboards, laptimer, and relatives along with the stock Tachometer overlay. I was already happier than a pig in **** with this setup from late June until now, so I will continue to be happy with it moving forward.
