Bankler

That's amazing. Since I added the groove time and all that, I have never gotten a perfect score myself. Great work! Find the trk file and make a video! :)

Thanks! Sure, I bought an Obutto Ozone chair a few months ago, with centerstick mount and so on. It's standing next to my desk (not really a good chair for office use). This is perfect for VR when playing actual missions. However, when just fiddling around in the editor and learning new weapons and systems, I very much prefer using screen instead of VR and sit in front of my desk, having manuals and coffee ready. It was a hassle to unscrew the who joystick/base from the Obutto everytime I needed it on the desk, so I bought an extra base from Virpil (just moving the grip only takes 20-30 seconds). Also, sometimes the new little wing(wo)man prefers me using one or the other. :thumbup:

Thanks for the input! Did some more research. It turns out it is because I have two joystick bases connected. Stock WH for the VR chair rig and a VPC WarBRD for the desk (I'm moving the grip between them depending on where I sit but keep both bases connected). When unscrewing the grip from the stock WH base, apparently that base sends constant BTN2 (pickle button) signal. So as soon as I select a bomb, it drops. If I pickle once when starting the mission (on the VPC that is), the button state seems to get reset and the problem doesn't appear. So possibly more a problem related to how things are wired in the WH base than a DCS issue. It is not in any way related to the centerline station as I first thought.

Tried loading a centerline Mk84/83 bomb on a Hornet. When I select it in the sms panel it just jettisons. Is this a bug or some weird feature? Anyone else experiencing the same (in my case, it happened when starting airborne). If not intended, I'd be happy to make a proper bug report with trk.

Thanks for the report! It has been solved locally and fix will be in the next update! :)

MJDixon>> That was beautiful! Never been able to hold an on-speed donut like that in the final turn! Great work! Now again, but break <0.5 after the bow! :thumbup: Mule>> I think 47-50 is pretty good! One thing to think about is that the scoring rewards safe flying. So in the groove, it's better to be a little high than a little low. As soon as you start drifting into the red you'll lose a ton of points. And yes, leaderboards would be really cool, though I don't know if/how that could be implemented with DCS scripting.

Thanks for the info and the warm words! Glad you like it, means a lot! Such a shame the opacity setting stopped working! This mod seems like a reasonable fix for the non-working spotting as a workaround until they adress that issue for real! It sort of does the trick, but it looks a little funky when the dot suddenly appears without fading in. ED, if you read this: Please take a look and see if you can fix the opacity setting in Labels.lua, which no longer works. Also, if possible consider adding font size and possibly even color for the distance array elements, so that it can be tweaked to be minimal size and almost transparent at great distance, fading in and getting bigger as it gets closer.

Does the opacity setting really work? For me, the dot seems to render at 100% at all distances, regardless of opacity settings.

I have problems getting precise coordinates from the F10 map. When selecting the DDMM.MMM it indeed gives me 3-decimal precision numbers. However, when moving the cursor around, these coordinates don't update until I move it enough for a 0.016-0.017 increment. So moving the mouse slowly to the right it shows:" "...46.283" "...46.300" "...46.316", instead of updating the number on every pixel. 0.017 increments is equal to around 76 ft. So the imprecision is enough to miss the target. Is this a problem everyone has, or is it some local error/glitch? In the mission editor map everything works as expected. This is only when in-game using the F10 map.

