Smashy

Ah, thanks @Minsky!

Thanks for the great work @Minsky. One question, is the RWR/HARM codes page missing? I did not see it in the zip file I downloaded. I'm keeping the older version around because the having the HARM codes readily available is pretty nice.

Whenever I change monitor options, DCS restarts itself. It's pretty painful to make the switch. The only thing different between my usual monitor config and the Apache is the viewport names: $ diff CUSTOM\ -\ AH-64D\ PLT\ MFDs.lua CUSTOM\ -\ default\ MFDs.lua 2c2 < name = _('CUSTOM - AH64D PLT MFDs'); --- > name = _('CUSTOM - default MFDs'); 18c18 < AH64D_PLT_LEFT_MFCD = --- > LEFT_MFCD = 26c26 < AH64D_PLT_RIGHT_MFCD = --- > RIGHT_MFCD =

From TWS, establish STT and then enter RAID mode. All visible trackfiles are shown with L&S star symbol. Additional oddities: entering RAID seems to "work" after establishing STT track from RWS EXP is boxed when entering RAID. Note: in the attached track, I'm not hitting the OSB to box EXP, I'm using the "RAID/FLIR FOV" HOTAS function to enter RAID weird numerical values displayed in RAID mode where target altitude differential is typically displayed multiple L&S with SCAN RAID.trk

I went to an airshow a couple of weeks ago and got a chance to look and touch an AH-64D on static display. The 2 pilots were there and really took their time to interact with the crowd. I was able to ask a bunch of questions. I asked why the FCR wasn't mounted and he said in the Apache's current role, it's a 300-lb weight sitting way above the helo's CG so it's usually not mounted. He said it would be useful in a peer/near-peer conflict but not in the COIN stuff they're doing now. I then asked if the TADS was where the magic happened and he said that it was a system from the 90s that was badly in need of an update. In his words, it was "trash", LOL. So it turns out even RL pilots wish for fixes and improvements even though the gear and tech is working as intended

Great video and I'm really looking forward to making some ham sandwiches after this feature drops. After watching it, I had a couple of questions. Was the cut landing grade a one-off error or does Mode 1 still need a bit of tweaking? This is more of a procedural question, but I notice Wags drops gear then trims for onspeed AoA, drops half flaps and does more trimming, drops full flaps and does more trimming. For CASE I, I drop gear and full flaps all at the same time while in the break and try to estimate trim so I'm close to onspeed AoA after coming out of the break. I do the same for CASE III but have to hold more forward stick to prevent full flap condition from pitching the nose too far up while I trim for onspeed AoA. With Wags' approach, it makes the straight-in dirty-up a lot less stressful. With a properly executed CASE I break, I don't know if there's enough time to do the sequential gear/half flap/full flap operation. Do real-life Navy guys follow a specific procedure for this or is this all personal preference? I'm genuinely curious so I hope this thread doesn't get locked, LOL.

Just to clarify - you're not using Helios to export any viewports, right? Instead, you're using custom PLT and C/PG monitor configs to handle viewport exports? If that's the case, do you have any tips on how to dial in the placement and dimensions of the exported viewports so they line up with your Helios profile? Up to this point, I've been using trial and error and it gets tedious with all the DCS exits/restarts.

Is there a solution that does not involve using a unique monitor config? It would be cool if the MFDs could change dynamically when moving to the PLT or C/PG seats. I'm not sure this is possible, given what little understanding I have of DCS viewport exports. Hopefully someone muchly more cleverer than me can figure something out.

Here's a video from Redkite that explains how trim with non-FF controls can get tricky.

One example I can think of is an emergency autorotation. Imagine being trimmed for forward flight and you lose power. Being able to instantly find the center of cyclic and antitorque in a sprung joystick and pedals is pretty handy. I used trim reset a lot in the Huey while learning autorotation. I would create a mission where I would start in the air and cut fuel to the engine. It took me a couple of crashes to figure out that when you airstart in the Huey, it's trimmed for forward flight and pulling the cyclic full aft doesn't give you enough pitch authority to enter a successful autorotation.

I was one of those hoping for a trim reset function and am glad it's going to be included. However, I'll try your method and consciously try to be more active on setting trim to see how well it works. I do have the control overlay open and it can be pretty distracting so anything to help me get rid of it is welcome.

Clicky buttons are the best! I want this so much. I'm using TM Cougar MFD panels now and the mushy membrane buttons aren't the most satisfying to push. Also, they don't have enough buttons to emulate the Apache MPDs.

