Thanks for the help. Dan
I would bet its the DAX drivers as opposed to SSDR. I have one game that expects the default sound device to be assigned to a real device (like speakers, etc) and I have to disable the DAX sound devices before it will run.
Go to the control panel, look under sound devices and disable the DaX entries and see if it will now work.
I was able to reproduce it by adding in a ton of virtual audio cables to prove it wasn't SSDR specifically
That it's a problem with GTA being overwhelmed by the number of serial ports makes sense. The fact that the game's authors don't know how to write code that enumerates serial ports without limits is a bit, ah, surprising... but then again, I suppose they didn't expect anybody to be running their game on a system with four dozen serial ports either.
We're starting to see a trend here... there is apparently some software that doesn't like so many serial ports in the system. It seems to me that a valuable change to DAX would be to have it create and delete its serial ports dynamically. Admittedly, I haven't really looked at the overall architecture deeply enough to know if this is realistic -- I suspect some sort of architectural change would be necessary. But I *do* know that it *is* possible to make serial ports dynamically appear and disappear at will (this happens all the time when you plug-in a USB to Serial converter... Poof! A serial port gets created! Unplug it... Poof! It's gone.)
IDEA - To accommodate poorly written cohabitating programs could DAX add a global DAX-down/DAX-full/DAX-minimum toggle that would temporarily cycle through a DAX totally disabled, DAX totally running and a DAX in a minimum usable configuration (for sleep/wakeup/monitoring features where a pipe needs to be maintained) series of modes?