Sgt_Baker

This is normal behaviour. The TGP has much higher zoom than the Maverick's sensor. That grey blob you see in the crosshairs of the Mav display is indeed the car you have locked up, and is enough for the Mav to guide to its target. Incidentally the Maverick is usually able to lock and fire from a range of about 8nm.

Yep, that's right. If you mean the +/- it should probably say N/S. The trigonometric cosine function. So enter your latitude in decimal degrees, press cos and then multiply by 60 (for nautical miles, which is the easiest to remember for precisely this reason).

Which AV software? This happens from time to time. When I push 2.7.1 to release, 99.99% certain the false positive will go away. In the mean time, you might want to notify your AV software folk that it's a false positive. --Baker

Keep the UDP. UltraMFCD will be broadcasting a small "heartbeat" status message on UDP broadcast. You will be able to look at that message and decide whether you want to engage TCP to download a stream. It's designed to be stateless, so there's no complicated negotiation involved, no syncing of framerates, no complicated streaming media types... Calculator-grade. :)

Just to clarify: The streams would be available over LAN/WiFi via TCP/IP. No need for strange USB shenanigans. I don't want to touch anything to do with USB either.

There would be no merging of projects required. I'm making the streaming protocol so easy to consume that you could probably get it to work on a modern graphing calculator, let alone an Android/iOS device. :D I'm going ahead with early Alpha PC <-> PC streaming now, but if at any time in the future somebody wanted to include uMFCD streams in their app they'd already be available.

Just an FYI: I'm presently in the process of implementing network video streaming of UltraMFCD exports. The idea is that any network connected device/app etc can easily consume them with minimum fuss, so that could include Cockpit++ if you so desire.

Here's a handy table: Lat nm mi km +/- 0 60.00 69.05 111.12 1 59.99 69.04 111.10 2 59.96 69.00 111.05 3 59.92 68.95 110.97 4 59.85 68.88 110.85 5 59.77 68.78 110.70 6 59.67 68.67 110.51 7 59.55 68.53 110.29 8 59.42 68.37 110.04 9 59.26 68.20 109.75 10 59.09 68.00 109.43 11 58.90 67.78 109.08 12 58.69 67.54 108.69 13 58.46 67.28 108.27 14 58.22 67.00 107.82 15 57.96 66.69 107.33 16 57.68 66.37 106.82 17 57.38 66.03 106.26 18 57.06 65.67 105.68 19 56.73 65.29 105.07 20 56.38 64.88 104.42 21 56.01 64.46 103.74 22 55.63 64.02 103.03 23 55.23 63.56 102.29 24 54.81 63.08 101.51 25 54.38 62.58 100.71 26 53.93 62.06 99.87 27 53.46 61.52 99.01 28 52.98 60.96 98.11 29 52.48 60.39 97.19 30 51.96 59.80 96.23 31 51.43 59.18 95.25 32 50.88 58.56 94.24 33 50.32 57.91 93.19 34 49.74 57.24 92.12 35 49.15 56.56 91.02 36 48.54 55.86 89.90 37 47.92 55.14 88.74 38 47.28 54.41 87.56 39 46.63 53.66 86.36 40 45.96 52.89 85.12 41 45.28 52.11 83.86 42 44.59 51.31 82.58 43 43.88 50.50 81.27 44 43.16 49.67 79.93 45 42.43 48.82 78.57 46 41.68 47.96 77.19 47 40.92 47.09 75.78 48 40.15 46.20 74.35 49 39.36 45.30 72.90 50 38.57 44.38 71.43 51 37.76 43.45 69.93 52 36.94 42.51 68.41 53 36.11 41.55 66.87 54 35.27 40.58 65.31 55 34.41 39.60 63.74 56 33.55 38.61 62.14 57 32.68 37.61 60.52 58 31.80 36.59 58.88 59 30.90 35.56 57.23 60 30.00 34.52 55.56 61 29.09 33.47 53.87 62 28.17 32.42 52.17 63 27.24 31.35 50.45 64 26.30 30.27 48.71 65 25.36 29.18 46.96 66 24.40 28.08 45.20 67 23.44 26.98 43.42 68 22.48 25.87 41.63 69 21.50 24.74 39.82 70 20.52 23.62 38.01 71 19.53 22.48 36.18 72 18.54 21.34 34.34 73 17.54 20.19 32.49 74 16.54 19.03 30.63 75 15.53 17.87 28.76 76 14.52 16.70 26.88 77 13.50 15.53 25.00 78 12.47 14.36 23.10 79 11.45 13.17 21.20 80 10.42 11.99 19.30 81 9.39 10.80 17.38 82 8.35 9.61 15.46 83 7.31 8.41 13.54 84 6.27 7.22 11.62 85 5.23 6.02 9.68 86 4.19 4.82 7.75 87 3.14 3.61 5.82 88 2.09 2.41 3.88 89 1.05 1.21 1.94 90 .00 .00 .00

