Jump to content

** UPDATE: Ground Radar 2.0 & Multiplayer Flight Planning **


Cobra847

Recommended Posts

Could you try the default radar settings with "Rocket Attack" mission? Also, could you check that you have no controller axis assigned to the radar gain axis? If you have an axis assigned, could you disable it for the test? It looks that your radar gain settings might have been very far from the default value.

 

The screenshots from the first post in this topic were taken in the default air start settings - LOG - with no more than two clicks on the gain used and without changing the antenna elevation.

Here they come. Nothing changed unless otherwise stated.

 

All settings default, radar gain on axis assignment max.

1355407705_AlldefaultRGonAxis.thumb.jpg.306e8c04c5406499a42a1a49f2ecf255.jpg

 

All settings default, radar gain not on axis assignment.

522198187_AlldefaultRGnotonAxis.thumb.jpg.0f404a6bac8e180f57e33716949acb83.jpg

 

All settings default except gain, on max with keys, radar gain not on axis assignment.

843414544_GainmaxRGnotonAxis.thumb.jpg.a5407bd4c696e8038395205524f182ff.jpg

 

All settings default, radar gain not on axis assignment, July same time of day and "summer clear sky no wind" weather preset.

1001388311_AlldefaultRGnotonAxisSummerCAVOK.thumb.jpg.7a28a0d7d261b2f71bf6f1cac243292c.jpg

 

On all above I had about 25 FPS while heads down on radar screen. I also tested to turn off the mirrors, increased FPS to around 35 but did not have any effect on the image. Turning to summer had basically the same effect as turning up the gain slightly, and also increased the FPS a bit.

All game settings and modification to the miz file was followed by a DCS restart.

 

 

LOG mode still not really usable in this situation while perfect in 1.5.7.

 

 

 

My conclusion on the Radar Gain with axis assignment problem is that I don't seem to have it? When I have it assigned to an axis my default gain is the same as if not assigned to an axis and tuned up with key commands. And my lowest gain axis setting result in a completely blank screen, same as for keys only.

 

Both missions I have used for the tests are attached.

 

 

I did test the "Rocket Attack" mission, same modification procedure as with Interdiction (filename explains it all):

1057748192_View10km@1500m1.5.7.thumb.jpg.5d8ff9d904306bc258973b77e8f8ded7.jpg

1812422247_Alldefault10km@1500m1.5.7.thumb.jpg.79266c768f7a1d75f654d61e5c094c2e.jpg

100836365_View10km@1500m2.5.3.thumb.jpg.989d47e5c4f1d08835ca1717c465a2e9.jpg

156062526_Alldefault10km@1500m2.5.3.thumb.jpg.25ea1b6d8b34bf70140468d292de0577.jpg

444235935_View5km@1000m1.5.7.thumb.jpg.762030226b509ac09f9ec32567457e40.jpg

1118314376_Alldefault5km@1000m1.5.7.thumb.jpg.56d34290bfc552249819ae62b73bb561.jpg

842721877_View5km@1000m2.5.3.thumb.jpg.a10ce6357c010237863bb3b7f8aa9e49.jpg

2026072273_Alldefault5km@1000m2.5.3.thumb.jpg.dd5138be05369ab45ddbd29dc2a182fa.jpg

The default seams to be usable here but more washed out than 1.5.7. The missions for 2.5.3 are attached.

 

 

 

 

EDIT:

When I talk about "usable" in this context, I refer to nav fix situations, not target acquisition.

Interdiction radar test.miz

Interdiction radar test summer CAVOK.miz

AJS-37 Rocket attack radar test.miz

AJS-37 Rocket attack radar test 10km.miz


Edited by Holton181

Helicopters and Viggen

DCS 1.5.7 and OpenBeta

Win7 Pro 64bit

i7-3820 3.60GHz

P9X79 Pro

32GB

GTX 670 2GB

VG278H + a Dell

PFT Lynx

TrackIR 5

Link to comment
Share on other sites

Great, now, your second radar image is very close to mine. So indeed your previous pictures were taken with very high gain settings.

I thought that was the issue - a very dark terrain - as it was very different from the screenshots everyone presented. However, now I believe that you might refer to the shape of the lake that was visible in 1.5.7 and now is gone. And it's all related to the interpolation algorithm used. Previously, the algorithm was very aggressive and tried to fill even very long gaps in the returned signal. Now, it's improved and should not present false information about the terrain when no information is available. Let me illustrate it with an example:

 

The view:

 

Interpolation_landscape.jpg

 

 

