Pikey Posted December 23, 2018 Posted December 23, 2018 Linked to the ASL post I did, the BRA is never correct and in fact changes constantly depending on Azimuth setting. Tried both magnetic and true (although setting the HSI measurements to true actually only changes the heading tape and HSI rose compass, it doesn't change the final result. I've verified this by looking at the heading of the JHCMS whilst leaving the TDC over the contact, then cycling the Azimuth degree scan. The BRA will keep changing despite the contact never moving (or the TDC, you dont need a contact, but nice to verify that the contact in the JHCMS is not accurate either) Interestingly the Bullseye stays the same during this. I believe this is something to do with the zoom scaling of the radar scope. The Azimuth changes and the BRA would be correct if the Azimuth scan actually filled the entire scope width at the current AZ setting. However, for some reason the ASL seems to remain as the correct % of the full 140 degree scan, instead of zooming. I think if zooming is correct, then the radar hits should move outward like the bullseye marker does as if in a moving scenario. If the zooming is not correct then the BRA should refer to the absolute correct location as if not zoomed. ___________________________________________________________________________ SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *
Pikey Posted December 30, 2018 Author Posted December 30, 2018 Since i've seen other bugs reported over the time period I need to bump this. The BRA is simply bang out wrong and must be reported as a bug. ___________________________________________________________________________ SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *
Svend_Dellepude Posted December 31, 2018 Posted December 31, 2018 Looks a bit fishy. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.
Pikey Posted January 7, 2019 Author Posted January 7, 2019 It's plain broken. It reads all sorts of different angles depending on the AZ sweep selection. Pretty amazing that relatively speaking not a large amount of people care or notices actually, I guess this really is just a single player game after all! I can name more than 15 Hornet drivers right now that find it frustrating, annoying and desperately need a fix. ___________________________________________________________________________ SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *
Manuel_108 Posted January 8, 2019 Posted January 8, 2019 I find it annoying even in simple single player missions to be honest. I find myself always having to use 140 azimuth.
Pikey Posted January 17, 2019 Author Posted January 17, 2019 Still broken in the 16th Jan patch. ___________________________________________________________________________ SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *
BarTzi Posted January 25, 2019 Posted January 25, 2019 +1 What kind of track can help the devs the most here?
Deezle Posted January 25, 2019 Posted January 25, 2019 Took me about a minute to reproduce this and make a track.BRA.trk Intel 9600K@4.7GHz, Asus Z390, 64GB DDR4, EVGA RTX 3070, Custom Water Cooling, 970 EVO 1TB NVMe 34" UltraWide 3440x1440 Curved Monitor, 21" Touch Screen MFD monitor, TIR5 My Pit Build, Moza AB9 FFB w/WH Grip, TMWH Throttle, MFG Crosswinds W/Combat Pedals/Damper, Custom A-10C panels, Custom Helo Collective, SimShaker with Transducer
Manuel_108 Posted January 25, 2019 Posted January 25, 2019 Just loaded your track, looks just like Pikeys video and corresponds with what I see on my end as well.
Pikey Posted January 26, 2019 Author Posted January 26, 2019 Still broken in last hotfix as of time of posting. Disappointed that a trackfile is apparently required in order to get traction with the developers. This can be seen in seconds whilst looking at any Hornet radar whilst looking at other bugs. Steps to reproduce, change the azimuth and watch the BRA change angles without anything else. Nothing else required. Loading up a trackfile takes infinitely longer, a complete restart of DCS. I had hoped that providing a video showing the same thing took <30 seconds of effort and saved you a lot longer. ___________________________________________________________________________ SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *
david.lind Posted January 27, 2019 Posted January 27, 2019 This incorrect implementation is annoying.
Svend_Dellepude Posted January 27, 2019 Posted January 27, 2019 Relax guys. Just use 140° and all is good. It's WIP. There is a track now, so it's gonna be fixed sooner or later. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.
Ashilta Posted January 27, 2019 Posted January 27, 2019 I confirm I can reproduce this as well. Every damned time I fly. It's actually quite limiting and, I would imagine, not tricky to fix...
Recommended Posts