P3D2 does honestly run better than X-Plane 10 does on my PC

 

X-Plane 10 was released on November 2011, how about we pick this debate up again in Nov. 2015, after LM has had 2 years to improve its initial release

 

If you'd said 'P3D2 runs better than XP10 on my PC' or 'P3D2 will run better in Nov. 2015 than XP10 does now', initially, we wouldn't be having this conversation.

Whichever platform can help me "train" to do this as accurately as possible -- wins!!

 

 

Fair deal?  

 

I gotta go fly Wales now and find this little gem of a spot!

 

Ah, HD videos of the Mach Loop in Wales. One of my favourite YouTube timewasters:)

And again I am getting OOMs with autogen at Dense, the default Acclaim and FTX AU SP4. That last one apparently simply is too heavy for P3D v2...? I had an OOM after some five minutes, VAS at 3.0 and after restarting I had an OOM within 30 seconds, VAS at 2.5. This sucks big time...

Sad to hear... It must be something about the autogen fade-in (which I have disabled), since I run autogen at extremely dense (LOD 4.5) and have no OOM problems presently.

So, we need to face those autogen pop in again, like in fsx?

So, we need to face those autogen pop in again, like in fsx?

 

Kinda brings up the point that maybe those FSX programmers knew exactly what they were doing..........

 

Right now LM is probably a little stuck between their new stuff and the old FSX stuff.

 

Frankencode.

So, we need to face those autogen pop in again, like in fsx?

 

No!... running it fine, along with Volumetric Fog and some, if not all of the availible shadow options.

 

With these settings, which is far from maxed, but looks decent, and better than I have FSX  - full saved settings below - I have run FTX AU-SP4 almost all day long without an OOM... This is with default aircraft, or Ant's Tiger Moth. REX4 2048 clouds - 4096 Airport textures @32bit... 2048 max texture load in sim.

 

 

 

[GRAPHICS]

TEXTURE_MAX_LOAD=2048

NUM_LIGHTS=4

MIPMAP_VC_PANELS=1

TESSELLATION=1

COCKPIT_HIGH_LOD=1

AIRCRAFT_REFLECTIONS=1

LANDING_LIGHTS=1

DAWN_DUSK_SMOOTHING=1

LENSFLARE=1

HDR=1

BLOOM_LEVEL=2

SHADOW_QUALITY=3

CONTENT_NO_SHADOW=0

INTERIOR_SHADOWS_CAST=1

EXTERIOR_SHADOWS_CAST=1

SIMOBJECT_SHADOWS_CAST=0

TERRAIN_SHADOWS_CAST=1

VEGETATION_SHADOWS_CAST=0

BUILDING_SHADOWS_CAST=1

CLOUD_SHADOWS_CAST=0

INTERIOR_SHADOWS_RECEIVE=1

EXTERIOR_SHADOWS_RECEIVE=1

SIMOBJECT_SHADOWS_RECEIVE=0

TERRAIN_SHADOWS_RECEIVE=1

VEGETATION_SHADOWS_RECEIVE=0

BUILDING_SHADOWS_RECEIVE=1

SHADOW_DRAW_DISTANCE_LOW=4000

SHADOW_DRAW_DISTANCE_MID=6000

SHADOW_DRAW_DISTANCE_HIGH=8000

SHADOW_DRAW_DISTANCE_ULTRA=12000

SHADOW_NUM_CASCADES_LOW=4

SHADOW_NUM_CASCADES_MID=5

SHADOW_NUM_CASCADES_HIGH=7

SHADOW_NUM_CASCADES_ULTRA=12

SHADOW_LOG_PARTITION_LOW=0.850000

SHADOW_LOG_PARTITION_MID=0.850000

SHADOW_LOG_PARTITION_HIGH=0.850000

SHADOW_LOG_PARTITION_ULTRA=0.850000

EFFECTS_QUALITY=1

EFFECTS_DISTANCE=1

[DISPLAY]

SKINNED_ANIMATIONS=1

TEXTURE_BANDWIDTH_MULT=60

UPPER_FRAMERATE_LIMIT=30

TEXTURE_FILTERING=16

MSAA=8

SSAA=0

FXAA=0

VSYNC=1

TRIPLE_BUFFER=1

WideViewAspect=1

FullScreenExclusive=1

FullScreenAutoFill=1

[PANELS]

PANEL_OPACITY=0

[sCENERY]

IMAGE_COMPLEXITY=5

[TERRAIN]

LOD_RADIUS=5.500000