And the corresponding radar image, using both the old and the new algorithms:

InterpolationComparison.gif

 

 

There are more empty areas when using the new algorithm than when using the old algorithm, and those areas represent the invisible sides of the hills and ridges. This way you can properly interpret the rising terrain (darker shade), the ridges (the edges) and the regions which are invisible for the radar. Unfortunately, those obscured areas look very similar to water.

 

Back to your original testing spot. By coincidence, at that specific location, the old interpolation algorithm filled the gaps, recreating the shape of the lake on the radar display. It looked like the map of that region, but it was less realistic as the radar had no information about those points.

 

I hope that this explains the difference you observed. smilewink.gif

Regards


Edited by Super Grover

Krzysztof Sobczak

 

Heatblur Simulations

https://www.facebook.com/heatblur/

Link to comment
Share on other sites

...

Yes, I understand that the radar needs line of sight and should not give information about things behind obstacles. That part is much better, thanks. But my problem is different. If you look at the first picture in post #142, the ocular view (or whatever I should call it), you can see it has line of sight of that particular part of the lake I'm interested in, the beak straight below B3 and perfect for a radar fix (I'm not a native English speaker, "beak" is the best word I found for what we Sweeds call an "udde", that small land mas stretching out in the lake). When using LIN I do get a good picture (after some tricky, sensitive adjustments of the elevation using only buttons since no axis can be assigned), but in LOG it's basically impossible, especially for B-scope. You did get a return showing the beak in post #148 (but it was very washed out and hard to see), I guess it was maybe due to slightly different location/altitude than in my examples.

Now, I don't know enough about radars to say that this issue, if an issue at all, is wrong or realistic, it's just that I get the feeling that on this distance (10km), elevation difference (about 400m) and line of sight, a better and more clear picture in both LIN and LOG mode should be possible, with less hassle with the elevation (i.e. in a wider range).

Never since the introduction of DCS 2.x I have been able to use that B3 as a radar fix point while actually flying (no active pause), well in no mission actually, while in 1.5.x it is very easy. I do believe the Ground Radar 2.0 will make it better and easier overall, but I really looked forward to be able to use that B3 again... ;-)

Helicopters and Viggen

DCS 1.5.7 and OpenBeta

Win7 Pro 64bit

i7-3820 3.60GHz

P9X79 Pro

32GB

GTX 670 2GB

VG278H + a Dell

PFT Lynx

TrackIR 5

Link to comment
Share on other sites

Looking at the first picture in #142, I can see that new radar 2.0 representation is indeed more correct; you have some hills obscuring the radar LOS that are not shown in the old version. Just pay attention to the right side, there are hills whose radar Shadow is not existing in 1.5.7.

 

The problem is that hills' shadows and water bodies share same color which makes the picture somewhat confusing, but it's correct; water absorbs almost all radar energy so no return is detected.



Link to comment
Share on other sites

...

Yes I know that, but I'm not interested in the overall shape of the lake, only that landmass (wrong spelling before, sorry) below B3 going out in the lake, clearly visible for the pilot and in line of sight for the radar.

Helicopters and Viggen

DCS 1.5.7 and OpenBeta

Win7 Pro 64bit

i7-3820 3.60GHz

P9X79 Pro

32GB

GTX 670 2GB

VG278H + a Dell

PFT Lynx

TrackIR 5

Link to comment
Share on other sites

Looking at the first picture in #142, I can see that new radar 2.0 representation is indeed more correct; you have some hills obscuring the radar LOS that are not shown in the old version. Just pay attention to the right side, there are hills whose radar Shadow is not existing in 1.5.7.

 

The problem is that hills' shadows and water bodies share same color which makes the picture somewhat confusing, but it's correct; water absorbs almost all radar energy so no return is detected.

 

Actually at shallow angles water reflects almost all waves in the forward direction. There is some backscatter which is not very pronounced compared to hills etc. For radio waves to be absorbed you have to transmit at very steep angles, which typically do not happen in a low flying Viggen. The conclusion does not change though.

Link to comment
Share on other sites

Thank you very much heatblur! I tested it yesterday and I'm really pleased with the results, now it behaves how it should! Impact on fps is minimal, if any. I know praise and encourage are important for you, so I wanted to spend some minutes to leave my positive feedback! :)

 

Thank you! :)

Nicholas Dackard

 

Founder & Lead Artist

Heatblur Simulations

 

https://www.facebook.com/heatblur/

Link to comment
Share on other sites

