Jonathan Berthier

Well considering this thread on their forum it appears a patch may be needed to fix the water textures issue and possibly others (see this other thread here) so right now I would not use REX at all.

It didn't work for you because you made the 3.1 install over your existing 3.0 install which was obviously asking for trouble... whereas he said he did a full uninstall before installing the 3.1 version so he'll be just fine.

That's wrong actually, it's just that P3D is missing some kind of "render each screen separately" option that for example many racing simulations have (iRacing comes to mind) in which case if well configured you don't have any distortion at all.

He said he saw this on Windows 8.1 Update 1 and Windows 10 while you both have Windows 7, so that may be a hint there.

The best way to handle multiple monitors, well at least in the case of a typical 3-screens setup, would be the way iRacing does it: Look at the Display section: providing your monitor info, viewing distance and monitor angles, bezel correction is taken into account and the ideal FOV is calculated for you. Never in another sim of any kind I've seen something so straightforward and efficient.

Just check the Learning Center for a complete reference of what you can do :wink: http://www.prepar3d.com/SDKv2/LearningCenter/getting_started/performance/tuning_guide.html

Ah, now the weekend can't be over fast enough Great news!

That's the first thing I noticed right away -even with shadow quality at medium- along with the water rendering improvement :-)

Good morning from France! Did a full clean install, re-installed most of my add-ons (FTX Global/Vector/OpenLC/Mesh 2010 and REX 4 so far) and all is well in the world :-)

Great Scott! Well I stand corrected then... but I'd still go for a full re-install for future releases anyway.

I'd rather go with a full install, I know it can be tedious with all the add-ons to reinstall but I always prefer to go back to a "clean" base, it's like a good old disk format every now and then, never hurts ^_^

Nope, we have to wait for the next released drivers (most likely beta version) that will fix the problem.

Hi Rob, if you go for the AXE (which I also strongly recommend) you might want to wait a little bit as Aerosoft is about to release the A318/319 probably by the end of this month if all goes well, and then a bit later the A320/A321 which will be like an updated AXE but clearly an all new product considering the features list, the biggest one being a weather radar ! As Richard said the co-pilot option is great, and for these new products they will include several voice packs with different languages (well, all in spoken english with a different accent and a few sentences in the native language). For the little story I did the "french accent" recordings for the PIlot Flying, can't wait to hear the results :-) You have all the info here: http://forum.aerosoft.com/index.php?/topic/82081-airbus-projects-preview/ PS: thank you for all your posts/videos on the beta status, I rarely post but I read a lot ;-)

http://forum.avsim.net/topic/448194-p3d-v22-native-texture-bug/

It's a bug with the latest NVIDIA drivers, you need to revert to the 337.88 WHQL version. See here : http://forum.avsim.net/topic/448146-texture-triangles/ and here : http://forum.avsim.net/topic/446301-nvidia-340-series-drivers/