Jump to content

[FIXED] The old ground stabilize issue is back


J20Stronk

Recommended Posts

Same issue appeared again after 2.5.6 update.

My Hardware: ROG Strix X570-F Gaming - AMD 5600X @ 4.7 ghz - G.SKILL TRIDENT 32GB DDR4 3200 (14-14-14-34 CL) - GigaByte 3080ti OC 12gb - Corsair MP600 Force 1TB - 2 x EVO Nvme 500GB - Virpil Warbird Base T-50CM2 and TM Throttle + Trackhat + G25 + AOC AG271QG 27"

My Modules: JF-17, F-16C, AV-8N/A, F-18C, ASJ37, MiG-15Bis, MiG-21Bis, Fw-190D, Bf-109K, P-51D, F-86F, Ka-50 III, UH-1H, Mi-8MTV2, NS430, FC3, A-10C, Mirage 2000C, L-39, F-5E-3, SA342, Spitfire, AH-64, Mirage F-1CE.

My Maps: Nevada, Normandy, Persian Gulf, Syria, South Atlantic.

Link to comment
Share on other sites

Is this issue WIP? Any news?

My Hardware: ROG Strix X570-F Gaming - AMD 5600X @ 4.7 ghz - G.SKILL TRIDENT 32GB DDR4 3200 (14-14-14-34 CL) - GigaByte 3080ti OC 12gb - Corsair MP600 Force 1TB - 2 x EVO Nvme 500GB - Virpil Warbird Base T-50CM2 and TM Throttle + Trackhat + G25 + AOC AG271QG 27"

My Modules: JF-17, F-16C, AV-8N/A, F-18C, ASJ37, MiG-15Bis, MiG-21Bis, Fw-190D, Bf-109K, P-51D, F-86F, Ka-50 III, UH-1H, Mi-8MTV2, NS430, FC3, A-10C, Mirage 2000C, L-39, F-5E-3, SA342, Spitfire, AH-64, Mirage F-1CE.

My Maps: Nevada, Normandy, Persian Gulf, Syria, South Atlantic.

Link to comment
Share on other sites

Excellent

My Hardware: ROG Strix X570-F Gaming - AMD 5600X @ 4.7 ghz - G.SKILL TRIDENT 32GB DDR4 3200 (14-14-14-34 CL) - GigaByte 3080ti OC 12gb - Corsair MP600 Force 1TB - 2 x EVO Nvme 500GB - Virpil Warbird Base T-50CM2 and TM Throttle + Trackhat + G25 + AOC AG271QG 27"

My Modules: JF-17, F-16C, AV-8N/A, F-18C, ASJ37, MiG-15Bis, MiG-21Bis, Fw-190D, Bf-109K, P-51D, F-86F, Ka-50 III, UH-1H, Mi-8MTV2, NS430, FC3, A-10C, Mirage 2000C, L-39, F-5E-3, SA342, Spitfire, AH-64, Mirage F-1CE.

My Maps: Nevada, Normandy, Persian Gulf, Syria, South Atlantic.

Link to comment
Share on other sites

  • 2 weeks later...

I'd like to report that as of the March 20th patch, STT also has a similar issue where it didn't before.

 

Rolling violentely and rolling inverted will break lock, but the RDR page does not show the target moving off screen.

 

Before 20/3/2020, STT actually behaved correctly; the target moved along the screen as you turned different headings regardles of ownship attitude and roll/bank.


Edited by J20Stronk
Link to comment
Share on other sites

Very disappointed. Still unfixed!

My Hardware: ROG Strix X570-F Gaming - AMD 5600X @ 4.7 ghz - G.SKILL TRIDENT 32GB DDR4 3200 (14-14-14-34 CL) - GigaByte 3080ti OC 12gb - Corsair MP600 Force 1TB - 2 x EVO Nvme 500GB - Virpil Warbird Base T-50CM2 and TM Throttle + Trackhat + G25 + AOC AG271QG 27"

My Modules: JF-17, F-16C, AV-8N/A, F-18C, ASJ37, MiG-15Bis, MiG-21Bis, Fw-190D, Bf-109K, P-51D, F-86F, Ka-50 III, UH-1H, Mi-8MTV2, NS430, FC3, A-10C, Mirage 2000C, L-39, F-5E-3, SA342, Spitfire, AH-64, Mirage F-1CE.

My Maps: Nevada, Normandy, Persian Gulf, Syria, South Atlantic.

Link to comment
Share on other sites

I'd like to report that as of the March 20th patch, STT also has a similar issue where it didn't before.

 

Rolling violentely and rolling inverted will break lock, but the RDR page does not show the target moving off screen.

 

Before 20/3/2020, STT actually behaved correctly; the target moved along the screen as you turned different headings regardles of ownship attitude and roll/bank.

 

I’m not so sure it only started a couple days ago, I do a lot of BFM and have had trouble maintaining a lock right on someone’s six for a couple weeks. I always thought it had to do with elevation or stabilization bug so I wasn’t going to report anything until those were fixed but maybe that’s not what is causing it.

Black Shark Den Squadron Member: We are open to new recruits, click here to check us out or apply to join! https://blacksharkden.com

E3FFFC01-584A-411C-8AFB-B02A23157EB6.jpeg

Link to comment
Share on other sites

Very disappointed. Still unfixed!

 

 

