Kappa

Thank you Hardcard for your detailed reply, very kind of you. I understand what you say, but my goal is to populate SETs (or arrays, or something) from prefixes, without defining all group names in the script manually, and then iterate some commands for each group in the set to make it spawn and cofigure it. So you say, I can't use a GROUP_SET with unspawned groups, can you tell me why the following code works? As you can see I define the RecceSet before to spawn RECCE Groups but in deeds they do their recce job within the Dispatcher :huh: I think it is because a SET get automatically updated...What do you think? Moose docs https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Core.Set.html

i have to try this, maybe it will work... local RecceSet = SET_GROUP:New():FilterPrefixes('RECCE'):FilterCoalitions("blue"):FilterStart() Recceset:ForEachGroup( function (group) local SpawnRecce = SPAWN:New(group) :InitLimit(1,0) :InitRepeatOnLanding() :InitDelayOff() :SpawnScheduled(60,0) end )

Yeah, i think you're right, so i've tried this but had no luck... still something wrong local RecceSet = SET_GROUP:New():FilterPrefixes('RECCE'):FilterCoalitions("blue"):FilterStart() local function confRecce() RecceSet:ForEachGroup( function(RecceSet) local RespawnReaper = SPAWN:New():InitLimit(1,1) RespawnReaper:InitRepeatOnLanding() RespawnReaper:InitDelayOff() RespawnReaper:SpawnScheduled(60,0) end ) end

Hi, i have this case where I set a respawn and respawn on landing for 6 RECCE groups. This is the code that works but it is not so smart RespawnReaper1 = SPAWN:New('RECCE-REAPER #001'):InitLimit(1,1) RespawnReaper2 = SPAWN:New('RECCE-REAPER #002'):InitLimit(1,1) RespawnReaper3 = SPAWN:New('RECCE-REAPER #003'):InitLimit(1,1) RespawnReaper4 = SPAWN:New('RECCE-REAPER #004'):InitLimit(1,1) RespawnKiowa1 = SPAWN:New('RECCE-KIOWA #001'):InitLimit(1,1) RespawnKiowa2 = SPAWN:New('RECCE-KIOWA #002'):InitLimit(1,1) RespawnReaper1:InitRepeatOnLanding() RespawnReaper1:InitDelayOff() RespawnReaper2:InitRepeatOnLanding() RespawnReaper2:InitDelayOff() RespawnReaper3:InitRepeatOnLanding() RespawnReaper3:InitDelayOff() RespawnReaper4:InitRepeatOnLanding() RespawnReaper4:InitDelayOff() RespawnKiowa1:InitRepeatOnLanding() RespawnKiowa1:InitDelayOff() RespawnKiowa2:InitRepeatOnLanding() RespawnKiowa2:InitDelayOff() RespawnReaper1:SpawnScheduled(60,0) RespawnReaper2:SpawnScheduled(60,0) RespawnReaper3:SpawnScheduled(60,) RespawnReaper4:SpawnScheduled(60,) RespawnKiowa1:SpawnScheduled(60,0) RespawnKiowa2:SpawnScheduled(60,0) This is what I think would be smarter but I can't get it to work. setRespawnRecce = SET_GROUP:New():FilterPrefixes('RECCE'):FilterCoalitions("blue"):FilterStart() RespawnRecce = SPAWN:New(setRespawnRecce):InitLimit(6,6) RespawnRecce:InitRepeatOnLanding() RespawnRecce:InitDelayOff() RespawnRecce:SpawnScheduled(30,0) Can someone help me?

Forget about it... CTLD wasn't loaded yet... thats why :music_whistling:

Hi, I have a problem, can someone halp me plz? I get an error when tryng to set an existing unit as JTAC using ctld.JTACAutoLase. See attached Images

Yeah, A-G mode and CCRP, the MFD was SOI. I'll have one more try tonight. If I won't be able to get int to work i'll post a .trk TY

Ok, so here is the point... To slew the TGP it seems I need to set the Master Arm to ON. Strange behaviour, is it modeled correctly?

Try to go back to spectators and then ttake the slot again, this works form me every time.

With TMS down it should go back to bore sight. However, if you say it is working, maybe I have some problem with keybindings or joystick settings... I'll check it. TY QuiGon :thumbup:

Last night I had a flight with the F-16 and I wasn't able to slew it and to center it in bore sight.. It's been a while since I used it in A-G the last time so maybe I did something wrong but... Can you guys confirm that the tgp is working?

Anyone know when ED will release the next update? I'm looking forward to get this bug solved and I really hope they'll solve it in the next update...

I have the same problem with dates :thumbup:

I was very disappointed from the Harrier, then i bought the F-18 and I've found it is far from being complete too... No SLAVE on Target point for TGP, No TGP Box on HUD, no horizontal movement for Radar, INS bugs and more... What can I say... Now Harrier doesn't look so bad... :megalol:

Maybe you mean 4th September :smilewink:

A bug, i've also reported it in the bug section and Wags marked it as REPORTED, so ED confirm there is something wrong. It happend since they implemented INS so it must be related to it. I really hope they'll fix this soon :)

Unfortunally they didn't fix this in yesterday update. Hope for the next one :thumbup:

I use to turn off the TACAN volume in the AUDIO panel on the left console. Don't know if there is some way to turn off the tacan system it self... I think it's part of MIDS.

Bore range should be 20 nm. 10 nm is for 30x20 and vert. In this moment the ACM modes are not modeled correctly please see this: https://forums.eagle.ru/showthread.php?t=256266

This was exactly what I was asking to my self... There is a workaround?? AFAIK misalignment increases with the flight time. So if you'll make some tests keep in mind that you will get different resoults if you don't keep this in your mind. With a 100nm navigation the misalignment is very evident, it makes impossible even the use of LGB's since the HUD gives you incorrect drop parameters that will make you drop a bomb far away from the target and it will not be able to spot the TGP laser because of the distannce or maybe the bomb has a completely wrong angle... Unfortunally this bug makes the F-16 almost useless in A-G for now... Hope they'll fix it soon. :smilewink:

Hi Wags, thanks for your reply, it is very nice to see you ED guys taking care of us on the forum, very nice. Maybe I wasn't clear enought in my previous message, unfortunately my english is rough and rusty. I am talking about all ACM modes, so bore and vertical are very slow too. It may be releted to the bug mentioned by Alfas (Thank you Alfas), I wans't aware of it. I will try to pay attention to my radar elevation and if I find out something more I'll let you know. Thanks

Hello, I was wondering if the tracking speed of Bore, 20x30 and Vertical scan are modeled correctly. I mean, it takes al loooooooot of time to lock a target and sometimes it so slow that I just give up and fire without a lock leavig all the hard work to the missle seeker... Is really that slow IRL or it is WIP?

Thanks for fixing it :thumbup:

Yes, for sure but i don't have my PC because I'm not at home and it was a long mission with many clients and it would be a pain to analyze trk and find where it's happened... It's easier to reproduce it following what I've wrote before. I'm sorry, I know that the trk is needed but I can't provide it in short time. The issue has been noticed also from my wing buddyes so i'm am pretty sure there is something ED should check. unless the problem was somehow generated by the server we were on... I'll try to have some tests tonight if I can

Anyway if someone here has time to check it out, this can help: TWS mode -> lock TGT in STT - > turn exeeding the radar gimbal limit-> STT lock won't brake