RvEYoda

That isnt going to work. Simply because leavu3 uses several native libraries for graphics and audio (Desktop LibGdx libraries). If you really want leavu3 running on android, your best bet is to do a proper android port - Since it's built on libgdx this shouldn't be very hard if you got android dev experience (I don't).

Your router. Unless you explicitly open the ports yourself in your router or enable some kind of DMZ setting - it isnt open. But some people tend to do just that - enable DMZ, which is a potentially BIG security problem.

Don't forward leavu3s ports online.

You have to run windowed mode if you want to use leavu as an overlay. Uncheck "full screen" in options and set your resolution fake fullscreen/full screen windowed You can use CTL SHF Home/End to bring on top/set behind

Quick question. Since lua has no widechar support and uses just bytestrings. Can we assume DCS always outputs strings in lua environments as utf8? (e.g. Export.lua) Thanks.. /Y

Hmm.. I don't think I will make an ADI any time soon, sorry.

If you set the fuel for the Su27 in the mission editor and have it start in the air, you get significantly less fuel when you start the mission. Example: * Set mission editor to 6% fuel * START IN AIR * Start mission * Engines dead ingame (Zero fuel) Seems like the total quantity is wrong by 1-1.5 tons. For example we also tried setting it to 40% and got about 25% ingame :S. The bug is especially annoying for dogfight training missions in multiplayer (or aircraft performance testing like we did in the squad today :)). EDIT: We unzipped the mission file and the mission (lua file) actually shows the correct number, so we think the error is caused by the game somewhere after that. EDIT2: Sry, this is not the beta version I used - it's just the normal 1.5 version. See screenshots below. The behavior does NOT happen for F-15.

I think you guys just accidentally added something with notepad++ :). It's just a standard json file and I use ++ myself.

well. If things arent working with the combined exports... 1. Install the default script for helios 2. Download the latest dcs remote. It has automatic script installation built in the first time you launch it... That hopefully does it :S. dcs remote just appends the current export.lua with a dofile for dcs remote, if it isnt already there

Nice one

The 5 at the bottom are just default settings for the pages. The first 2 are experiment development stuff. use3dBscope is deprecated and should be removed (leave it at true!). The default leavu behaviour for rwrSeparateSrTr (=false) means that for example Sa10 search and track radars just show up as 10s. If you instead set rwrSeparateSrTr to true it will behave like in the game where you have several different types of threats. But personally I have very bad memory of what is what so I prefer just having them clumped up into one type.

Kind of - JarJar is your own default data link callsign. You should really change that... Edit your static-data.json in your dcs remote folder. More detailed markpoint guis will have to wait until we implement LotAtc<->Leavu3 integration :). Im already talking to the guy and we're going to do a planning session some time next week.

A simple version of that is already in. Just click anywhere on the HSD :)

Pretty high fuel loads and full a2a missile loadout. So I guess it is based on actual forces on the wings.. Do we have some graphs showing the real life flanker limits vs payload? Doesn't the built in limiter have any awareness about the payload?

We were flying a bit of guns and 2v2 today.. There seems to be something off with how the flanker behaves now... We have all lost our flanker wings around what seemed like 6-8 gs repeatedly :P. No need to go up to 12+ Gs (up there it's guaranteed though). But it was like our 2v2 bvr session today when RvE-Dackster was turning back hot with his flanker... and his wings fell off :). I had the same problem myself when I tried to fly the aircraft. In the end we all stopped using the su27 in bvr cause ... yeah... the wings just kept falling off.. There is something possibly wrong with the new damage behaviour ^^. And Im saying that as a person who is quite biased in the f15 direction. We need to be able trust our aircraft that our wings wont fall off at 7 Gs steady turn.. :) EDIT: Ok in the track it actually shows Dackster @ almost 10gs when the wings break off.. I guess at least better than 7

Bug fixed (Or rather, the win32 behaviour worked around)

Basically leavu and dcs remote are pretty much always backwards compatible during updates. So no absolute requirement to update just because you see a flashing button :).

FYI the noFocusOnClick leavu3 setting is a bit finicky. It ONLY works if you 1. double click leavu3 2. Immediately after you double click leavu3 (before leavu3 appears!), click another window :). No clue why. Some win32 API magic. Same should be true for starting multiple windows by script. Initialize the script, then before any window pops up (asap!) click something else :S

I have an automatic build tool that puts up new versions for download as soon as I change anything. I wont post in this thread unless there is a major change somewhere. I think I just added some more logging. :)

yep. Enable noFocusOnClick in the leavu3 config file(s) :thumbup: Maybe this should be the default setting ..

no clue :S. Havent seen that. Can you upload your dcs remote log file somewhere? So i can see all of it? Also what java version do you have? What OS are you on? I only tested on win10, ubuntu 1404 and macos so far. Also make sure your java jre is 64 bit!

Interesting. Could be a bug or limitation somewhere. As I don't have any secondary monitors... wanna jump on ts or pm and talk to me about the problem? We can probably find a workaround

Because leavu3 is out :), see --> http://forums.eagle.ru/showthread.php?t=164329

Create a launcher script and have 3 different config files. Or 3 different unzipped directories ( your choice). Leavu3.jar also accepts a command line parameter - the path of a different config file.

To quit leavu3: Right click the icon in the taskbar. Click close Or Click the icon in the taskbar, then alt+f4 To increase the text size, edit the symbolScale parameter in leavu3's config file