DarkCrow

I made up this form to make it easier to plug in all the info I need. I don't have internet at my house right now but when I get to a location that has it I'll upload it just incase anybody would like it. Sent from my iPhone using Tapatalk

I also should note that I did my test in Nevada. At the location I was at I had a 12.19 declination and the MGRS were aligned to true north so I didn't need map correction. Sent from my iPhone using Tapatalk

I'll give it a go the other way when I get some time again. Sure was fun and thanx fir the help. Sent from my iPhone using Tapatalk

Took me a really long time to attempt the way I just did it because I was trying to learn it so I have only done it once. I was within 3 seconds North and 4 seconds west. I created a waypoint then created another waypoint 5000m away. I then used the polar coordinate function to create a waypoint 10000m away on the same heading. I used the NADIR to show my precise heading. I tuned to the NDB so the ADF needle would point to it. I then used the Viviane in slaved mode to aim at the needle and give me precise heading. Subtracted the 2 headings to get my angle for that formula. I then flew to waypoint 3 and did the same. I now had my distance to waypoint 2. I flew to waypoint 2 and got my heading there for the original formula. I was looking for an invisible target because I just set the radio trigger on the bulls eye so I wasn't sure how close I was but my range to the target from waypoint 2 or "d" in the formula was only 2337 meters. Sent from my iPhone using Tapatalk

Thanks a bunch Ramsay. Going to play with this now. I think the may be a reason to use the Polar Coordinate Function of the NADIR. I can start at position "A" get the coordinates, use the viviane to get coordinates a set distance away ( This would be the center of my "Baseline". The point which I would find the distance to.) Then use the polar function to create the 3rd waypoint an equal distance away on the same heading. This would be point "B" where I get my other angle measurement. Time to test it out. Thanx again. Sent from my iPhone using Tapatalk

I forgot the mission editor only allows you to transmit as low as 300 Khz, so Medium Frequency Range :) Sent from my iPhone using Tapatalk

In another thread Ramsay provided us with a formula to accurately calculate the coordinates of a target using the Viviane and NADIR: UTM N Cos (bearing + declination + map correction) * (range/10) + CurrentUTMNorth UTM E Sin (bearing + declination + map correction) * (range/10) + CurrentUTMEast I have some ideas for some missions and want to do something a little different but don't have the math skills and understanding to figure out how to do it even with the power of google. So I figured this would be a good thread for those of you that know the formulas could share with us here. (Also I want a formula that can be done on a scientific calculator and not an App or program that does it for you. It's more fun!) Here's a scenario: Target is a small shed, in a heavily defended city, that has a omnidirectional antenna broadcasting data in the Low Frequency range. You are able to pick this up and use your ADF to find the bearing to it but can not overfly the city to pinpoint it. (Basically a NDB.) You can mark your current coordinates using the NADIR. Use your Viviane and the formula above to calculate another point's coordinates a set distance perpendicular to your target. Fly to that location and find the heading to the antenna using your ADF. So what formula would I use with UTM coordinates to find the targets coordinates? I have 2 sets of coordinates, the distance between those coordinates and the bearing to target from both sets of coordinates. This could also be useful for calculating a targets coordinates outside of the laser ranger finder's 15000m range. If you can see the target you would still be able to use the Viviane's bearing. Sent from my iPhone using Tapatalk

Another thing this just made me think of is air threats. It is harder to spot something that isn't moving so maybe when near an air threat air speed must be below say "2ms" and altitude below "30 meters agl" and they'll hold their fire. I'm not sure if you can attach a moving zone to an aircraft but if you could, you may be able to have them hold fire unless you're in their zone and the above conditions aren't met. Sent from my iPhone using Tapatalk

Awesome ty, I'll have a look. Sent from my iPhone using Tapatalk

I haven't learned how to yet. I'm slowly picking stuff and I'll get there. This is just a start. Sent from my iPhone using Tapatalk

Alright, thanks to the both of you I was able to find out how to do what I wanted to do. My goal was to be able to have enemy units not fire on me if I was below a certain altitude 'above ground level' to simulate terrain masking'. In the ME it only gives you the option of below altitude 'above sea level'. With mountainous terrain it would not work very well. So my plan was to use the radar alt values. So in the arg_int.lua I found the argument id for the radar altimeter and it is 94. In the mainpanel_init.lua I found the guage parameters. I was able to use the Cockpit Argument In Range with the argument of 94 and had it trigger a message between the min value 0.035 (10 meters) and max value 0.072 (20 meters) Sent from my iPhone using Tapatalk

