Donut

Why can't ED just provide us with more detailed information and actual gameplay footage? It's a little concerning that they are not...

Yes, that is correct. What is incorrect right now in DCS is that the FORM knob should control the intensity of and turn off the formation lights (top and bottom of fuselage, both sides of vertical stabilizer)....but currently, it does not.

Same here. I have a hard time buying something before actually seeing it in an actual gameplay video and not a edited music video.

Great post. There should not be a single question as to what we should expect in regards to the Supercarrier now that ED is asking for our money. Unfortunately, there is nothing but questions. No gameplay video, specific details, how it performs in regards to FPS, etc. What happened with the F-16 release should make all of us a bit more cautious before jumping in on another Early Access release. I learned my lesson though and won't jump into another Early Access until ED is more open and informative.

Needs ED response... Yes, that is how it works now and how Wags explained it in the video...I strongly believe that it is incorrect. The problem right now is with the FORM knob. When the MASTER knob is set to NORM and WING/TAIL, FUSELAGE both set to BRT, the FORM knob should control the intensity of all formation lights from off to bright. Other than that, it seems that all other external lighting controls are working correctly.

I believe this is incorrect. Due to forum rule 1.16, I unfortunately cannot show you why.

ED response needed... Thank you for suggesting that. From what I am reading, when the MASTER knob is in NORM, the FORM knob should control the formation lights brightness and turn them off...this is not the case in DCS.

Yes! A man with great taste, and the resources to make it happen in DCS! Hopefully we see the Hellcat as ED's first WWII Pacific fighter!

Same for me. After what happened with the F-16 release, I am extremely hesitant to make any more Early Access purchases. There needs to be a tremendous amount of detailed information provided tomorrow before I would even think about pre-ordering.

That update was posted in the Hornet section. There was very little mentioned about the F-16 except for the radar gunsight.... We could use another Viper Mini-Update from Wags.

Oh man...no Tomcat update with today's latest Open Beta patch. Any news or update on the Forrestal and everything mentioned back in October? Last I heard was that the plan was to have the Forrestal in the first patch in January...

Needs ED response... Roger that...thank you so much for the feedback. Can we get an ED response and move this to the bug section?

Agreed...air to air is borderline useable right now with all the bugs. Remember everyone, implemented does not equal working. The reason I created this thread is to determine what is working and bug free out of what is implemented. This isn't about missing features, systems, or weapons that are to be implemented later in Early Access.

Thank you for the feedback, I knew I wasn't crazy...do you know what exactly isn't working correctly?

Thank you for the info. In your normal daytime configuration, the formation light that illuminates the vertical stabilizer would be on...is this correct and normal operation?

3 months into Early Access...what is the current state of the F-16? What is good/bad, what works, what doesn't? Personally, I am finding that it's still at a point where it isn't worth flying due to all the bugs and negative learning that comes from it. Yes, I know...Early Access. There comes a point though where we should start to see significant progress being made in fixing what is wrong and getting the F-16 up to speed in regards to a basic level of reliable functionality and quality...not even considering advanced weapons and systems yet. Just from reading the forum bug reports, it still seems that very little if anything is working right... Even the FM, aircraft handling, and control inputs seem to be incorrect/WIP, making just simply flying the F-16 very frustrating. This may be a question that only ED can answer, but at what point will the F-16 be in a state that is useable for correct operation and proper learning...just at the most basic level? The latest newsletter states a goal of completing the F-16 in the next 12 months...currently, I am finding that the F-16 isn't even at the level of quality that the Hornet was 18 months ago.

Why is this a wishlist item? Our job as paying customers in Early Access is to find out what is bugged/incorrect/incomplete, etc., and report it to ED. The helemet is wrong...this should be listed under the bugs section until corrected.

It's still confusing and doesn't make sense, as the knobs and switches do not do what they are labeled as doing. Does anyone, hopefully with real life experience, know the external lighting switch and knob positions for startup, taxi, takeoff, inflight, etc.? Maybe this will help me to better understand. Thank you!

So are traditional sticks like the Warthog not compatible or at the least, not ideal for use with the F-16 then?

Since release, the DCS F-16 nosewheel steering/rudder input has been significantly different compared to other aircraft. This may or may not be true to real aircraft behavior. I find the F-16 requires constant rudder input on takeoff and landing rolls in all weapon loadouts and/or clean. I find that it can be managed though and that I can maintain centerline if I continually "dance" on the pedals. It's really an art form that requires a bit of finesse.

Whoa, great news! Thanks for the heads up! Question though... I currently use EVGA Precision to limit my FPS to 60...would using NVIDIA Control Panel be better for limiting the frame rate?

Hmm, so I may have spoken too soon. Did some flying today....first flight, I got the brief screen flash again(during startup), but this time I didn't lose control input...I lost control input a few minutes later (right after raising the gear on takeoff). Strange stuff, will need to investigate further. FYI, the gear lever is mapped to a axis on my gamepad...still think that's causing the issue somehow.

I have noticed that achieving a precise pitch angle in the Tomcat is near impossible. Now, I know that the HUD is not to be used as a precise instrument, but isn't the VDI supposed to be? If I press CTRL+Y to bring up the flight data, the pitch angle shown and what my VDI is reading are a few degrees off. Is this correct behavior? How can I achieve precise pitch angles in the Tomcat?

+1 Very well said. Excellent work ED, very excited for this map!

+1 The Tomcat needs this...if not done by ED, hopefully Heatblur implements this with the Forrestal.