Tip

 

If you run into un-rendered auto-gen like so.. Change your texture resolution to a different value, (this will fix it) and back again.. So go from say, 4096, to 2048, hit ok, then revert back.. This doesn't survive a shutdown and restart and seem region specific (I only see it in Hawaii)..

 

 

 

Credit for the work around goes to "PP" on the Prepar3D forum - http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=3918

UK2000's VFR Airfields packages do the same thing but the textures on the trees look far more obnoxious, lol. Nice tip, thanks for passing it along.

I have v2 up and running using saitek cessna yoke throttle and rudder pedals. It was a bear to get the controls setup because of all the dupilcate entries for each module but I finally got it. I still have one problem that I cant figue out. I cant get slew to work right. tried resetting the keystroke but whenever I try to use it the plane just spins around on the ground. Does anyone have any suggestions?

I had really bad blurry ground textures and autogen popping (despite having an i7 2600k @4.8Ghz, 16GB of RAM @2400Mhz, a GTX780Ti and P3D2 on a fast SSD), but after reading a post by le-alex on the Prepar3D forum about setting the fps to unlimited, it got sorted out. Now I have sharp ground textures and no popping autogen.

 

So if you're experiencing any of these issues, try setting your fps to unlimited.

 

My frame rate controls are now set up like this:

 

VSync on, Triple buffering ticked and target frame rate at unlimited. I now get a steady 60 fps and nice textures and autogen.

For those using three screens, the rain does not fill the whole view and you still suffer from the umbrella effect. A workaround for the time being is to use the rain40.fx fix which I originally got from avsim. I simply copied the one over from my FSX folder as I had the fix already in place. The file in P3D is located in the \ShadersHLSL\misc folder.

I now get a steady 60 fps and nice textures and autogen.

 

Were, what weather, what cloud textures and with what aircraft?

 

 

I cant get slew to work right. tried resetting the keystroke but whenever I try to use it the plane just spins around on the ground.

 

Check if another controller isn't also assigned to slew: it might interfere. Make sure only ONE controller is assigned to slew.

 

 

Were, what weather, what cloud textures and with what aircraft?

 

This wasn't really about fps, but fixing an issue with blurry textures and popping autogen. But since you ask, I was flying the Carenado A36 over Norway (around Oslo Gardermoen, ENGM) with all the Norwegian freeware, FTXG, default cloud textures and default weather.

 

There is now another solution for the blurry textures and popping autogen (courtesy of Jean-Paul (jpmes) over in the Prepar3D forum). The solution was to add the affinity mask setting in the config file.

 

So now I can limit my fps to about 30 fps or use unlimited without getting blurry textures. I still haven't decided what is smoothest though.

Has anyone found a workaround for the bug that causes loss of click spots if you save a new default flight? There must be a line in that default flight file that isn't making it into user saved flights.

Has anyone found a workaround for the bug that causes loss of click spots if you save a new default flight? There must be a line in that default flight file that isn't making it into user saved flights.

 

lol. There is a sticky in this forum with the answer highlighted how to fix it.  :lol:

Hi all,

 

Did some testing today and this is what I have got... before reading the list below, this is the list of things I have installed. Moreover, the airplanes I used were mostly the Airbus X Extended and the Carenado A36 Bonanzo

 

• Airbus X Extended 1.16 with hotfix 19
• FlyTampa Montreal with the update

 

1. Regarding FXAA, I had it on at first. I did not realized it at that time but the autogen buildings were quite blurried as mentionned earlier here. When I ticked the setting off, I had a small gain in FPS but most importantly, the buildings are now way sharper than before.
    
2. While tweaking and flying around, Prepar3D crashed several times (5) and this is what caused the five crashes:
   a. StackHash_d004 (black textures on the ground and when I got in the menu, it crashed)
   b. ASC.DLL (of which I am pretty sure was caused by the Airbus X Extended)
   c. d3dcsx_43.dll (playing around in the menu)
   d. d3dcsx_43.dll (playing around in the menu)
   e. D3DCOMPILER_43.dll (happened in the menu while clicking one too many times on the "ok" button)
    
3. The CTDs I had with Prepar3D are pretty much all related to the instability in the menu. When you click more than twice on a button, the sim stops responding and from times to times a CTD follows.

What I would perhaps suggest to LM would be to improve the menus. They are painfully slow (the map for instance...) and bound to CTDs from what I observed. Moreover, I would perhaps forget the idea about the loading process in-sim (as compared with a loading bar) because it always looks as if the sim is just about to crash. But don't get me wrong, all in all, I liked my experience with Prepar3D and will continue to follow up the different posts to make it better and will wait for LM updates.

