ajax

If the module hasn't been sanitized, maybe you can try something like: base.os.time() base.math.random() or even _G.os.time() _G.math.random() I have no idea if this will work.

Updated file at top post.

@Kilix does auto turn to target work in trimmed hover? Yes Doesn't it need autohover to work? No

I've found that if you hide the FARP in the mission editor it will not automatically show up as a waypoint. If it is not hidden it will have its own waypoint.

*** Laser must be on *** 1. Reset the targeting system (backspace key). 2. Select target with datalink panel. 3. Press ingress button on datalink panel. 4. Uncage skhval (o key, I think -- mine is mapped to joystick). Skhval automatically slews to target. Edit: This is how I do it. There may be other ways. Also, I am writing this from memory, so hopefully I didn't forget a step.

Am I missing something? I use the datalink ingress function to automatically slew the skhval to the target all the time.

Just a heads-up: Apparently, the latest update changed the ME quite a bit. I think I've got it sorted out, but I want to check a few more things before I post the update.

Thank you, Frogfoot!

You may want to ensure 'a' is non-zero before the division operation.

The ruler still works in 1.5 ... sort of. It just doesn't show the line. The pertinent information (distance, bearing) still shows up on the header area.

I tried to build one, but didn't get very far: http://forums.eagle.ru/showpost.php?p=1713904&postcount=216 OP: The grid looks like 10km x 10km

Is it possible for a DCS Team member or Tester to acknowledge this post and report this bug? It's not a superficial cosmetic-type bug -- it's one of the most used avionics functions of the Kamov. So it's kind of a big deal for us Black Shark pilots.

You can get an older list at post #7 in this thread: http://forums.eagle.ru/showthread.php?t=126293

I'm not talking about fairly new DCS versions, I'm talking old, old missions like some originally written for BS1 or FC2. Also, the error occurred in the log file when saving the mission not at run time. This sounds like it's a different problem. A couple of things you might check: 1) If you're using DCS 1.5 or 2.0 make sure you're not using a 'mission start' trigger. It may be fixed now, but it was broken for these versions. 2) If you are copy/pasting from notepad++, try different encoding settings, for example try UTF-8 or UTF-8-BOM.

Trigger: can't execute trigger, err:"[string "?"]:1: bad argument #1 to 'loadstring' (string expected, got function)" I've gotten that same error. It generally appears when an older mission is updated and saved in a newer version of DCS. I've never been able to fix it, but it doesn't seem to really hurt anything.

It's always been that way. You will find that the next time you start DCS and go into the ME your new path will now be the default path.

And in 1.2.16

The PVI-800 will not allow entry of any western longitude > 99° 59.9' . I assume that because there was no need to do so earlier, this bug has gone unnoticed. However, with the advent of NTTR there is a need to enter these coordinates. This is not just a 2.0 open alpha issue -- the bug is present in 1.2.16 too. The original posts are here http://forums.eagle.ru/showthread.php?t=154106 and here http://forums.eagle.ru/showthread.php?t=154300

Yes, thanks!

canadianbaken, did you post a bug report?

Well, I just tried it -- you're definitely not crazy. It will not accept a 1 after setting the minus. In fact a 0 is the only number it will accept.

It depends on your reference. In the Ka-50, longitude in the western hemisphere is entered as a negative number. To the OP when you get to the longitude part enter 1 (for negative) then the longitude xxxyyz format (xxx degrees, yy minutes, and z tenths of minutes).

When flying a Ka-50 in Death Valley below sea level, the Ka-50 explodes every time. I haven't determined if the engine temps got too high or if there is an invisible "hard deck" that I keep hitting. Does anyone know?

Because it was originally defined as stated, and the earth is an oblate spheroid -- the circumference is longer around the equator than around any meridian. :)

I don't think it is advised either. However, it is used (albeit incorrectly) as a unit of distance: It goes on to provide the following definition:… 1 knot = 1 nautical mile/hour = 1.852 km/h exactly. This is based on the internationally agreed length of the nautical mile… …Knot is sometimes mistakenly used to refer to the nautical mile itself, but this is incorrect… https://blog.globalair.com/post/Origins-of-Knot-and-Nautical-Mile.aspx