DieHard

Thanks guys in response to my GCI question.

Yes! Fly 104th's server at night time conditions , usually wee hours NY time to see cockpit instrument illumination is not working or some of it that does is way too dim >>> compared to my Black Shark experience since 2011. 2.5 is in Beta for a reason. Just be nice to the developers. They want us to report the odd-ball stuff. Over time I am sure these quirks will be fixed properly. -+- I have noticed a few times mis-labeling of controls and even doubling with the same control's commands to 2 different controls in "Adjust Controls" . My setup I have pre-programmed controllers thru CH Control Manager. I just re-type DCS side "Options\Controls" and change control commands to what I had in 1.5 .

+1 Thanks Devrim .

GCI__Question ========== What can GCI see? If I take off from a Red FARP and head for mountain valleys for cover (radar blindness), can a Blue GCI guy see my movements outright from the get-go, in real time, or do other factors play in such as placing radar units close in to my area and such working tactics ?

SRS is not used very often on the RED side. Finally found out a few nights ago that my SRS is setup correctly. Somebody came on and wanted to do a coordinated attack. Both TS3 and SRS I expect professional in-flight comms behavior. If idle talk and BS; I mute my end and fly quietly solo! RED needs to start acting like a pro air force and work as a team.

A tree got me last time almost to my destination... Not easy sneaking in under the radar in Ka-50 . Wee hours and nobody on also is helpful.

I have a GTX 970 and 17-2600 CPU which is considered low level currently. Once I get loaded up in game on this server I can run my 970 wide open, all settings maxed out with frame rates over 60!! In previous editions of DCS I had to do the opposite. I am truly surprised and happy.

I fly red. I'm not pissed. I thought this server was about WAR! I try to get in close behind the blue all the time. Huey pilot >>> Cheers!!! More fun to vulch blue airdales while they are taxiing or taking off...

and (the last song of the four is Blooze singing)

Yes, made a mistake. Misread full spec sheet. Recommended PSU is 600 watts. I should be fine I think. Thanks.

Does the GeForce GTX 1080 Ti draw the full 600 watts in DCS? DCS Multiplayer? My current machine I have a 850 watt PSU and runs fine on GTX 970. I do not use VR. Will I need more power?

Whenever I complain, I'm told I'm too sarcastic and get another warning! I would pay an update fee if DCS does a good job at it with improvements.

Yep! I figured that was probably the situation, before I posted top-of-thread.

1.) Ka-50 2.) Voice Attack ? NO 3.) Scroll Lock keyboard button for PTT and CH Control Manager Fighterstick set for same. 4.) Easy Comms were on, on my side Single Player; Off on 104th's server. Thanks for reply. I will further experiment. Will report back, later, with results.

Well, that is not how it has been in the past 8 years...

Ka-50's NVG is nice improvement in 2.5 OpenBeta. Was on 104th's Multiplayer "Operation Longbow" 6 AM mission start and still dark enough. On FARP loaded NVG and noticed viewing instruments were fuzzy.

Kneeboard on/off is one item and a few others down the list have changed . I use a Logitech G510 keyboard with the option of having 54 extra keys as a utility per aircraft. Current Ka-50 setup for 1.5.8 is not identical to 2.5.0 OpenBeta. Of course I can setup another mapping. Just bringing this issue to your attention.

My 2.2.0 Alpha was on a separate SSD. 2.5 OpenBeta install copied some files but did not hurt it in any way and left it intact. Before-hand I backed it up on an external hard drive just in case.

Me, too in Ka-50. I have not had problems with rearming. I have used all the red-team farps. Do not know about 104th. There are other servers that require complete shutdown for refueling and rearming. I have not messed with the radios, I leave them alone. I almost always fly solo except listening to the airdales' teamspeak channel. Start up and shutdowns I use the 2-key cheats. ********************************************************************************************************* ___________________________________CORRECTION : See my Message #334 this thread

re: === https://forums.eagle.ru/showpost.php?p=2963204&postcount=1122 Step #12) Whoop and shout, you have radio comms -+- Prior to 2.5 Beta Update. I have latest update installed. I cleared everything SRS and reinstalled latest. ========================== QUESTION concerning PTT Microphone : ========================== PTT in TeamSpeak 3 works fine Microphone in SRS looks to be open microphone >>> always on I set the PTT button to my stick which translates to my keyboard Scroll Lock : SRS_CONTROLS : =========== COMMON_PTT : Device = Keyboard Button = 70 I tested it with TS3 off. Audio Preview. 5.189.162.17:5014 Microphone is always on. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> How do I fix this for PTT only?

Still on Windows 7 Pro on a 2011 Alienware desktop, i7-2600 water cooled and GTX 970, 16GB ram. Happened in Multiplayer on the 104th's "Operation Longbow" earlier today flying Mi-8. Much thanks for the helpful how-to. =========================== My log .zip file got corrupted , so no-go for now. It will happen again and I will try to post the .zip file, then.

I need a how-to instructional. Game Crash Log for 1.5 : How Do I Attach the .zip File ?

Just read Message #31. I will give it another go.

(re: top of thread) Red Ka-50 needs ability for NVG and weapon loadout choices at FARPs or airports. Otherwise, what's the point of playing?

Manual update will be a DCS Friday patch at some time in near future?