Processor AMD Ryzen 5 7600 6-Core Processor 3.80 GHz
Installed RAM 32.0 GB (31.1 GB usable)
System type 64-bit operating system, x64-based processor
Edition Windows 11 Pro
Version 23H2
Installed on 16.09.2023
OS build 22635.3140
Experience Windows Feature Experience Pack 1000.22686.1000.0
The issue
When selecting "Position Spread" or "Positional Audio" from the plugin menu:
CrossTalk: Too many candidates for MainWindow. Report to the plugin developer.
There are no other logs.
I have had the issue for a while and throughout multiple Windows 11 updates, so it's not a patch thing.
What I tried:
TS3 versions: 3.3.2, 3.5.5, 3.5.6
Compatibility mode for teamspeak exe
run ts3 as admin
What the issue might be
~I had a kind of similar problem with a script I wrote when switching to win11. I think they changed something with getting window handles or similar. I didn't fix it, as it was just a convenience thing, moving a window to another desktop.~
Nevermind, that was an Issue with the new "Windows Terminal", because the PowerShell process doesn't have a window itself and there is, to my knowledge, no simple way to find the Windows Terminal Prcoess related to that specific shell.
system
Processor AMD Ryzen 5 7600 6-Core Processor 3.80 GHz Installed RAM 32.0 GB (31.1 GB usable) System type 64-bit operating system, x64-based processor Edition Windows 11 Pro Version 23H2 Installed on 16.09.2023 OS build 22635.3140 Experience Windows Feature Experience Pack 1000.22686.1000.0
The issue
When selecting "Position Spread" or "Positional Audio" from the plugin menu:
CrossTalk: Too many candidates for MainWindow. Report to the plugin developer.There are no other logs.I have had the issue for a while and throughout multiple Windows 11 updates, so it's not a patch thing.
What I tried:
TS3 versions: 3.3.2, 3.5.5, 3.5.6 Compatibility mode for teamspeak exe run ts3 as admin
What the issue might be
~I had a kind of similar problem with a script I wrote when switching to win11. I think they changed something with getting window handles or similar. I didn't fix it, as it was just a convenience thing, moving a window to another desktop.~
Nevermind, that was an Issue with the new "Windows Terminal", because the PowerShell process doesn't have a window itself and there is, to my knowledge, no simple way to find the Windows Terminal Prcoess related to that specific shell.