Jump to content

Recommended Posts

Posted
9 hours ago, BIGNEWY said:

Hi, 

we will be taking in the feedback from everyone over the coming days and tweaking in future updates.

thank you

I'd suggest that any changes should probably result in an option selector in the difficulty settings that can be set and enforced on all clients in a multiplayer environment. This is the only way to get most of the people happy, by giving them all the options to choose from. Those should be the prior system, the current one and probably new one that's kinda a blend of both which probably should be the default one as well.

 

Wouldn't want to have better visibility for a patch or two, only to have it taken away from me just because most of the community thinks it's not realistic and maybe even making a radar for finding bogeys superfluous (which it totally shouldn't). Ever player/simmer is different and they all have different setups. Making it possible to scale it to everyone's preference is the right way to go. It also makes it more barrier free for people with vision impairment. And making it so that a server can enforce a setting will kill any discussion about exploiting it right at the get go. We've been through that with the label thing a lot already. And I think using the label system as a substitute workaround in the past for what was added now apparenty (didn't have the chance to try it myself yet) is a thing that needs to be replaced, and the moment for that is right now with the new approach. It just needs ways to customize for best possible personal experience.

  • Like 2

dcsdashie-hb-ed.jpg

 

Posted (edited)

@Flappie I wasn't able to disable new dots in VR the way it described in the patch notes:

There are other reports about it too. Maybe I did something wrong or maybe sharpening affects it as you wrote? I do have DLSS and DLAA enabled and sharpening set to 0.5 as suggested.

Checked 2D with just DLAA too: new dots are still there

Edited by lester

Все написанное выше является моим оценочным суждением

Everything written above reflects my personal opinion

 

Занимаюсь "активной пропагандой Американцев на данном форуме" © Flanker

Posted

I like it. Better than before - easier but still hard to spot stuff.

  • Like 5

[sIGPIC][/sIGPIC]

"Great minds think alike; idiots seldom differ.":pilotfly:

i5 3750K@4.3Ghz, MSI Z77A GD55, 8GB DDR3, Palit GTX 670, 24" Benq@1920*1080, X52 Pro, Win 7 64bit.

Posted

I'm unable to disable new spotting feature aswell. 

My autoexec.cfg is working fine as I have other commands there.

Anyone with better luck?

 

  • Thanks 1

Kowalsky

- "Fox 3" simply means that you have commitment issues

Posted
vor 2 Stunden schrieb chichowalker:

It's disgusting and unreal. I can not deactivate it adding the line in autoexec.cfg. Very nice to be able to increase visual settings with DLSS but not good to see a big dot at 30 NM from your position. This kind of demands has to be discussed with real pilots before being implemented, it's my point of view. In real aircraft operations when flying, it depends on weather, visual environment and more things, the distance from where you can have tally or visual can be different, but normally is below 5-10NM. My recommendation is to have the opportunity to deactivate as an option in DCS settings.

Enviado desde mi 21051182G mediante Tapatalk


 

As already mentioned, evidence would be very helpful here. 

  -picture

  -resolution

  -graphics settings

 

That would support fine tuning.

on other systems you see the dots max to 12-15nm miles so how do you get your 30nm?

  • Like 2
Posted
vor 7 Minuten schrieb average_pilot:

In my opinion spotting needs a physics based approach.

The difference and the main task is that the final result is almost the same on all systems.   What's the point of having a perfect result on 3440/1440 if everything above or below it delivers completely different results?  

so the feedback here is precisely what is being asked for.   How does spotting work on different systems 

  • Like 3
Posted (edited)

My feedback is:

3840x2160 No DLSS, MSAA4x= Perfect, smooth transition from imperceptible dot to a recognizable one from 30 to 10 nm
3840x2160 No DLSS, TAA or DLAA= tends to be too small
3840x2160 DLSS Quality, Balanced, Performance= slightly too small
3840x2160 DLSS Ultra Performance= blurry, and probably too big at medium/close range.
1920x1080 No DLSS, MSAA4x= Too big in general and dramatically increasing FOV
1920x1080 No DLSS, TAA and DLAA= maybe the size here is correct but lacks of smooth transition

Tested on a 32 inch 4k display.

Edited by falconzx
  • Like 4
  • Thanks 1
Posted

In vr the new spots are gigantic. At first i tought i have lots of dark puffy clouds in the horizon but they ended up being these new spots.

  • Like 3

Fighting for peace is like screwing for virginity.

Posted
1 hour ago, average_pilot said:

