Donut

Great post and fun to read! Now here are some of my Christmas wishes that only Santa could probably ever deliver... Dear Santa, 1. World War II Pacific with a map for Hawaii, Midway, and the Guadalcanal/Solomon Islands/Coral Sea area 2. Essex Class aircraft carriers 3. Grumman F4F Wildcat 4. Grumman F6F Hellcat 5. Grumman TBF Avenger 6. Oceana NAS and offshore training areas 7. Grumman A-6E Intruder...I know, Heatblur might be able to pull this one off... 8. E-2 Hawkeye with multicrew capability 9. Ready Room 10. Updated logbook to include U.S. Navy ranks and tracking of carrier landing grades :xmas:Merry Christmas and Happy Flying to all!!!:xmas:

What is the "HOTAS HARM sequence"...and where was this mentioned?

Great question...it seems that the Christen Eagle II is taking a lot longer to release then originally planned. According to this post: https://forums.eagle.ru/showpost.php?p=3471322&postcount=1, the CE II would have been given to ED for initial review on May 9 so there must have been some significant issues that needed to be corrected. I wonder how this delay affects the Corsair and associated content (Pacific map and aircraft carrier)…?

Good question...holding the TDC while slewing seems impossible with my X-55 HOTAS. I am trying to figure out a possible solution but cannot come up with anything that that wouldn't be unrealistic and dysfunctional and also significantly mess up my current control mappings.

This is incredible work! Thank you so much for doing this!

I have tried out VR in DCS with the Oculus Rift and the immersion is incredible and it is something I will without a doubt upgrade to someday. Like you however, I hope the next generation of VR and higher resolution will be here soon, although; I haven't really heard of anything on the horizon. I am also a little concerned as well about what type of hardware the new VR headsets will require.

Disturbing and a huge oversight indeed. I seriously cannot wrap my mind around their decision not to include NAS Fallon. They put so much effort into adding civilian airports and yet we are missing one of the most important US bases and what would be a very much needed and only NAS in DCS. NTTR is supposed to serve as a realistic training area before "deploying" to other maps such as the Persian Gulf and Caucasus. While we only had the A-10C as the main full fidelity module, NTTR and Nellis AFB was perfectly fine, however; DCS is becoming much more naval aviation oriented with the Hornet and Tomcat and NAS Fallon is very much needed. The location of NAS Fallon is already within the boundaries of the NTTR map but it is just outside of the detailed area of the map. It is approximately 68 nm to the northwest of Minas airport. The detailed portion would have to expanded only one grid square to the northwest to include NAS Fallon. I really hope they reconsider and surprise us all with the very much needed NAS Fallon.

The last mention of LTWS that I can find is in the 10/18/2018 Hornet Mini-Update: https://forums.eagle.ru/showpost.php?p=3661070&postcount=80 "3- A/A radar antenna. When complete, then LTWS." I don't know exactly what radar antenna means in this context but maybe the mention of further radar debugging in the latest mini-update refers to this radar antenna as well and is needed to be complete before LTWS.

In regards to IR Mavs, it will be more than bug fixes...it will hopefully be actually implementing the correct version of the AGM-65 that the Hornet carried which is the F. The Hornet did not carry the D or G which is what we currently have in DCS. In the end, the only two versions of the AGM-65 that the Hornet will carry is the E and F.

This should not be backburner stuff for ED. I consider the game to be broken if I can only fly a mission solo because my wingman cannot air to air refuel. We should not have to be adding mods for such a basic but vital part of flying the Hornet in DCS.

Yeah, this is concerning for sure. I would like to buy a Thrustmaster HOTAS but am holding off until I see what the Hornet stick is like. I don't want to go ahead and buy the Warthog only to find out that I wish I had bought the Hornet stick instead.

Great stuff as always! Thank you for the presentation, I definitely learned a few things!

TrackIR here until the next gen VR headsets with increased resolution as well as the VR improvements in DCS and implementation of Vulkan.