Ty Polie. Just opened it and saw one of the things I would use it for. I used to use conditions of speed less than, altitude below ( would have to check terrain alt) and vertical speed range of 0 just to see that I was landed. I see in the training mission you just put cockpit parameter equal to IS_LANDED. This is a great resource and ty again for taking the time to reply. Sent from my iPhone using Tapatalk

I was in clickable, it may be here in arg_int.lua. Ty for your help. Sent from my iPhone using Tapatalk

Ah, ty. Sweet I'll have to play around with this! Looking at this, and I'm new to this, I see that for instance I can use this to turn on or off Radio altimeter and maybe even set the warning dial on it. What I am curious about is can I get the reading and use it similar to the ME's above alt or below alt trigger function? Say for example "below 15 meters AGL" Sent from my iPhone using Tapatalk

Just as the title asks. I'm looking to create missions with the Gazelle and am curious if there is a guide with the cockpit parameter values, ID's and their function. Also cockpit clickable functions would be helpful. I thought I read also from the developers that the radar altimeter could be used as a cockpit value but don't quote me on that. Sent from my iPhone using Tapatalk

It's a good idea in theory but not practicality. The reason being that most module campaigns and payware campaigns were designed in Caucasus. So you would make a lot more people mad that would lose all their payed for content or would be forced to buy the map in order to use it. Sent from my iPhone using Tapatalk

[emoji3] Sent from my iPhone using Tapatalk

I guess to illustrate the difference in the grids to the f10 map use the mission editor ruler and run North at a heading of 0 degrees then look where your grid lines are. Your grid lines should be a reference to true north but they are not. Sent from my iPhone using Tapatalk

He's saying the same thing above. To calculate where true North is while using a magnetic compass you have to account for the deviation of magnetic North from True North. This is called declination or variation. I think where you may be mixing things up is the UTM grids and lat and long lines. On the f10 map the terrain is oriented to true north. However the UTM grids are not in the same direction. They deviate from the flat maps true north 4 degrees west. so this is where the map correction of adding another 4 degrees in addition to the magnetic declination comes in play for UTM. 7 degrees when using lat and long lines on the f10 map that is oriented to true north. I believe this maybe from taking a rounded grid and overlaying it on a flat map oriented to true north on our displays. Sent from my iPhone using Tapatalk

I guess another variable that may throw off accuracy could be the helicopters altitude in relation to the target assuming the laser range finder is finding angle distance directly to the target and not doing any computing of helicopters altitude. So if I was reading 5000m away at 10m altitude my indicated range should increase if I was say at 2000m altitude in the same spot. Not sure how much. I guess you could use a similar formula using your radar altitude and slant range to target to find your ground distance to target then use that in the other formula. I need to sleep, I may be over thinking this[emoji12] Sent from my iPhone using Tapatalk

How it works the polar coordinate system in the nadir ? Just out of curiosity, does the map correction come from display a sphere on a flat surface than using UTM grids overlaying that? On a side note I first thought you meant + or - 0.1 foot ( 0.1) but now realize you meant + or - .1 minute. [emoji4] Sent from my iPhone using Tapatalk

Also like you said range will play a large factor. If you are close to the maximum range of 15000m of the Gazelle's laser, + or - a half a degree off on either map correction or magnetic declination is going to make you further off than if you were 5000m from your target. Sent from my iPhone using Tapatalk

The difference between magnetic North an True north is called declination. Some also say deviation and use them interchangeably. I have to account for declination when I'm installing a directional antenna on a tower ( such as a point to point dish) and I use a magnetic compass. Wouldn't need to with a GPS alignment tool. I believe the map correction comes from taking a round surface and putting it on a flat map. So when I was using the NADIR declination of 6.4 and the incorrect map correction of +7 I was too far East. Using the 10.6 you told me hit the target because it was almost like using a declination correction of 6.6 and map correction of 4. Maybe just using the NADIR declination and 4 map correction would work. I haven't tested in the Gazelle but the further East or West you travel the higher and lower your declination should be. Sent from my iPhone using Tapatalk

[emoji106] Sent from my iPhone using Tapatalk

Ty. Excellent find. I flew to roughly the same spot, was within a couple hundred meters range and a degree heading as I was when I tried before. I used the heading + your 10.6 declination + correction and sent the coordinates to a M270 that rained down directly on the target! The NADIR still changed my entries aswell but it didn't make a big enough difference I guess. I was using 6.4 from the NADIR for declination + the 7 for map correction before. Sent from my iPhone using Tapatalk