That was my point, making it so that the final size and contrast against the background depends only on the optical properties of some model of light and camera sensor and not the final screen resolution.

 

Physics/optical based approach doesn't work, as your monitor has a finite number of pixels to represent a point in space. You have to account for a screen resolution, otherwise you get system that was on before this update. When I set my resolution 1920x1080, I can easily spot aircraft in the VCCT bubble. Same environment but on 3440x1440 or 3840x2160 and I'm blind as a bat.

Reason is, for the same point in space, 1080 resolution has 1 pixel, but 1440 or 2160 resolutions have 4 or 8 pixels, meaning the actual dot is rendered smaller. The result? The smaller resolution, the easier spotting. 

It really sucks that we all strive for better graphics, better fidelity, but to be able to see anything you basically have to run as smaller resolution to get any sensible spotting available.

 

Transferring IRL spotting to a video game is not that simple, as in video games on a computer screen you generally see less far away than you would be able to see IRL and that needs accounting for

  • Like 3
  • Thanks 1
Posted
As already mentioned, evidence would be very helpful here. 
  -picture
  -resolution
  -graphics settings
 
That would support fine tuning.
on other systems you see the dots max to 12-15nm miles so how do you get your 30nm?
VR Reverb G2
DLSS quality, sharpening 0.5, LOD slider at 0.8
Resolution override with toolkit 3300x3225
DCS textures high
Clouds high
Water medium
Rest of AA modes off.
Anisotropic 16x
Shadows low
Terrain shadows flat
SSS off

Distance of the contacts known by AWACS or airborne sensors.

Enviado desde mi 21051182G mediante Tapatalk

  • Thanks 1
Posted
10 hours ago, twistking said:

I agree. Unfortunately for me, i have 1080p monitor, so that excessive visibility is all i know since forever. In good weather, i never ever locked a bandit with radar before i could easily see him visually. I was hoping that the 2.9 update would finally make spotting more realistic...

i want to add, that this is for 2.8 and earlier. i have not yet tested 2.9.

My improved* wishlist after a decade with DCS ⭐⭐⭐⭐🌟

*now with 17% more wishes compared to the original

Posted (edited)
8 hours ago, Hobel said:

Yes, but this has to work for all kinds of resolutions, everyone here has different hardware.  The thing certainly still gets fine tuning

 

BTW.   It would be helpful if pictures were posted of what distance the dots were actually seen, no feelings of "that might have been 20nm", what resolution  And graphic settings, there are many different reports of the new spotting

 

I just checked my track and discovered this bandit was indeed a KC-135. Above comments removed until I can test further. 
PS I understand this feature is about dots. If you see an actual aircraft outline that’s not the new spotting. 

Edited by SharpeXB
  • Thanks 1

i9-14900KS | ASUS ROG MAXIMUS Z790 HERO | 64GB DDR5 5600MHz | iCUE H150i Liquid CPU Cooler | ASUS TUF GeForce RTX 4090 OC | Windows 11 Home | 2TB Samsung 980 PRO NVMe | Corsair RM1000x | LG 48GQ900-B 4K OLED Monitor | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5

Posted
5 minutes ago, evilnate said:

I like it. If others don’t, maybe add slider to reduce size or draw distance?

There shouldn’t be player controlled visibility settings. It would wreck multiplayer and divide it up with settings. That’s what happened last time with the Model Enlargement feature. The goal I’m sure is to have a solution that works well enough for everyone. 

  • Like 1

i9-14900KS | ASUS ROG MAXIMUS Z790 HERO | 64GB DDR5 5600MHz | iCUE H150i Liquid CPU Cooler | ASUS TUF GeForce RTX 4090 OC | Windows 11 Home | 2TB Samsung 980 PRO NVMe | Corsair RM1000x | LG 48GQ900-B 4K OLED Monitor | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5

Posted
1 hour ago, SharpeXB said:

There shouldn’t be player controlled visibility settings. It would wreck multiplayer and divide it up with settings. That’s what happened last time with the Model Enlargement feature. The goal I’m sure is to have a solution that works well enough for everyone. 

I don't see any issue if it's only to make it smaller than default. Have a slider with 100% as the top so if someone thinks the dots are too big they can reduce them. No advantage is gained this way. 

"It takes a big man to admit he is wrong...I'm not a big man" Chevy Chase, Fletch Lives

 

5800X3D - 64gb ram - RTX3080 - Windows 11

Posted
Just now, DayGlow said:

I don't see any issue if it's only to make it smaller than default. Have a slider with 100% as the top so if someone thinks the dots are too big they can reduce them. No advantage is gained this way. 

