wernst

I tried the old (stable version) A-10C NIGHT cockpit and could see how much different it is in comparison to the new one. Switches and knobs are clearly visible, flood light is functional, no much monitor brightness adjustment needed. The new cockpit is "nice" to look at but it's almost not usable at night.

new cockpit at night is too dark - no buttons visible At night the new cockpit and outside scenery appears much darker than before. Floodlight has less to no effect in order to brighten the cockpit inside, buttons and knobs are almost unvisible. Increasing monitor brightness or gamma doesn't help much as only instruments and HUD getting brighter but buttons and knobs stay in dark. EDIT: sorry for double posting, this issue has already been adressed just before by webweaver40 2nd EDIT: Just loaded an old stable version (2.5.3.24984 of 12/12/2019): Everything is fine with A-10C Cockpit at night, all controls clearly visible

+1

"2016 was supposed to be the great year for the Carriers in DCSW". This was a vague approximation about the future. It clarifies potential customers questions as fully as vague approximations can clarify. What's the problem here? I'm happy that ED finally made it.

+1 +1

sorry, you're right. Of Course, 190 kts was my initial approach speed on downwind (gear down) and sure not the final touch down speed. On final after setting the AoA for landing configuration the touch down speed was always below 150 kts. But even so the grass at the end of the RWY could then be seen in detail.

I canconfirm your findings. Landing roll is by far too long, effect of applying full wheel brakes is barely noticeable. Landing without any payload, with half fuel, moderate headwind, full speed brakes, touch down on threshold at 190 kts may end up in the grass at the end of RWY (e.g. CAU, Senaki)

Yes, it is. I tried to setup the gun on the ground. I thought there must be a simple solution - yes, there is one, a stupid simple solution. Thanks toutenglisse.

Sorry, for my beginner’s question. I can’t activate the gun, why? What I did and what I see: Switching Master Arm selector to “ARM” But in the SMS page the status is still “SAFE” not “ARM”. And, the master mode A/G switch cannot be activated - no green “A/G” lights up. The SMS page shows 578 on top or the triangle. What am I missing? I’m afraid it’s a simple but stupid fault.

really great animation mod which I was desperately looking for (making a little video clip, a fighter pilot tells a story) I'm a reasonable DCS pilot but unfortunately I'm not smart in programming the ME properly to get the pilot acting and running. Any guess when your video guide will be available?

+1 it's not only an experiment, it's my standard takeoff from ground practice with the Hornet. Just don't do anything with the stick until nose is up and you have smooth lift off. The FCS will automatically set the flight controls to best climb attitude. Once you have positive climb take back ontrol of the stick. It's the same practice as with takeoff from carrier. You give full throttle and let go the stick until positive climb. With e.g. FW190 Dora any takeoff is by far more complicated and critical.

I know it's normal. My reply was meant for dutch60 who is missing the 3D GPS in the L-39 cockpit. The NS430 panel bug only effects the 2D overlay version for all modules. The Mi-8 and L-39C have the 3D GPS on start. But the L-39C must have the gun sight disabled.

Having the same 2D issue. The 3D GPS in cockpit for the L-39C is working but you have to disable gun sight first.

I don't have any external mods but I have the same problem as many others have.

EDIT: issue has been solved by recent hotfix today I realized that the NS430 doesn't work anymore. A couple of weeks ago it was working well. I have the latest beta 2.5.4.26368 installed. I initially found this issue on Caucasus with UH-1H and P-51D but all modules are affected. With LShift+LAlt+B the NS 430 windows appears with the “NS 430” labeling on the top bar of the window, but the window is empty. There is no GPS user interface in the window. Instead there is only some part of the external view visible within this window. Yes, I have all modules enabled for NS430 cockpit under "options/special" Yes, I have purchased all three versions of the NS 430 (2D, 3D cockpit for Mi 8 and L39) The 3D cockpit versions of the NS430 for the Mi-8MTV and L-39 are working. EDIT L-39: after gun sight OFF, 3D cockpit version is working On the same PC I have the latest DCS 2.5. stable installed. Here everything related to the NS 430 works fine. Is there anything wrong with one of the latest beta updates in relation to the NS430?

