Jump to content

Recommended Posts

Posted

Hi,

 

I tried a lot to play with FLAGs to create complex mission, but I always fail. Always.

 

Thanks to all people that help me to solve problem via the forum, but the use of FLAGs is still really obscur to me. I am just unable to set a flag and be sure that is working as is suppose to, even by reproducing example found in the forum.

 

So, please, a guide to specific use of FLAGs is necessary, in my opinion.

 

Thanks.

IAMD Ryzen 9 5900X 12x 3.7 to 4.8Ghz - 32Go DDR4 3600Mhz - GeForce RTX 3080 - Samsung Odyssey G7 QLED - AIMXY

Posted

A flag is basically the same as a variable that can hold a logical or integer value. For debugging, you can display the value of a Flag with a small do script:

 

This script piece allows me to include Flag (Flag 101 on the sample) values on a message:

trigger.action.outText( 'Vertical Speed on touchdown: -' .. trigger.misc.getUserFlag ( '101' ), 30 )

 

What originates confussion, is that the default trigger type only last until the first time it becames true, dissapearing afterwards.

 

The new manual of DCS has a nice section on triggers, give it a read.

Best regards

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

  • 2 weeks later...
Posted (edited)

A flag is a condition required for something to happen.

 

It can be one of many conditions or the single one.

It can be a condition sine qua non without which the action that depends on it will not happen or just a condition that modifies the effect of the action in a certain measure.

 

So for that flags can be true or false or have a value.

When they are in true or false mode they just enable or disable the condition they are associated with. But the condition still can be one of many for a required action... so you can have multiple true/false flags for one action to actually trigger.

When they have value they can do the above if specified by the effect like in an on/off (0 vs 1) switch or for example you can make an action happen when a flag is 0 and another action when the flag is 1. that means you have an action that happens when 0 and another action that happens when 1, etc. so 0 doesn't necessary means disable something.

You can have also conditions that depends on a ever increasing condition so you have flags that need multiple values. example... from 0 to 10.

Having flags with values allows you to set multiple actions depending on multiple values of same condition. IE you can have 3 actions or more for same condition.

Also you can make flags and triggers influence other flags so you basically create complex programming.

Example.

Blue wins if flag 1 is 10

Red wins if flag 2 is 10

And you have each time blue kills an unit flag 1 increases value by one and flag 2 decreases by 1.

And also when red kills a unit flag 2 increases by one and flag 1 decreases by one.

 

And so on...

 

True... the ME should be more visual... like IL2GB has or even better.

Edited by zaelu

[sIGPIC][/sIGPIC]

I5 4670k, 32GB, GTX 1070, Thrustmaster TFRP, G940 Throttle extremely modded with Bodnar 0836X and Bu0836A,

Warthog Joystick with F-18 grip, Oculus Rift S - Almost all is made from gifts from friends, the most expensive parts at least

  • Recently Browsing   0 members

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