Rockrend

Not necessarily...See this post for some further detail if you would like the steering T back on the HUD. https://forums.eagle.ru/showthread.php?t=238676

Here you go aaaaaaa.miz

I’m away at the moment but I can get it done on the weekend.

Thanks very much for the reply, it makes much more sense to me now you’ve explained the likely thinking behind the change.

Did you ever get a response or answer to this question? I would have though it would be relatively easy for Heatblur to answer.

Excellent....thanks very much.

That would be very useful. I’d appreciate it if you could post it.

I can’t say for sure. Perhaps you might like to report it as a bug.

Yes. You can load and unload troops but you will have to set it up previously in the mission editor. I don’t think you can make them fast rope.

@Pikey is correct, it is days. Glad you got the orbit working :)

I haven’t seen the post you are referring to but what you say is true...you only see this if a player is hosting the MP mission. I tested this yesterday. If the players are not the server host then all should work as normal, just as @QuiGon mentioned above. Additionally, it not the only thing that doesn’t work as expected when a player is hosting a MP mission.

+1 me too....Tried to use it for the first time the other night and no joy.

Does anyone know if this has now been acknowledged as a bug by ED yet, I added the track files almost a week ago? It’s obviously not going to stop a mission but it’s relatively annoying.

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