Jump to content

Recommended Posts

Posted

I apologize in advance if this thread is in the wrong spot.

 

In previous version of DCS World (I'm running 1.2.1 now) I created/butchered an existing DCS single mission into a multiplayer basic training mission. The mission involved multiple flights of blue aircraft, many of which were armed, and also included a stationary destroyer. After learning about triggers and waypoint actions and all that, I determined the "cleanest" way to prevent the AI from randomly decimating my practice targets was to set their first waypoint action to ROE = WEAPON HOLD.

 

This seemed to do the trick, but after testing the mission in the new version of DCS World they are ignoring that setting and going about their merry way ruining the Russian's toys before player arrival.

 

I realize this issue would probably be better served with triggers (mission start is all I need, they will never need to go weapons free at any point), but I've yet to get a working one for ROE in the new version. If anyone has any pointers or mini-tutorials on doing this properly it would be greatly appreciated.

 

As a second very minor note, I've been trying to get a red smoke marker to point out the target zones, but the best I've been able to do is either a one off or making them spawn new every second. The format right now is ONCE, FLAG IS TRUE (generic true flag I created), SMOKE MARKER(s). Smoke markers unfortunately run out over time though. Not as pressing an issue as the ROE one, but still there.

 

Thanks for your time gents!

Semper Gumby, Always Flexible

Posted

I think this might be a ship thing - I once made a little mission to play with triggers and see how effectively the AI performs SEAD, and put a carrier in a bay because I thought it'd be neat and I'd have it launch planes against my SEAD flight, but it kept firing missiles and scaring away my recon plane I was using to trigger the activation of the SEAD flights, no matter what I set its ROE to.

Maybe ships have so many different things on them that some of them aren't "reached" by the ROE commands but remain on automatic.

For when it goes wrong: Win10x64, GTX1080, Intel i7 @3.5 GHz, 32GB DDR3, Warthog HOTAS, Saitek combat rudder pedals, TrackIR 5 / Vive Pro, a case of Pabst, The Funk

Posted

Thanks. So, for me the OHP engages, but the aircraft don't do anything. And yes, ships might not be quite done in that respect yet.

  • Like 1

[sIGPIC][/sIGPIC]

Reminder: SAM = Speed Bump :D

I used to play flight sims like you, but then I took a slammer to the knee - Yoda

Posted

Frigate, not destroyer, sorry ;). You gentlemen may both be right on it being a ship issue (worked before, doesn't now, gotta love computers). I dropped another armed apache flight in with the same ROE settings to check if it was just ships, but I may have inadvertently set them to CAP (which I believe overrode the initial ROE check when they got shot at by the target groups). Poor troubleshooting on my part, but I appreciate the time and input guys, you learn something new every day.

  • Like 1

Semper Gumby, Always Flexible

Posted

No problem, I think eventually ships will be made to obey these things. :)

[sIGPIC][/sIGPIC]

Reminder: SAM = Speed Bump :D

I used to play flight sims like you, but then I took a slammer to the knee - Yoda

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...