do you notice any degrades on picture quality if you use Sony TV at 4K with 4:2:0

 

Only if I set video output format to YCbCr 4:2:0 which does get me 60Hz.  If I set to RGB (30Hz only) the picture quality is outstanding.  You would NOT want to run YCbCr 4:2:0 -- the difference is VERY obvious.

 

I would like to see how the 980 does with 4K over HDMI 2.0 since it's supported.  Anyone using that combination?

 

Cheers, Rob.

Thanks, Rob. I'm considering the Seiki 4K TV. Given this potential 4:4:4 sampling problem in many 4K TVs, maybe I just stick with one to do full color 4K @ 30Hz, as you said the results on your TV is outstanding at 30Hz. 

Wondering if any else has had this problem? I posted it in

http://forum.avsim.net/topic/454383-dsr-causes-runtime-error-6025/#entry3104785

 

DSR causing R6025

 

Any opinions?

The best IQ improvement with DSR is no more aliased control surfaces or shimmering gauges.  Those are the #1 and #2 reasons why I use DSR.

 

Cheers 

jja

The best IQ improvement with DSR is no more aliased control surfaces or shimmering gauges.  Those are the #1 and #2 reasons why I use DSR.

 

Cheers 

jja

I saw this with the very first use in the SkyMaster C377, and I haven't looked back...!   :rolleyes:

 

344.48 installed and approved. DSR activated on my 2 x GTX 770.

 

Given that Nvidia says that DSR is only supported now in their 970/980 cards, how exactly did you manage it on your 770s?  I don't even have any DSR options in the control panel for my GTX 780 ti cards (3 of them).

Given that Nvidia says that DSR is only supported now in their 970/980 cards, how exactly did you manage it on your 770s?  I don't even have any DSR options in the control panel for my GTX 780 ti cards (3 of them).

DSR is not supported on SLI.

 

 

DSR causing R6025
 
Any opinions?

 

Highly unlikely ... this is the more likely issue described in Microsoft's docs: http://support.microsoft.com/kb/125749

 

Most likely cause is at development time you call a linked/referenced DLL that is not the same once deployed to a "end users" environment.  For the first time in my life I experienced the R6025 error when I loaded Aerosoft's A321 ... this is the ONLY aircraft so far that has triggered this error.  Aerosoft's A320, A319/318 don't trigger this error. 

 

Cheers, Rob.

 

Given that Nvidia says that DSR is only supported now in their 970/980 cards, how exactly did you manage it on your 770s?  I don't even have any DSR options in the control panel for my GTX 780 ti cards (3 of them).

 

 

In the release highlights of the 344.48 WHQL : "The 334.48 brings support for Dynamic Super Resolution (DSR) to Kepler and Fermi desktop GPUs". 

 

(Source Wikipekia) "Fermi is the codename for a GPU microarchitecture developed by Nvidia as the successor to the Tesla microarchitecture. It was the primary microarchitecture used in the GeForce GeForce 400 series and GeForce 500 series. It was followed by Kepler, and used alongside Kepler in the GeForce 600 series, GeForce 700 series, and GeForce 800 series"

DSR is not supported on SLI.

 

But you can activate and use it on a SLI configuration (what I do). DSR don't use the full power of several GPU's but works anyway.

DSR causing R6025

 

Any opinions?

The error is arising from P3D, and evidence is mounting that it could be after some kind of interaction with the display system. So perhaps DSR, changes to screen resolution, closing the sim down (the display mode changes), another process interacts with the display (possibly by calls to devicecaps), and others.

 

The only time I saw it was with the vanilla sim 2.4, and a paused saved flight with baron was loaded from the menu, the sim was left paused for 10 minutes, came back to find R6025 from MSVCR100.dll followed a couple of seconds later by dxdiag.exe in DivX.dll.

 

Tried it again and again - nothing.

 

 

Highly unlikely ... this is the more likely issue described in Microsoft's docs: http://support.microsoft.com/kb/125749

 

The error is arising from P3D, and evidence is mounting that it could be after some kind of interaction with the display system. So perhaps DSR, changes to screen resolution, closing the sim down

 

Thanks for the input guys. I uninstalled 344.48 and reinstalled and it hasn't happened since.

I guess SLI is just too small a market for nVidia to focus much attention on.

 

Sums it up perfectly. Now that we have such potent GPUs from NVIDIA why would they continue to push SLI and Crossfire which were likely designed and offered as an interim solution to future proof the lesser breeds? Looks like those of us who were persuaded to invest in SLI may have been let down (duped?) by yet another company (remember Microsoft?) whose primary concern will always be profit rather than customer interests and that leaves an unsavoury taste in my mouth.

 

Such a pity both Microsoft and NVIDIA continue to have such a stranglehold on the world market.

 

I hope that I will be proved wrong and SLI/Crossfire will, in time, become a reality in P3D but, with each passing day, it's looking more and more like Lockheed Martin's original hopes and expectations have been way off the mark and those of us who were persuaded to invest in a dual GPU setup dedicated to Prepar3D will now be regretting that decision.

 

Mike

I uninstalled 344.48 and reinstalled and it hasn't happened since.

Thanks for your input Avidean.

 

 

Thanks for your input Avidean.

 

That's very nice of you to say Steve

But I sure take an awful lot more out of this forum than I put into it. LOL!

The error is arising from P3D, and evidence is mounting that it could be after some kind of interaction with the display system. So perhaps DSR, changes to screen resolution, closing the sim down (the display mode changes), another process interacts with the display (possibly by calls to devicecaps), and others.

 

Steve, you may be on to something there. I got my first R6025 error today. I had the sim set up with low visibility, volumetric fog, aerosoft's twotter and Orbx PNG. Closing the sim down gave me the error.

 

However, I think this is a nvidia issue, not a LM issue. Last week, I also got a R6025 error playing skyrim. Again the gpu was working hard and the program just quick. So I'm guessing something's off with nvidia/os as opposed to the program running.

 

Jess B