1 hour ago, Dominique_K said:

<sigh>

Eye adaptation  is a questionable  idea in the first place but adding a parameter to cancel it which does not work, is irritating.

Yeah, even if the parameter is not official... not in the graphics menu, as Raytracing (there from release to tease us!).

Eye (non)adaptation along with the stroboscopic effect of the props is part of their intention to show the sim as through a camera, not human eyes... film grain and vignette also point in that direction.

31 minutes ago, Sethos said:

And Richardo yet again taking offense to natural conversation happening on a forum, classic avsim! 

No, no, your wrong its not classic avsim its classic "Recardo"🤪😄

Edited December 10, 20214 yr by Nyxx

33 minutes ago, rayharris108 said:

DX11 mostly. I did try DX12 and performance was only slightly reduced but with noticeable stutters, as most have seen.

Getting the same. Massive stutters...

56 minutes ago, Sethos said:

And Richardo

 

26 minutes ago, Nyxx said:

its classic "Recardo"🤪😄

No idea which person you are referring to.

Just now, Ricardo41 said:

 

No idea which person you are referring to.

Yet you quoted both, knowing it was directed at you. 🤔

1 hour ago, Ricardo41 said:

Lol, in this thread about the beta half the folks telling us why they won't install the beta. Classic avsim!

Probably because the topic is titled "There's no reason not to jump into the beta IMHO", so we're giving reasons why that isn't true for some of us 😉 It invited a response (as all discourses do), whether in agreement or not. Like your post has.

Edited December 10, 20214 yr by March Hare

55 minutes ago, MrFuzzy said:

Eye (non)adaptation along with the stroboscopic effect of the props is part of their intention to show the sim as through a camera, not human eyes

This is the absolute opposite of my understanding of the intention of eye adaptation, which is to mimic the very natural effect of pupil dilation as light levels change when we look from inside to out.

What on earth makes you think it’s supposed to mimic a camera lens which automatically adjusts to keep the same aperture for all conditions?

I normally dont hesitate to try new software. In case of MSFS I installed it a year ago and never had any problems (hardly any ctd's) and the problems we all had were solved either by a SU, hotfix or patch by developers.

Although I have no idea when the hotfix is released I'd rather wait for that then experiment with a beta fix, a second install and create new problems.

I expect the hotfix will come rather sooner then later.

 

43 minutes ago, scotchegg said:

This is the absolute opposite of my understanding of the intention of eye adaptation, which is to mimic the very natural effect of pupil dilation as light levels change when we look from inside to out.

What on earth makes you think it’s supposed to mimic a camera lens which automatically adjusts to keep the same aperture for all conditions?

He said "Eye (Non) Adaptation", not eye adaptation, so it looks like you are both in agreement. 
Non-adaptation (or eye adaptation off) makes it look like a camera image with no simulation of the pupil.

Edited December 10, 20214 yr by bobcat999

43 minutes ago, bobcat999 said:

He said "Eye (Non) Adaptation", not eye adaptation, so it looks like you are both in agreement.

I don’t know any variable in the cfg about (non) adaptation. 

21 hours ago, stefanwa said:

So far so good for me, but the clouds sometimes still look horrible on my sytem (PC, Radeon 5700, latest AMD 21.12.1). This screenshot was taken minutes ago flying into GLCA with live weather:

https://drive.google.com/file/d/1JJCLubZn5TdPppFspBmc3mHgtah6EzRV/view?usp=sharing

I'm hoping Asobo is not done with cloud rendering and modeling per se.  As far as METAR integration goes it's def improved in the hotfix beta, but cloud depiction still needs focused work and I think it still could happen but may be challenging to do and still retain the remarkably performance-friendly weather now happening.  Primarily for me it would be more work on specific cloud morphology, and some degree of grid artifact coming from how they're rendering clouds. 

1 hour ago, hansb57 said:

I normally dont hesitate to try new software. In case of MSFS I installed it a year ago and never had any problems (hardly any ctd's) and the problems we all had were solved either by a SU, hotfix or patch by developers.

Although I have no idea when the hotfix is released I'd rather wait for that then experiment with a beta fix, a second install and create new problems.

I expect the hotfix will come rather sooner then later.

To be frank pre hotfix beta was still decent for me so I can see why you're not clamoring for relief.  Only once had the sudden change in weather associated w/ entering a new METAR zone, and otherwise it was still decent.  FWIW, I've done one full reformat and reinstall of Win 10 and MSFS a few months ago, and while it takes awhile to do it requires little to no user input, no reconfiguration per se, and all my controller settings were retained.  This is the exact opposite of what happens when you reformat and reinstall P3D w/ addons for example.

New report on graphics driver 497.09 post hotfix 21.18. 

Whilst continuing SU7 hotfixes public beta testing this morning, after many days CTD free, I had a succession of CTDs and could not even load a basic flight. This initially resulted in me being unable to load into eg Orbx EGKA or EGHI airport without CTD, which had never previously been a problem even after SU5. After I uninstalled all mods, and even loading into default airports, got CTD after 5-10 minutes. The common factor was a windows error message: Application has been blocked from accessing graphics hardware.

So I then reinstalled the older nVidia driver 496.76 and reloaded the sim with my basic set of mods (CJ4, WT G3000, C208 mod and a number of mod airports, and Orbx re-enabled. This time it loaded perfectly and I was able to do a short flight. 

Just thought I'd give a heads up - and of course it could be something with my machine, although I have made no changes or updates since yesterday. No idea why it just decided to bomb out today, after a number of really good days. Maybe a server side change?

Thoughts, anyone else had a similar experience?

42 minutes ago, rayharris108 said:

New report on graphics driver 497.09 post hotfix 21.18. 

Whilst continuing SU7 hotfixes public beta testing this morning, after many days CTD free, I had a succession of CTDs and could not even load a basic flight. This initially resulted in me being unable to load into eg Orbx EGKA or EGHI airport without CTD, which had never previously been a problem even after SU5. After I uninstalled all mods, and even loading into default airports, got CTD after 5-10 minutes. The common factor was a windows error message: Application has been blocked from accessing graphics hardware.

So I then reinstalled the older nVidia driver 496.76 and reloaded the sim with my basic set of mods (CJ4, WT G3000, C208 mod and a number of mod airports, and Orbx re-enabled. This time it loaded perfectly and I was able to do a short flight. 

Just thought I'd give a heads up - and of course it could be something with my machine, although I have made no changes or updates since yesterday. No idea why it just decided to bomb out today, after a number of really good days. Maybe a server side change?

Thoughts, anyone else had a similar experience?

I don't know if you are running DX11 or DX12, but I have not tried MSFS using DX11 since DX12 came out and I have not had any CTD's running DX12 with the 497.09 driver.

44 minutes ago, rayharris108 said:

New report on graphics driver 497.09 post hotfix 21.18. 

I had a succession of CTDs

Thoughts, anyone else had a similar experience?

Yes, it seems that only few people have a stable configuration with this duo.

1 hour ago, scotchegg said:

I don’t know any variable in the cfg about (non) adaptation. 

That's the point.

EyeAdaptation = 1 means that the pilot's eyes in the sim are supposed to have the capacity to adapt to different levels of light, therefore the exterior should not be heavily overexposed when you look at the instruments.

Instead, what we see on the screen is what a camera would see: strobo effect from the props and overexposed exteriors when you focus on the instruments. It's all part of the cinematic style choice that MS/Asobo made, also confirmed by film grain and vignette. Like in this video, you see what a camera would see, not the person holding it.