Jump to content

Onni

Recommended Posts

The new update seemed to make the radar so much worse

Cant find a target even 30miles out eventhough I know the altitude, am I missing something or is this a bug?

Several other people were complaining about it on the GS server aswell.

Link to comment
Share on other sites

Yes the Radar is kinda messed right now. Doesn't show donors' tracks from friendly planes and AWACS on ATTK RDR. Also, I noticed that looks break too easily, even when target is how without changing direction or altitude. 

- Hardware: i7 13700K || RTX 4090 || 64Gb DDR5 6000MT/s || 2Tb NVMe || 3440X1440 || Virpil Constellation Alpha Prime || Virpil Wrbrd Base || Virpil T-50CM3 || Winwing PTO 2 || Winwing MIP w/o UFC || Track IR

- Fixed Wing Modules: F/A-18C, F-16C, F-15E, F-14, M-2000C, JF-17, AV-8B, F-5E, A-10CII, Flaming Cliffs.

- Rotary Wing Modules: UH-1H, AH-64D, SA342

- Terrains: Marianas, Nevada, Persian Gulf, Syria

Link to comment
Share on other sites

Can confirm. Easy test: Start up the "Fighter Sweep" Mission. Radar is unable to pick up enemy fighters until they are within 20-30miles. The SA6 was already launching at me close to WP3 before I even got any contacts on the radar. Before the patch, one was easily able to pick up the bandits after take off from the carrier. Now I am almost in visual range and still no contact... 