Cheers

 

 

What I would perhaps suggest to LM would be to improve the menus. They are painfully slow (the map for instance...)

 

I also had this when I first installed V2. After enabling Aero peek it went away along with a few other issues? Perhaps just a coincidence?

What I would perhaps suggest to LM would be to improve the menus. They are painfully slow (the map for instance...) and bound to CTDs from what I observed.

 

I never had any problems with p3dv2 - no freezes and no crashes, good fps and smooth display.

 

But as soon as I run the Aerosoft AXE (Airbus X Extended 1.16 with hotfix 19)  the trouble starts for example when changing the size of the P3D-window, full screen, load fuel etc.

 

Until Aerosoft brings out the solution I am not using this aircraft. Presently I am flying QualityWings Avro85 as the only airliner that I have and that will work with P3Dv2. Again, so far not the slightest problems with it even when using FSDREAMTEAM Groundservices (trial version).

 

So I am very happy with my P3Dv2 as such.

 

Jürgen

Hi all!

 

The testing of Prepap3D V2 continued today. Although I was quite underwhelmed at first with Prepar3D, now, I am more and more confident with Prepar3D - although it needs lots of work still. The display settings I have are now quite cemented. Here they are...
 

 

P2Dv2-1

P2Dv2-2

 

P2Dv2-3

 

P2Dv2-4

 

P2Dv2-5

 

Now, regarding the findings that I have made today, they follow here under. The small flight I have done was a VFR flight at 3,000ft from Montreal (CYUL) to the airport I've learned to fly, Mascouche (CSK3). I flown in the Carenado A36 Bonanza and had no other sceneries other than that of FlyTampa Montreal.

 

1. Whenever the menu bar is shown, I have a drastic loss of FPS (+- 10FPS) which is quite curious but is something other members have shared. Only here, it is an impressive loss.
    
2. During the flight, at times I can have a steady 25-26FPS without stutters whereas at other moments I have stutters at that same amount of FPS. I suspect that it might have been because the attention/focus of the computer was not all towards Prepar3D as I was switching from Google Chrome to Prepar3D back and forth at some point.

Now, regarding Aero Peek, it was on on my computer so I tried turning it off to see whether it would do a difference or not. In the end, turning it off got me 1-2FPS more. It also seemed to lessen the stutters mentionned above but without eliminating them completely. With regards to the menus and the map, it is still as slow as before.

 

To Jurgen, thanks for your advices. I can't wait for Aerosoft to release a fix for the Airbus X Extended. It will be a turning point as I will most probably do my first real flight then.

 

Cheers!

Try turning off terrain shadows. Others have reported that terrain shadows cut FPS 50 percent. I have vegetation shadows on and like the effect, but I haven't tested the FPS impact.

Hi all,

 

Did some testing today and this is what I have got... before reading the list below, this is the list of things I have installed. Moreover, the airplanes I used were mostly the Airbus X Extended and the Carenado A36 Bonanzo

 

 

• Airbus X Extended 1.16 with hotfix 19
• FlyTampa Montreal with the update

• Regarding FXAA, I had it on at first. I did not realized it at that time but the autogen buildings were quite blurried as mentionned earlier here. When I ticked the setting off, I had a small gain in FPS but most importantly, the buildings are now way sharper than before.

• While tweaking and flying around, Prepar3D crashed several times (5) and this is what caused the five crashes:

  a. StackHash_d004 (black textures on the ground and when I got in the menu, it crashed)

  b. ASC.DLL (of which I am pretty sure was caused by the Airbus X Extended)

  c. d3dcsx_43.dll (playing around in the menu)

  d. d3dcsx_43.dll (playing around in the menu)

  e. D3DCOMPILER_43.dll (happened in the menu while clicking one too many times on the "ok" button)

• The CTDs I had with Prepar3D are pretty much all related to the instability in the menu. When you click more than twice on a button, the sim stops responding and from times to times a CTD follows.

What I would perhaps suggest to LM would be to improve the menus. They are painfully slow (the map for instance...) and bound to CTDs from what I observed. Moreover, I would perhaps forget the idea about the loading process in-sim (as compared with a loading bar) because it always looks as if the sim is just about to crash. But don't get me wrong, all in all, I liked my experience with Prepar3D and will continue to follow up the different posts to make it better and will wait for LM updates.

Cheers

Same.. Every crash I have is menu related either entering or exiting a menu