If anybody runs into a problem where P3d crashes when loading scenery at 83%, reinstall ASN, or download the latest free beta version and install it. That solved the problem for me. 

 

 

Yes indeed!... this is the main area that V2.2 is lacking for me, in visual terms.

 

Yes it is, isn't it ...  :biggrin:

 

 

 

Was affinitymask disabled in this release?

 

The AffinityMask settings appear to be more intelligent ... in 2.1 Affinity was core 0 not used, core 1,2,3,4,5,6,7 used (254).  In 2.2 Core 2,4,6,8,10 used (1364 - which is what I manually set in 2.1).  So I'm not setting Affinity at all in my Prepar3D.cfg any more ... the settings LM use are the best for my system.

 

 

 

I sometimes seem to get blurries but I am flying in PNW right now and there are lots of trees there.

 

That'll happen to me also with certain PNW or NCA areas ... specifically very dense AutoGen areas such as major cities like Seattle or San Francisco.

 

To everyone using Orbx products -- Orbx have a new common Library out so be sure to install it.

 

It's really good to see so much positive feedback.

 

Cheers, Rob.

 

 

So Rob are you full time ASN or do you still use FSGRW, what are the differences? SHould I buy ASN?

 

Full time ... not sure I'm ever full time anything other than I have let FSX go.  I have OpusFSX, ASN, FSGRW and patiently wait to see what REX folks deliver for weather.  I believe FSGRW needs to get updated to work with 2.2 ... that may have already happened, not sure.   As for which to buy, not sure I can say one is better than the other ... if you TrackIR then you'll get rotating clouds in all 3.  OpusFSX seems to take a while to get the weather updated, ASN is very fast but I couldn't find a REFRESH now button, FSGRW default setup tends to want to do a lot of Stratus clouds which as you know exaggerate cloud rotation issues even more.  They all do a good job representing conditions ... ASN probably has the most weather options and you can run a weather radar on a separate PC.  If I had to favor one right now, it would be ASN ... but that could change on REX release and/or new updates from OpusFSX and/or FSGRW.

 

Cheers, Rob. 

 

 

