Captain Orso

Since it seems nothing is working as it ought to, I would say you are doing everything wrong. I'm sure, if you know what you are doing, you can use OvGME to implement the mod, but the fact that you are using OvGME to implement this into '..\Saved Games\DCS.openbeta' makes me question whether you actually do know what you are doing. Follow the instructions and copy the downloaded '..\Scripts' folder into '..\Saved Games\DCS.openbeta'. Done. When you say, you are "walking around" the map, are you talking about the 3D view or F10? You do not click the LMB to "anchor"--whatever that is supposed to mean--the F10 map--the one you should be using with Scratchpad. In the F10 map, you press and hold LMB to drag the map to the position you require--the scroll wheel allows you to zoom-in and -out. With the Scratchpad window open, click on the empty check-box to the right of the <-- --> arrows to place the center-dot at the center of your display and add the +L/L button to the right of that. The white dot is what is used to tell Scratchpad what coordinates you wish to record. Where ever the dot is when you click +L/L determines the coordinates recorded. Zooming in as far as possible onto a position and putting the white dot directly over the point to record will give the most accurate results. If you are using Draken35's download, follow the readme instructions to implement any required extensions, and follow the instructions to use them.

CTLD was only a ready example to illustrate what I'm actually trying to achieve. I'm actually trying to find a way to use the rangescript.lua (https://github.com/ciribob/DCS-SimpleRangeScript) without editing it to implement the setting I want. I'm still trying to find a away to test changing variables, but it seems that the script used the same variable name (same variable??) in two different functions, setting the variable each time, so probably my efforts are for naught *frown* I want to set maxAlt, minAlt, and range.bombingMinAlt from within the mission.

Two and a half years later and I see that I never reported that I had discovered what the issue that I was having was *sigh* Management Summery The Strafe Pit area definition through following the plotted path of a 'Late Activation' vehicle somehow got pulled apart. Per definition the first leg of the path and the last leg must cross, thus forming an enclosed area, which is the Strafe Zone. In my mission the start of the first and end of the last legs were very close to the crossing. The mission had been modified many, many times and somewhere along the way, for whatever reason the crossing of the first and last legs became uncrossed No crossing, no enclosed area, no strafe zone definition, no rangescript function. I then made the crossing very distinct, with the first and last legs clearly crossing and the start and endpoints far enough apport that even a Japanese earthquake won't uncross them again. One simple thing I might suggest would be, instead of this difficult to use vehicle path to create an enclosed area, simply use the now for functional trigger zones. A Quad-point trigger zone would be perfectly function and easy to create in the ME and easy to reference within the script - easy-peasy.

I know I saw it somewhere and I can't remember where and I can't find it, but.... How do you set a script's variables from within the running mission? For example the ctld.lua has ctld.Trace = false a variable set with the default value 'false'. There is some why to change 'ctld.Trace' to another value, like 'true' through a trigger within a mission which has loaded the script, something like under TRIGGER - - ACTIONS DO SCRIPT 'ctld.Trace = true' but that is not the correct format for the command. Anyone know how to do this? Thank you

Sexy French voice says: Monsieur, are you looking at my... back side? FEMALE!! Sexy female voice....

I know I saw it somewhere and I can't remember where and I can't find it, but.... How do you set a script's variables from within the mission? For example the ctld.lua has ctld.Trace = false a variable set with the default value 'false'. There is some why to change 'ctld.Trace' to another value, like 'true' through a trigger within a mission which has loaded the script, something like under TRIGGER - - ACTIONS DO SCRIPT 'ctld.Trace = true' but that is not the correct format for the command. Anyone know how to do this?

The map is really beautiful and the land itself is simply fascinating. Flying missions here is fun. While building them, you just have to remember, January is summer and July is winter or else the days are very short and dark lol.

Here are some quickly made screenshots. The last one is actually from the Falkland, because... why not.

I just had to say, the mountains on the South Atlantic map really do look fantastic now I have only one question... where the hell is "Shroders"?! DCS World Changelog and Updates of Open Beta 8< DCS: South Atlantic by RAZBAM Simulations 8< Adjusted the stands at Shroders to allow for Hercules parking 8< Keep up the good work

Oh man, forest for the trees... I think the real question is, what are those islands, and when do we get to bomb them?

Yeah, since the CTLD JTAC also tells you what type of unit is being lased, you can go to the F10 map with Scratchpad and check the coordinates against what JTAC is posting. I'm just thinking the whole time, there's gotta be a better way. I think I need to write a plugin for Scratchpad to collect the data from the JTAC report, let me pick the JTAC unit and take the coordinates from that, then use those LAT/LON/MGRS to put down a marker of some sort I can put into the RTE and then DIR the point to put the home plate over it. I'm also starting to set everything up the run the ship from CPG, but I've got a very long way to go with that. Also I really hate how slow and sloppy the AI Pilot is, like if we're passing over a small town and I want him to fly as low as possible up this avenue, you can forget it. Either live with the crappola way George flies or do it myself.

Hi LorenLuke, I'm going to tell you a secret... I have had the KU setup on my keyboard for many months, BUT not permanently. I use a 'switch' modifier. I can very quickly enter an MGRS... while on the ground--I hate landing away from airfield/FARP. I cannot tell you how many times I got snagged on the ground by unseen detritus and crashed the rotor into the earth Anyway, I had a free toggle switch on my Thrustmaster Warthog Throttle--the one I use for lowering and raising the undercarriage on all other aircraft--setup as a 'modifier' 'switch'. So when flipped up, practically the entire keyboard is mapped to the KU, including the NUM block. Using the keyboard like this I can very quickly enter anything into the KU, especially MGRS coordinates, as 1. I can ten-finger blind-type, and 2. I have the number block mastered, because in my youth I worked as a cashier for several years, plus two years in accounting working mechanical calculators. The problem is, for ten-fingers you need... ten fingers, ie none for the cyclic, and for the number block I absolutely need my right hand, and flying the lefthanded cyclic is not pretty for me. But you did make me realize that I'm already switching to the CPG seat to switch to 'weapon follow' view so I can see what the Hellfire is doing in-flight, so I might as well switch to CPG to enter the target coordinates. In fact I might as well setup CPG as far as I need to rifle off LOAL Hellfires and turn the nose to keep on target. *sigh* if George were not so ret... learning impaired, life could be so much easier. Thank you

In the end, I'm trying to compensate for the inability of George to 'write' down the target coordinates the JTAC is providing, enter them as a target point and making the target point available that the pilot can aim the aircraft, and thus the Hellfires, at it so that the LOAL HF have the best possible opportunity to find the target lased by the JTAC while in-flight. At some point, the updates to the trim and SCAS have made it impossible for me to put the Apache into a stable hover into which I can apply Altitude and Attitude Hold while I enter/edit a waypoint for me to use as a target.

Many thanks for all the info, LorenLuke. I've been trying to implement and test it, but with limited success. The CAQ works as you said and the video show, but I can find no use for it. The deviation between the TSD map and the F10 map are far too great and the scale of the TSD map is so poor. You would need a map at a scale of about 1-50,000 or even better, 1-25,000 and these appear to be about 1-100,000 at best. I'm going to have to set up a special mission, emulating what 4YA does, but without enemy CAP constantly buzzing around my head. I'd rather not try to make any statements about viability, before that, because there have been too many variables and incidents. One irritating thing I can say is, at dusk and afterwards you can easily see the JTAC's 'sparkling' of the target, but not through the HDU and NVS, but only through the naked eye - smh.

Just MHO, but I think the gaps between those concrete slabs could be toned down a bit. The reality look quite a bit more subtile, to me at least.