Well, I read my post again and I should have been a little more specific. My results are with the Hornet only and I have not flown any other module to test how they perform on my system. The FPS and performance information that I have given though is indeed correct for me and what I am seeing each time I fly the Hornet. Now sure, when I set my FPS to unlimited, I will see it climb to 120's-140's (with CPU and GPU loads nearing 100% at times) if I look in the direction of open sky, water, or desert but as soon as I look towards or fly over a congested area, average FPS will drop to 70's-80's with the occasional dips below 60. There is no way at anytime while flying the Hornet with my system and in game settings that I could sustain anything near my 144Hz refresh rate. I could of course lower my settings but I paid a lot of money to finally get DCS looking good with high graphics settings so I will live with the reduction in FPS. As for TrackIR...I first read on the forums about stutters when FPS was not 120 or 60 but didn't think I had issues until I tested it out and boy was I surprised...I never noticed the stutters until I limited my FPS to 60 and panning my head around was very noticeably smoother. Another benefit of limiting my FPS is that my CPU and GPU loads are cut in half and not spiking to 100% anymore. Your comments on Vulkan are encouraging and I hope we see it soon. Apparently it is in internal testing by ED. So...to the OP...as you can see, there are a lot of variables that will determine if you will benefit from a 1440p 144Hz monitor but at the very least, get the best GPU that you can afford.

I upgraded from 1080p to 1440p about a year ago. The increase in resolution is really amazing and has many benefits; however, it comes at a significant cost. Your 1060 will struggle unless you turn down in games setting significantly. I have a 1080 Ti and drop below 60 FPS in some situations with the below in-game settings. My monitor has a 144Hz refresh rate and as you probably already know, it's completely useless to me and far as I can tell. Also, I have had to limit my FPS to 60 to support the TrackIR refresh rate of 120Hz...120 FPS is not achievable either in DCS with high settings, hence the limit to 60 FPS. So, 1440p is great and I highly recommend it over 1080p but it will need significant hardware to support it and to me, any monitor with a refresh rate over 60Hz is useless for me right now because of TrackIR and the struggle to maintain 60 FPS at all times. Hopefully Vulkan API and optimization of the Hornet will increases overall performance and FPS but until then, it's a struggle.

Wow, impressive work...thank you for the research. If your data is correct, which it seems to be...this is a serious problem. Can one of the forum moderators merge this with the other posts regarding this topic and move this to the appropriate bugs forum? I can only hope that we get this corrected with the new aircraft carrier module and that they aren't using the same data from the old one.

ED just needs to add NAS Fallon to the NTTR map. It only requires expansion of one grid square to the northwest of the current map. Then we have a NAS with IFOLS for out Hornets and Tomcats.

Video is not working...

My apologies. I did not mean to derail or hijack the thread, however...low FPS, FPS drops, stutters, etc... it's all the same and is happening in all types of situations and stages of flight. There are some underlying performance issues in DCS with the Hornet and hopefully the solution will fix all of this. For starters though, I just want to see ED acknowledge all of our posts.

Yep, the Hornet is really hard on FPS and it's made worse with any Hornet statics around. I was on the deck of the Stennis in the #1 spot starting up and when I looked over towards the island with a few Hornet statics in front and my FPS dropped to 53. My shadows are turned down low as well. This poor performance really needs to be addressed but I have yet to see anyone from ED respond to any of the numerous threads about this issue.

Don't forget Vulkan API, improved weather/clouds, improved US aircraft carrier and ATC...

I cannot begin to fathom why in the world they did not include NAS Fallon. It's location is within the boundaries of the current NTTR map. NAS Fallon is 68nm northwest of Minas airport. They would literally have to just expand the map one grid square to the northwest to include NAS Fallon. They put so much effort at including various civilian airports on the NTTR map but failed to include one of the of the most important US military bases...for a military combat flightsim. Maybe at the time of development, they weren't sure about the Hornet and didn't know about the Tomcat.

I haven't heard anything from ED about the updated Stennis and deck crew other than that it's in the works. I know that Heatblur put work on their deck crew on hold because ED is working on it as well. As for the TM Hornet stick...I haven't really heard anything since this past Summer when they announced a planned release by the end of 2018...which seems highly unlikely at this point. I don't really know what the delay is on this unless they are working on a complete HOTAS and will include a throttle as well but that may just be wishful thinking.

Here is ED's plans for 2018 from last year to give you some perspective on what to realistically expect. https://forums.eagle.ru/showpost.php?p=3338291&postcount=123 As you can see from what was planned for 2018, a lot has yet to be accomplished which creates an ever increasing backlog each year. I don't see ED really planning anything new for 2019 because there is so much from past years that needs to be accomplished first.

Okay everyone...I found the solution!!! Go to DCS World\Mods\aircraft\FA-18C and open the Views.lua file and find the following line near the top... CameraViewAngleLimits = {30.000000,150.000000}, The default values are 20, 140 which gives a midpoint of 80. I changed it to 30, 150 to give me a midpoint of 90 on my HOTAS zoom axis which now matches by default FOV of 90 that I set. Hope this solution helps!!