But then the player is forced to decide between an ugly game or being at a disadvantage. I think we want to get rid of that dilemma. 

i9-14900KS | ASUS ROG MAXIMUS Z790 HERO | 64GB DDR5 5600MHz | iCUE H150i Liquid CPU Cooler | ASUS TUF GeForce RTX 4090 OC | Windows 11 Home | 2TB Samsung 980 PRO NVMe | Corsair RM1000x | LG 48GQ900-B 4K OLED Monitor | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5

Posted (edited)

This is the entire point of the exercise. Make the spotting fair for everyone.

They have to start somewhere, and it is a lot better than before. I would rather deal with big dots than spamming zoom to see objectsat anything more than CRT resolution.

I am sure it will change as they fine tune it.

Edited by Daemoc
  • Like 2

Ryzen7 5800X3D - MSI MAG B550 Tomahawk MAX - 64Gb 3600MHz DDR4 - RX 6950 XT - SoundBlaster -Z

Posted (edited)

Here's what I see in both 4K and giving it the "cheat test" by dropping my res to 1080p

EDT: after trying this out more I find myself thinking these dots are simply too big and too visible. They seem to be nothing more than the dot labels forced on.

I can't easily see the bandits at extreme range really any better than before and only slightly better at closer distance of about 14 miles. This is maybe a little better than in 2.8 but not really extreme. These targets are in ideal conditions, they're moving, and I know where to look, otherwise they'd be realistically difficult to spot.

And a big thank you! to ED for fixing the replay feature that now works for testing like this.

KC-130 in 4K.jpg

Migs in 4K.jpg

distant fight in 1080p without HAFU.jpg

distant fighter in 1080p.jpg

Screen_231020_074617.jpg

Edited by SharpeXB
  • Like 1
  • Thanks 1

i9-14900KS | ASUS ROG MAXIMUS Z790 HERO | 64GB DDR5 5600MHz | iCUE H150i Liquid CPU Cooler | ASUS TUF GeForce RTX 4090 OC | Windows 11 Home | 2TB Samsung 980 PRO NVMe | Corsair RM1000x | LG 48GQ900-B 4K OLED Monitor | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5

Posted

This actually seems good to me.

 

  • Like 1

i9-14900KS | ASUS ROG MAXIMUS Z790 HERO | 64GB DDR5 5600MHz | iCUE H150i Liquid CPU Cooler | ASUS TUF GeForce RTX 4090 OC | Windows 11 Home | 2TB Samsung 980 PRO NVMe | Corsair RM1000x | LG 48GQ900-B 4K OLED Monitor | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5

Posted

Question for ED Devs:

Is the new spotting simulating an increase/reduction of the dot visualized when the LOD is the lowest ( for example HIGH FOV but close range) based on the actual target visible surface?

  • Like 1
Posted (edited)

I also don’t see a disadvantage now is using 4K. The dots aren’t any smaller and the distant aircraft are of course better defined and more easily ID’d

I can’t test what this looks like on a native 1080p screen though. Nor VR

Edited by SharpeXB

i9-14900KS | ASUS ROG MAXIMUS Z790 HERO | 64GB DDR5 5600MHz | iCUE H150i Liquid CPU Cooler | ASUS TUF GeForce RTX 4090 OC | Windows 11 Home | 2TB Samsung 980 PRO NVMe | Corsair RM1000x | LG 48GQ900-B 4K OLED Monitor | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5

Posted
6 hours ago, SharpeXB said:

There shouldn’t be player controlled visibility settings. It would wreck multiplayer and divide it up with settings. That’s what happened last time with the Model Enlargement feature. The goal I’m sure is to have a solution that works well enough for everyone. 

I see no problem with giving player control over visibility, provided multiplayer servers have the option to turn it off. A lot of the user base is not on multiplayer.

  • Like 3

I'm Softball on Multiplayer. NZXT Player Three Prime, i9-13900K@3.00GHz, 64GB DDR5, Win 11 Home, Nvidia GeForce RTX 4090 24GB, TrackIR 5, VKB Gunfighter III with MCG Ultimate grip, VKB STECS Standard Throttle, CH Pro pedals

Posted (edited)
26 minutes ago, sthompson said:

A lot of the user base is not on multiplayer

Exactly. Let's stop gatekeeping things.

Instead, let's allow server owners to override local client spotting settings to ensure fairness, much like you can with dots in missions, and let's allow people to do whatever the hell they want to adjust and tweak their settings.

Edited by ColinM9991
  • Like 1
  • Thanks 1
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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