TESSELLATION_FACTOR=85

MESH_RESOLUTION=25

TEXTURE_RESOLUTION=27

AUTOGEN_VEGETATION_DENSITY=4

AUTOGEN_BUILDING_DENSITY=3

DETAIL_TEXTURE=1

WATER_REFLECT_CLOUDS=1

WATER_REFLECT_USERAIRCRAFT=1

WATER_REFLECT_SIMOBJECTS=1

WATER_REFLECT_TERRAIN=1

WATER_REFLECT_AUTOGEN_VEGETATION=1

WATER_REFLECT_AUTOGEN_BUILDINGS=1

WATER_REFRACT_CLOUDS=0

WATER_REFRACT_USERAIRCRAFT=0

WATER_REFRACT_SIMOBJECTS=0

WATER_REFRACT_TERRAIN=0

WATER_REFRACT_AUTOGEN_VEGETATION=0

WATER_REFRACT_AUTOGEN_BUILDINGS=0

ENABLE_BATHYMETRY=0

WATER_CLARITY=30

WATER_DETAIL=4

[WEATHER]

CLOUD_DRAW_DISTANCE=6

DETAILED_CLOUDS=1

OPTIMIZE_DENSE_CLOUDS=0

CLOUD_COVERAGE_DENSITY=8

THERMAL_VISUALS=0

DownloadWindsAloft=0

DisableTurbulence=0

VolumetricFog=1

[TrafficManager]

AirlineDensity=20

GADensity=25

FreewayDensity=10

ShipsAndFerriesDensity=20

LeisureBoatsDensity=10

IFROnly=0

AIRPORT_SCENERY_DENSITY=2

 

 

 

I have run FTX AU-SP4 almost all day long without an OOM

 

Well, then it must be my PC... I use lower settings than you do and can't fly for 5 minutes without an OOM above FTX AU SP4. The problem is this is on a fresh OS so reinstalling the OS won't help either here. I just disabled FTX AU and flew above FTX Global for a while: no OOMs. But if I can't use FTX regions, I don't know what I am going to do with all this... I already couldn't use the Norway freeware anymore and I don't feel like flying above FTXG only. I really hope the upcoming patch will do wonders...

FTX AU SP4. That last one apparently simply is too heavy for P3D v2...?

 

I've not had any luck with FTX regions ... but the OpenLC seems fine.

 

LM did change the AutoGen system (for the better IMHO), but in doing so they may have created some unexpected results.  

 

Like I said in my LM forum post, I think it's a threading timing issue and/or contention problem ... those of VERY difficult to track down and in some cases you just have to resort to what I call "safety code".  What I mean by that is I know about where the problem could be but can't positively duplicate it consistently ... so I add code to check conditions and adjust accordingly (may or may not be successful).  There's also "defensive code" ... checking for condition that you never ever think can happen, but sometimes does happen.  But bare in mind, the less code you have the faster the product is ... so conditional checking isn't something one always does when one expects a situation to never happen.

 

And there is also debug only type code to log to file or whatever, but again, that process in itself can skew the process and prevent it from happening.  So in a word, it's a big challenge!  I'm not trying to defend LM, I'm just giving you some insight into the development process and issues I've bumped into before and had to resolve.  But the problem is solvable, and I hope LM solve it rather than go back to the old way of AutoGen.

 

Like the most noble moderator of this forum suggest, be patient and give it time.  I'm cautiously optimistic and LM say they are still on schedule for a Jan release of a patch (so worst case that's only two weeks away).  In the mean time, I'm exploring the million other things I can do with flight simulation, FMC, flight planners, NavData, programming my GoFlight modules ... that'll keep my busy for at least 2 weeks.

 

Cheers, Rob.

Well, then it must be my PC... I use lower settings than you do and can't fly for 5 minutes without an OOM above FTX AU SP4. The problem is this is on a fresh OS so reinstalling the OS won't help either here. I just disabled FTX AU and flew above FTX Global for a while: no OOMs. But if I can't use FTX regions, I don't know what I am going to do with all this... I already couldn't use the Norway freeware anymore and I don't feel like flying above FTXG only. I really hope the upcoming patch will do wonders...

 

Keeping in mind how many reports there are around regarding OOM's in P3D.2 i dare saying - it most likely ain't Your PC!

For now maybe the best thing really is to wait and see what the announced first SP will have to offer.

Cheers, Christoph

