Legendofdino

Obviously right now we can’t setup sequences in ME therefore I’m curious what if any method can be used to move say if I have waypoints 6-9 which are my attack sequence waypoints to sequence 2 the anything after that to sequence 3 for the egress back home? Besides deleting and reentering those waypoints along w posn data what other options do I have?

Ideally if you’re performing SEAD then you’re looking to suppress enemy air defenses so by firing a harm at a tracking station in a real environment would cause them to turn off their search radar effectively suppressing them but not necessarily destroy them. In DEAD you are looking to kill the tracking station and perhaps launch sites probably to attrit the enemy so a mav may be a more suitable option.

If what’s been stated before about flight deck lighting not correlating to objects on the deck then how are we seeing it on Razbam’s LHD? https://forums.eagle.ru/showpost.php?p=3684083&postcount=401 Please ED, lets see the flight deck lighting implemented

The heatblur team has done a phenomenal job implementing realistic head movement on their F14. What is the possibility of Implementing this into the hornet?

There's a HMD OSB option which pops up on supp menu when jhcms is turned on w night day option. Doesn't seem implemented yet.

To answer your question about real life, there’s a program called JMEMS, the Joint Munitions Effectiveness Manual which calculates target info such as armor thickness and gives recommendations on best ordinance to be employed.

Revisiting this because I believe it’s important and interested to know from devs if there’s a lingering reason why it’s not active in game if modelviewer has option.

My votes for F/A-18D!

Use the attitude hold option on AP system, first button on scratch pad. For radar altimeter warning use radalt gauge located on panel under hook lever.

Yes and only getting better

Thanks so much for the great resource. I have a slight issue though when I open my \Saved Games\DCS.openbeta\Config\Input\FA-18C_hornet\joystick\Throttle- HOTAS Warthog.diff.lua it looks nothing like what all is posted here. Instead my code looks like: ["added"] = { [1] = { ["key"] = "JOY_BTN27", }, }, ["name"] = "RADAR Switch - OPR", }, Am I opening the wrong file?

Good info here, just a quick input on my methods. In the break at 350kias I usually drop power to idle, deploy the brake until 240kias, drop gear and flaps with usually about 20* of turn left for my downwind. I keep the power off until I approach 150ish kias but I keep a scan of my VSI, alt, and AoA indexer. Thats not to say that every pass is perfect, if I do have some lift that's raising my nose out of that 600 asl then nothing wrong at that point with using a little forward stick to keep the nose down until she stabilizes.

If not hostile then definitely rude. The data cartridge next to IFF and SA page are probably the most important features of the hornet. Successful implementation would allow for greater in-depth mission planning through preprogrammed CMS profiles, waypoints with detailed information, IFF squawk codes, and weapons profiles. All of which have the potential to be configured in programs such as Combatflite before one ever enters the pit. So lets try not to answer a question the "Wish List" forum with "NO" right off the bat without understanding what's being asked. /end rant

Lots of good info here. To input my .02, it takes a lot of practice to develop what I would refer to as a workflow in the pit. Detecting and engaging bad guys requires a combination of using the sensors in the pit (rwr and radar), getting your head outside the pit scanning, using, bogey dopes to point your nose in the right direction, and probably most importantly finding a friend because 4 eyes are better than one. You have to develop a method that works for you in interpreting the data from all these inputs sometimes in situations that can develop quickly.

Perfect ty!

Got it to work but it also removes the screens in the pit when in default F1. Is there a way to avoid this?

So all im gathering is +purposes = {render_purpose.GENERAL} is added to each file? Can this be run in JSGME?

Good morning, As the title states, i'm looking to remove the MFD's from the Alt F1 view on the hornet. I tried modifying the ViewportHandling.lua located in \Scripts\Aircrafts\_Common\Cockpit with no luck. Any other ideas? Looking to use the view to record gun cam footage. Thank you!

Well this is awkward, bahah. Real hornet driver versus Guy who saw it on YouTube.

Since we now have the hornet, adding Fallon and NAS Lemoore where the West coast Navy hornet squadrons are stationed only makes sense. Plus the flight from Lemoore to Fallon is gorgeous over the Sierras. Please please ED! It would make for much more of an immersive experience for virtual squadrons to conduct deployment workups from Lemoore into nttr allowing for that transition into a hostile region like Caucasus or PG

Please consider adding more lighting to the flight deck of the Stennis. I’ve attached a photo taken from Vulcher’s Row on the Stennis during my 2016 deployment during night flight ops.

I had a problem with turning into the groove where I would consistently exit the crosswind turn far wide if I kept my AOB at 30*. I learned that not controlling my decent rate had a trickle down effect which caused me to be fast in the turn which caused me to overshoot. When I controlled my descent rate to -100-400fpm, locked my AOB to 30* til the 90 and then make small adjustments I was able to roll out in the groove each time. Also turning on ICLS helps too.

Good evening, After the last update on OB ive started to experience a few issues. One being that I have a lag spike which lasts approximately 20-30 seconds upon booting into the pit in singleplayer missions. In multiplayer, I'm connecting to a server and getting to the roles screen where my game freezes but continues to play the background noise then goes to a server timed out after about a minute. Please advise what logs might be needed to help diagnose the issue. Thank you. Dino

First off, I’d like to start by saying that I think I speak for the overwhelming majority who appreciates the fact that they have any hornet to fly in and are sometimes overshadowed by the negative few. Having said that, if I may make a recommendation given the current state of the hornet, perhaps you may entertain the idea of releasing OB updates the first three weeks of the month followed by a stable update on the last week of the month. Given my interest in the hornets new features I find myself using the stable version less and less but I’ve heard numerous times where bugs are pushed to the stable release when they were reported in the previous weeks beta. I believe the different update schedule serves as a win/win for both sides as well. The thousands of us who use the OB regularly are your beta testers and lord knows the community let’s you know when you’ve pushed a bug into any release therefore give us those three weeks a month of back to back OB updates so we can find the bugs faster. It’s not a knock on your internal testers but it’s just fact that a small group of individuals is not going to be capable of running the hornet through the multitude of scenarios which thousands of us will. This solution would also likely speed up the release of features given the communities ability to find and report bugs than the current pace. Again, thank you for giving us such an awesome product that I truly love flying each and every chance I get. Dino

So I've noticed that since the newest FM edits that the previously published curves don't work quite as efficiently. Has anyone modified their curves since and willing to share? Thanks.