Crap, I just got the memory error popup. I was on AP @ 3000 ft with a little bit of left rudder plugged in so I could do a circle around KSEA area. I left for about 30 minutes, came back and had the message. I fired up the same saved flight and GPU-Z and I was only using 1.5gb of the 4gb available on the card. I have 8gig of system memory but CPU-Z does not show useage.  Someone posted the same issue in this thread and he had stated that it was VAS. Not sure what that means. Is that GPU mem?

 

What tool can I use to monitor system memory?

 

Bob

Curious. Which aircraft?

Curious. Which aircraft?

Default Carenado A36

 

Bob

Well, I uninstalled it.  Autogen is now drawn in a limited radius, just like FSX, and pops in at fairly short range, just like FSX.  There are now blurries, just like in FSX.  And now there are stutters, just like in FSX.  Except for HDR, which I do like, and shadows, which I mostly can't use without too big a hit to FPS, there doesn't seem to be any advantage anymore, and almost no addons are supported for it.  Texture loading is slower than FSX.  Planes take forever to load in from external view and do so pieces at a time.  There are strange graphic flashes all the time.  

 

And that's a fresh install of 2.1 with ONLY P3Dv2 supported addons installed (just the Orbx scenery offered with P3Dv2 installers).  Nothing else.  No tweaks, no FSUIPC.  Nothing.  So, the problem is not me, or my machine, but P3D.  The only benefit over 2.0 is that I didn't get an OOM in my limited testing (something I got almost every flight with 2.0 after a short time).  Everything else seems worse.  

 

I'm glad I only bought a month long developer's license to test it out.  So, only $10 spent.  I sure wanted to like it, and hoped for improvements, but for every step forward there seems to be at least one step back.  

Mipmapped VC isn't working for the Q400, but does work on some other Aircraft ... seems to be aircraft dependent.

That's good to know, but "not working" in what sense? With 2.0, if you had that box checked and used various 3rd party complex aircraft, it would cause a CTD. I assume that's what you mean.

I see the facts and I accept them and it's not really a problem for me ...

I think that's a good approach if it is ok for you. I also have to accept what I see, but I don't like it...

 

 

 

perhaps it's your expectation that's the issue?

 

 

