RvEYoda

the hsd is centered at 0.25 of the screen in that current screenshot so this means the "60" represents 60 nm for the outer (3rd) circle. inner circle is 20 nm if it would be centered at 0.5 then the scale reading would be 40 nm, representing the second circle, just like F4AF. Yes the Flagpole is the most important on that picture prob :). The only thing that can quickly let you know where you are going imo.

... that have leavu :P

Look closer, it is already in :) ( just a diff format, flag )

All will be explained in time :book:

Simulating key commands is not required. LEAVU has a direct lua input bus through ERI radar :) LEAVU sends "X,Y\n" to ERI, and if X and Y are numbers, it is interpreted as LoSetCommand(X,Y) Havent tested it yet though. Could be interesting!

Yes, you all must connect to the LEAVU datalink host first, like this :

Yes its in blue. I use the default icons of the F16 MLU 2 manual. Leavu2 does not currently support customization of icons, so for now at least it shows only the standard icons

I was allowed to release this test image of leavu 2.0 outside beta forums, enjoy ! : As you can see it demonstrates the panel's aspect independence and navigation features. This aspect independence is also why we cannot just fit a normal picture of an mfd on top. Some people have different screen aspects and sizes. I'm open to suggestions on how to solve the issue of the panel having no cool panel picture ;).

Leavu cannot do it no, but would it be possible to write such software? yes .

F4AF target step is too perfect, or more correctly, its environment is too perfect ;) I originally used AF as a reference for LRM, before I got the more accurate information I have now. However LRM will not be updated as Ive left that project. Regardless there wont be any LRM for FC2. 1. Target track files are the names of the actual tracked contacts in the avionics memory/ram. The creation of such files are too fast with lockons lua export - it is faster than the ingame radar display, which causes the user to be able to step "too soon". Therefor I introduced a delay.

After speaking to a US fighter jet pilot I have adjusted the target step capability for the FC2 eri radar mod to better resemble real life behaviour. The main changed are : 1. Introduced a significant delay to the initial creation of track files 2. Introduced a delay to the actual stepping mechanism 3. Introducing a random factor to the stepping mechanism.

Actually now that Im thinking about it... We dont need to download the servers... I just got an idea :) : Every server that wants to be listed in our browser installs a special server script This script transparently and automatically connects to our server list when they launch a mission and says "hello im running mission..., with mods... , and settings ....", and then continously feeds our server with real time data. So in fact, we dont even need their server list... It will be visible of course automatically in the ingame browser, but also feed the necessary data to our browser. But it would also be good to list the "default" servers who don't use this server script

Yeah once it got to Wvr we were in trouble!

I really hope ill be allowed to download the server list... Man what an awesome browser we could make :)

I think the client will never run the servers copy. It just checks if clients and servers have the the exact same file contents. If they are identical then the client is allowed to join the server, and the client runs his own (identical) file. The server doesn't export a file to him. For this reason I posted in the wishlist thread and asked ED to allow us to connect to their server which tells what game servers are online. This would allow us to create our own server browser with chat functions and more importantly MOD statements for each server. For example you click 104th server and you get msg : "This server uses mods A,B,C. To play on this server you must have them installed." and if they are just lua then "do you wish to activate mods A,B,C?", like an automatic, per-server mod manager. Cause diff servers will for sure have diff settings. And this method would solve _all_ such issues :) ED doesn't have to do anything for that to work except allow us to download the server list.

In the RvE 80s server we had almost 2 migs per 1 F-15 This worked very well with payloads 4xAim7 and 4x9 vs 4x73 +2xR27 in the end we logged the results and I think blue won 2 games and red won 1 each game lasted for a few hours

you mean you want to click like touch buddy RWS/TWS on OSB buttons, control scan zones etc? That is a possible future feature for the LEAVU F-15 module.

Thank you wed. If there are any special instruments you would like to see in LEAVU for US or RU planes, please let us know. If you know good algorithms for certain situations for transferring this or that, that is also very welcome. Post that in the leavu thread please and I can see it fastest :)

But how would you access the luaExprotFunctions Likely LO does something like function LoGetMySpeed....[definition] -- make functions visible dofile(export.lua) LoGetMySpeed = nil ; -- functions no longer acceessible If you write your code in other export files it has not effect, because the functions are just nil. This is at least what i experienced when testing it

I have tested this.It does not work for me as the "LoGet" functions and "LoSet" functions are only accessible from within files triggered by export.lua. If you put them in other lua files they did absolutely nothing for me. Only from export.lua can you retrieve this data when I tested it.

Correct

No it works like this : Export.lua can contain lua export functions. These can be global ( access data on all players ) or local ( access only self data ) in config.lua you can turn off global functions only. Config lua does not turn off export.lua Where it says EnableExportScript = false -- set true to enable Export.lua script, please is wrong. "EnableExportScript = false" only disables Global export. Local exports in export.lua are still possible. For that you need to do integrity checks on export.lua so that client uses a blank file With integrity checks you can turn off both.

yes. As I've always said LEAVU needs Local lua export. (LoGetMySpeed...etc) LEAVU does not need Global lua export (LoGetWorldObjects and LoGetObjectById) You can also see this in the source code of LEAVU in the links ive provided. The comments about global export that Case found in a file were old and are not valid since about 2-3 weeks back. In LOFC and FC1.12 the previous LEAVU required global exports by using the global function LoGetObjectById, this was due to an issue in FC 1.12 with exporting local radar data of F-15. This now a non-issue. ( The issue was it was only working for Ru birds ) If you write 5000 lines of code in a short time, then yuo will likely forget an old comment here and there. Thank you for telling me I have updated the source and removed these wrong comments.

LEAVU uses custom export.lua. if it doesnt have the modded export.lua then LEAVU does not work LEAVU export.lua looks like this function LuaExportStart() end function LuaExportBeforeNextFrame() end function LuaExportAfterNextFrame() end function LuaExportStop() end function LuaExportActivityNextEvent(t) local tNext = t return tNext end -- We need som basic math functions dofile("./Config/export/math_fcns.lua") -- Include the Eagle radar improvements dofile("./Config/export/ERI_fcns.lua") -- Include the LEAVU functions dofile("./Config/export/LEAVU_fcns.lua") All code is available for public viewing here : http://kenai.com/projects/leavu2/sources/subversion/show/LEAVU?rev=171

Youve got mail