FYI: Recently DEKA's radar programmer was able to continue his work on the radar bugs and I believe someone from DEKA group (uboats?) stated last week that the radar was more or less fixed internally and that it was under testing. And it is a good thing that DEKA does actually test these changes instead of rolling them out in a hurried patch. And that is also why the recent changes did not make it into the last patch. I am sure we can safely assume to see the radar issues getting fixed next patch, though. And on top of that DEKA even stated they will be implementing new and more refined features for the KLJ-7 concerning notching and target lost behavior. Good stuff if you ask me...:music_whistling:

Link to comment
Share on other sites

Hope so

My Hardware: ROG Strix X570-F Gaming - AMD 5600X @ 4.7 ghz - G.SKILL TRIDENT 32GB DDR4 3200 (14-14-14-34 CL) - GigaByte 3080ti OC 12gb - Corsair MP600 Force 1TB - 2 x EVO Nvme 500GB - Virpil Warbird Base T-50CM2 and TM Throttle + Trackhat + G25 + AOC AG271QG 27"

My Modules: JF-17, F-16C, AV-8N/A, F-18C, ASJ37, MiG-15Bis, MiG-21Bis, Fw-190D, Bf-109K, P-51D, F-86F, Ka-50 III, UH-1H, Mi-8MTV2, NS430, FC3, A-10C, Mirage 2000C, L-39, F-5E-3, SA342, Spitfire, AH-64, Mirage F-1CE.

My Maps: Nevada, Normandy, Persian Gulf, Syria, South Atlantic.

Link to comment
Share on other sites

It's getting better now, but we need tester team comfirm it's OK for publish.

 

I can help with testing

My Hardware: ROG Strix X570-F Gaming - AMD 5600X @ 4.7 ghz - G.SKILL TRIDENT 32GB DDR4 3200 (14-14-14-34 CL) - GigaByte 3080ti OC 12gb - Corsair MP600 Force 1TB - 2 x EVO Nvme 500GB - Virpil Warbird Base T-50CM2 and TM Throttle + Trackhat + G25 + AOC AG271QG 27"

My Modules: JF-17, F-16C, AV-8N/A, F-18C, ASJ37, MiG-15Bis, MiG-21Bis, Fw-190D, Bf-109K, P-51D, F-86F, Ka-50 III, UH-1H, Mi-8MTV2, NS430, FC3, A-10C, Mirage 2000C, L-39, F-5E-3, SA342, Spitfire, AH-64, Mirage F-1CE.

My Maps: Nevada, Normandy, Persian Gulf, Syria, South Atlantic.

Link to comment
Share on other sites

what do u mean ??

 

u need a Test team or u already have and waiting them to replay if its working or not ?

 

 

 

 

I think he is referring to DEKA's internal tester team to give him a thumbs up.

 

But if DEKA is need of more testers I would also happily offer my assitance.

Link to comment
Share on other sites

why the title still WIP i think they said that they fix it and we will wait for next update right ??

 

 

DEKA did indeed provide a fix with the last OB update. It made the radar useable again but radar mechanics are still not "perfect" at the moment and that is why they chose to label this whole topic as WIP. DEKA told the community that they are still working on the proper integration of the notch filter, for example. They are definitely on the right track. And from what I personally saw on some servers in the last few days the elevation issue is not fully fixed, either. For example, the cursor elevation might show rather interesting (negative) values after unlocking a target or a target moving away from you is nearly impossible to lock in MED PRF. I also found that targets very close to you with a rather large altitude differential are nearly impossible to lock or even be detected although being still in the gimbal limits of the radar and elevation settings correct. So, there are definitely still some issues to address.

 

 

I understand we will see further improvements with the next OB update that might eliminate most of the inconsistencies we are still seeing. Remember, this is a very complex topic and these things take their time. I am confident, though, DEKA will fix these issues in the next few updates. Fingers crossed...:P


Edited by Tango3B
Link to comment
Share on other sites

DEKA did indeed provide a fix with the last OB update. It made the radar useable again but radar mechanics are still not "perfect" at the moment and that is why they chose to label this whole topic as WIP. DEKA told the community that they are still working on the proper integration of the notch filter, for example. They are definitely on the right track. And from what I personally saw on some servers in the last few days the elevation issue is not fully fixed, either. For example, the cursor elevation might show rather interesting (negative) values after unlocking a target or a target moving away from you is nearly impossible to lock in MED PRF. I also found that targets very close to you with a rather large altitude differential are nearly impossible to lock or even be detected although being still in the gimbal limits of the radar and elevation settings correct. So, there are definitely still some issues to address.

 

 

I understand we will see further improvements with the next OB update that might eliminate most of the inconsistencies we are still seeing. Remember, this is a very complex topic and these things take their time. I am confident, though, DEKA will fix these issues in the next few updates. Fingers crossed...:P

 

u are absolutely right i start to think that i am the one who can't use radar cuz everytime i face close target i am dead he can lock me and i am struggling and can't see him on my radarscope and PL-5 dont track targets that was very weird in a situation of 8km he go straight did u know that i forced to change to SD-10 and kill him in 5KM i am impressed of how SD-10 can maneuver in this distance

Link to comment
Share on other sites

u are right i should but vertical scan wont pick anyone flying around 20KM there is a certin range if u didn't lock him before it 50/50 u will see him in radarscope otherwise nope he will force u to stay in defense unless a friendly force him to defend so u can recommit and sometimes as i said before PL-5 fly in a straight line even if u have lock


Edited by Chiron
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...