The MPDs exported fine without any changes but I'm seeing the same thing with the CP/G displays being exported even when I'm in the back seat. Is there a way to dynamically change these when crew positions are switched? I'm afraid that the answer may be "no" as the exports appear to happen when the module loads. Maybe the only way to get it to work is to have the module reload when changing seats. Sort of like when you jump into another module with the RALT-J command.

Good tip. You can also take a look at the ones that ship with Helios and Helios profiles and use them in your Stream Deck profiles. I'm just getting started with Helios and it seems to be a great compliment for my Stream Deck, especially for aircraft with large amounts of steam gauges. I tried Ikarus, but it didn't seem to play well with the DCS Stream Deck plugin.

Disregard my question. After looking at the problem for a bit, I was able to modify the P-51D.lua file to get it to feed the Stream Deck what I needed. I wanted to be able to display coolant temp, oil temp and fuel levels in gallons of all tanks. I referenced other Stream Deck threads in the forums here and looked at other module exports files to get a good idea of what to do. I used the Model Viewer to eyeball the relationship between DCS ID values and cockpit gauge values. That worked well for the ones with linear relationships. The fuel tanks seemed non-linear so I found an online function generator and used it to generate some parabolic functions. Yay, math! All that was left was to copypasta some really simple lua stuff and massage it to work for me.

How to you reformat the raw output from the P-51D.lua to something that's better suited for a Stream Deck button? I've been interested in doing exactly what you've done in this P-51D example video. Did you have to modify the P-51D.lua to get this done? If so, I guess I better start learning some LUA scripting!

Nice work! I'm just starting to learn the A-10C after getting familiar with the Hornet and from what I've seen so far, the Hog's HOTAS system is far superior to the Hornet's. The context-sensitive nature of various switches and short/long presses allow a ton of functionality to be mapped to the stick and throttle. With the Hornet, there is a lot of button pushing to do in the cockpit. I've mapped critical ones to my stick in a hack-ish way to keep my hands on the controls during critical parts of a flight (e.g., the laser target designator toggle switch on the right console is mapped to a joystick button) but there is still a fair amount of hands-off going on, which can get tricky. I put a lot of thought and effort into getting my Hornet HOTAS configuration dialed. I'm working on my A-10C HOTAS config now and it looks like the default settings are a great start, unlike the Hornet. Is that an accurate impression? Does the A-10C HOTAS scheme allow mostly hands-on during the most critical parts of a mission?

Refrain from peeking at the mission editor and F10 map and you should be good. I made the mistake of looking at the mission editor on one of the earlier missions and the surprise was spoiled. Since then, all I do is review the briefing text and images carefully and refer to the kneeboards while in flight.

This one drove me crazy too! The Hornet's radar is bugged and won't lock on to any helicopters, at least the ones I've tried. The Flanker and Eagle have no problems. I think this is a reported bug and hopefully will be fixed at some point. Minor spoilers below (highlight the text to see it)... My gunnery pretty much sucks so I had a hard time gunning the slow moving Mi-8. After multiple attempts I gave up and adjusted my loadout in the ME. I got rid of some Mavs and loaded up some AMRAAMs instead. Or maybe it was AIM-9s, I don't remember. My wingman was really good at getting the surface targets with his Mavs so I just let him take care of the boats. After he was done, I just shot AMRAAM in VISUAL mode or heaters at the helicopters. Pretty cheap move but it helped to advance the campaign.

I'm slowly making my way through your campaign and have reached mission 5. So far it's been a lot of fun and the feel of escalation and increased activity is definitely there. Nice work! On the topic of the mission editor, I did go to the mission editor as part of the mission brief for the first couple of missions but did get some spoilers that way (.i.e, saw the popups that happen in the middle of the mission). Now, I'm just relying on the text brief and associated images and hoping for the best.

Ah, thanks. I did go for cat 2 and my wingman queued up behind me. I kind of forgot about him and started pushing to the check in waypoint and he burned a lot of gas trying to catch up

I'm playing version 2.9 hotstart and found that cat 1 is blocked by parked aircraft in mission 4. Is this just me? (sorry for the dark screenshot)

Thanks @gregzagk. I missed getting Pontus this sale but it's still near the top of my list. I don't think I'll let a few seconds of odd (to me) dialog prevent me from checking this one out!

I'm very interested in this campaign and like the concept of it but when watching Redkite's video of it, I did not care for the voice acting at the 10 minute mark. Are there a lot of these awkward conversations in the rest of the campaign?

Various ranges from 0-10miles, various aspects, look up/look down, hi/med/interleaved PRF. None work in the current open beta. F-15C works fine. 2.5 Hornet radar works fine.