Strange issue out of nowhere - Any game I launch that is supported by Simhub, will start, hang and then go into a "not responding" state in the Task Manager. If I kill the Simhub process in Task Manager, the game will instantly stop hanging and begin to run fine.
This is happening while running 9.01.1 and 9.1.6.
Notable change: I'm running SimagicPro manager 2.0 for my wheel base and they had an update today, including wheel firmware. However, I played for about an hour after that update with no issues. I come back an hour later and we're in the state described above.
Upgrading to 9.1.6 didn't make a difference. How can I begin to troubleshoot this, as I miss my simhub 🙁
/edit - the issue had to do with the simagic FW revision I was running (v182 breaks ability to use simhub telemetry without locking up your game). reverting to v181 solved this issue....but simagic doesnt make it easy to find earlier FW revs.
Update - I've discovered that if I turn off the simagic wheelbase, I can run games from Simhub without them hanging/not responding, but of course, the wheel is turn off....
So this is probably a simagic issue with the 182 FW, but it's rendering simhub useless to me in the mean time. There must be some communication between the wheelbase and simhub that's causing a conflict and making these games hang until either the simhub process is killed, or the wheelbase is turned off.
Reverting to earlier FW on the wheelbase doesnt seem to be an available option with simagic :/
It could be the following is happening. According to this video SPM2 has telemetry built in. Which would mean race data is processed through SPM2 and through SH. If so your CPU likely can't process it all at the same time, while also running the game.
Advice from this point of view would be to use only 1 application that serves race data. Or if possible, to stop UDP data going through SMP2 and only use SH for that.
@botmeister interesting! Great advice - thank you. I should figure out the differences in the telemetry available between the last 2 Simpro Manager 2.0 updates, as it all worked right up until v2.0.252 was released, then figure out how to flash the wheelbase with FW to an earlier revision, as there doesnt appear to be a way in the simpro manager SW to stop the telemetry generated there.
So I was able to get the Simagic wheelback back to an earlier version of the wheelbase firmware (v181) and that resolved the issue. In fact, it looks like v182 isn't available anymore. Possible it was a release candidate that they put out too early? Who knows....
I hope this thread helps someone in the future.