RvEYoda

So then it wont piss you off if I implement mathematical ECCM that is 5 nm accurate from 150 nm out? I think you are just looking for things that allow you to say "Yoda's work is baaaaad, it must burn, burn the Witch!, Burn her!"

Like i said range estimation from triangulation is impossible if you are flying parallell to your target. In ALL other cases it works. The longer the range and more perpendicular flight paths the better ;).

Sure I can. With 2 sides I can pick the third freely. also http://en.wikipedia.org/wiki/Limit_(mathematics) Jokes aside, and knowing that the target is not mach 5 and knowing where I am going is more than enough to give a rough estimate of target position.

No it is not. it gives a very good estimate unless you keep flying straight at the target. A simple way would be to make a barrel rolling motion, and within a few seconds you will know the target range with decent accuracy. (Enough accuracy to determine if he is a threat or not)

If the taret is heading straight towards you or straight away from you your estimation will be super accurate. If he is moving similar to you(no bearing change), then you get problems.(but in that case you can filter out good headings vs bad very easily)

Wrong. You can triangulate with one radar, to keep it VERY simple: Just take a few snapshot from different posiitons and angles, and make some assumptions about the target, such as his speed (perhaps 0), and you will get a decent estimate even vs supersonic targets. This is how the real thing works, just a LOT more advanced. I could implement such a triangulation, but it would probably be so accurate that everybody would think "cheaeeeeeeeeat", thus I implemented a much weaker variant

Yep, all such scripts have to be inside the export.lua environment. (exporting data and sending input commands)

All my scripts for fc2 use only instrument data. You can do a search for "LoGetObjectById" or "LoGetWorldObjects" in all my scripts and you will find zero. The only reason why they did not do this in fc1 was because in fc1 many of the game's instrument exports were broken/buggy, so I was forced to use non-local data as a workaround.

Ingame EWR can transmit data updates even if the receiver is covered by a hill. It only does LOS checks on the actual radar, NOT the datalink. Leavu is the same. Radar is LOS checked, datalink is not.

I don't have to know the time of its scan. Data shred over leavu is _identical_ with what you see on your own radar. If you got target STT, then leavu shares STT data. If you got target scan rws, leavu shares scan rws data. scanning 4B 6A RWS yields at best one update every 4 seconds. STT yields at best whatever you set the datalink server to distribute data at.

- LEAVU datalink update rate is NOT 50 ms, it is whatever you want it to be. - Provide me with a source saying that 50 ms is incorrect for RL datalink (for example say "our friend pilot claims...") - Old school F-16 dlink reconenct at 8s intervals and update faster (prob 1/s or less) - Leavu doesn't need "reconnect" and update rate is 2-4 times per second with default settings. - Ingame GCI/EWR/AWACS sees "everything", with Leavu someone has to fly out there and use his radar - Leavu does the same. If you lock a bandit STT you can provide faster updates to your wingmen (since you know more) compared to tracking him 4B 6A RWS

I have suggested this numerous times in relation to leavu/eri/etc. Someone with good luagui knowledge could probably integrate this with the ingame server browser. Unfortunately i have nowhere near that kind of knowledge. The downside is that people can export scripts that read stuff off your harddrive and send to a host over network socket: the primary reason why export.lua can no longer be exported automatically/invisibly in fc2.

If you look in /Config/graphics.cfg for OldLandNoise { perSquare = 5; perSquare2 = 150; front = 1000; back = 10000; top = 2500; map_high = 20000; bottom = 2000; noisemax = 0.5; noisemin = 0.1; } and change it to OldLandNoise { perSquare = 5; perSquare2 = 150; front = 1000; back = [color="Red"]30000[/color]; top = 2500; map_high = 20000; bottom = 2000; noisemax = 0.5; noisemin = 0.1; } Does it help? It was like this for me too, please let me know if it helps

*Placeholder*

Definitely a bug in the game's export, not a bug in tacview. I've reported it on the internal bug system. Now we can just pray :P I used this script to log function LuaExportActivityNextEvent(t) local tNext = t local o = LoGetWorldObjects() for k,v in pairs(o) do n = n+1; logText("\n"); if v.Name then logText(v.Name); end logText(" | "); if v.UnitName then logText(v.UnitName); end logText(" | "); if v.GroupName then logText(v.GroupName); end end logText("\n"); logText("\n"); tNext = tNext + 1.0 return tNext end It returned: F-15C | Blue F-15-5 | Blue F-15-5 But should probably have returned: Maverick | F-15C | Blue F-15-5 Track was taken from 104th server

I dont have an HSI, only an mfd HSD page, but yes, just click add two times.

for me it gives major performance improvements and lower ingame stutters.

I'd like to separate these two crashes, I think they are caused by separate issues. There is another thread for the weapon cycle bug I believe.

cant, in windowed mode i get very low fps, input delays and vsync is always on :(

Just had the same crash again, Just like AS says when trying to lock a jammer.

I have had the same problem many times,sometimes when locking new targets a2g, sometimes when changing weapon, always like AS above Below is the crash log from one of my crashes # -------------- 20100330-143952 -------------- I:\...\UserInterface.dll # C0000005 ACCESS_VIOLATION at 021A8AB9 01:00037AB9 # # EAX = 00000000 # EBX = 00000004 # ECX = 00000000 # EDX = 00000007 # ESI = 3A5C81D0 # EDI = FFFFFFFF # CS:EIP = 001B:021A8AB9 # SS:ESP = 0023:0012FB10 EBP = 00000000 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00210246 021A8AB9 00000000 0001:00037AB9 I:\...\UserInterface.dll ?changeSelectedItem@MultiColumnListBox@@QAEXHHH@Z()+79 Is anyone else getting this? (Check the .crash filers in /Temp/)

would be a lot of for work someone to implement more instruments. I currently don't have the time, way too much work. yes with datalink you can play many people together and see each other. For other AC it might display wierd stuff, the navigation(HSD) screen on the MFD probably works but I suggest not trying anything else. The MFD instrument was basically made for the F-15. The ADI (test instrument) works for any aircraft. The HUD is just a test, it does not display anything, just a black screen

In a later version probably. Right now I'm happy it works without crashing :). Will work on preset/saved settings when I get time.

Go into 'LEAVU_fcns.lua' and set 'g_netUpdateDt' to 0 Maybe your laptop is having problem with the OpenGL graphics? Can you test what FPS (fraps) leavu runs at without being connected? (should be 10 fps without connection)

The data sampling rate of leavu is the same as your ingame fps, but currently capped at about 30-50 fps (you can unlock this yourself). I am running it myself around 30 fps for leavu and also have it on my laptop. You find it lagging? Are you using some wireless connection for it? What is your ingame fps? Your leavu screen should look virtually indistinguishable from the game, even if running on a separate computer. What s the performance of your laptop?