Raising the stakes a little this time, with FSDT installed on both ends and the QW757 as our chariot.

 

 

You can follow along here.

 

PLEASE NOTE: I am externally limiting to 30 FPS.

 

Hey at least it's not snowing in SoCal today:

 

 

I still think 4096 looks weird, almost too much detail.

 

 

 

...and we're off...

 

 

Nice picts
 
my P3dv2 is now rock solid
I reinstalled Visual Studio 2012 (VC++ 11.0)
NET framework. 4.5
Visual Studio 2005 redis.
I used migration tool for a couples of add on then uninstalled it and took the back up to restore P3DV2 .
MIPMAP VC   and mute on lost focus  UNCHECK  scenery high and dense  , clean my pc with pc cleaner

 FTXG 1.2 INSTALLED WITH OPUS

I juste did 3 legs in US with out resetting P3DV2   
 
FSDT ...  the stakes are pretty high  looking forward and good luck ...

nice shots . is  that ENB series mod ?

nice shots . is  that ENB series mod ?

 

Nope, just the built in HDR with shadows.

Nope, just the built in HDR with shadows.

 

oh ok, that's P3d , I thought it was FSX sorry did not realize it.

Nice shots! Good to see that things are moving towards regularly scheduled sim operation!

Brian, can you make sure to record VAS usage?

 

Thanks for making these tests, as along hauler like myself, I need to make sure I can myself.

I'll certainly check it at JFK after I land, but I'm not monitoring it real time or anything.

 

In the cruise right now over the desert I am at a staggering 1GB  :lol:

Honestly a bit disappointed to see that the 757 doesn't seem to have backlit/emissive  gauges in P3D2 at least.

Wrapping things up now...

 

 

Descending into NY, I have to say I really like the way the lighting is done now. I can't wait to see how it looks once we have fully P3D2 native replacement textures.

 

 

So....yeah...I think the FSDT stuff isn't quite compatible yet  :lol:

 

 

 

And finally for you VAS counters, as soon as I cleared the runway, I alt-entered to grab this:

 

 

..and another at the gate to be sure:

 

 

So, there it is. 

 

The moral of the story is, P3D2 is mostly fine. If it's broken for you, it's because you broke it.  :lol:

Niiiiice... I agree. People need to stomp duping 200GB of FSX addons into P3Dv2 all at once then screaming it's broke when it doesn't work right.. Legitimate core bugs.. Can't slight them but the the rest.. Yeah.. the tides are turning. 

Thanks, Brian. Can you please share your settings? Just so I can do a little comparison myself.

I'll post the relevant .cfg info:

 

[JOBSCHEDULER]

AffinityMask=84

 

TEXTURE_FILTERING=16

MSAA=4 * I do add a bit of SSAA to this

SSAA=0

VSYNC=1

FXAA=0

TRIPLE_BUFFER=0

 

UPPER_FRAMERATE_LIMIT=0

WideViewAspect=True

 

INTERIOR_SHADOWS_CAST=1

INTERIOR_SHADOWS_RECEIVE=1

 

TESSELLATION=1

TEXTURE_MAX_LOAD=4096

HDR=1

BLOOM_LEVEL=2

SHADOW_QUALITY=1

LOD_RADIUS=4.500000

TESSELLATION_FACTOR=85

MESH_RESOLUTION=20

TEXTURE_RESOLUTION=25

AUTOGEN_VEGETATION_DENSITY=1

AUTOGEN_BUILDING_DENSITY=1

 

Not pushing it hard at all obviously but, 30 FPS must be maintained or I get cranky  :lol:

You changed to AM 84? I thought you agreed 14 gave night and day results? What made you flip? 

No, I asked you if you did. :lol:

 

I tried it for the B6 trans-con and saw some strange core usage, namely the primary core chosen was core 2...an HT core...not that it really matters, and perf seemed fine, but 84 gives me really nice load balancing.

 

I meant to add to our other thread but got..."distracted"..that one major difference is that, I find the internal frame limiter to be the work of the devil.

 

Seriously.

 

No other setting in any of the menus causes as much chaos to my FPS as that slider.