johnv2pt0

Looks great! Thanks ~

What are the radio's called in the JF-17? Does it use FC3 right now?

Anybody know the lua file in which the radio menu stuff resides? I know I changed the size and color before, but can't remember nor find where it was! TYIA

No, these are the only events we have access to and countermeasures aren't included in SHOT. https://wiki.hoggitworld.com/view/Category:Events If you're making a SP mission you could look into cockpit arguments to detect the hotas button press but it's impossible in MP. I'm not familiar with cockpit arguments though, so that's all I got.

No unfortunately. I did this in one of my missions by using MIST for setting the flag and then using signal flare on unit within the ME triggers.

I understand your thought process on this. With that in mind, please don't add a random delay to install it via groundcrew. If it can't be an option for the ME, then every single time most people start it up there will be an arbitrary and forced annoyance. My choice would be to have it installed by default and an option for the ground crew to remove it if desired, regardless of whatever delay you decide to program into it. Loving it, keep up the great work ~

Thanks all.

Thanks Habu. I do use MOOSE for some things, but honestly my problem with it is trying to keep up with changes and finding the proper documentation. If I want to do X, I need to check the sample missions within eclipse (which doesn't completely answer my question), look at the moose documentation online (which doesn't completely answer my question), watch his videos (which doesn't completely answer my question usually because something within MOOSE has changed), and then try to sift through thousands of random posts on the discord (which doesn't completely answer my question). It's an exercise in frustration for me. I think what FlightControl is doing with it is amazing, but something just doesn't click for me.

I think MOOSE clones groups that it creates, so you might be able to set the ai task on your example plane, and then use the pushAITask SSE function within your moose script. https://wiki.hoggitworld.com/view/DCS_func_pushAITask God speed sir!

Ok, I got it working by just doing the math, but I would still like to know if that function is built into the SSE somewhere. Thanks!

Your scenario won't allow for using the ME advanced waypoint action or triggered action of bombing? I can't help with MOOSE, but just want to make sure that you know that option is available to you.

Is there a way to do this within the SSE and not ME trigger?

Off the top of my head, the GBU-31/V penetrator. I think it takes 2-4 MK-84s. And this is basically the same on the RED side... the BetaB500/500sph penetrators will take it out with 1 but 2-4 KAB-500

Great first pass on the binding additions! In addition to what others have said, I would like to have the UFCP brightness rotaries as axis.

Anything new to share on this?

Just had this happen to me as well. Hot start @ 30k' nose on a willing human target. Radar NOT in standby or sil...cycled them on / off multiple times to try to get it. EDIT: Tried it again after leaving server and reconnecting. Worked. Scenario exactly the same. Might be related to the issue where electrical power didn't work on first try? I will report back if I have time to test it.

Just to add another datapoint, DCS always crashes when ld-10 is fired in SP mode and hits it's target. Multiplayer.

Thanks for the pics, I never would have seen them. Razbam being razbam. Gonna just start saying "RBR" from now on I think.

Devs, this may also explain some bad FPS with the HSD page up and many RWR contacts on screen. Just as a datapoint, in the single player mission I was just flying I was getting 60 fps with the HSD off and only 20 with it on while all other factors equal. Ooof!

It's important that we can use the ME to adjust the presets like in most modules. I don't think 200 is necessary, but having at least 20 is important for those of us that fly in large MP groups. However, being able to adjust 200 frequencies wouldn't be unwelcome and is better than not having any IMO.

I'm a little confused on why this seems to be an issue with so many developers. And I don't mean this as an insult or troll, but quite literally everything that is used in the jet routinely should be bind able by any device / button box. This is a simulation and many people build cockpits or have simple button boxes for commonly used actions in the cockpit. The whole point of have external control devices is so that, like in real cockpits, you can reach out and touch something without even having to look at it. This becomes even more important in the VR age. If you interact with it in a routine combat flight, it should have a non-greyed out binding available for any controller that is detected and recognized by the game options. This include lighting rheostats (and as axis options!)...I only mention that specifically because for some reason this doesn't make it into most of the jets. Thanks for the hard work...really enjoying what I've seen so far!

Redkite just posted a video and answered this question. So Deka, consider this a feature request! It would be great to split the sub displays into separate viewports in the future. Can't wait to try it out ~

Great video! Answered a lot of questions. Thanks ~

Has the Deka team thought about the problem people who export in game mfds to secondary monitors with Thrustmaster cougar MFDs are going to have because of the size difference? I'm ignorant in how exporting those sources takes place in the coding, but it would be nice to split the lower half of the mfds into a separate export so nothing is hidden by the thrustmaster mfd bottom bezel. Would that be possible?

Thanks for the update IronMike.