----- // AV8B causes server crash \\ -----

[BIGNEWY]

BIGNEWY, please find attached an archive containing :

- autoexec.cfg

- options.lua

- DxDiag.txt

- dcs.log

 

2018-05-30 11:08:31.312 => First client access

2018-05-30 11:15:07.020 => second client access

 

approx 11:38 : desynchronization from clients, IA don't seem to moove anymore, server console is "not responding".

Problem solved when the client change slot to spectator or any other module than Harrier.

 

Only one error related to Harrier found @ 11:28 after a plane crash :

"2018-05-30 11:28:38.334 INFO SCRIPTING: Event unit - Pilot Dead

2018-05-30 11:28:38.334 INFO Scripting: event:type=pilot dead,initiatorPilotName=bob,initiator=Pilot #025,t=62617.184,initiatorMissionID=1397,

2018-05-30 11:28:38.490 ERROR GRAPHICSVISTA: Can't open model AV8BNA_DESTR."

 

Hope you can help us...

 

Here the archive : http://teamcity.fr/LPF-diag.zip

 

thanks xvx45

 

but getting a 404 on the link

[xvx45]

thanks xvx45

 

but getting a 404 on the link

 

link corrected, sorry for that

http://teamcity.fr/LPF_diag.zip

Edited May 30, 2018 by xvx45

[xvx45]

@BIGNEWY If you need to test directly on our server ask for the name or password to myself or Whisper (I'm the sysadmin and he's the Mission Master)

[BIGNEWY]

thanks, a little busy at the moment but will take a closer look soon.

 

With your dxdiag and no sound card, it has been known to create issues.

[xvx45]

thanks, a little busy at the moment but will take a closer look soon.

 

With your dxdiag and no sound card, it has been known to create issues.

No problems, I totally understand ;)

I've noted that, in fact there is an audio card but Windows Audio Service was disabled. I changed that, Whisper make a test actually to see if there is any changes.

I'll tell you if there are any changes. If not, I'll send you a new dcs.log and dxdiag (no changes to config).

 

Regards,

[Kirk]

Looks like i found a temporay workarround to make it useable on the Kirks Hangar DCS Server. I installed a virtual sound card on it and after that the testflight went without a single desync. Seems like it has an issue when the machine does not own a soundcard.

 

 

here the one i installed "trial version" worked for me.

 

 

http://software.muzychenko.net/eng/vac.htm

Edited May 30, 2018 by Kirk

[Whisper]

Same for us, looks stable once soundcard activated.

Thanks for the heads up, sorry for the heat but being in the dark that long (it prevented any usage of Harrier for months) without feedback is kinda hard.

[Ciribob]

Glad the soundcard worked :)

 

Sent from my ONEPLUS A3003 using Tapatalk

[xvx45]

+1 To Whisper, after reenabling Windows Audio Service, seem to work like a charm.

We will test it some days then going back for a report ;)

Thanks for advices

 

Regards,

[BIGNEWY]

great news guys, thanks

[Paul1994]

Nooo, It would be so simple? Just with activate Window Audio systems and that's it?

[Paul1994]

Unfortunately after activation test of the Windows Audio Service the problem remains the same envion 10 minutes of games after it is back to the problem of desynchronization

 

 

 

To see now with the sound card evaluation test can be that the results will be better

Edited May 31, 2018 by Paul1994

[xvx45]

Unfortunately after activation test of the Windows Audio Service the problem remains the same envion 10 minutes of games after it is back to the problem of desynchronization

 

 

 

To see now with the sound card evaluation test can be that the results will be better

 

In our case we just enable the service disabled by myself 2 years before today ;) In our case it was working because we have an audio card built-in the server.

If you don't have one, you've to install a driver like this one https://www.vb-audio.com/Cable/ that will create a virtual audio card, then DCS see it and no more errors related to that in DCS.log.

Make a look to your DCS.log file and look to SOUND "entries" at the beginning of the file, if the text was like that :

INFO    SOUND: XAudio2: Using device ID:'' Name:'', channels: 0
ERROR   SOUND: XAudio2: can't create MasteringVoice
ERROR   SOUND: Failed to start SND_Renderer.
ERROR   SOUND: can't start renderer

=> there is a problem ;)

 

Since we enable the service, DCS can access to audio device, the text is now :

INFO    SOUND: XAudio2: Using device ID:'{0.0.0.00000000}.{8308564e-f47c-45fd-bfd5-6a29a623022c}' Name:'Casque (Périphérique High Definition Audio)', channels: 2
INFO    SOUND: XAudio2: channel layout: Headphones/Stereo
INFO    SOUND: Using SSE FTZ/DAZ mode.

=> No more errors ;)

 

You not just need to enable audio service, DCS must be able to access them (as I've understanded).

 

Regards,

 

Edit : you have to restart the game after enabling an audio device

[Paul1994]

Oh that would be nice but I understand nothing about Virtual audio cable, just a driver file nothing more? how to visualize your operation corerect ect?

 

But there is something different about this module compared to the others which does not require any installation de programme autre.

[xvx45]

Oh that would be nice but I understand nothing about Virtual audio cable, just a driver file nothing more? how to visualize your operation corerect ect?

 

But there is something different about this module compared to the others which does not require any installation de programme autre.

 

Vietual Audio Câble is à virtual audio card to be able to pass sound to mic or live edit audio and so on but in your case you just only need the virtual audio card. Once installed and Windows rebooted go into Windows audio settings and select the virtual audio card as default for playback and recording but it must allready be the case if you don't have audio card before (must be the case if you have the problem).

No matter why is made virtual audio case for our case ;)

I think with this module every client try to play an audio file, and the server in DCS is just another client in fact...

 

Regards,

Edited June 2, 2018 by xvx45

[Angus]

Hi All , we try the virtual sound card , this solve the problem . thanks from VMA 131 !!!!! :thumbup:

[dimitriov]

To complete Angus post, in fact we didn't use the virtual audio card, simply reenabled the windows audio service. It seems taht the virtual audio cards don't work on every servers (or maybe is it simply because windows audio was disabled), anyway, it completely fixed the problem.