|
|
Post by volkerboehme on Apr 18, 2010 13:17:10 GMT -5
Hi all,
we have just uploaded an upgrade for the Lockheed EC-121 Warning Star Airborne Early Warning (AEW) aircraft, originally released by Manfred Jahn and Team 1049 about a year ago. It should be available from Flightsim.Com tomorrow.
This upgrade adds a working radar system to the AEW aircraft. This radar is able to detect AI traffic in real-time as well as taking bearings and distance measurements of individual contacts. Terrain is displayed as well, maximum range is 240 nm. Traffic is detected to some 80 nm, which seems to be a FS limit. While not tested yet, it should also be able to detect multiplayer aircraft.
Best regards,
Team 1049: Volker Böhme, Luis Pallas, Bill Tyne and Stefan Werner
|
|
|
|
Post by tcreed on Apr 18, 2010 18:16:09 GMT -5
Volker...in addition to the 1049 fde upgrade, just super, thanks to all involved..!!
brgds
t creed
|
|
|
|
Post by volkerboehme on Apr 19, 2010 10:34:22 GMT -5
Hi all,
it's up at Flighsim by now. Seems like they wanted to be nice and supplied a download link to the base pack as well. However, the file referenced is a upgrade as well. The base pack needed is "wv2-1.zip".
Best regards,
Volker
|
|
|
|
Post by Connie Flyer on Apr 19, 2010 16:46:25 GMT -5
Thanks for the credit line Volker, this looks great!
|
|
|
|
Post by okami on Apr 20, 2010 11:53:23 GMT -5
Just noticed something odd on a "patrol flight" - I just completed a flight from LFPO to EGKK (Paris Orly to London Gatwick). Somewhere halfway the channel, my radar suddenly refused to display traffic. Could it be that there's a limit to the amount of plots the radar can display? UK airspace can be a bit busy with Heathrow and Gatwick in close proximity...
Regards,
Nikko.
|
|
|
|
Post by volkerboehme on Apr 20, 2010 14:21:49 GMT -5
Hi,
never experienced that before myself. Maybe try to reduce traffic density or range and try again?
Best regards,
Volker
|
|
|
|
Post by okami on Apr 20, 2010 15:07:01 GMT -5
Hi, never experienced that before myself. Maybe try to reduce traffic density or range and try again? Best regards, Volker I tried reducing the range, but it gave no effect. I also tried it by switching the radar off and on again, but that gave no effect either. I even put on the traffic labels, as I thought for a moment it was a traffic failure in FS9 itself (such a failure preceded the crash of my previous computer), but it turned out there were a number of aircraft in the immediate vicinity, so it wasn't that. The only thing I didn't try was reduce the traffic density, though. If the failure occurs again, I'll try that. I hope it doesn't, though. |
|
|
|
Post by Defender on Apr 20, 2010 15:11:03 GMT -5
Hi Nikko,
I did quite a lot of testing around the LAX area and never had a problem. Difficult to know how to test your experience but just now I'm over the English Channel at 100% AI and I've got 22 AI targets on the screen and no problems. How does that compare with your numbers? Are you using GA AI as well? I never bother with GA aircraft.
Our team will also be interested to learn that I've got one target at 98 miles and another at 84. We never got any above 80 miles in testing.
By the way, the targets will disappear on "pause". Perhaps there are other functions that have that result?
Best regards
Bill
|
|
|
|
Post by okami on Apr 20, 2010 15:54:36 GMT -5
Hi Bill, Well, I usually fly with traffic and GA at 100%, so maybe there's something in that. I noticed another weird thing, though: there seems to be a bit of a blind spot on the radar at approximately 207° and 58.5 miles aft of the aircraft - during my test flight I saw plots partially disappear at this location. Unfortunately I forgot to take a screenshot of them actually disappearing, but I marked the position with my green bearing on the screenshot below. As to distance, I noticed some odd results there as well. While 80 nm is given as a top range, I just did a second test flight, and spotted one target at 90+ nm, as you will see below (yellow bearing)....  Regards, Nikko |
|
|
|
Post by Tom/CalClassic on Apr 20, 2010 16:30:06 GMT -5
Hi,
I think the range is actually around 110 NM, the distance FS loads AI traffic?
|
|
|
|
Post by Defender on Apr 20, 2010 16:38:29 GMT -5
Hi Nikko,
I've just done another test out of curiosity and probably the ultimate test area, orbiting around Philadelphia with NY and Baltimore/Washington well within range.
Well I actually got a target at 119 miles but with 30+ targets on the screen at say 120 mile range setting I found that an entire group of two or three targets (but certainly not all) would suddenly disappear at the middle ranges and immediately get replaced by another little group well inside the 120 miles. That suggests capacity. I also got a screen freeze at one point with around 34 targets.
I wonder whether it's a video card issue rather than FS? I think our advice meantime is to reduce traffic density in busy areas as Volker suggests.
Bill
|
|
|
|
Post by okami on Apr 20, 2010 17:04:03 GMT -5
Personally, I don't think it's the video card. I managed to finish my flight - well over half an hour after my radar failed - while my computer had no problems at displaying the scenery or traffic at any point after the failure. Perhaps it is some odd quirk in the radar module, after all it is the one unknown factor in the whole equation.
|
|
|
|
Post by Defender on Apr 20, 2010 17:11:42 GMT -5
Tom, Just for the record here's a screenshot in case it never happens again! The target at the very bottom of the screen shows 119.4 miles in the tooltip. The tooltips by the way come with the optional "200" gauges listed in the panel.cfg Nikko, Thanks - I'll keep testing. Bill  |
|
|
|
Post by Tom/CalClassic on Apr 20, 2010 17:57:05 GMT -5
OK, it's 120 NM.  |
|
|
|
Post by riogrande on Apr 21, 2010 9:06:06 GMT -5
I'll bet it's that darn volcano again!  Marv |
|
