Steve Gee

That is my exact problem. The squelch sound volume can't be changed and is extremely loud. I was able to reduce it through creative equalizing of sound frequencies, but it affects other sounds. I don't use headphones, I have a 5.1 surround system.

No, I select a map theme as my background, so I see the different planes when they load. I've had the F-14 since it was released and the background's never shown for me.

Really something minor I noticed long ago and never really thought much about it until today for some reason. Running the one screen @ 5760 x 1080 setting in game. When I load a mission with the F-14, once the loading screen changes to the screen where the plane name shows up at the bottom, the background doesn't change to show a Tomcat. It stays the what I guess is the ED default background of clouds. Every other plane, at that point in the loading process, changes to the loading background of said plane. The F-14 never has for me. Insignificant, yes. But, maybe something to throw in the March 2021 to do list. :)

Not talking aircraft specific. :) That was part of the other discussion, do all "parties" in a scenario besides aircraft add to the datalink picture, such as ships and ground stations? And if they do, wouldn't the datalink from any source then, such as the CVN's, show the entire picture so it wouldn't matter the selection?

R Ctrl + R Shift and NumPad / and * will zoom your "seat" as I call it, in and out to either of the views in your screens and then you can save it like Habu mentioned, with SnapView Saving on and R Alt and NumPad 0. That will now be your default view when you get in that cockpit.

Is there a table/chart/anything that shows the ranges the radar sets in DCS have? Got curious to the, if any, differences between having your datalink between your plane and AWACS and carrier(s). Initially, I've noticed the carrier's radar range doesn't seem to be as far as the AWACS and it's limited/masked by terrain it seems. That in turn got me curious to the connections, if any again, with the datalink components such as AWACS, ships and the like, to give the player the overall picture. Or, is it just one big broadcast "photo" taken from the map instead of actual radar imaging/processing?

I wonder if there's any sort of table/chart, giving the ranges of the radar sets emulated in DCS? Off to ask ED. :)

Thank you, good sir. :)

Did some switching between the two today in a MP session...I know, not the best testbed, noticed the carrier would show the rescue helicopter assigned to it on the TID, AWACS (E-3) never did. Maybe just a mission design thing. Range was definitely shorter for the carrier compared to the AWACS before they showed up as datalink targets.

I'm having the same problems as the OP did, with the same missions pretty much. Would like to have the fixed ones as well, if possible. Thanks. :)

That was my initial thinking, E-2/E-3 aren't horizon limited but I was wondering just what the depth of ED's AWACS portrayal is? Are they...AWACS/ship radars/ground radar...linked in any way or are all assets standalone? I can't see any sort of shared information network, so my guess is it's simplified.

I was wondering what the major differences, if any, between having the datalink hosted by the carrier, as opposed to the AWACS?

In external/F2 view, when you zoom out and get to the point the next LOD takes over, the wingtip formation lights disappear completely while all remaining external lights remain visable.

We can have different helmets until the view externally is zoomed out to the 2nd LOD level, then the LOD3_1 file takes over the helmet graphic rendering and it changes to have the same helmet for both pilots, as only one helmet texture file is rendered/assigned to the helmets..

Sort of pilot related. Is there a change planned/mentioned for the helmets to have different textures for the Pilot/RIO in all LOD's? Or, is that just a Top Gun movie thing and they all had the same look in Fleet service?

+1

Glad to hear a semi-firm date for the -A (October patch). Had some rig upgrades planned, gives me more time to complete them.

It was my favorite plane in Flanker 2.5.

Thanks. :) So, nothing major...EGT/TIT and scale(s) it looks like. I remember reading the Nozzle Position gauges we have currently are actually TF30 ones. Curious if they are or if they'll get changed as well?

I was actually able to equalize the depth I guess you could call it of the radio sidetone, so my Tomcat's flyable again. It's the only one of the sounds mentioned by some here that I had problems with. I know ED's lighting changes, for the better I have to say, sets back your overall development schedule but it works out in the end. I know the sound ones will as well. :)

I know we'll see/get a new EIG for the B sometime when HB's done with A production, but I was wondering just what ARE the differences between the two, visually? Or is it just internals? The only pictures I've found all look like the one that's modeled in the B currently. Thanks for any pictures anyone can share/link. :)

If you have to turn a certain volume down because of extreme loudness and it affects another sound's volume, that's not control. That's adaption. And, it only happened once. :) Like the F-16's initial startup when ED left the Squelch turned off.

Happening since previous patch of today (8/19) for me. Whenever I use the JESTER interface (key command A), the sounds from it are very, very loud. Loud enough to damage my speakers loud. In other words, really LOUD. And, I see no adjustment within DCS for this volume. I know ED's adjusting sound, and seems like everything else, levels so I'm guessing this will be rectified once they are done tweaking, as the lights were?

My bad, seems to be something external causing to skip that middle step, keystrokes work as intended. Thanks.

Not sure when, since it was a few versions ago that I played DCS, but now for some reason if I program the PZ70 Flaps switch to move the flaps incrementally on my F/A-18...Full/Half/Auto...using the appropriate key commands, the flaps selector won't stop at the Half point, only at Full or Auto. Checking the key commands through the keyboard, the switch moves as it should. In the past, it's always worked as it should, but it's not any more. Is there a new setting or something I'm missing with the latest version of DCSFP?