Geraki Posted November 15, 2020 Posted November 15, 2020 In FCR RWS or TWS when you have radar contact history symbols when you put the cursor above it, must not display the contact altitude , The altitude must displayied in the FIRST solid square contact and not in History. Imagine having 4 contacts in close formation with all History squares displayed the altitude when touched my cursor. it will mess up the SA. Only in the first and "Bolded" square contact, the cursor gives the altitude data and not for contact history.
Florence201 Posted November 15, 2020 Posted November 15, 2020 Iirc, you shouldn’t get history displayed in TWS, unless contact maneuvers. The computer predicts where the radar contact should be [sIGPIC][/sIGPIC]
Frederf Posted November 15, 2020 Posted November 15, 2020 Been meaning to report this. RWS contacts show up to 4 contacts with increasing visual fade for previous contact detections. In DCS all of the contacts, faded history and most recent, are showing the altitude number when only contacts detected in the latest sweep should (i.e. 100% brightness). If TWS has this kind of display possibility regarding contacts the same logic applies, no altitude numbers for history.
ED Team NineLine Posted November 16, 2020 ED Team Posted November 16, 2020 Hey guys, please include a short concise track, and I can look into it. Thanks. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
Geraki Posted November 17, 2020 Author Posted November 17, 2020 Here I attach some screenshots in EXP and Normal mode. As you can see when the cursor is above history contact it's getting the altitude number multiple times, this is wrong the altitude num is available only in the first solid contact. Regards
Frederf Posted November 17, 2020 Posted November 17, 2020 Faded history contacts are working a little funny for other reasons but currently if a single object has generated a series of faded and non-faded contacts then cursor over any of them causes altitude numbers to appear under all of them. Track provided. A slightly related issue is that the histories are being managed oddly. I was able to generate 12 concurrent symbols on the display from a single airborne object which should be impossible. The contact brightness schedule seems to be a function of raw time and not event-based as a function of completed frames. For short duration frames many frames can occur before the oldest contact has a chance to expire. APG-68 operates differently than F-18 radar which is time-based and not frame-based. Early APG-68 demote contacts to the next history brightness simultaneously at end of frame. Everything detected in current frame is all current frame brightness and then at the beginning of the next frame (extreme point in azimuth for final bar) everything dims/disappears and the new frame begins. That does have the potential for a contact at the end of a frame to be almost immediately demoted when the next frame begins. I don't know if there's some minimum duration to prevent this or what. It may be possible that later -68 update history on a rolling frame basis, e.g. a contact discovered on bar 3, 34° right won't demote to the next faded level until bar 3, 34° right of the next frame. That's definitely a question for an SME.F16 RWS History Alt.trk
Recommended Posts