Was on BlueFlag MP server before and wondered why the F16 have their way with me. F18 radar has serious problems seeing targets and looses track easily. :( 

Link to comment
Share on other sites

Before the Update you could find people a bit outside your Radar Elevation, that is now gone. you can only see them if they are strictly within your Elevation. I don't know if it's intended like that or not. The Radar no longer locks up during F poles which is nice, but it has become quite annoying, a couple of times now i had a hard Time maintaining a lock on Helicopters at rougly 20 miles distance, also a couple of times i could not find cold fighters in front of me (10-15nm range) with the Radar, even though i knew they were there through SA aswell as GCI.

Ohh and the Fighters were f16s, as far a i know they don't have a jammer, correct me if im wrong

 

Link to comment
Share on other sites

Quote

And I have experienced weird range jumps and unusable locks with target that are 20-30 Nm but said to be 99+Nm by the radar. Had to unlock, relock many times before having a correct launching cue. Weird and annoying, cannot use the Hornet anymore on MP PVP servers as I'm a sitting duck right now.

As it turns out, it seems that's a feature due to jammers...


Edited by Arnaud
Link to comment
Share on other sites

Yep, several new bugs have appeared in AA radar.

 

Pic attached is "fake" priority trackfile which sometimes appears. Notice how cursor was placed on it, but HAFU doesnt replace the cross (because its not a real trackfile). They sometimes appear in Dugout too.

 

xvxcvxvcv.png


Edited by dorianR666

CPU: AMD Ryzen 5 1600X

GPU: AMD RX 580

Link to comment
Share on other sites

I just spent some time A/B'ing the release version (2.5.6.59625.1) and the current open beta (2.5.6.60720) and air radar contacts are definitely a lot more slippery in the beta.

 

I set up a test mission with 4 Su-27s at 10/20/30/40 miles off my nose, co-altitude.  They were set to just orbit their starting waypoints.  I was in active pause.  I'm not sure if this affects anything so I ran a couple tests w/o active pause and didn't notice any real differences.

 

With the release version, all 4 contacts were solid all the way up until the notch and then they'd reappear after the Flankers were no longer beaming me.  I'd lose 1 or 2 a few times but for the most part, radar contact was pretty consistent.


With the beta version, I had a very difficult time maintaining radar contact with all 4 Flankers.  The worst part was that different contacts were dropped at different times for no apparent reason.  It could be the 40-mile contact heading away from me or the 10-mile contact heading right at me.  It seemed random.  I ran the test multiple times, moving my scan center around and altering PRF but could not find a way to achieve the consistency seen with the release version.  I wondered if the Flankers had some magic ECM enabled so I modified the test to use MiG-15s, assuming they had no ECM.  Same results.  I then tried with 4 Il-76s and then saw behavior closer to the release version, but still not quite as consistent.  So now I'm wondering if something was changed with the Hornet's radar, RCS profiles, or both.

 

Perhaps the new AA radar behavior is a reflection of the Real Life (TM) Hornet but it could also be something that needs fixing.  I'm ok with either, but the uncertainty is what kills it for OCD me.  I'm going to be using the release version for now and dip into the beta to check out the new features every now and then.  Not a big deal, that's why it's called a beta.

Link to comment
Share on other sites

The last OB messed up with the Hornet radar so much is barely unplayable in GS right now. The TWS Auto simply can't be used, the targets disappear in front your eyes on radar and Data Link.

Computer: Potato

Modules: FC3 | M2000C | A/V8B | Viggen | F-5E | F-14B | F-16C | F/A-18 | A-10C | Supercarrier :mad::mad: | UH-1 | MI-8 | Gazelle | KA-50

Link to comment
Share on other sites

I took the time to setup a couple of missions and the results are inconclusive.  Also, I was incorrect in my previous post.  In my previous tests, I was not co-altitude with the targets, but above.  That makes a significant difference I think when it comes to Doppler notching.

 

I set up 3 tests:

- co-altitude over water at 18,000 ft

- co-altitude over land at 18,000 ft

- differential altitude over land, me at 18,000 ft and Flankers at 12,000 ft

 

I used AA master mode, TWS with a 4-bar/40-deg scan using interleaved PRF.  I kept it in manual and tried to keep the scan centered of the group of 4 contacts.  In all co-altitude tests, my results were practically identical.  No glaring differences.  In my overland tests with differential altitudes, I had mixed results.  It seemed that the beta would have a hard time reacquiring contacts after they stopped beaming but so did the release version occasionally.  The behavior seen in the beta could be seen in the release version every now and then.  However, I could not get the beta to reacquire the contacts quite as reliably as in the release.  That said, the differences were minimal and could be accounted for another factor in my admittedly poorly-controlled experiment.  Tracks attached of some differential overland tests for anyone interested.  The big difference can be seen after the headings of the Flankers swing through 90 degrees and come out of my notch.  I've also run this mission multiple times using active pause and time acceleration to see contact acquisition behavior.  In those tests, it was harder to see differences between the release and beta versions.

 

I might do some more testing later if I get some time.  I'd also be interested in seeing tracks of those reporting that they are seeing a definite problem.

Tracks.zip

Link to comment
Share on other sites

Honestly don't know how this was not picked up immediately upon testing the update prior to release...I'll leave that for another conversations. Radar is basically borked. Are we looking  at at least another month before we can use the Hornet in air-to air engagements or we looking at a hotfix?

  • Like 2

Asus ROG Maximus X Apex//Core I7 8700K @ 5.3Ghz //32GB DDR4 RAM//Asus 3090 RTX//4K monitor w/ TrackIR 5

 

 

 

Link to comment
Share on other sites

  • ED Team

Moved to main discussion,

 

the issue is reported, as soon as I have any news I will let you all know. 

 

thanks

  • Like 1

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

  • ED Team

Hi,

 

the issue with contacts not showing when the scale is changed from 160 to 80 is reported. 

 

thanks

  • Thanks 1

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

Update from my previous post. I appeared to be one of the few that didn't observe the subject radar performance anomalies, so I went back for more data with a more careful eye. TWS behavior appears largely okay, but the L&S track does drop more frequently now when in RWS/LTWS. I spend most of my time in TWS so I didn't really notice it at first.

Nevertheless, I think folks in this thread are definitely on to something and it's important for the ED team to check it out.

Thanks for the update, BN!

Link to comment
Share on other sites

So sad that updates or fixes are breaking down so often what was already done in A/A radar. 

While focus is on less essential A/G radar (is so with use of modern ordinance and pod) I could only wish the A/A part could at least be somewhat on spot and bug free. That's a bigger priority TBH...

 

(sorry if it looks like ranting, not my usual doing normaly) 

 

Rig: MB Gigabite z390UD, CPU Intel I7 8700k, RAM 32G DDR4 3200 Gskill ripjaws, GPU MSI RTX2080SuperOC, HDD Crucial mx500 1tb M2 sata, PSU Corsair 850W, watercooling Corsair h100,

 

Controlers TM f/a 18 stick on Virpil warbrd base, TM cougar f16 stick on cougar base, Cougar F16 throttle on TUSBA, ch pedals, TM cougar MFD

 

27" monitor with trk IR 5 and HP Reverb HMD.

 

 

Modules F18, F16, F86, Mig15, FW 190D9, Nellis range map, Aggr campaign, Middle East map

Link to comment
Share on other sites

  • ED Team

Even though the Hornet has been out a while, it still remains an active development module in early access, these things can be expected during that period. We try our best to make sure these things done happen, but the more complex the Hornet gets, the easier for something to slip through. Thanks.

  • Like 2

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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