Cool VL Viewer forum

I just tried a reinstall (to the Program Files, not x86) and had the same issues. Tried also deleting the SecondLife folders in AppData to see if purging settings would help, but again, same issues.

Highly doubt these problems are AV related - again, disabling the AV in it's entirety had no effect on the problems presented.

EDIT: Will try the sound tweaks, didn't see that on my first read.

EDIT2: Tried swapping both the fmod.dll and SLVoice.exe from Alchemy, but unfortunately no luck. Same problem. Also tried with the files from the Linden viewer, again, same problem. Both viewers work fine by themselves, and do not present either the swapped channel issue or the voice issue.

Just tried out of curiosity to swap the fmod.dll and SLVoice.exe FROM CoolVL over to Alchemy and see if it had any problems - Alchemy runs fine, voice functions as expected. Weird, but at least that (likely) rules out problems within fmod.dll and SLVoice.exe themselves

It looks like you did not see the "EDIT" I added to my last message a few hours ago (only a few minutes after I posted it). The sound issue is resolved for next release.

As for the SLVoice issue, I'm short of ideas...

"Disabling" an antivirus will just disable its real time engine, but won't remove the DLL hooks it installed in the system (these hooks are used to intercept sensitive system calls and prevent viruses/malwares to abuse them).

In any case, I cannot diagnose an issue I cannot reproduce myself and that leave no trace behind itself in the logs...

You could try and open the Windows events viewer (to be found among the administrative tools) and see if any error (or even warning) message is issued (most likely to appear in "Windows log" -> "System") when you try and launch voice from the viewer...

Ah, sorry, didn't see that edit!

I'll put this to rest right now because I will have access to a machine without an AV installed in the next week, so i'll come back once I've tested on that machine to see if there's any different behaviour.

Thanks for being patient with me!

I lied, couldn't resist tinkering some more.

I FIXED IT! (or more accurately worked out a bodge)

Using a tool called TCPView, it turns out that for whatever reason CoolVL isn't launching SLVoice (or at least it never starts listening), BUT if I launch it manually from the CoolVL install location, it launches and listens on port 44125. If I then set the VivoxVoicePort setting to close to 44125, then wait for CoolVL to scan over 44125, it then connects and voice works! (also fixes the FPS drops, as expected).

I've attached the CoolVL logfile (no SLVoice log is being generated) using the above method.

I also noticed the command Alchemy uses to start SLVoice is in a slightly different format than that of CoolVL: (namely the position of the -i call)


CoolVL:


EDIT: Poked around in command prompt. The command CoolVL uses does not launch SLVoice. BUT, swapping around the formatting (putting the -i call at the end, and putting the log directory in quotes) gets it to launch properly, so the working command is:

So I've found that a good way of getting CoolVL to play nice with Voice enabled, is to launch TCPView, launch CoolVL (and log in) find out what port CoolVL is attempting to use for voice, and through a (non-elevated) command prompt, run the above CoolVL command with the port swapped out for one which is about to be scanned

It's not a fix, but a proof that, on your system, the SLVoice executable fails to launch, which, again, makes an anti-virus impeachment (Trump antivirus ? ) probable...

Please, try the Event Viewer trick I described in my last message: it may well give you the reason for the failure/refusal to launch the voice client.

As for the parameters, they are the same (just the log level which you changed from 0 to 1 in my viewer). The ports range is different too (but if it worked with port 44125 by launching manually, it should also work otherwise).

Sorry, I should have mentioned - I did look in the event viewer, but nothing relating to CoolVL or SLVoice was in there - also, see my above edit - restructuring the format of the command CoolVL uses to launch SLVoice gets it working (at least from command prompt)

EDIT: Could the reason for this be that the user directory (C:\Users\Tim Horton\) contains a space? I know command prompt gets funny if you address a directory which has a space, but don't enclose it within quotes

Hmm... It's not the order of the parameters, but the quoting that might explain it !

What happens if you create an account with a name without space (try "guest" for example) and use the viewer from it ?

We are posting too fast after each other !

And yes, this is likely the problem... Windows way of starting a process is totally retarded; under Linux or macOS, you pass a table of string arguments, so it does not matter if they contain spaces or not, while under Windows you pass a single string, with the space as an argument separator...

For next release, I modified LLProcessLauncher to quote any argument containing a space, under Windows only, of course.

Just did a quick test on another user account (w/o a space) and SLVoice fires up just fine. Seems like the lack of quotes causes SLVoice to fall over on my main user account due to that space in the log directory.