Guess I'm just not there yet... but trying. 

 

R U guys doing any adjustments to the p3d.cfg file?  I've tried some photoreal scenery and it is blurry as heck not far from the plane.  Messing with different settings.  R U using the settings in-game or from the Nvidia Control Panel?  I understand Nvidia Inspector does not work? 

 

Have a 2GB GTX670.  Dang, my P3D1.4 is sharp as nails but this one's got me head scratchin'.  :huh:

Hi,

 

I'm using FTX Global, I haven't tried using photoreal scenery in P3D 2.0. But I remember photoreal being blurry up close in FSX, so I imagine it would be the same in P3D 2.0.

 

 

Guess I'm just not there yet... but trying. 

 

R U guys doing any adjustments to the p3d.cfg file?  I've tried some photoreal scenery and it is blurry as heck not far from the plane.  Messing with different settings.  R U using the settings in-game or from the Nvidia Control Panel?  I understand Nvidia Inspector does not work? 

 

Have a 2GB GTX670.  Dang, my P3D1.4 is sharp as nails but this one's got me head scratchin'.  :huh:

 

 

R U guys doing any adjustments to the p3d.cfg file? 

 

Try these steps if you haven't already:

1. If running nV Inspector, bring up the Prepar3D profile and delete it.
2. Next, go into V2's Display Settings and set FSAA to OFF, MSAA to 4, and AF to 16x.
3. Play w/ all the sliders until you're getting your %GPU utilization to maybe 90% and are happy w/ the general scenery, lighting, graphics settings.  I run frames UNLIMITED w/ v-sync on.

This resolved the blurry textures which I complained of early on but quickly learned many/most of Inspector's driver config settings are ignored by DX11.  LM says they are working w/ nV to try to address this.

Hi,

 

I'm using FTX Global, I haven't tried using photoreal scenery in P3D 2.0. But I remember photoreal being blurry up close in FSX, so I imagine it would be the same in P3D 2.0.

 

Same here. I'm using FTX Global for textures so far. I have not tested my photo scenery yet. I use the Mega scenery for Hawaii, So Cal, NYC, Denver, Dallas and Boston City for P3d 1.4v. I'm still testing P3D V2 with FSDT, Latin VCR, UTX and Fly Tampa sceneries. Once those are done I'll start adding photo scenery and see how it works.

I thought 1.3 was great, 1.4 was awesome. But... 2.0 is.. It's the first iteration of P3D where I truly feel like ghost of FSX past was kicked out of bed..  Sure there are obvious similarities and legacy things but what they managed to pull off is a rarity..  To completely gut the engine of  20 sum plus years of code (FSX still had assembly code in it.. lol), kick DX9 out of bed, merge in DX11, yet still keep backwards capability without invoking "legacy mode" or some other dumb layer that I've seen software companies invoke and claim "full backwards capabilities".. Is amazing. 

 

I thought 1.3 was great, 1.4 was awesome. But... 2.0 is.. It's the first iteration of P3D where I truly feel like ghost of FSX past was kicked out of bed..  Sure there are obvious similarities and legacy things but what they managed to pull off is a rarity..  To completely gut the engine of  20 sum plus years of code (FSX still had assembly code in it.. lol), kick DX9 out of bed, merge in DX11, yet still keep backwards capability without invoking "legacy mode" or some other dumb layer that I've seen software companies invoke and claim "full backwards capabilities".. Is amazing. 

Here Here--well said!  

 

I can't speak to 1.3 or 1.4, but I do recognize what we have is a familiar face w/ a very new engine inside and that means greater upside potential compared to what FSX has to offer going forward.   That said, if I had to have only one sim installed I would clearly keep FSX over P3D V2 because I do find myself in my favorite planes and 3 out of 4 of them are PMDG.  But again, the upside potential seems real here and that bodes well for all simmers going forward.

After purchase, simply direct REX to the location of the simulator you wish to use and your set to go.

 

Tim, my backup folder I'm pretty sure is named 'Initial_Backup' or something along those lines, which if recall occurred because I elected not to back up default textures when I installed REX E+ for FSX, but my memory could be failing me.  Does that sound correct to you, that if it has that name implies no backup took place?   If I had backed up the default textures from FSX, would I chose a different folder to back up P3D default textures?

Hello Guys,

 

I am going to buy my P3D V2 in upcoming weekend :smile: . but I still don't know "Migration tool" is "Must have" add-on for it or not? My PC runs under dual boot situation and I will install P3D on separate OS. So :

 

1)just copy my fsx.exe on P3d main folder

 

2)adding FSX registry (by flight1 tool) 

 

3)create related folder for fsx.cfg and dll.xml

 

are enough?

 

I don't want have problems or conflicts after releasing native installer for some add-ons.

 

Thanks for your advices

Thank you very much!!

 

Regards!

It's not that radical Mitch   :wink:

 

If I don't have working clickspots / mouse cursor in Full Screen Mode soon, I'll be deleting it too......  (only until it's fixed though :wink:).

 

Also the Black Screen stuff and needing to toggle between window and full screen mode is a big pain.     I personally think P3D 2.0 has amazing potential, but at this point, has some pretty fundamental bugs.

 

You could always use WindowedBorderlessGaming -- its available for free, makes windows apps 'full screen'.

You could always use WindowedBorderlessGaming -- its available for free, makes windows apps 'full screen'.

 

 

No use because P3D 2.0 uses that system by default (well a similar one with the same result). So it IS already a borderless window! P3D 2.0 doesn't have regular fullscreen mode at all.