ok., "WIP". But there is another note saying: "A release of a feature-complete module is scheduled for January 23rd, 2019" I doubt it that the dev team is able to polish the basic deficiencies of their graphics programming within the next 14 days. The promo trailer should show the highlights of the final product, shouldn't it? Don't get me wrong. I truly appreciate DCS's second release of a purely civil plane. Even more as it is dedicated to aerobatics mainly. But (un)fortunately I'm fully spoiled with the extraordinary high standard of all DCS's modules so I can't help comparing any "newcomer" with the existing ones.

My disapointment is a result of seeing the promo video. I suppose the promo video is made at it's best to generate DCS pilots excitement. The two pics of a real CE II cockpit and the sim version of it may give some impressions of what I mean. It's all about light! The DCS CE II has unnatural flat lighting, it has no shadows and reflections which make the perfect 3D impression. It's the same seeing this plane in the air. It looks unnatural flat, kind of 2D. The plane appears badly superimposed to the environmental textures. One can see unnatural sharp borders between the plane and the background textures. I doubt it's written in any of DCS's graphical engines. Look at the other DCS planes, they all appear photorealistic on the ground and in the air, you'll have difficulties to see whether they are sim or real. They are simply great! When the CE II modul is available you may put it next to a F-18C and you'll get my point.

yes, exactly!

Yes! The plane graphics (cockpit, external) indeed is much below to the level of all other DCS planes. It's on a level like the planes of early MS FS days. The detailed DCS terrain textures don't help much to improve the bad appearance of the CE 2.

Thanks Frederf, yes, the issue with the warning is clearly related to trim settings before take off. But the warning lines appear during landing under conditions wich I still don't understand well. Of course the plane has to settle on the main wheels first when touching the ground. After the main wheels have touched the ground I try to hold the nose up as long as possible to avoid damage to the nose wheel. (As I have been trained to do in RL) If I'm able to manage to let the nose wheel sink buttery smooth down to the ground I'm fine, no warning. But as soon as the nose wheel touches the ground a little harder the lines appear plus warning tone. My initial conclusion: The display of warning lines depends on how smooth the nose wheel have touched the ground, a kind of indication that the nose wheel may have been damaged. But according what you have explained it's not. What is it? When beeing on short final I usually don't trim anymore and AP has been deactivated much earlier before.

After hot start and before taxiing I get these 4 tilted lines on the lower part of the HUD plus system warning lamp / tone. The lines disappear after take off. The same messages appear during landing when the nose wheel touches down a little harder than usual.

Yes, the TM Warthog grip is really solid made of metal. As it's compatible with the Virpil base I'll buy the base only - regardless of any TM version II for the Hornet.

well said, can't agree more. I openend my TM Warthog stick recently in order to clean and grease the moving parts. I was shocked how cheesy and primitive the overall design of the mechanics is. One shouldn't say "mechanics" it's cheap "plastics" only. I'll soon buy the Virpil stick.

as drPhibes has already explained its 84X and 84Y, they are different channels. TACANs double the number of channels by having an X and Y bands. This allows more TACANs to be used without repeating channels too close to each other. Most civilian systems use X channel spacing. The plane transmits on 1025 MHz and the ground Station replies on 962 MHz. In a Y channel system the plane transmits on 1025 MHz and the ground Station replies on 1088 Mhz.

Yes, discwalker, you have a valid argument, carrier op could be an issue if NWS is not reliable. But it simply isn’t unreliable, it's working well. I have bound “HI” function of NWS to the pinky lever of my TM Warthog joystick. In order to maneuver the Hornet slowly on the carrier deck I keep the “HI” function continuously to ON by holding the pinky lever down. With little or more inputs to the rudder I’m able to fine control a gradual deflection of the nose wheel hence the fine control of the movement on deck. Of course, with full rudder input the nose wheel will deflect 90 deg and block any controlled movement. Even if this happened I may simply release the rudder input and I’m immediately fine. I really don’t understand the issue here. Yes, there could be a limitation for the nose wheel max deflection, e.g. to a max of 75 degrees. But I can live with situation as it is right now without any headaches for me - and for the ED team.