RvEYoda

I hear you. I'm listening to you. But not necessarily agreeing with your opinion. From my perspective we're opening up the sim to a wider and more deep range of gameplay options. Now that ED is improving the server admins' options - it should not stop either group from having fun. I believe every server admin should have the right to restrict the options for their server, and staying within the rules of the server any player should be allowed to play the game to his/her maximum enjoyment. Example: RvE dedi will allow export.lua based cockpit mods (incl leavu), while other servers might not, depending on their preference. I don't recall actually what happened 5+ years ago (I stopped playing lofc/dcs for personal and professional reasons), but I've seen some people kept using leavu2 (still top thread in fc2 mod forum) up until the leavu3 release. There have also been some leavu clones made out there incl dlink. I've been away too long so I don't know what really has been going on in the community. Was leavu2 and the other mods incl dlink also banned from public servers and events?

Actually I had no idea it bypassed IC when I started developing it. I thought server admins were free to allow and disallow whatever scripts and files they wanted configured through IC. But apparently we now have learned that unpatched IC does not check the Saved Games/DCS folder. Not sure what you mean about catching Coff off guard. Coff has been very friendly in helping out the community with both setting up server configuration and helping out modders. I was recently invited to an ED lua developer mailing list where we can discuss bugs, features, etc of the lua export. I find the aggression totally unnecessary. I have no quarrel with you or your squad so I don't know why all of this hostility has to be written here. GG did not build leavu - I don't know why his comment made you think Leavu was "designed" to bypass IC. He did however help out with finding out what the correct rwr unit names are, which I thank him for. GG is simply stating limitations of unpatched IC as far as I'm concerned. Again, you'll need to ask him.

Chill guys. I don't want this thread banned. :). Everyone can configure their server to their own liking.

Imo the only relevant part really is what a server admin considers legal for their game or not. Leavu was developed with the ground that server admins could allow vs disallow it - depending on what kind of game/atmosphere they prefer. It turned out that the game's IC was not capable of that - so the developers will very shortly add a new setting to remedy that. That's really what this thread should be discussing.

I know I have not been clear about this - A standalone DCS Remote = dlink server :). Just Download the dcs remote on any machine you like and run it there. NOTE: Edit its config file (dcs-remote-cfg.json) so it doesn't try to connect to a missing DCS and spam log-errors. It will come down to a per-server basis - For example we will host a dedi server soon where cockpit tools/cockpit mods/home cockpits are allowed. If we are requested by other server admins to not fly in their servers with leavu I will respect that. I cannot speak for others trying to get into server with mods, nor am I a leader of my squad - but if I see something that should not be there I will let them know. But the new setting in the game (a few days ETA?) will fix that regardless. So far though I have not received any messages, but if there is some concern, just PM, email or hop on rve TS. Remember however that we have had guys from like 10 diff squads on the dlink so it can be difficult to reach out to all for you - I for one do not have their contact information - nor am I logging their details (and adding such logging might even be legally questionable). I recommend you do not post in this thread with such message - as it will lead to crazy trolling and I will most likely miss that message anyway. If you are a server admin feel free to message any of the RvE veterans like Myself, Flame, Yorz, etc. I hope you make the decision based not on who screams the loudest, but actual public opinion or your own squad's internal opion. Possibly one or two reasonably neutral votes like "How do you like flying with leavu/cockpit mods in our server?" "Do you approve of others flying with leavu/cockpit mods in the server?" If you got like 2% of the community being anti-leavu, It would be a little sad to see it go away imo. But if like 40% are against it for your particular server, then definitely dont have it on your server. -------- On the behaviour of awacs + sneakers (or whatever you call it :)) - I have not seen that personally with leavu, but it would not surprise me, as I also agree such behavior is a powerful tactic already used by many non leavu users in most servers. Obviously it is made more powerful with flight data link - but so is flying high with good spread, grinders & what have you. / My 2c

Well it's up to the admins to decide what is allowed in their servers, events and competitions. I expect it should only be a few days before ED releases their announced on/off switch for local data exports.

