It probably needs to be said that, at least in my sim/setup, when going from "Minimum" to "Normal", the fps went down from 42 to 35 (same spot).
But still a great find, and the flickering textures were driving me crazy.. So thank you!

<r><br/> <br/> This is what LM should take a look at and fix asap. The problem is existing btw. since v2.0 as far as I can remember – already then I said there are problems, and the problem was ignored. If only I could dig out that post…<br/> <br/> Maybe present in all versions (since resources are ...

<r><br/> <br/> ...Textures gradually becoming more crisp the closer you get. Locked frames or not, makes no difference. No edits done to the CFG file either (tried the ‘usual’ tweaks) without any success. From what i’ve gathered searching on the issue this is apparently intended behaviour to save VA...

<r><br/> <br/> Amazingly enough, this hotfix was released during a time when Pete Dowson (of FSUIPC fame) was not on vacation, which I think marks a first for the franchise! <E>;)</E><br/> <br/> Yes, that must be a first <E>:)</E><br/> Objectflow tells me it's not happy with 12945, but still works l...

<t><br/> In Prepar3D v2 Hotfix (2.5.12944.0) I am revisiting the blurry ground problems I had in v2.2 (or maybe it was 2.3)..<br/> <br/> Video showing the problem:<br/> Youtube<br/> Zoom is at 1.0 btw.<br/> <br/> Have tried several tweaks in the cfg - Use of Affinity mask and several others. No chan...

<t>Probably not, since the values in P3D is given in degrees?<br/> <br/> I mean, since the bezel correction in Nvidia is to compensate for the width of the monitor frame (bezel).<br/> <br/> <br/> <br/> My guess is that these are used in conjunction with:<br/> <br/> Code:<br/> MultiViewDisplay Enable...

Same problem here.

Nevermind, fixed it by deleting fsuipc.ini and transferring controller settings and (some of the) other settings to the new generated ini file.

Du you mean this version?

Tried that, but at least on my system that crashes P3D2 too (MSVCR100).

<t><br/> <br/> Quote:<br/> Quote from Junior on August 12, 2014, 04:43<br/> <br/> Using the Full Installer solved the problem.<br/> <br/> <br/> <br/> A full uninstall v2.2 and full install v2.3 I guess will reset everything, so non-compatible DLLs will no longer be loaded afterwards.<br/> <br/> But ...

<t><br/> <br/> Quote:<br/> Quote from peppy197 on August 11, 2014, 19:48<br/> <br/> One reported he did successfully install the patch over 2.2.10438 (AVSIM) if I am not mistaken<br/> <br/> <br/> <br/> +1<br/> <br/> I had ..38 too, and patch went well (except for FSUIPC refusing to cooperate after p...

<t><br/> <br/> Quote:<br/> Quote from Junior on August 11, 2014, 17:52<br/> <br/> I updated using the patcher and it went well but I got a fatal error (or CTD) upon loading the sim. I will look again tomorrow.<br/> <br/> EDIT: I decided to download the full installer to see if it makes any differenc...

<t>If you are using Windows' default sound device for sound and default communications device for ATC, it might be Windows is doing this.<br/> <br/> <br/> <br/> You can test by turning off the automatic Windows mute by right clicking the speaker icon in the task bar, selecting 'Playback Devices', go...

Hehe, you may be right. A CPU/GPU suffering from placebo would explain a lot of things

Probably the affinity mask alone yes. I knock off all cores in task manager and that pretty much takes care of the blurries. Like LM noted, v2.3 will use all available cores.

Thought so

Ah.. the placebo we all suffer from at times