On 6/14/2019 at 9:23 AM, Bert Pieke said:

You might just want to try V4.5. (Client upgrade only), after backing up your current install so you can go back to it..

The scenery visuals have improved, especially with higher resolution photoscenery which Orbx uses near airports all over the place.. It really does look better..

Thanks Bert but it sounds like a royal PITA, upgrading all the planes to 64-bit status, etc...then having to do a complete new install when my current hardware gives up the ghost, and right now it's living on borrowed time.  I look forward to the total upgrade because I know I will see some significant improvement even in visuals and performance, but remain in no hurry until the box dies.

As others have said, it’s worth updating the gpu. If you are patient it might make sense to wait until the next gpu cycle to happen so that you can pick up one of the current RTX cards cheaper (so you can use ray tracing, if that appears in future flight Sims). If you can’t afford it don’t bother,  none of this is important. 

The other thing is the price of prepar3d in the first place - it’s a couple of hundred dollars unless you are a student. 

When I think back to FSX or fs98 then p3d 4.5 is worth every penny. 

Each time I startup the sim sitting in the fs labs, maddog or pmdg.... 

The morning or evening sun is shining trugh the window when I takeoff and I can see the thousands of buildings ( te gb south or klas....) 

It was worth every penny. 

It's simply amazing. 

 

 

 

You will get the fantastic extra Saudi Airport of Sharuah

https://en.wikipedia.org/wiki/Sharurah_Domestic_Airport

Where you can fly a Saudi or NAS flight to a staggering 4 destinations. 

Who needs updated airports like joburg, doha, murcia or Istanbul when you got this hidden Saudi gem

Maybe the USAF will use it when trump invades Iran.  

Year of the simmer and all that eh Simbol,I bet your mate didn't let you in on the Sharuah secret when he chatted you up at the conference last year did he.  😊🎉

 

Edited June 23, 20196 yr by fluffyflops

On 6/7/2019 at 11:34 AM, MarkW said:

Not when P3D v5 forces the issue and they no choice.  Let hope....I am looking at you PMDG and ORBX.

id be willing to bet 100 dollars,Pounds or  euros that when you fly into EGLL or KLAX on v5  it will still be stutter fest when using a payware a/c like the pmdg or fsl 

 

1 hour ago, fluffyflops said:

when you fly into EGLL or KLAX on v5  it will still be stutter fest when using a payware a/c like the pmdg or fsl

Is this not already the case in V4 ? Also is it really planes that kill performance ? I would rather think it is scenery

No more cursed OOM errors.

Yea, for me it was going from 32 to 64bit, better photoreal scenery and extending autogen out farther.  Big improvements.

51 minutes ago, jfri said:

Is this not already the case in V4 ? Also is it really planes that kill performance ? I would rather think it is scenery

It's everything combined that exceeds the processing power of whatever hardware you're on.  Since it's a simple matter for the developer to add features controlled by sliders that easily exceed anyone's hardware the real cause of killed performance is...failing to live within your hardware performance budget, and then being disappointed that it's...a stutter fest!

Edited June 23, 20196 yr by Noel

51 minutes ago, jfri said:

Is this not already the case in V4 ? Also is it really planes that kill performance ? I would rather think it is scenery

nope its been an issue since the start, its still the same fsx engine dressed up and modified (for the better).  but its still the same fsx engine.   Same hooker, different snazzy dress.

7 hours ago, jfri said:

Is this not already the case in V4 ? Also is it really planes that kill performance ? I would rather think it is scenery

Although complex planes make matters worse, I agree that it is scenery complexity that drives the engine to its knees. Somehow the P3D engine and Windows I/O handling are not able to keep the fluidity going while lots of detailed scenery is being loaded and displayed.. You might think that scenery loading could be done discreetly in the background.. but in this sim, it can stop the action cold..

They can make matters a *lot* worse. Before I upgraded last year, I used to turn off the co-pilot's displays in the PMDG 747. That helped. I also ran the low-res cockpit (you can enable it in the PMDG settings menu on the FMS) which helped. But I'd still get stop-motion framerates any time I flew into a populated area whereas with other less hi-fidelity planes I'd get at least 20fps.

This was kind of an issue since 747s generally don't spend a lot of time at regional airports out in the country. 😉

 

17 hours ago, Bert Pieke said:

...... You might think that scenery loading could be done discreetly in the background.. but in this sim, it can stop the action cold..

I find for my sake, given the photo scenery I use and that I like autogen trees when I am not in photo scenery, plus systems heavy aircraft now, toning down anti aliasing helps a lot without losing much in sharpness or jaggies being added.  Anti Aliasing can exponentially load a sim.  Also, by toning down AI, just having enough to enjoy it on landing or watching it zoom by in the flight levels, it helps me in P3D quite a bit.  For some reason AI, autogen, heavy scenery and so on does not have any impact in Xplane11, but there I still tone down anti aliasing. 

I also do not let aniso filtering exceed eight in either sim, again I still have sharp scenery, plus the fluidity I prefer in both sims.  In P3D I have my fps locked now at 25 fps because it helps with texture loading and fluidity, because it is the variation of fps in flight that can sometimes give the sim a herky-jerky feel. 

I could go higher but I do not mind.  I also use Nvidia inspector to set my Vsync rather than the sim, and also use the Adaptive setting there.  Last Jim Young instructed me to turn off my cpu Turboboost.  I could not do this in BIOS because my BIOS was locked down, but I found Throttlestop online and that was able to allow me to turn off Turboboost--again to reduce variations in framerate....

I also removed setting core affinity in the .cfg file, made no difference except for placebo effect, as was pointed out to me here by another member.

John