Maybe that's true. My expectation is that all resources in terms of GPU and CPU power are fully used (which they are not) and that P3D2 doesn't perform much worse than FSX because from my point of view it only adds some eye-candy compared to FSX which should be possible to achieve without a significant loss in fps (or smoothness) just by taking advantage of todays GPUs. There is no game-changing new functionality or breathtakingly different graphics compared to FSX (and that's a difference to your Crisis example). Maybe these expectations are too high... Maybe I was just hoping that LM is able to achieve this and now I'm disappointed. Everybody is different. And the good thing is: Everybody has a choice. Some will accept P3D2 in its current state and others won't. Time will tell...

 

 

and almost no addons are supported for it.

 

Here is the master compatibility list for add-ons that work in P3DV2.x: http://forum.avsim.net/topic/426926-p3d-v2-master-compatibility-list/ many (not all) add-ons do indeed work.

 

Here are the Orbx product compatibile with P3DV2.x:

http://www.orbxsystems.com/forum/topic/68566-master-list-of-all-p3d2-ready-orbx-products/

 

Here is the most recent Orbx common libraries you'll need to install AFTER install other Orbx products: http://www.orbxsystems.com/forum/topic/72009-orbxlibs-for-p3dv2/

 

I've removed Vector v1.0 (waiting for v1.1 due Feb 22nd) and EU Ireland v1.0 as they have some issues, they work in P3DV2 but not what I would consider working well.

 

But it's probably a good idea to judge P3V2.x on a fresh install without Add-Ons, otherwise you're probably not doing yourself or the product justice.

 

The only thing that surprised me with P3DV2.1 is the stutters, never had the problem before in at any significant level.  But this could just be a nVidia driver issue and not an LM problem ... I can count numerous big name 3D shooter titles that had very similar problems with stutters and it took a few months for nVidia to release drivers/profiles that corrected the problem.  LM have submitted the P3DV2.1 to nVidia for review, so hopefully we'll see a driver profile out of them (not sure about ATI side?).

 

Rob

That's good to know, but "not working" in what sense? With 2.0, if you had that box checked and used various 3rd party complex aircraft, it would cause a CTD. I assume that's what you mean.

 

No, as in the MFD's don't light up if you have VC mipmapp checked.

There is a significant performance increase as a result of overclocking a GTX780.

 

I added 220Mhz to the Core clock

and the same to the Memory clock in Afterburner.

In the default flight running but with static image VC image

just sitting on the Runway only the clouds moving the frame

rate increased by about 25% after I applied the new clocks in afterburner.

That's about as much as I can OC this card and stay afloat.

 

 

I did this with everything maxed out.

Not the way to run the sim but that

Equals a big increase with any settings.

 

Just a observation for anyone interested

 

 

Here are the Orbx product compatibile with P3DV2.x:

http://www.orbxsyste...-orbx-products/



Here is the most recent Orbx common libraries you'll need to install AFTER install other Orbx products: http://www.orbxsyste...libs-for-p3dv2/

 

Thanks Rob but those links are not working!

There is no game-changing new functionality or breathtakingly different graphics compared to FSX (and that's a difference to your Crisis example).

 

HDR is considerably better, volumetric fog is amazing, many more shadow options, pop free autogen ...

 

If you can make FSX look as good as this:

 

or this:

 

Then I'll paypal $100 to you.  Above is "as is", hop in and fly at a given airport using four 3rd party products, Sim720 Oban, Aerosoft Thessaloniki, REX 4 Texture Direct, FTX Global.

 

The cycle from FS9 to FSX is almost identical to the cycle from FSX to P3DV2.x ... yes time will tell and if history repeats most will be on P3DVx.x at some point within the next year or two (unless LR or someone else comes out with a game changer).  

 

Rob

 

 

I left for about 30 minutes, came back and had the message.

 

A couple of times in FSX I left my aircraft sitting at an airport, unpaused, and came back 20 minutes later to find FSX had closed itself.  No idea why, and I didn't know about the Event Viewer at the time. 

 

There may be a Windows problem at work here.  I suspected the screen saver kicking in, but that's not supposed to happen.  Could be something else related to it if you aren't doing any kind of input for an extended time.  Others have no problems leaving a flight running overnight, so it's more likely a problem with our specific systems.  Just in case, I made a special desktop theme especially for FSX that did not have the screen saver enabled.  I had no problems since, but then I don't leave my aircraft unattended very long at a time.

 

Hook

 

 

Thanks Rob but those links are not working!

 

They work for me?  Are you a registered user?

Here is the master compatibility list for add-ons that work in P3DV2.x: http://forum.avsim.net/topic/426926-p3d-v2-master-compatibility-list/ many (not all) add-ons do indeed work.

 

Here are the Orbx product compatibile with P3DV2.x:

http://www.orbxsystems.com/forum/topic/68566-master-list-of-all-p3d2-ready-orbx-products/

 

Here is the most recent Orbx common libraries you'll need to install AFTER install other Orbx products: http://www.orbxsystems.com/forum/topic/72009-orbxlibs-for-p3dv2/

 

 

Yes, I know all that.  I wasn't talking about addons that maybe will work in P3D.  I was talking, specifically, about addons that are supported for P3D, which is why I said almost no addons are supported.  

 

Perhaps, after LM figures this all out, if they do, and make enough money doing so that they don't dump the project because of all the hassles, and developers start supporting P3D, which they might, but might not, I'll try it again.  

 

HDR is great.  Volumetric fog isn't usable for everyone, nor are shadows (at least terrain, vegetation and object shadows).  Autogen pop now again in 2.1 just as in FSX.  

Autogen pop now again in 2.1 just as in FSX.

 

It certainly isn't for me.

This is the point. Regardless of all the nice looking graphical features, 18 to 24 fps at a busy airport with a plain vanilla install on high end hardware (GTX 780) is ridiculous! And it even gets more ridiculous when you look at GPU and CPU utilization. What's so difficult to understand about it?

 

Am going to be waiting with anticipation to see the paper you put to the P3Dv2 team on how to improve the sim engine further. Lots of moaning in this thread and not one workable and constructive solution apart from this one that has been mentioned a few times - turn your frame counter off and enjoy what you have. I used to be the same as you, chasing frames and getting annoyed. It is a hard addiction to stop, but you can break it.

I totally support LM with the development and improvement of P3D, but tbh, my addon packed FSX is simply running beautifully. It remains to be seen whether P3D is gonna make or break under the same load, plus water is still visually terrible and the spinning clouds is kinda laughable. 

It certainly isn't for me.

 

You need to look again.  Take a flight over any urban area.  What used to be autogen drawn out to the edge of your field of vision in 2.0 is now drawn only out to the radius that was about usual in FSX, and as you fly further, areas of autogen will pop in just as they used to.  I just flew over Melbourne, from Lilydale, and there was no city to see until I got fairly close, and then, just as the good old days, a few skycrapers popped into otherwise empty landscape, and then, as I got closer, buildings popped more and more until I could see a city.  This has been confirmed by a good many people.  Try it again yourself.