Oilman100

Unfortunately not, it doesn’t recognise the additional MFD LEDs, so you can only have them either on or off using the Win controller properties which is pointless. Ok thx for the reply, if you ever solve it please post the solution.

A little bit of help required, I use the original files in the post and got CMFD working no problem, can you tell me exactly what files and line numbers you modified to get the LEDs programmable within the Target script. I have no programming experience so will just mimic what you tell me. Much Appreciated

Be interested to see how you mange to get on with getting the additional 2 MFDs LEDs working within a Target script to enable individual programming. Good job so far and thx for sharing

If you are interested PM the person in the initial post and he will send you the details to sign up

If you are interested PM the person in the initial post and he will send you the details to sign up,

Many Thx

Did you figure out how to change the HMD so we can get both colours to match ?

I’m seeing exactly the same issue and it was there before this patch, I’m assuming it is realistic but agree you can’t shade it from the sun like you could in real life. There is an option for reflection on DDI’s but that did not fix it. I ended up using the AMPCD which is more awkward but at least you can read it.

You need to use the the Target Script or GUI if you want to associate them with key presses, it’s all explained in the manuals, worth the effort as the MFD’s make a real difference to indicate certain button presses e.g air brake on, you can have MFD flashing or A/P on LED comes on to remind you the A/P is engaged and so on

Many Thx for your quick response

https://forums.eagle.ru/showthread.php?t=228510&highlight=Ogg+music This link has all the info you need to create and use you own Theme or change an existing one, including pictures and music

Simple question, how do you add the Mod Description in the bottom box, I can put the cursor and highlight but cannot add any text, thx

I agree it can be done, using the Target software makes the hardware so much more flexible and allot more Hands off especially if you are using VR. I have always wanted to get the Hotas system to make the flying experience as best as possible. As you can tell I’m a big advocate of using the Target software (script editor) the time invested will make big returns in the future that simply can’t be done matched within DCS keymap. Of course everyone has a preference, but don’t rule it out. My 2 cents worth

You set up everything in Target and it just generates a keep output, DCS sees it as a combined virtual controller, all you have to set up in DCS is the axis bindings and ensure the key presses correlate between Target and what is in DCS keymap.

I would imagine not many people use that setup which could be the reason you are not finding anything. I’m not sure whether HOTAS One is compatible with Target software but if it is I would encourage you to build your own profile using the GUI version rather than the script as it’s easier. Once you start to develop your own -roofless the combinations become endless and there is plenty of support on this forum if you get stuck.

You would need to use the Target software, suggest just using the GUI version, you can create IO on S3 very simply. I used to use Foxy but Target is the same concept and GUI is even easier.

I have seen this exact same issue, with Tacview it is a very consistent burst height of about 700ft and as you stated it becomes inaccurate and the kill zone is allot less. I’ve also use PRI mode and this works as stated with a burst 1.5s after release, but requires a bit more calculation to get the right release height. Has been like this for a long time, the Rockeye has also the same issue

If you go into FLIR mode and designate it tracks pretty much 100% of the time, in CCD it is allot more tricky. I tend to use CCD to identify the right target and the switch to FLIR for point track mode.

No the laser is LTR and firing as the Mav picks it up and slews to it, on the HUD the designating boxes from both TPOD and MAV are overlapped showing good lock

The other error I’ve found, is that you can lock onto a moving target via point track and in the TPOD on the DDI it tracks perfectly, uncage the MAV and it finds the target immediately with both symbols in the HUD view overlapping. Now the issue, they stay static on the ground and do not track the moving vehicle, however look at the TPOD DDI and it shows it’s still tracking the vehicle. Leave this and the TPOD tracks for another mile and the symboled remain at the original location. It looks like although you designate a moving target, it actually designates the ground instead, very strange and only since the last patch.

Using the TPOD to lase a Target, all is well on the first missile release, it locks and releases missile, the issue is on the 2nd missile, undesignate the original target and designate the next one, laser fires and uncaged Mav skews to target but remains as an X, cage and uncage, slews directly over target and again Mav remains crossed out. Within 5miles and good angle. It only happens with the second one.

Is there anyway to set a default profile, I have quite a number and it always defaults to the A-10C which appears first in my list.:doh:

If you just need the same sequence every time then use the SEQ command SEQ(PULSE+’n’, PULSE+’m’, PULSE+’g’) Add the MAPKEY you want before it and on 1st press you get n, next press m and next press g, you have to finish the sequence each time, for it to cycle back to ‘n’ again. Hope this helps

Mine came through instantly with PayPal so no issues here