FoolTrottel

👍

Same here... Channel one is all quiet! We are all kinda unrecognizable on the server though: I did hear you speak just now lama!

You'll be on your own there, lol ...

I am talkin'!

As for SRS: Do it like this, should work: is this a DD only thread? I sure hope so, lol. Tried to talk to me, myself and I, but due to local and surround sound... could not really test it with ourselves!

Maj. Britt Fen ?

Hurry up... so I can add them to CechkSkins! You done yet? Stop reading, go skinning! 😊

Ah, yeah, I know that feeling ...

Done!

Saturday would work for me, Friday not.

Good luck, take care!

lol, can't even use two pc's to test ... I have only one game account!!

In the end, it looks like the complexity of all the items listed is giving us some challenges. Indeed. And the one that bother me the most, is the restart-mission issue. The fact we cannot seem to easily restart a mission ... We will never prevent issues from happening with that number of pilots in a multi-engined a/c, spawning in a parking spot with engines off... Whatever we do to be prepared, the chance something bad happening is always there. Not saying we should ignore the technical issues, control issues, pilot errors. No, for sure we should test, and test and be focused ... be prepared. I'd like to figure out why these PWCG mission restarts are so prone to failure - I mean, we have plenty restarts in normal coops, which are run from the same Dserver - only one difficulty settings was changed for PWCG - and I can't seem to remember any restarts being that troublesome - Some do fail, but mostly due to operator error : Generating a mission too late, while it's already loading in the Dserver, pressing the wrong button etc. To test this, and draw some conclusion is nearly impossible. I can run one server, and have two clients connected... tops... lol.

Me too ...

In this circumstance, you may want to dial back the instrument lighting a bit, it might get too bright!

Noobs!

What I learned from this: Second spawn (the one where I let the mission rotate, ie. not re-loaded on the server) the in-cockpit view was incomplete, had to wait until a/c left and right showed up. And that was when some high pingers lost connection. As this did not happen on 1st and 3rd time: any mission restart in this campaign will now mean the dserver.exe needs to be stopped and started. And, if Fen keeps on using the 2.PWCG Mission icon on the server, then the large .mission file will also be deleted -> much faster loading ... Cool stuff, I mean the mission flying itself was. And nice. And thanks!

I am sorry, but this makes me think of a tip like 'Make sure your engines are running, as it makes for a much easier take off run' ... Instrument lighting has been like the first thing I switch on when in cockpit, like forever, and ever !

No need to do this. This one time was a special occasion...

+1

Should be for each and every a/c that has a radio ... well ... See here: https://docs.google.com/spreadsheets/d/1tzd996zJ1t0heZ-t1PpL7vNUIZbXl7pI6De0GThN1Qw/edit#gid=1869108790 So, after reading that, I still do not know...

Technical support for moving a slider? You kiddin'?? How old are you then?

Check what sound device is selected when you right click speaker icon and select Open Volume Mixer. Try with as many devices disconnected as possible: Maybe one is acting as a mouse wheel? Can you lower the volume? Any sound effects activated? Dolby, or ... Atmos? Check device manager, remove all sound devices, reboot and let windows discover and install them again? In other words: Basically, I have no idea!

It takes your current age into account, and thus it tries to prevent you from suffering further loss of hearing ... Windows HearLow (TM) it's called.

Good Show!