I'm really looking forward to this next update,was hoping for some kind of target return data for some vehicles/sams Not everything relies on CLOS or optical tracking or detection which can put a strain on my eyesight.I'm no programmer but a LUA script could return some data for bearing on detected aircraft,taking into account of aircraft ECM ect.
I tried making a trigger zone around the Osa9a33 to make an audio bleep once inside that zone,only thing that's missing is some kind of cue as to what direction?Whilst I get many hours of enjoyment from this sim,it is a flight sim not a sam sim,but would appreciate some extra targeting information for sam/standalone radar units.
In the following video it describes how an f16 was shot down by the sam operator turning the radar on and off,(next update) the detection range is aprox 65 km,but the way the sim is now you can't optically track something 65 km away,that's the reason I would appreciate some extra targeting info for units equipped with radar.
What do you think?would appreciate your thoughts on this,I mostly play with ground units not aircraft.
3 Samsung 27" LED Monitors powered by a Zotac 4GB 680GTX. Set at PCI Gen3. 5760 x 1080 resolution. MSI z68a-gd80 (g3) motherboard Ivy Bridge 3770k 3.5Ghz 32GB RAM (all .pbo's loaded into a 12GB RamDisk) TrackIR4 zboard merc keyboard Saitek X-52 stick/throttle/pedals Logitech MOMO racing wheel/pedals Razer Deathadder 3500 black mouse Sony receiver for 5.1 surround sound. 5 speakers and powered sub-woofer.
I'm sure Belsimtek loves all these delays, seeing as how revenue from their product is tied up in them...
My Rig:i5-3570k @ 4.2 GHZ W/ Corsair Hydro H110 Cooler / Asus Sabertooth Z77 Mobo / GTX 1070/ 16 Gigs DDR3 RAM / A Few SSDs, and a Bunch of HDDs / All held together by: Corsair C70 Case
Other Assets Deployed: HOTAS: Thrustmaster Warthog SN#22621/CH Throttle Quad/MFG Crosswind Pedals SN#0004 TrackIR TIR 5 w/ TrackClip Pro Simpit: Obutto R3VOLUTION
Yeah, i definitely feel for Belsimtek. Reading Wag's last update on the ED site, it seems that the delays are stemming from features that aren't related to UH-1 compatibility.
IMHO, ED should have limited the 1.2.4 patch to whatever was necessary to implement the Huey and whatever features were complete and stable by the time Belsimtek was ready to go, and then left the rest for another patch - even if that patch were to be only a few days or weeks behind.
It's a 16-page thread that is now locked. I've no issue with the pricing but like I've said many many times on this forum from almost every announcement they make......ED's communication is absolutely shocking, this is yet again another bad example.
The 'Subject to Change' disclaimer is starting to become a catchphrase.
How is saying "Subject to change" an example of their "Absolutely shocking communications"?
EVERY change log I've ever seen for an up coming patch, not just ED either, has included that "catchphrase". Would you rather have them hold up the patch for weeks if they ran into a problem and couldn't complete one of the listed items?
will this fix the smoke effect issue and shooting/dropping payload probs? 
