Lekaa

You did a wonderful job, I'm verry happy that someone is doing the A10! Now it'll be more enjoyable thanks to you a little feedback, If able, Let the current mode be there all the time, ie, not "mode" on the option but the current selected mode, ie CCIP , CCRIP, GUNS or NAV. Just like you have it now, it will show you the modes that you are currently selecting while toggling but let it stay with the current selected mode. Bad explanation but I hope you understand it. Secondly Let the Mode be on the TOP UFC option 1. Third, when you can, The Scratchpad is just like the Apache, I think. It can take letters and numbers. shown in the HUD usually and on the CDU, computer to the right knee. and the radios, You have to select the "Preset" to have the preset shown as the picture. Main radio is in the HUD, Second radio on the orange box Also, The Gun count is perfect, if you run out of places where you can place the gun count, you could skip the altitude. Again, Thank you!!

Oh I see. It's shown on the middle of the left mfd om the weapons page, it will also be shown on the hud when toggling between them. Do what you see fit in that case

Appreciate it, ithe preset channels on com1 and com2 for the 2 radios, not the FM one. Scratchpad, and on the options maybe current selected mode. Nav, ccip,,ccrp, gun. Steerpoint. Gun count(bullets) Total fuel Chaf/flare count

I really wish that someone could do the A10IIC here, i tried but it's Chinese for me =(

Picture is not working

@NineLine i wish when you make a report for this if it will be reported that you tell the team to have a failsafe that hinders this from happening. Also say to the team that this issue is only on the dedicated server platform. I have reported earlier that when spawning AI units also in the dedicated server using moose, they will also be doubled in the LINK system both on the SA page and on the radar page. Even though you have trackfile, then you will have 1 trackfile and 1 doner and its still the same contact. All this began when the new Link16 system.

Set the STN to something like 00400 but if it still works correct, then it's something else. Might be old miz.

It would make more sense if ED put a stop for such a thing from their end that this can not ever happen. there is also issues with spawning in f18/f16/f15c using moose. They will be double in the link network.

That is not the Link16. push the D/L twice, and then "ON" it should say "127 ON" Never the less it's ON according to the MFD.

Hello. Since the last update i've noticed some new changes to the radar with the letter M on a new contact on the radar scope. It also introduced some new bugs. When having Datalink contacts on the radar page and all the sudden you alter your elevation on the radar, the radar "forgets" those contacts. the radar do not update you any longer on the position or gives you Alt and speed info even though you move your courser to that contact may it be friendly or unknown. You still see them on the radar screen but do not do any update like the SA page does. Even the Threatcross is forgotten and only visible and basically stuck If you want to watch everything look at radar2.trk (That is what I have recorded and uploaded to youtube) Youtube video of the issue. It's easy enough to try it out your self once you understand the issue. radar.trk radar2.trk

Yes, we did a mission 2 days ago and that was on all the hornets and f16 so I opened the miz and saw that there was nothing wrong. All though my mate who did the mission had changed the STN to the tail number of the plane so we had 00400 and 00300 and so on, they were all effected. I tried to play with the STN to see if the problem got away and everything I tried, I tried it on a dedicated. Nothing I did with the STN helped. Only thing that worked was delete the client slots but before deleting them I copied the current one and them deleted the old. Also I tried to change the STN on the new copied one and we had the issue again so it's something to do with that but not only.

I even see some people doubles on the Datalink like in this picture https://ibb.co/xj30gF3

Trackfile : https://easyupload.io/q567xs Miz to test it on ( do it on a dedicated ) : https://easyupload.io/hhskyy

I have noticed this problem more often now. I realized that the only thing you can do to fix it is to delete the client slot from the ME and then add it back again. Then it will work. I have a case where I had to delete all the slots and re-add them again just for that issue. Still have a backup of it, but it's not in the ED standard with Caucasus and a couple of stuff at max. Also worth noting, the issue is only on the dedicated server.

did you find the culprit for this behaviour?