hmm. leavu and dcs remote are made to support any other mod simultaneously, however, the other mods might not be. Just for testing you could try 1.5 with an edited export.lua to only include the dofile on dcs_remote.. Purely for testing purposes. Again, you can always jump on rve TS to get help.

well hmm.. I checked your files and couldnt find anything wrong - however - I saw you have a lot of different alpha & beta installations. Which one have you been testing with? Can you test also with the standard non-beta 1.5? I mean the ED developers are currently working on implementing the allow_ownship_export switch and it may be forced off in the current alpha versions - I dont know. If the standard 1.5 or singleplayer doesnt work, then jump on rve ts and lets see what s wrong.

I think you may have misunderstood how to start or install it. Maybe jump on to rve TS and get some help? Also I only see a stack trace (some text) from something. You'll need to actually attach both log files for me to figure out whats wrong.

Agreed with everything except "no way realistic". Imo albino turkeys are still turkeys. So an upgrade to albino turkey is still better than staying with vanilla chicken.. get it? :)

Fully respect what you're trying to do. Enforcing vanilla gameplay is probably something many want the option to do, though I have no interest in attending such events myself. Like I said before, I was under the assumption the allow_ownship_export was already implemented before through IC, though it turns out now IC could not handle it. However please stop claiming it's a hack. Leavu is based on ownship data given by APIs documented by ED. There is no more hacking involved then developing new flyable aircraft like the mig21. Leavu has no gods eye data source of the battlefield - it runs entirely on data from own aircraft instrument and sensors shared across a flight data link. In the future however, with the LotAtc integration being made - gods eye will be closer - but still limited by what the actual awacs and ewr radars see on your side (just like lotatc - exact same limitations because leavu would use the data given by lotatc). And of course it requires the server admin to enable the feature in lotatc. I don't know who was talking about it earlier but RL GCI can give you more info than Leavu not less - both vocally but also over two way messaging and symbols

if you use symbolScale above 1.5 (low res monitor), OSB button texts will collide with other text. To solve that you must disable rendering of OSB button text (Click the osb button marked 'OSB' or disable it in the config file). You can also chose to make the window wider.

So - I just found this thread! Are you guys saying you cannot block leavu3 with existing IC? I always assumed you could when I started developing it :S. I haven't received a single message from server admins about it - I just assumed they were happy campers just like us. Good then they you can now have a simple button for it that fixed the problem. I'm a little sad though that many people simply refer to cockpit extension mods as cheats. There's really a lot of effort put into enhancing the flight and combat experience, environment and immersion in both lets say helios and leavu3. I guess we're all looking for a different flight environment online. Some prefer the game to act one way, some prefer another. I think some of the RvE members, Flame especially, are thinking of launching a dedicated server where such tools are encouraged - and we're also working together with LotAtc developers to create a fully integrated environment between awacs-gci-leavu. Me personally I have no interest flying a game with limited avionics when I don't have to, but thats just me. Server admins should of course be able to configure and restrict whatever they want. Leavu3 capabilities is really nothing special in terms of modern aircraft. In fact it is quite and intentionally dumbed down in many areas. We really only use ownship data (such as explained earlier by devs with ownship export API) - and it is quite limited. Way back when we developed Leavu2, the ED developers helped us directly to adjust and improve the self data export APIs. We really couldn't have created the mod without them/you and we're really happy about the help we got. If you, ED, have any questions or if you have time to answer some about these APIs or future of these kinds of mods, that would be highly appreciated. This has pretty much been the case since 2007 or so I believe (Around 2012 I took a break from hobby simming - still simmed/flew professionally though) - So Leavu2 was never "abandoned" because of some kind of hate or flame wars as was suggested earlier in this thread. It's just that this particular developer's personal hobbies changed over time :=). Leavu2 and Leavu3 are almost identical in terms of presentation and capability - with some small presentation differences. Leavu3 is just better code and dcs support, whereas leavu2 was awful code and doesnt really work well with anything beyond lofc 1.2. Possible future ideas include: - HMD on google glass :)... All those missing bfm modes :pilotfly:. - Server browser with integrated mod-manager & IC

