Cina - I tried the same "sharpen off" after you left on Friday. Though
I'm not using any reshade tool.
Just like you, I was appalled at the blurred graphics of the cockpit and
find it hard to believe that any game should need a "sharpen" option
(though I was using 2x AA, could try without) to get a clear picture.
Again, just like you, it was like not wearing my glasses.
So, just now, I tried with AA off. The cockpit was still pretty blurred,
but not as bad as with AA on. Though, of course, I had all the aliasing
artefacts.
The lesson is that it's a Signal Processing game - removing aliasing
produces blur everywhere (but maybe not much on 'plane edges, because
the game "knows" those are away from other things like ground, clouds),
sharpen (or indeed the extra "resolution" offered to VR users) removes
some blur, but introduces its own artefacts (likely 'plane/cloud
flickering, the "halo" around distant aircraft).
On that latter point, the one combination I haven't tried is viewing
aircraft in flight against cloud with no AA and no sharpening.
56RAF_phoenix
On 06/12/2019 08:43, Marcin Wochnik wrote:
Hi Guys,
Just my small observation on the topic. Like you know I'm using Reshade for better color saturation in game and a sharping shader called AdaptiveSharpen (I'm not using ingame Sharpen feature). Last time I made some tests and disabled AdaptiveSharpen in Reshade (ingame Sharpen still unchecked) and the game was horrible. Blurred like I've never seen before. Blurry cockpit, landscape, everything. I felt like my vision defect (I'm shortsighted) has doubled. I put the shader back up again and all returned to normal.
I think there is something wrong with the game when you need to use sharpening tools to make ok for 20/20 eye sight. Or maybe there is something wrong with my rig or me. I'm going to ask my son to look at it. He's got 20/20 eyesight and can tell if the image is blurred with sharpen off.
Cina
niedz., 1 gru 2019 o 09:45 klem56 <dmarc-noreply@xxxxxxxxxxxxx <mailto:dmarc-noreply@xxxxxxxxxxxxx>> napisał(a):
Well Guys I drained my piggy bank, took out a mortgage and bought
a RTX 2080 Ti, mostly for better DCS performance and with an eye
to VR in the future. It arrived yesterday (Saturday) and it went
in and was working from the off (same driver as the GTX980). I
tried it out off-line with the visibility mission I posted last week.
In IL-2 BG I was disappointed to find no improvement.... until I
went full Ultra and turned HDR on (HDR didn't seem to make
difference with the 980). The first attachment is with HDR On, the
second with it off. A clear difference in a/c spotting. The third
attachment is my in-game settings and of course I am running
Reshader a la Cina which I am not going to faff around with at the
moment. I'll get to that and other in-game settings later although
it may not make much difference as I'm convinced the faults lie in
the game graphics.
In DCS I am running four separate viewports (some people don't
realise that the card is generating four different views, not
carving up one large view). My fps in flight was around 25-30. It
is now quite steady on 70. Each viewport is over 2 megapixels,
total > 8mpixels. VR Valve Index only requires two 'viewports',
separately generated images of 1440x1600 = 2.3mpixels each,
whereas my screens are 1920x1080 = 2.07mpixels and Index therefore
has 10% more pixels on each 'viewport', so the 2080Ti should be
able to run Index at a pretty high fps. Out of interest I tested
two and three viewport views on my screens and the results came
back as follows:
4 viewports (current setup, total 7680x1080,
8.3mpixels)............................... 70 fps
3 viewports (forward view, no instruments, total 5760x1080,
6.2mpixels)......100fps
2 viewports (forward view on two screens, total 3840x1080,
4.15mpixels).... 130fps
VR Index is 2 viewports, total 2880x1600, 4.6mpixels. So, I guess
VR (Valve Index) will fall somewhere between 100 and 130 as there
are more pixels involved on each screen but surely must well
exceed 100 fps ?? IMHO I would expect around 120fps.
Of course it won't stop me getting killed but at least now I have
a better chance of seeing them coming =-O
klem
http://56punjabvirtualsquad.boards.net/
ASUS ROG Strix Z390-F mobo
i7 8086A @ 5.0 GHz with Corsair H115i watercooling
Gigabyte 2080Ti GAMING OC 11Gb GPU
32Gb DDR4 RAM
500Gb and 256Gb SSD SATA III 6Gb/s + 2TB storage
3 x 27" monitors @ 5760x1080 + 27" 1920x1080 in Tee format
TM Warthog Throttle, TM F18 Grip on Virpil WarBRD base
TrackIR4 with TrackIR5 software
Cockpits in LEA Extended Input on 10" iPad
Windows 10 Home 64bit
On 26/11/2019 11:05, Marcin Wochnik wrote:
Hi Klem,
I checked your mission again yesterday. Made sure I set the
expert mode with alternate visibility unchecked. It was quite
different. All the planes seemed to flicker. I could barely see
the last 3 aircraft on 1 o'clock and the last one on my 10. But
when I just touched my zoom in button all barely seeable contacts
turned black and were easily visible. But that behavior of the
planes is known and there are few posts on the forum describing it.
If I were to spot the furthest contacts on my 10 o 1 in
multiplayer I would be unable to do that to be honest. I would
even struggle to see those 8 km away in the same lighting
conditions. I will try to post a video from what I see from the
cockpit.
Cheers,
Cina
P.S. I recently unchecked 4K textures in BOX graphics settings
(Dutch pointed that to me last time) and I must say that this
eliminated stutter further. I only get them at mission start on
the airfield and they never come back when I'm airborne. The
image is crisp as before and I didn't notice any degradation of
image sharpness. The side effect is that the skins of aircraft
seem to pop up when you suddenly look around in a more pronounced
way. But I can live with that and this is also well pointed out
to developers in few posts on IL2 forum.
pt., 22 lis 2019 o 06:55 klem56 <dmarc-noreply@xxxxxxxxxxxxx
<mailto:dmarc-noreply@xxxxxxxxxxxxx>> napisał(a):
Thanks Cina, meanwhile I am going to recheck my monitor
settings to match popular reviews although I have done this
before.
klem
On 21/11/2019 13:39, Marcin Wochnik wrote:
Hi Klem,
I will check that for you during the weekend. Hot period
started at work.
Cheers,
Marcin
śr., 20 lis 2019 o 14:21 klem56 <dmarc-noreply@xxxxxxxxxxxxx
<mailto:dmarc-noreply@xxxxxxxxxxxxx>> napisał(a):
Cina/Guys,
I have set my graphics to exactly what Cina uses. It
doesn't seem to
help at all. I used the attached mission in which there
are Spitfires
from 3km to 10km at 1km intervals in front ranging from
10 o'clock (3km)
through to 1 o'clock (10km). I start the mission and
leave it on
autopilot. I look around immediately and the only one I
can see is 3km
away at about 9:30 o'clock. It is a very small dot just
a few pixels
(I've attached a jpg of it). If I zoom in I can just see
the one at
about 10:30, 4km away. btw Speed should be 200mph.
In the attached screenshot I have circled the 3km a/c.
Cina I'd be
grateful if you could run the mission and send me a
screenshot of what
you see, especially in the 9 through 12 o'clock view.
Thanks guys,
klem
-- http://56punjabvirtualsquad.boards.net/
ASUS ROG Strix Z390-F mobo
i7 8086A @ 5.0 GHz with Corsair H115i watercooling
EVGA GTX980 GPU 4Gb superclocked
32Gb DDR4 RAM
500Gb and 256Gb SSD SATA III 6Gb/s + 2TB storage
3 x 27" monitors @ 5760x1080 + 27" 1920x1080 in Tee format
TM Warthog Throttle, TM F18 Grip on Virpil WarBRD base
TrackIR4 with TrackIR5 software
Cockpits in LEA Extended Input on 10" iPad
Windows 10 Home 64bit