And, even now, you would probably not be able to complete a flight across a continent with high quality airports at both sides and all photoreal along the way in the PMDG T7(when it's released).  That too would OOM P3D now too I bet.

 

That will depend on how those detailed airports are produced, FSX ported ones could (and most likely will) stay in memory.  However, airports designed carefully for P3DV2.x will not ... I believe FSDT are working on P3DV2 exclusive airport(s) KIAH ... but we will just have to see if that airports stays in memory long after it's out of visible range.  I don't know the criteria by which P3DV2.2 will release resources ... hopefully airport designers do.

 

Cheers, Rob.

 

 

ASN is very fast but I couldn't find a REFRESH now button

 

Rob

It is under Tools > View debug window > Refresh weather

I'm not using NV inspector . . . and P3D2.2 looks and runs just fine.  Yes, if I zoom way in on my C-172, there are some jaggies (but who flies like that?).

 

THIS is hardly a "jaggy mess" to me.

Here you go... No Inspector profile (completely deleted it) and look at the wonderful jaggies. Yep, that with 9x MSAA and 16x AF.

 

And, even now, you would probably not be able to complete a flight across a continent with high quality airports at both sides and all photoreal along the way in the PMDG T7(when it's released). That too would OOM P3D now too I bet.

 

Honestly I think you are wrong in this regard. Who knows what PMDG are doing regarding NGX and T7 P3D compatibility but I beat if it was just a case of getting a compatible working version we would already have them by now. PMDG are the kind of company that will probably rework both bird to make them not only Compatible with Prepar3D V2.X bit also highly optimized for V2.2.

 

I regularly flew my NGX between FlightBeam and FSDreamTeam airports some in ORBX regions with REX Textures all over the place with the system tuned to just barely maintain 30FPS in any situation. Did I occasionally get OOMs? yes I did, but I always saved the flight as soon as I heard the FSUIPC ping so it didnt bother me that much. My opinion is that the very same can be done in P3DV2.2 except you can leave a much big margin to protect against OOMs. Sure you cannot run it will all the slider to the right just yet and currently it would be very difficult to do that maintaining 30FPS anyway without  3-way SLI with 3 GTX 780's at least so the point is mute.

 

what is relevant though is that with the current best FSX solution you can run P3DV2.2 maintaining 30 FPS in any situation with any aircraft and any addon in any whether and experience a whole new level of emersion and graphics quality that is far superior to FSX under the same conditions. Now I am speculating a little here but my experience up to now with P3DV2.2 hold that opinion up. It is early days but I have great confidence in this sim.

 

FYI, I managed to get it to OOM with the same setting as the above post and the somewhat compatible Milviz 737-200c SP2. SP4 is apparently not at all compatible with P3DV2 and apparently wont be until the new year. That is very disappointing indeed.

 

I understand the iFly 737 NG is compatible and I am wondering if PMDG and Milviz are going to get caught with their pants down with 737 fans who have moved to P3D V2.X

 

 

The AffinityMask settings appear to be more intelligent ... in 2.1 Affinity was core 0 not used, core 1,2,3,4,5,6,7 used (254).  In 2.2 Core 2,4,6,8,10 used (1364 - which is what I manually set in 2.1).  So I'm not setting Affinity at all in my Prepar3D.cfg any more ... the settings LM use are the best for my system.

 

Rob, I just discovered this to be the case as well.  I tried a couple of different values and then removed the Affinity line altogether . . . and my FPS went up . . . quite a bit (as in 25 to 30%)!  After struggling with v.2.1, my biggest mistake was trying to 'fix' what is no longer broken P3D.

Here you go... No Inspector profile (completely deleted it) and look at the wonderful jaggies. Yep, that with 9x MSAA and 16x AF.

 

I only see 'jaggies' on the aircraft. Everything else in that image shows antialiasing in full force. That tells me it's not about the AA settings being used. Look at the arrow line under the aircraft... it's edge is pretty smooth for an angled line.

I only see 'jaggies' on the aircraft. Everything else in that image shows antialiasing in full force. That tells me it's not about the AA settings being used. Look at the arrow line under the aircraft... it's edge is pretty smooth for an angled line.

 

That picture actually is with P3D at it's best. I just took off from KIAD and the cloud shadows edge was a massive jaggie edge, along with the gate lines.

 

There is no way I can fly this without an NI profile.

OH and P.S.

 

I wonder if some of the people saying they don't need or use a profile have a default profile setup that is actually assisting?

 

I ask because even with supersampling and 4xS AA going on in the background my frames are the same as without using a profile. I wonder if they have some extra AA going on in that they aren't even aware of.

Yeah... here ya go... tell me that's some awesome default 8x AA here! ;-0

 

 

 

Rob
It is under Tools > View debug window > Refresh weather

 

Excellent, thank you.

 

 

FYI, I managed to get it to OOM with the same setting as the above post and the somewhat compatible Milviz 737-200c SP2. SP4 is apparently not at all compatible with P3DV2 and apparently wont be until the new year. That is very disappointing indeed.

 

I don't know what your settings are, but when I switch between aircraft that are not officially supporting P3DV2.x I do this:

 

1. go to the location I want to takeoff from

2. select the Aircraft I want

3. load weather or not (manually of have weather engine do it)

4. save flight

5. exit P3D

6. double click on the saved flight .fxml file to load P3D again

 

I only do this for aircraft that are NOT officially supporting P3DV2.x.  This method ensures I minimize VAS usage.

 

Something else I stumbled on in 2.2 release, I seem to gain about 25% performance using Unlimited frame vs. Locked frames.

 

Example KSEA (extreme settings):

Locked 30 fps = reported 15 fps

Unlimited = reported 19 fps

 

Cheers, Rob.

 

 

I wonder if some of the people saying they don't need or use a profile have a default profile setup that is actually assisting?

 

I'm currently not setting any AA in my NI profile, I use one but not for AA ... that's all set to Application-controlled.  I only use the profile for:

 

Texture filtering - Quality: High Quality

Texture filtering - Trilinear optimization: Off

Multi-display/mixed-GPU acceleration: Single display performance mode

Power Management mode: Prefer maximum performance

 

I'm setting AA in P3D to 4X MSAA (FXAA off) AF 4X and that's it.

 

It's not as nice as SGSS AA, but it's not as bad as your images.  Are you deleting your NI profile prior to setting AA in P3D?  Your images look like AA is not being applied at all.

It's not as nice as SGSS AA, but it's not as bad as your images.  Are you deleting your NI profile prior to setting AA in P3D?  Your images look like AA is not being applied at all.

 

Exactly! The profile is completely deleted and that's what I get with 8x on a 770 GTX 4GB card. Just did a clean install of the latest "official" drivers as well, but regardless P3D as always looked like this unless I fiddle with AA in Inspector.

Just did a clean install of the latest "official" drivers as well

 

FYI, a clean install of drivers will recreate the Prepar3D profile, so you'll need to delete it again.  With no application specific profile set, the drivers will use the "Global" profile.

 

EDIT: so your Global profile will need to be set to "Application Controlled" for AA and AF.

FYI, a clean install of drivers will recreate the Prepar3D profile, so you'll need to delete it again.  With no application specific profile set, the drivers will use the "Global" profile.

 

EDIT: so you Global profile will need to be set to "Application Controlled" for AA and AF.

 

I deleted the Prepar3D profile after the install. Global profile is set as you describe.

You never need highmemfix as it is already "fixed".

 

Suggest you try with no tweaks first. In your start menu under LM you will find a list of tweaks suggested IF you need them, but very good results are being found with no tweaks.

 

Sent from my Mobile thing

 

Thanks, I've removed all additional tweeks and P3D seems to be running great.

 

I still get 'flickers' of lights in the distance -- annoying. Should I be using Nvidia Inspector (bioshock profile?) to minimize this aspect?  

I went the upgrade route. Initially had some issues but deleted the shaders folder... info I found at the P3D forums.    Stuttering and low frame rates. Came here today.... saw the sticky post at the top of the threads by Fr. Bill.  

 

Deleted the 4 folders (watch your customization files).... rebooted the machine.... re ran the patch installer.

 

BOOM! Looking great.  Even bought the REX P3D license.... wow!

If in doubt; delete the shader cache! It won't hurt a thing, and the new shaders will compile in mere seconds

 

Where is the shader folder?

 

ShaderHLSL? 

 

Do I delete the entire folder within P3D?

 

PS: Yes, the OOM thingi is so so much better.... VAS usage is good so far.