Degrees of latitude are always 60nm. Degrees on longitude are ~60nm at the equator and 0nm at the poles and can be calculated using the following formula: DegreeOfLonLength = Cos(Latitude) * 60 nm DegreeOfLonLength = Cos(Latitude) * 69.0468 miles DegreeOfLonLength = Cos(Latitude) * 111.12 km ...for nautical miles, miles and kilometres respectively. --Baker

Thanks! Feedback, both good and bad, is very important. :)

New UltraMFCD 2.7.1 Beta available here. Includes new dual kneeboards and other fixes. Changelog: NEW: Dual DCS and UltraMFCD kneeboards. NEW: Kneeboard exports available in all DCS modules, even when no other displays exported by UltraMFCD. NEW: UltraMFCD kneeboard displays updates from DCS Kneeboard Builder in real-time. No restart of flight required. FIXED/NEW: Fixed bug where DCS kneeboard would display inside other exports. DCS kneeboard now exported as a full UltraMFCD display. NEW: UltraMFCD plays a warning sound if it detects problematic settings upon DCS launch. FIXED: Bug where blank displays could remain on-screen from previously flown aircraft. FIXED: An UltraMFCD window, when clicked, will now move to the foreground as expected. FIXED: Circumstances where UltraMFCD displays might prevent DCS receiving keyboard/joystick input due to clicked UltraMFCD export window stealing focus from DCS. FIXED: Su-25T Shkval display now correctly remembers its position.

Yeah, I've already clarified that above. DCS 1.5.4 is the version of DCS prior to the unified EDGE builds between 1.5 and 2.1. Edit: Almost exactly one year old. Note the first post in this thread where I state "For DCS 1.5.5+" etc etc :)

Hang on a sec. Just spotted that you're still using DCS 1.5.4 (alarmingly easy to get number-blind in my line of work). UltraMFCD hasn't been compatible with DCS 1.5.4 or below for a good long while now. Any particular reason you're still using that version of DCS? --Baker

If you're experiencing crashes it might have something to do with the new "Deferred Shading" option in DCS. Try with/without and report back here so others can see.

In the next release: UltraMFCD & DCS Kneeboard Builder 100% compatible with each other. PLUS: Changes made to kneeboards while in flight will show up in the UltraMFCD kneeboard instantly. No need to restart the flight.

Hi uscstaylor, I'm 99% certain that the issue here is SweetFX. UltraMFCD and SweetFX have never got along well, and indeed it is something I've been intending to get around to fixing. Try disabling SweetFX completely and give uMFCD a go. Then, until the fix is implemented, I suppose it's a decision on your end as to which you want more. Incidentally, the Deferred Shading issue only concerns the latest DCS 2.1 Alpha, not DCS 1.5.4. --Baker

Update regarding DCS 2.1 Alpha Bad news and good-ish news. The bad news is that UltraMFCD crashes DCS when the "Deferred Shading" option is enabled. The good-ish news is that everything still works with Deferred Shading disabled, along with UltraMFCD already being prepped for dealing with new rendering stuff in DCS 2.x, so accommodating the new DCS rendering stuff might not take as long as it would otherwise. --Baker

Yes, that's already planned. Initially I thought of just cheating and implementing the F-15C TEWS for all FC3 aircraft, but that's... you know... a cheap and dirty trick and not in keeping with the rest of uMFCD. Principally this requires my spending some time flying around in said aircraft to familiarise myself with the operation of the Russian RWRs and any quirks they might exhibit. --Baker

For that matter, any chance we could do the same for the modified shader that enables colour LITENING?

Hi, In the course of the development of UltraMFCD I've recently fixed a long-standing bug where the DCS kneedboard would render over the top of other exported displays. Unfortunately the two lua files that I've modified are included in the multiplayer integrity check, so will cause said check to fail on certain MP servers. Is there any chance you could add the size/hash of the two modified files (which I can provide verbatim so you can ensure no "funny business" is taking place, of course) to the manifest check such that users can use UltraMFCD for its new kneeboard functionality on all MP servers? Best regards, Baker

Yeah, this could be some unexplored corner of our code bugging out. It's designed to work with absolutely any monitor setup/arrangement, yet clearly impossible to test every monitor/resolution/arrangement setup on this end. In these situations it helps to "start from the beginning", setting DCS to single-screen and the "1 monitor" setup, then turn things up until something goes wrong. Make a note of exactly what you did and let us know. :) --Baker

Looks like there's a colossal update to DCS 2.1. It would appear, from reading the changelog, that big changes have been made to the rendering engine. Downloading and running tests now...

The kneeboard fixes haven't been released yet. I'm also in communication with the developer of Kneeboardbuilder with a view to solving any issues regarding out respective apps' coexistence, which has been an issue in the past. --Baker

I apologise for the outburst. If, however, I don't implement this or that request within the next billion years.... so be it.

"If only you, Baker, could spend $60 and a load of time and effort on making my idea work?"