Rockrend

Looks like something might have been broken in the last OB and Stable updates then. Anyway the track files should help to identify the where the problem is hopefully.

See the post above for a step by step. I can upload a very short example mission if you like.

Yes there is... Create a Reaper Set its task to AFAC Go to the advanced WP actions selection for WP0 Confirm the "Start Enroute Task" is set to to FAC Confirm the "EPLRS" is set to to On Confirm the callsign, frequency and modulation Create a second WP (WP1) close to the target Go to advanced WP actions selection for WP1 Create a "perform task" command Set that command to "orbit" and set the other settings in that command Create a "Start Enroute Task" command Set that command to "FAC-Engage Group" Set the group to the group name of your target Set the weapon to AUTO set the priority to 0 Set the Designation to LASER Check the datalink box Confirm the callsign, frequency and modulation are the same setting as before Fly the mission

Have a look at this thread. Please let us know how it works out. https://forums.eagle.ru/showthread.php?t=236551

Thanks for the reply. I can see what you mean.

Unfortunately I missed this thread and created a new one a couple of hours ago with exactly the same issue. I posted a couple of tracks in my thread https://forums.eagle.ru/showthread.php?t=239255. Check them out and see if it's the same as what you are seeing. I'd be pretty sure it is. Hopefully this can be looked at and fixed in due course.

Track files attached Thanks for your reply @NineLine. My apologies, please find two tracks attached. The one named GBU AUTO shows that I cannot select AUTO without first selecting CCIP and the cycling back to AUTO. The one named GBU AUTO cycle demonstrates cycling the program button, where programs 1-4 are all CCIP modes initially (program 5 is set to MAN and remains that way) and then if I continue cycling the program button, then programs 1-4 become AUTO. Hopefully these will illustrate what I'm seeing. GBU AUTO.trk GBU AUTO cycle.trk

[NEED A TRACK] GBU AUTO Bombing Mode Problem Hi all, I'm running stable V2.5.4.29167 and flying the Paveway II Laser Guided Bombing Practise Mission. I'm initially unable to set the bombing mode to AUTO despite pressing the correct selection, it just stays at the default setting it was when I load into the mission, CCIP. In order to actually select AUTO, I must first select the CCIP button and then cycle back to AUTO for that setting to "stick". I'm not seeing this behaviour with Mk82 etc in other missions, only the GBU. I haven't included at track because the mission I'm flying is from the default F/A-18C Missions Menu which we all have access to. Additionally, if I cycle the program button, programs 1-4 are all CCIP modes initially (program 5 is set to MAN and remains that way) and then if I continue cycling the program button, then programs 1-4 become AUTO. I wasn't seeing this behaviour prior to the update that moved the stable version to 2.5.4.29167. Can you please put this on the list to be fixed. Thanks in advance.

Thanks for the reply. Much appreciated.

I haven’t been able to find it either. Hopefully someone can chime in and let us know where it is.

It switches from the normal mode (servoed) which is corrected for positional error by the CDAC, to the standby mode (pressure) driven by the static system. This mode is uncorrected for positional error. By the way, I see you fly in MP with a human RIO. Would you mind giving you perspective on the question below which I posted recently. Thanks very much When I activate the LTS test in MP with a human RIO he does not see the annunciators illuminate in the RIO cockpit, although I see them in the pilot cockpit. Whereas, if I’m in SP and activate the LTS test in the pilot cockpit and then switch to the RIO cockpit I can see the annunciators illuminated. I also see the same behaviour when I run the INST test regarding the fuel quantity gauge in the RIO cockpit.

Hi all, When I activate the LTS test in MP with a human RIO he does not see the annunciators illuminate in the RIO cockpit, although I see them in the pilot cockpit. Whereas, if I’m in SP and activate the LTS test in the pilot cockpit and then switch to the RIO cockpit I can see the annunciators illuminated. I also see the same behaviour when I run the INST test regarding the fuel quantity gauge in the RIO cockpit. Are others seeing this same behaviour or is it just me, would be god to know. Thanks in advance for any input from others Rockrend

Have a look at this thread. Let us know how it works out. https://forums.eagle.ru/showthread.php?t=236551

You could use Perform Task/FAC-assign group and select laser designation. You need to have the Predator or Reaper set to an AFAC task to get the options to appear. Hope this helps.

Thanks very much for the reply. Seems like there is a dozen ways to skin this cat. It’s really great that the people in this part of the forum are so helpful and willing to share their knowledge.

Thanks very much for all of your help. That was exactly what I was looking for.

If you want to get back to the default unit templates, just remove the template.lua file from the saved games directory. This will leave DCS to use the default templates file located in the Eagle Dynamics directory.

Thanks very much for the reply, I appreciate it. Now, can anyone point me to where i can find the correct syntax to script an output method to print the fuel status. Thanks in advance.

Hi all, I'm very new to scipting and am keen to learn more. I have a question which I hope someone can help me out with. I've seen the following information regarding the getFuel script on the Hoggit page (https://wiki.hoggitworld.com/view/DCS_func_getFuel) and I'm not sure if I'm reading the example correctly. It states the following: The following is the fuel returned for a flight of 4 F-15C. The flight lead has 0 external fuel tanks with each subsequent wingman adding a 610 Gal external fuel tank to their payload. local flightFuel = {} for i, unitObject in pairs(Group.getByName('flight'):getUnits()) do flightFuel = Unit.getFuel(unitObject) end Returns the following: Unit 1 Fuel: 1 Unit 2 Fuel: 1.3026511669159 Unit 3 Fuel: 1.6053023338318 Unit 4 Fuel: 1.9079535007477 Does this indicate that the script will display on screen the information about fuel state above (in red)? I've amended the 'flight' information with the correct name of a two aircraft group in the mission and it seems that the script is running correctly (no errors) but I can't work out if it's supposed to display anything on screen or not. Some assistance would be very much appreciated and I'm sorry for such a noob question. Thanks in advance.

I tried this morning and the launcher will not fire without the optical tracker and the blindfire radar together in my experience.

I’m using the most recent DCS stable version and the GBU12 definitely works with a JTAC. I made a mission not more than 5 minutes ago with 4 vehicles lined up I a row and a JTAC. I needed to set my aiming point for the GBU12 in between the 2nd and 3rd vehicles to have the weapons lock onto the JTAC laser correctly. Perhaps your aiming point for the GBU12 might be the issue. Good luck with figuring this one out. Additionally you can find the CTLD details here https://github.com/ciribob/DCS-CTLD

I’m using the most recent stable version of DCS and have noticed the AGM65 F locked (LKD) symbology on the HUD no longer appears when the weapon has locked. It did previously in version 2.5.3xxxx The weapon still works correctly and slews much better now (thanks ED) but I’d like to know if this is occurring just at my end or if it’s something that is common and will be fixed in time. This occurs in all scenarios as well as the Hornet AGM65 F instant action mission. Thanks in advance. Nick

Thanks very much for the reply.

I’m not sure if this is the way the real setup works but I experience the same as you. If however I place 2 radar units with multiple launchers in the same group then 2 missiles will fire almost simultaneously. Hope this helps you.

Just the default clouds and sky for me...I wonder what the problem is?