And again I am getting OOMs with autogen at Dense, the default Acclaim and FTX AU SP4. That last one apparently simply is too heavy for P3D v2...? I had an OOM after some five minutes, VAS at 3.0 and after restarting I had an OOM within 30 seconds, VAS at 2.5. This sucks big time...

 

This is really bizarre as I have way more loaded along with AU SP4 (REX4, OPUS, B1900D) without an OOM even after hours. However, I'm not using Nvidia Inspector, and the only cfg tweaks I'm using are TML and AM. Can you post your settings? And are you running any tweaks in the CFG and NI?

However, I'm not using Nvidia Inspector, and the only cfg tweaks I'm using are TML and AM. Can you post your settings? And are you running any tweaks in the CFG and NI?

 

Hm, NI... I might see what happens when I restore the default nVidia profile but one thing I know is that things will look horrible in P3D, with a completely shimmering VC... Still, I will give it a go.

 

I only use the AM tweak and the shadows tweak (distance at 12000) and here are the settings I like to use for now with my current PC:

 

http://farm8.staticflickr.com/7411/11684016824_3b21cd417f_o.jpg

 

EDIT I just noticed I changed a few settings in the meantime: MSAA is at 4x (in order to work with NI) and Tesselation is at medium. ANd with FTX AU I use autogen at Dense.

Patience grasshoppers. There are at least three specific memory leak issues being addressed in the January patch. The increasd frequency OOMs in P3D at higher density settings is one of the problems that LM has promised they are investigating. I have confidence that the patch will bring the frequency of OOMs back to FSX levels or below while still having the GPU features of DX11.

I got my answer, no 64bit any time soon (beyond 2 years out)

 

It's absolutely on their radar though and well you know--2 years goes by pretty fast ;o)

 

P3D V2 just looks and runs fabulously once you can tame the OOMs, which I clearly have though I'm never sure how.  That a product like that has built in scalability such that it can't really be run full tilt IMO is a very good thing, and I am guessing as they fully understand the code they are optimizing (for performance primarily) the jump to 64-bit will be somewhat rote, i.e. they don't have to redesign the whole sim, so they are building on a platform I believe that will essentially endure but in 64 bit form at some point.  I won't be purchasing much if any content for V2 since it is clearly a temporary platform, i.e. one NOT to invest in for the long haul.  And fortunately many FSX apps will run on it.  Quite frankly I'd rather see PMDG hold off on supporting V2 because of the temporary nature of V2--that way I'm not tempted to pay what they will charge for it for what amounts to limited use!

 

 

As for running better, the fact you posted this on page 9 of a thread about OOMs should be proof enough that's not true. You might be able to tank your frames by setting all sliders to max in XP10, but one thing you don't need to do is spend your flights worrying about when the sim is going to CTD or OOM.

 

There's a heck of lot more to 'running better' than simply absence of risk for OOMs.  I have yet to have an OOM, and use FTXG, REX3, QW757, MD80 Pro & RA Duke, and have done cross country flights for 4+ hours.   I tried the XP64 demo and was so unimpressed graphically & performance-wise that I uninstalled it fairly quickly--OK, too quickly.  But really, not very impressive.  I think I need to install add-on scenery to help I guess.  P3D V2 runs like butter, looks unbelievably realistic and crisp (albeit it DOES need better AA).

I tried the XP64 demo and was so unimpressed graphically & performance-wise that I uninstalled it fairly quickly--OK, too quickly. But really, not very impressive. I think I need to install add-on scenery to help I guess. P3D V2 runs like butter, looks unbelievably realistic and crisp (albeit it DOES need better AA).

 

 

I did the exact same thing just a couple of weeks ago. I gave it about an hour or two and removed it, but I think it was my problem and not X-Plane. I think it was just too far removed from what I'm used too, couple that with an unintuitive GUI and the thought that if I bought it I would have to start all over again, was too much to bear. I wasn't bowled over by the way it looked or performed, but clearly both of those things takes time to address... and the same can be said of FSX/P3D in default form.

 

Having looked at the screenshots forum here, it is very clear that X-plane can look amazing, and people have it running well too... but like many others its not for me, at least at this point in time.

 

I still like reading about it, and looking at the screens people post, and think the sim-wars type posts [not the above I must add] is utterly crazy.

 

 

Anyway, I'm very glad I'm not the only person not being plagued by OOM's and other crashes... you start to feel like your BS'ing when all around you seems like they are having problems.

 

 

It's absolutely on their radar though and well you know--2 years goes by pretty fast ;o)

 

But as they say "there's many a slip between cup and  lip" and 2 years can be a  long tome.