Donut

+1 I have been hoping for a tropical Pacific island map...thank you ED!

Yes! Great news and great for carrier ops! Excellent choice of an area to map...looking forward to hearing about the details!

For those who have it, what are your thoughts on the Virpil VFX Grip? I have a Warthog stick now, how does the quality compare? How is shipping/cost, I live in the U.S. How is customer support? If the reviews are high, I am thinking of getting one once the grip with no twist axis is in stock again. I would consider the VKB as well, but it is not compatible with my Warthog base.

Agreed...very disappointing and very far from great. The F-16 had a better month than the Hornet and still seems to be taking resources away.

Don't have much time to test right now, but just did a quick 10 minute flight and it seems to have fixed the problem! I will test more thoroughly at another time, but this may be the fix! Thank you for your time and help!

How much knowledge does the F-14 pilot have on the radar and it's use? What is covered during training? In the Hornet and Viper, the pilot must obviously know everything about the radar and how to operate it, but that is not the case when you have a RIO.

The D or a B with the Sparrowhawk upgrade will allow the Tomcat to be used in much more realistic scenarios that extend into the 2000's and not seem out of place with the current line up of other DCS aircraft.

Thank you again for all the advice...I have attempted all of that already while troubleshooting on my end with no success. The only thing that I can think of is that DCS is losing focus for some reason...maybe due to the Logitech Gamepad I have connected or something else. It happens within the first 5-10 minutes of first starting DCS and never happens again within the same session.

Thank you for the help. My GPU driver is up to date. I have attached my DCS log. dcs log.txt

It would be interesting to hear if plans have changed and the Sparrohawk HUD is now a possibility...

+1 20 months ago, I bought what was advertised as a U.S. Navy F/A-18...we still don't have that.

Since the past few Open Beta updates, I have been experiencing the following problem... The screen will flash once and very briefly (like it does when pressing ALT + ENTER), a black box with the DCS logo also appears in the center of the screen during this brief flash. Once done, I find that I have lost all control inputs for a few seconds. Randomly pressing some buttons will eventually resolve the issue. This only happens once per session and all is normal afterwards. It has happened in various aircraft and on various maps. Any thoughts as to what this could be?

1. Completed/corrected F-14B cockpit 2. Jester LANTIRN 3. TWS Auto 4. Improved/additional over wing vapor 5. Improved/brighter exterior lights 6. Additional official squadron liveries 7. Ground power and air carts 8. F-14D and/or F-14B SparrowHawk upgrade 9. A-6 AI 10. Forrestal

Wink, wink...nudge, nudge.... Maybe SkateZilla knows something....

Great stuff, thanks for the update! Keep up the amazing work! Merry Christmas! Hope to fly the Corsair in 2020! :pilotfly:

Whoa, this is great news!!!! I was really hoping for a Pacific map!!!

It seems the October development update was overly optimistic...hopefully everything is okay. Nothing mentioned for the Tomcat was accomplished except for the helmet visor knob fix. Maybe we will get an update soon...

Running the latest Open Beta... All external lighting on, the port wing position light is not visible

Thank you for posting that...yes, does seem to be working as designed. They could have designed it better though... For the FORMATION knob, does "varies" mean that it controls the intensity of the white lights?

Thank you, looking forward to the update! Although, a new update in regards to the Tomcat may just be a copy paste of the October Thunder and Cat development update...

For some reason, the external lighting controls seem overly complicated and not very intuitive. At first glance, I would take each external lighting switch/knob at face value as they are labeled, but that doesn't seem to be the case. The FORMATION lights knob does not control the formation light that illuminates the tail. The FUSELAGE POSITION lights switch does not control the fuselage position lights located on each side of the engine intake. Can someone explain why this is and also give an in depth explanation on how these switches should be positioned for startup, taxi, takeoff, and during flight?

Well, if that is how it works...but it doesn't make any sense. The FUSELAGE position lights switch controls the tail formation light... The FORMATION light knob controls the positions lights... Huh???

It still seems to be EXTREMELY Early Access. A lot of things missing. For the systems/features that have been implemented, they are still bugged or incomplete. There really is little to nothing that is 100% fully functioning and/or correct at this stage of development...hence the reason for the lack of tutorials. Hopefully the update tomorrow will greatly improve on all of this and finally bring the F-16 to a state that is more useable.

It seems that the formation lights that illuminate the tail do not turn off when the formation lights knob is rotated to off.

You guys are right...I am being a bit over critical and not fully accepting and understanding the F-16 early access as it is. My apologies to ED. I am going to take a step back and start from scratch with the F-16 and give it another chance. I flew it a bit more today and realize the progress that has been made since release and the great potential for it to be something really incredible. Seeing the wing flex video today was very encouraging as well.