MIST spawned groups - take controle of units ?

[Zarma]

Hello guys.

 

I am using a modified version of Jinx's CASCAP mission which allow to spawn air and ground groups for tasking.

 

If I add a gamemaster slot, I can take control of the air planes I own (tested with mig21 and mig15), but not from the ground units even though I have CA.

 

Any clue ?

 

link to original mission : https://forums.eagle.ru/showthread.php?t=158936

[Zarma]

Bump.

[Grimes]

Mist doesn't automatically add a "playerCanDrive" entry for units which defines whether CA can control the unit or not. So where-ever it defines the groups that get spawned in that script you can just add a playerCanDrive = true entry and that should fix the problem.

[Zarma]

Thanks will try that.

 

And with the Viggen added, can we have the QFE over a specified zone ?

 

Edit : confirmed working. Thanks a lot.

Edited February 7, 2017 by Zarma

[Grimes]

What is needed to calculate QFE?

[Zarma]

I already have the position of the spawned target zone and have different coordinates format :

 

mgrs = coord.LLtoMGRS(coord.LOtoLL(unitSpawnZone))

mgrsString = mist.tostringMGRS(mgrs, 3)

 

lat, lon = coord.LOtoLL(unitSpawnZone)

llString = mist.tostringLL(lat, lon, 2)

ll2String = mist.tostringLL(lat, lon, 0, true)

brString = MA_getBearingRange()

 

_targetInfoPath = missionCommands.addSubMenu('Target information', _taskingsGroundPath)

 

missionCommands.addCommand('TARGET: Group of ' .. groupSize .. ' vehicles and infantry.', _targetInfoPath, MA_emptyFunction)

missionCommands.addCommand('LAT LON: ' .. llString .. '.', _targetInfoPath, MA_emptyFunction)

missionCommands.addCommand('LAT LON: ' .. ll2String .. '.', _targetInfoPath, MA_emptyFunction)

missionCommands.addCommand('MGRS/UTM: ' .. mgrsString .. '.', _targetInfoPath, MA_emptyFunction)

missionCommands.addCommand(brString, _targetInfoPath, MA_emptyFunction)

 

Is there a function to have the QFE, so the pressure at this position, to enter in the Viggen computer ? We only have it in the kneeboard if we plan the flight, not if we add a waypoint manually.

[Grimes]

There is no direct function to get the QFE or QNH, but I assume it can be calculated if certain values are known. It is just a question of what is needed. If it is just the altitude of a point above sea level then it should be relatively simple. I'm a little to sleepy to be reading about hectopascals or whatever else to figure out exactly what needs to be done.

[Zarma]

OK thanks for the help.

[Zarma]

After searching a little, I found some info.

 

In metric:

1 milibar is approximately equal to 30 feet. This calculation is therefore also approximate but is good for airfield elevations to several hundred feet since we round to the nearest millibar.

Divide the airfield altitude in feet by 30 to get the number of millibars above MSL. Add this to the QFE to get QNH or subtract it from QNH to get QFE.

For example, the airfield elevation is 200 feet. Diving by 30 gives us 6.66r. The QFE is 1023. Add 6.66 to get 1029.66 and round up to 1030 millibars, which is the QNH.

In imperial:

1 inch mercury is approximately equal to 900 feet. This calculation is therefore also approximate but is good for airfield elevations to several hundred feet since we round to the nearest hundredth inches.

Divide the airfield altitude in feet by 900 to get the number of inches above MSL. Add this to the QFE to get QNH or subtract it from QNH to get QFE.

For example, the airfield elevation is 300 feet. Diving by 900 gives us 0.33r. The QFE is 30.12. Add 0.33 to get 30.45 which is the QNH.

If the airfield elevation is below sea level, subtract rather than add and vice versa.

 

The trouble is you need at least one value (QNH) to calculate the QFE on a given location.

[Zarma]

Up ?