Ourorborus

Actually yes I was refering to real life civilian aircraft. As I was tought 25 years ago, most GA (at least back then) had a massive trim wheel that effectively needed you to look at the floor for about 4 seconds while rolling down the runway to set for t/o. The technique that was tought was to anticipate the out of trim (it wasn't ever that much if you were trimmed propoerly for approach) and trim out upwind when you can trim by feel and not need to look down at an indicator needle. It has been a long time since I flew censsnas though so maybe modern ones are better designed. If not, that would probably explain the scary wandering on the runway I regularly see from the tower.

Yes I have a cheap numpad setup for use in VR. Works really well. It is actually mounted upside down but I just mapped all the buttons to what I wanted. Yes I know I need to renew the stickers but I don't notice in VR as my

Push forward. No I'm not being flippant. Almost every aircraft has an issue where trim for final is different to trim for takeoff. You just fly the aircraft and trim out for the climb, If you spent time rolling the trim wheel forward on a GA aircraft before applying power you would run off the end of the runway. At least with the hornet it will trim itself once flaps are up.

Vr only here and I never use the body. In fact I find immersion breaking. This is due to the fact it blocks my access to controls. If it were my real body I could access those controls without thinking about it, but with the sim body I am painfully aware that it is not my knee/arm that is blocking my access. Sent from my SM-G980F using Tapatalk

Same here. Although I am new to MP so it could be something obvious I have overlooked.

Does anyone know the equivalent file for F18? Mine are now unreadable. F18 equivalent files can be found at \DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group

I Will try the manual mode tonight/tomorrow and see how I go. The odd thing is SSM opens and if I click test it works, issue sems to be with SSA.

I would say Stable = less frequenct changes. Still many bugs but they don't change very frequently. OB= Bugs change on a weekly basis. Something that worked last week may not work this week. You do get the latest cool features. Also worth considering: if you are learning an aircraft stable can be better as aircraft functionality doesn't change overnight. if you plan to use the forums for help you are arguably better with OB as almost everyone here uses OB and may not experience the same issues as someone on stable. I normally use Stable so I don't spend half my flying time developing new work arounds. Occassionally (like now) I bump to OB when I see in the forums some improvements in that I think I would rather not wait for. When they go stable I will revert.

Same problem here. If I let it minimise to systray, it vanishes if I mouse into systray. If I (following reinstall) keep it on screen, it looks like it is working but doesnt communicate with DCS.

I found the same. I wasn't sure if it was a change to how it SHOULD work or just a bug but now I find to slew the TGP to a waypoint I have to TDC to the MDI/AMPCD that I have the SA/HSI displayed on , then press the OBS for TGT designate. Then I can TDC back to the TGP. For me I usually have TGP on left and SA/HSI on the AMPCD (middle). I go TDC down, select waypoint/markpoint, Traget desig on the AMPCD, then TDC left to adjust the TGP.

The new clouds seem to have introduced the existing "cockpit too dark" issue to a wider audience. Many have complained in the past the brightness delta between inside the cockpit and outside is far too great. I.e if you set the gamma to see inside the cockpit the outside world is washed out or if you set the gamma for outside the cockpit is black hole. (not referring to cockpit vs external view, referring to the view outside while sitting in the cockpit) Now we have the new clouds the effect seems to have extended to shaadows cast by the new clouds. i.e if you set gamma for no clouds/ flying above the clouds, then flying under clouds is like night time. Alternativeley if you set gamma for in the shade, then above/no clouds is washed out. Of course not everyone experiences this, possibly due to hardware differences. Please implement a "Shadow intensity" slider in the settings so we can adjust the depth/relative darkness/insity of the in -game shadows. Overly dark when flying in shade under a cloud - Page 2 - Clouds and Weather - ED Forums (eagle.ru) Clouds shadow - Clouds and Weather - ED Forums (eagle.ru) P-47 cockpit too dark, a comparaison - DCS: P-47 Thunderbolt - ED Forums (eagle.ru) 2.5 Cockpit is too dark? - DCS: Mi-8MTV2 Magnificent Eight - ED Forums (eagle.ru) new cockpit at night is too dark - no buttons visible - Page 2 - DCS: A-10C Warthog - ED Forums (eagle.ru) [CAN NOT REPRODUCE]A-10C II Console and panel lights - Bugs - ED Forums (eagle.ru) Global Illumination/ Light Intensity - Page 2 - DCS Wishlist - ED Forums (eagle.ru) Still a very dark cockpit - M-2000 - ED Forums (eagle.ru)

This looks closely related to the common "cockpit is too dark" issue. I am one who (in VR) has to have all cockpit lighting on max in the middle of the day as unless the sun is beaming directly on my dash it is too dark to be readable. (Not the MFD displays, the physical labels etc.) If I turn Gamma up to compensate, the outside world is completley washed out. I have noticed this is because the shadows on my cockpit are too "intense" for want of a better word. It looks like the new clouds are casuing this same effect. The shadows are too "intense". i.e the delta between in and out of shadow is too great. Since it is not a problem for everyone (different hardware), a great fix would be a shadow intensity slider. In the mean time I'll stick to Release version until it is fixed.

When I learned to fly helo's many moons ago, I learned to rest my forearm on my thigh to provide finer control. When I first got my Warthog I set it up as a side stick as I had no way to mount in the middle. When I upgraded my chair to a Secret Labs titan, I found the big flat base of the warthog fits nicely on the big base of the seat. My thighs rest on top of the base locking it in place, putting the stick in the perfect position to fly like I used to. My fine control, immediately improved. So centre mount for me.

In the controls for recording HUD are down near our left knee. AFAIK they are not functional though. It would be a great addition for ED to add and would be available in many other acft as well.

A quick tip I learned today for AAR...... FPS!!! (or possibly frame time) I have recently upgraded from a GTX1060 to an RTX3070 (yay me) and today I loaded up DCS for the first time since the upgrade. I fly in VR and found the 1060 limiting but "playable" FPS was shall we say low.. (40-50). Loading up today the whole sim is soo much smoother. I didn't measure the FPS but it was an experience to see how much smoother it was. Why am I posting in an AAR thread? Because my take away was with the better performance AAR suddenly became easy! The much smoother gameplay had me connecting and reconnecting with ease. So anyone struggling with AAR I suggest lowing a few options (or upgrading pc if budget allows) and see if it makes a difference. It may be that what you thought was "good enough" may be adversely affecting your ability to make the fine adjustments needed to maintain station.

+1

When I used to fly in 2d I used the friction slider. In VR I use the mic transmit switch depress.

Clearly they do care or they wouldn't adjust the night lighting every patch. I think hardware and individual perception seems to play a big and unacknowledged part here. Every time ED "fix" the lighting we get equal numbers of "thank you" posts and "you have ruined it" posts. (I personally find the daylight way too bright compared to the inside of my cockpit.) Please ED, add some more user adjustable options for night lighting. Separate sliders for acft internal, aircraft external, ambient day lighting, ambient night, and ground objects would be fantastic.

Big newy, Cheers. As always love your work. To shorten my long post. Disabling guard receive on comm2 shouldn't effect dialled freq trans/receive on either box. Sent from my F8331 using Tapatalk

To back up GB. As an ATC either ashore or at sea, you always try to get acft on the ground as soon as possible. An empty strip bay/scope is far easier to manage than a full one. However, often delays are due to things the pilot is not immediately aware of. E. G. Weather. Obstructed deck/black runway. Ship not in wind/pitch/roll limits. Cable issues. Mullets refusing to give green deck. Other traffic. Traffic with higher priority. The list goes on. Any half decent ATC will inform the pilot the reason for any delay but it is not always possible... And I can imagine would be a challenge to code into dcs. A simple number x in the sequence would be nice though. Sent from my F8331 using Tapatalk

Big newy. There seems to be a disconnect between the statement of guard receiver and guard transmit. The first para states guard receiver is on but then the second statement states this restricts transmission to guard. Generally modern aviation radios have a guard monitor function. This means guard is received as well as the dialled freq. This feature does not effect the transmission freq. E. G. Radio has 121.5 dialled in. Radio will receive broadcasts on guard and 121.5 but will only transmit in 121.5. It seems to me the devs first statement indicates the guard monitor function is disabled on comm2. This makes sense as you only need guard monitoring on one box. Thus the radio should still have the dialled freq fully functional. Sent from my F8331 using Tapatalk

What sort of FPS do you get with the 2080ti and the Pimax?

I'm a former raaf controller and now civilians an regulator. In Aust 250 below A010 stands for all. Military for the most part follow the same rules as civvies. Except when in restricted areas designated for training where ATC doesn't play. Sent from my F8331 using Tapatalk

This. ...Has happened once or twice to me too.

You mean a say again function. Never say repeat on a radio. It is a brevity word for repeat last fire mission. Sent from my F8331 using Tapatalk