VERSION 4.1.0 EASTER UPDATE!! :drunk: You can now download version 4.1.0 in the Original Post! I'm blown away by the great reception here, on Hoggit and on Facebook. Inspired by all your kind words and based on your feedback, I sat down and polished things even more. The biggest change this time around is that you'll be able to track exactly how much score you get on each step. So it should be less of a secret how the scoring works. More importantly, I solved a bug where you didn't get any AoA score with the Tomcat. So if you struggled as much as I did with getting anyhing over 40 points with the Tomcat, now's your chance! In 4.0.0 the score was generally too low, since you didn't get anything for flying on-speed. Thanks Lymark for the heads-up on this one! :thumbup: With some black magic I managed to turn down the default Jester ICS volume in the F-14, so we don't have to sh*t our pants every time we start the mission and he calls out "Friendly 12 o'clock" at max volume! (Since this is a cockpit thingy, it'll only work in SP and for the host in MP). Finally, the groove time has been adjusted with a little more elaborate algorithm. Before, the timer always started when you reached inside 4 degrees of the centerline already. This turned out to be a little too early. Now instead, as long as you don't go wings level (i.e you're keeping a nice continous turn), the timer won't start until you're actually reaching the centerline. However, if you're flying an angling approach, meaning lined up left, wings level, the timer will start around 4 degrees from centerline just like before. This will hopefully give you more fair and accurate feedback on groove time, and it will be easier to hit 15-18 seconds than before. CHANGE LOG 4.1.0 * Added score for each step in the summary. * Fixed bug where you didn't receive AOA score with Tomcat. * Changed algorithm deciding when to start groove timer to be more fair. * Adjusted wire estimation slightly to eliminate some or all false-positive 3-wire estimations. * Cleaned up realtime text feedback. * Removed LSO text callouts (voice is still there!). * On SP startup, automatically setting ICS (Jester) volume to 10%. * Changed radio channel on Stennis to Ch 2 (264.00) * Removed the config-folder that was unintentionally in the miz-file. * Removed some unnecessary debug log stuff writing to dcs.log. Enjoy!

You need to pass the trailing ship behind the carrier below 1200 ft to get the script to start. Thanks! No, it doesn’t look right. Thanks for the heads up. I’ll need to double check for bugs related to scoring on the Tomcat! That one should be 70 points or so. Cutting the groove time is hard. Turning final a little earlier helps, like the second you get the abeam score or even slightly before (it won’t mess up your abeam score if you start the turn only one or two sec before the abeam score shows up). Try not to be angling approaching the groove slowly, but instead do a quite determined turn straight into the groove, so you don’t go wings level before you’re lined up. Also, don’t forget that the script isn’t perfect. Depending on your approach, a real LSO might very well have started the stopwatch later than the script does. So don’t take the groove time too seriously. If you think you’re doing good, you probably are. :)

It won’t give you an abort for altitude error unless above 1200. And no aborts for wrong speed. Again, does it say anything else than “aborted”? And can you provide a trk or tacview file? You can break anywhere from the bow to approx 4 nm. It’s your choice as long as you’re lined up with the brc. For the Tomcat altitude, since you’re over water, baro is probably the easiest to use. You can also use radar alt but have to deduct 100 ft or so (details about why on page 19 in this thread).

It checks if you get above 1200 ft or you’re to far from where you’re expected to be. Hard to tell where it goes wrong for you. Does it say anything more than “aborted”? If you want, you can attach a trk so I can look. Then I should be able to know for sure.

Hi GrowlingSidewinder! Love your Youtube channel. Nice traps there! (Edit: Realize this is an older video and thread though) If you want, please check out this mission that I made for practicing CASE 1 recoveries. I spent silly amounts of hours scripting and tweaking to get things right, and it has received excellent feedback even from real world Hornet drivers. In short, it will give you realtime feedback and a summary of your performance, making it a fun tool for practicing. Would be an honor if you want to try it out, bud'! :thumbup: LINK

Related, if you’re using a mix of Hornets and Tomcats. For Hornets it worked great to start an engine from cold, then taxi to clear the spawn points, engage the parking brake and start the INS align from your new spot. Doing this with the Tomcats caused all their waypoints to be in the wrong places. This is due to the stored heading assuming the aircraft to not turn before starting the alignment process. You may taxi, but not turn your nose in a new direction. Or you can of course do a full 9 minute align (not using stored heading). Details here: https://forums.eagle.ru/showthread.php?p=3873081#post3873081

After some discussion with buddy of mine, I guess all this does makes a lot of sense. If the stored heading merely is a heading saved on the aircraft memory, it surely makes sense that stuff will be rotated if you manually rotate the aircraft before starting the ASH alignment process. If this is correct, pretty sweet work on simulating that! :thumbup:

Problem: Waypoints can get the wrong positions if you taxi on deck before starting alignment Repro: Make sure "INS Reference Alignment Stored" is selected for your F-14. Spawn cold on Stennis. Start engines (do not arm ejection seat, otherwise Jester will start aligning already) Taxi to another spot on the carrier, making sure your nose is pointing somewhere else compared to the spawn point rotation (for instance, make a 90 degree turn). Engage parking brake and arm ejection seat, and continue with the full startup. Make sure it says "ASH" in the VDI, so you know the stored heading is used. After taking off, notice that all waypoint are now in the wrong places (they are rotated around you, the amount you turned on deck), making it impossible to use them for navigation. Remarks: The reason you might want to taxi before you align, is to make room for fellow players to spawn in (avoiding spawn collisions, and "flight delayed" problems, which is a mess when you are more than around 10 players). I'm not completely sure if this is a bug or if this is how it would actually work? If you don't turn while you taxi (just rolling straight forward), you'll be fine. If you don't use "INS Reference Alignment Stored" you'll be fine (but alignment will take 9 minutes or so).

Thanks a lot man! Means the world to me! <3 Make sure you’re not opening an older version that you have downloaded before. It should say version 4.0.0. If it says 3.0.0 it’s the old one (only Hornets). Let me know how it goes!

I’m not 100%, but I believe that the radar altimeter isn’t accurate over water. You need to look at the barometric alt, or deduct ~100ft or so like you found out. I also believe (again, not completely sure) this is intended behavior, like it was in the real F-14. Don’t quote me on it though. In any case, you can use the F10 map to verify what’s working.

My pleasure, bud'! Enjoy! (Hyped about your upcoming campaign btw, keep up the good work)

Does that mean you spawn with engines on on the cats? Can you decouple Hornets from the shuttle as well, or does that only work for Tomcats?

After a bit of work, I've now added Tomcat support for the CASE 1 mission. In short, you'll get feedback and score on how close you follow the Case 1 break and pattern. More details in the official thread: https://forums.eagle.ru/showthread.php?p=3868864#post3868864 (Actual download on page 1) Cheers guys! :pilotfly:

VERSION 4.0.0 F-14B TOMCAT UPDATE!! You can now download version 4.0.0 in the Original Post! Sorry for the lack of updates lately. I was busy getting a kid, yup, right during the F-14 launch! Finally I've come around to implementing F-14 support. It was a little challenge, since the scoring has to respect the different AOA required to be on-speed for the two different aircraft as well as some other differances, and I was determined to support both types in the same mission file, so that you can fly together with friends using a mix of Hornets and Tomcats. I also added groove time measurements and you can now get up to 5 extra points if you hit the recommended groove time of 15-18 seconds. Be advised that it's really hard for an algorithm to determine when exactly to start the timer. IRL it depends on the approach, like if the aircraft comes straight into the centerline lined up, or if it's angling (and probably a handful of other factors). According to my Navy contact, it's quite subjective. In this version, the timer starts ticking when you get inside of a 3-4 degree offset from the centerline. I don't claim that my current implementation does a perfect job, but at least it should encourage you to make a little tighter turn and not be that long in the groove. Hope you'll enjoy it! I can guarantee that getting a perfect score in the Tomcat is quite a bit tougher than in the Hornet (I have never achieved close to 75 / 75 myself yet!). Don't be shy to post screenshots of your scores or videos! It's always very inspiring to see people using the mission! CHANGE LOG 4.0.0 * Added Tomcat support (airborne, on catapult, cold start) * Identifying if you're flying Hornet or Tomcat and adjusting required AOA and such to match the current aircraft. * Added groove time measuring. * Increased max score from 70 to 75 (because of groove time score). * Adjusted overhead tanker pattern to make it fly smoother tracks. * Changed Stennis TCN to 74X. * Changed overhead KC-130 TCN to 37X. * Fixed bug that caused some problems when restarting the mission. Enjoy!

Did the carrier move straight north?

captflyby>> Thanks a lot! Some pretty good advice there! Woody01>> Thanks! I'll definitely take a look! Much appreciated! When stress testing this stuff, is the only way getting lots of actual people in (one aircraft per physical computer), or can I run multiple DCS instances and spawn several client aircraft from the same computer?