'gameDataFps' is the highest fps leavu will try to get data from DCS at. Every time leavu gets data from DCS, it also tries to re-render the display. Effectively, this means leavu will run 'up to' that fps. So depending on how much CPU room you have, you can set it higher or lower. If you have a monster machine and gigabit LAN - heck - set it to 500 fps, and leavu will run at the same fps as your game :). NOTE: Leavu will never run faster than your game. NOTE also: The highest accepted gameDataFps is 999 :). This just means up to 999, but not faster than the game itself.

It's called 'symbolScale' in the leavu3 config file. It affects everything - not just text. Both symbols and text become larger (They have to - otherwise the text could not fit inside the symbols :)).

I use it for both single and multi player.

1. Use the shell and experiment a bit. See what commands are required. Write them down 2. Yes, copy the stuff you found working into a text file, save as "hello.bat" or "leavu.cmd" or something. Run that script instead next time. My own scripts wouldn't make much sense to you as I run it on linux.

Hmm Im not sure how to explain it otherwise.. :S. The 'command line' is basically a shell/command prompt. In Windows the standard shell is CMD (some prefer powershell) - it is started by start -> run -> cmd. You can also run shell commands through bat/cmd files. In the old MSDOS days the shell was all you had. In linux or macos based OSes you quite often do daily tasks from the shell. Most programs can be started from the shell, for example if you want to start dcs, you can do start->run->cmd, then 'cd' to the dcs directory and type dcs.exe <ENTER>. In the same way you can launch java applications (sometimes packages as .jar files) with the 'java' exe, which is installed when you have java on your system. In that case you can do start->run->cmd, 'cd' to your leavu directory and type 'java -jar leavu.jar'. That way leavu starts and you also get all the logging output in the shell. Command line arguments are application parameters given after the application exe or .jar file. for example java -jar leavu.jar my-config-file.json. Here the text 'my-config-file.json' is a command line argument. Leavu is written to interpret the first command line argument as the config file path/name. By writing a simple cmd/bat file (=shell script) you can automate startup of several leavus with different config files.

Guys, Guys, you only need 1 folder. Just have 6 config files. Pass the config file you want to use as a command line parameter. Example: java -jar leavu3.jar my-cfg-file.json Make a cmd/bat file or something which starts 3 leavus. Much easier to handle program updates that way.

Thanks! - Would love to see a Shits n giggles with leavu mayhem if you ever get the chance:).

Well I don't know. The DCS FC planes have very similar data export, so getting more of them fully supported might be possible. However I'm not sure about the newer and somewhat more deeply simulated planes like A10C, mirage, mig21 etc. The reason is simply that I don't know how to extract equivalent data from the game - if it's even possible. If someone can give me APIs with equivalent data for other aircraft - supporting them would be super easy. If you'd like to lend a hand the best thing would be to use the http/rest API of dcs-remote + leavu to extract what is currently exported (run leavu and the f15 instant mission UNPAUSED - then just GET http://127.0.0.1:12340/export/dcs_remote_export_data() Take the resulting JSON and look for where I would get the equivalent data for the other aircraft. If it's available somewhere (different format is not a big deal), then sure we can discuss implementing that aircraft too!

I wish I could add carets for live antenna motion, but that data is simply not exported by the game for the F-15 through Export.lua :(. Otherwise I would have added it.

Thanks! Let me know if you run into any bugs or other issues. :pilotfly:

exactly No more 2-3G continuous guidance vs non-maneuvering target with the missile making a 10-20G S-jink half way to it - again vs non-maneuvering target:). That + Loft + im sure you discovered more stuff yourself - I haven't played much myself since I came back to the game.

If anyone is interested, all our tests so far suggest dcs DOES encode strings in Export.lua environment with utf8 :). We exported some cyrillic stuff, sent as json and it was successfully read on the receiving end!