Thanks for the update, awesome stuff. Couple things I picked up when reading the patch notes:

 

Interior engine sounds now loop properly

 

It seems better - but there is still a noticeable 'pause' when the throttle is at just below stage 1 afterburner.

 

Fixed RAT projecting through intake on left side of fuselage

 

I dunno what it is but there's still something poking thru in my left intake.

 

Small things - but I'd thought I'd point them out anyways. Keep up the good work :thumbup:

vig_2.thumb.jpg.0e119eff312ea656d30e057e155f3946.jpg

A-10C Warthog | AJS-37 Viggen | F-5E Tiger II | Mig-15bis | MiG-19P Farmer

Link to comment
Share on other sites

As a real life Airborne sensor operator I am really impressed with wath you have done with the radar. Bought the Tomcat and I am honestly really close to buy the Viggen now.

 

 

Great work guys. If you need help for anything let me know. Qualified on AN/APS and MX sensors.

Link to comment
Share on other sites

I was just wondering if I'm the only one with this problem with the radar picture:

 

In VR, it feels like the lower contrast compared to the DCS 1.5 makes it much harder to see details. Everything looks more washed out than in 2D. Am I the only one with this problem? Could it be because of my gamma settings?

Link to comment
Share on other sites

I was just wondering if I'm the only one with this problem with the radar picture:

 

In VR, it feels like the lower contrast compared to the DCS 1.5 makes it much harder to see details. Everything looks more washed out than in 2D. Am I the only one with this problem? Could it be because of my gamma settings?

 

I don't have VR (yet) but I swap between 2D and T-IR which I certainly notice differences in the views (which is very weird) but I haven't noticed a difference in radar image quality.

---

AJS37 Viggen, F-16C Viper, Adobe Premier.

X56 HOTAS, Ryzen 7, GTX 2070S

youtube.com/leadnapgaming

Link to comment
Share on other sites

The version that shipped today has poor performance in the 120km mode per our benchmarks.

Please report if you also see reduced performance in the lower range modes however.

 

We've fixed the 120km issue and that fix should be available on the next patch.

 

 

Works like a charm now!

Link to comment
Share on other sites

Works like a charm now!

 

Same here - was doing some flying earlier today and the system didn't even seem to notice the change between 15 and 120. Bravo!

---

AJS37 Viggen, F-16C Viper, Adobe Premier.

X56 HOTAS, Ryzen 7, GTX 2070S

youtube.com/leadnapgaming

Link to comment
Share on other sites

Radar 2.0 making drama already I guess, hehe , I want to see that myself and for my support of the rendering tech going forward with modules and/or DCS core.

 

I couldn't let the blunder steal the viggen's glory like this, so I had to do it.

 

Merry XMAS HEATBLUR SIMULATIONS !

Modules: A-10C I/II, F/A-18C, Mig-21Bis, M-2000C, AJS-37, Spitfire LF Mk. IX, P-47, FC3, SC, CA, WW2AP, CE2. Terrains: NTTR, Normandy, Persian Gulf, Syria

 

Link to comment
Share on other sites

  • 2 weeks later...
Is the new radar in beta only? I just purchased the Viggen during the holiday sale. Get around 70+ FPS normally but tanks to 20 (or even single digits) when the radar is set to 120 km.

 

New radar is in stable - but a fix for long range performance is still at beta. Its smooth as a butter now - I used to have performance issues too :smilewink:

 

It takes atleast two weeks for the next update (ED is taking a little break due to the holidays) - so I'd stay way from 120km mode until then; or even better, go Beta :thumbup:

A-10C Warthog | AJS-37 Viggen | F-5E Tiger II | Mig-15bis | MiG-19P Farmer

Link to comment
Share on other sites

New radar is in stable - but a fix for long range performance is still at beta. Its smooth as a butter now - I used to have performance issues too :smilewink:

 

It takes atleast two weeks for the next update (ED is taking a little break due to the holidays) - so I'd stay way from 120km mode until then; or even better, go Beta :thumbup:

 

 

Thanks! I've only ever had stable installed, I'm happy to wait in 60km mode :)

Link to comment
Share on other sites

Awesome!

 

Late to the party as I've just started using the forums but thanks for the updates of this lovely module and plane.

 

As has been said before, it's a dream come true for those of us born and raised in Sweden and seeing the Viggens in the skies.

 

Most fun module to fly for me, easily beating out some other more modern planes with newer systems.

 

/Wilbuz

Link to comment
Share on other sites

  • Recently Browsing   0 members

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