I know a few post back guys were saying I was crazy that 20fps isn't smooth. Please stop by anytime and we will have a beverage and fly for awhile to prove it. I am going to unlock the frames tonightandsee what it does.

I just cant see how 20 fps can be smooth. I have tried every setting and fps combo i can think of in 2.0 and 2.1. But nothing comes even remotely close to the smoothness in fsx set at 30 fps with 1/2 vsync.

Edited February 14, 201412 yr by n4gix
Removed excessive quote. Please only quote a few relevant sentences, and not the entire post!

 

 

I think I've narrowed down my OOMs to either the vegetation slider or using AS2012 for weather.

 

We may be on to something here. I'm getting a visible memory leak, but using OPUS weather, so AS2012 is not a culprit in my case. However the trees are. Flying over visible trees at any altitude, I can watch the free VAS winding down towards an ultimate OOM. Set the vegetation slider to 0, and the figure remains static. So there's a very definite correlation with trees. Now there may be something else in my setup that is interacting with the trees in my specific case, but for me, the vegetation slider is equivalent to an 'OOM slider'.

 

The next question is - whose trees? Mine are Orbx FTX Global trees. Are these the specific trees, or do the default ones cause the same problem? What sort of trees are you using, NikkiA?

 

 

The next question is - whose trees? Mine are Orbx FTX Global trees. Are these the specific trees, or do the default ones cause the same problem? What sort of trees are you using, NikkiA?

 

The default autogen.

 

That was the most frustrating aspect of my OOMs, I'm running default scenery library except for some korean air 777 flight plans. I haven't added any of my scenery because until it's stable with default, what's the point?

 

 

Any luck making the taxi and landing lights work?

 

No, I posted over at QW forum, but Lars feels it's an LM issue even though all my other aircraft work fine ... so it seems unlikely we'll get a fix from QW.

 

 

I'm running P3D2.1 on Win 8.1 and I'm not getting any of those studders.

 

Thanks for the info Arwen.

 

 

No add ons pure vanilla p3d2 with updates micro stutters , no matter what settings in display, far right far left fps 24 or 80 with all display far left 80 to 100 fps with clear skies, cannot stop these stutters check my pc. Plenty power to run either fsx or p3d. Before update no stutters . after update  stutters.  I repeat no addons . Rob,glad you posted to Lockhheed on this.   

 

Thanks denny, what OS are you running?  What controllers do you have attached?  If any, what happens if you disconnect them all and fly just keyboard?

 

Think I'll start a new thread specific to stutters ... too much "told you so" blah blah blah ... just not productive.

 

 

There is a small issue I found. The P3D installer sometimes fails to install legacy Simconnect drivers. I was getting very frustrated with my FSDreamteam stuff, none of it worked. I manually selected them and bingo, all good.

 

Hmmm ...I haven't tried this ... need to check into it (thought I saw SimConnect in my Control Panel install program list, but I'll double check tonight.

 

 

The next question is - whose trees? Mine are Orbx FTX Global trees. Are these the specific trees, or do the default ones cause the same problem? What sort of trees are you using, NikkiA?
 
The default autogen.

 

That's interesting - a general tree / OOM problem, then. I'll post details over on the LM forum to see what they make of it.

 

Curiously, buildings don't seem to be a problem.

I think I've narrowed down my OOMs to either the vegetation slider or using AS2012 for weather. Both seem to cause VAS usage to steadily increase.

 

Granted I don't have a lot of testing time on v2.1, but the one "crash" I did have (the sim locked up and then crashed to desktop), was one of the times I was using AS2012. I was also changing some of the weather 'in-game'... which may have been dumb...

Rob, Windows 7 64 bit.   All Saitek ,Yoke, rudder pedals , 4  of the small pro panels gauges,  and the larger radio, multi, and switch panels. Have tried running with all disconnected except yoke and rudder pedals. Don't know if I remember how to even use keyboard been so long HA HA  Your system specs seem close to mine except I use a 65 inch tv as my main monitor and a 24 inch monitor for Flightsim commander, which is my flight planner and moving gps  I run fsx fantastic ,but was hoping to switch to p3d for the future of Flight Simming going forward with Microsoft dropping fsx. Been simming for 16 years . Yes I am Hooked. Fly with my son in real life I not licensed but he is . Fly in  Cessna  182

Word Not Allowed made a great point in his blog the other day. Those who have FSX running well will be somewhat dissapointed with P3Dv2. Those who have FSX running poorly, will see an improvement in P3Dv2.

 

That is also my experience. FSX has never run better particularly with the current addon load. It may take a couple of years to get addon loaded P3Dv2 performance on par. And by then, we should be beta testing P3Dv64bit at the very least!!!

I have had FSX running very well for a very long time, since this upgrade.  However since installing V2 I have not been able to complete an FSX route.   Visually it just looks dull to me by comparison!  Perhaps the DX10 approach for FSX might be the best of all possible options currently.  After reading about the myriad problems w/ 2.1 I am not going to waste time and frustration installing it as V2.0 works very well, though I was looking forward to a few more problems being solved.  I think LM has definitely lost my confidence in that their beta testing routine must be very flawed to allow all of this to seep through.  It really seems again like another alpha or at least beta release.   I know they have a tall order, that being building a more robust new rendering engine while retaining backwards compatibility, and indeed this may imply difficulties forever moving forward w/ this so it may be less about a bad beta testing routine than just inherent troubles in their mission.  Very disappointment to me, and even if it's just a near impossibility to 'get it right' under these circumstances, they've definitely moved the line backwards it would appear and will clearly have lost new customers and a few old ones at least over the short term.

 

 

I'm running default scenery library except for some korean air 777 flight plans.

 

Where did you find a Triple 7 to work and certified in P3DV2?

Logic for me,

 

Vanilla FSX < Vanilla P3Dv2

Mature FSX + MY must-have addons > "New" P3Dv2 + somebody else's must-haves

 

Hard to believe for me that in 2014 A.D. I'm still using FSX, but until I'm convinced that the balance has shifted, then that's that.  It took me 3 years after FSX release to change from FS9, and I hope it doesn't take that long for P3D, but that's how long it was before what I was able to do in FS9, with the money I was willing to invest, I felt was finally surpassed by FSX.

No, I posted over at QW forum, but Lars feels it's an LM issue even though all my other aircraft work fine ... so it seems unlikely we'll get a fix from QW.

 

OK, that's too bad but thanks for forwarding the info!

 

Edited to add that I think it's a pitty QW look at the issue that way because now with lots of people wanting to have a good a/c in P3Dv2.1 QW could sell lots of extra copies of their BAe 146. Oh well...

Edited February 14, 201412 yr by WebMaximus

...........After reading about the myriad problems w/ 2.1 I am not going to waste time and frustration installing it as V2.0 works very well, though I was looking forward to a few more problems being solved. I think LM has definitely lost my confidence in that their beta testing routine must be very flawed to allow all of this to seep through. It really seems again like another alpha or at least beta release. I know they have a tall order, that being building a more robust new rendering engine while retaining backwards compatibility, and indeed this may imply difficulties forever moving forward w/ this so it may be less about a bad beta testing routine than just inherent troubles in their mission.....

 

 

I have yet to install the v2.1 patch, I going to do a reinstall of the Win 8.0 OS first to fix some other stuff...so I'm somewhat unqualified to speak on this topic.

 

 I certainly hear what you (Noel) and others are commenting on-  my thoughts are that it's amazing that LM could get this far with all of that old and somewhat dysfunctional legacy FSX code.  I think LM are in a lose-lose situation, on one hand we all want a much better platform (which I'm sure LM could do in a year or so if they started with brand new code-  look at what they  code for the military),  but that would break the legacy add-ons, then we'd all be attacking them about that.  I'm sure the day will come when a 64-bit version is produced and that will be the start of the legacy add-ons being incompatible-  maybe it will take a 32-bit and a 64-bit version being made available concurrently, so that we can all make a choice- better code and no legacy add-ons, or code encumbered by the past and the ability to have legacy add-ons.  But even then we will all complain, and it will start a "war" between the "32" and "64" folks, if history is any example to go by when we have had to make a choice between platforms.

 

Sometimes i think we are all (including me) the most difficult user-base that there must be out there for developers...

 

Bruce.

Well, finally had the time to do a 'real' flight in v2.1 after solving the TrackIR not working problem. (Sigh...) The first thing I focused on was VAS usage so after installing FTX Global I installed FTX AU and the A2A C72. Everything seems to perform without any direct problems. Yes, even the A2A C172. Maybe this has to do with installing Simconnect manually...? (The P3D 2.1 installer failed to install Simconnect on my PC, hence TrackIr not working!).

 

I then started a flight from Lilydale, AU, towards the east. This flight gave me OOMs in v2.0 within 1 to 5 minutes with autogen at Dense. With v2.1 I got an OOM after 20 minutes and with autogen at Very dense. So there defenitely is an improvement here but I still have to rely on FSUIPC's AutoSave in order to complete a flight down under... which isn't good. It's better, that's for sure, but still troublesome. The OOM came with VAS at 3.6 whih is better than 2.6 for sure but I didn't get to hear the FSUIPC VAS warning: it's still too sudden and to soon.

 

To my utter shock TrackIR refused to work again in v2.1 after that OOM...! After some fooling around I had this solved by repairing Simconnect (using the Windows Add/remove programs screen). Really very strange... and odd... and not good. Although I am glad I didn't have to restore my entire system AGAIN...!!!

 

Positive news: the white lights (FTX) are gone!

 

Negative news: it's not totally smooth. I cured the stutters I had at first for a great part by disabling the FTX Vector Road lights but there still are some slight stutters every now and then. It just seems less smooth than 2.0. Which is strange because LM 'found the cause of stutters'. Well, not on my PC. 2.1 introduced them again. I have set fps to unlimited (which seems to work best) and I also did NOT use the affinity mask tweak in the cfg. I also had vsync off and triple buffering. Maybe fooling around with those settings may help a little (although after reading various posts about this I am not too sure that will work). It's not as bad as in Rob's video (in his topic about it) but similar. BTW At one moment the stutters became just as bad as in Rob's video but I found out that was due to FSUIPC's onscreen VAS monitoring. After turning it off again, things were better but still not perfect.

 

AA doesn't seem better at all on my PC (with a GTX580). I will try one of those NI tricks to make it better but I will have to see how much that will hurt performance.

 

I like the new options on the Startup Screen (Load, Save, Flight planner). Should have been there in 2.0 already of course.

 

So all in all I don't really know what to think of it. It's not the giant leap forward I was hoping, specially due to those Simconnect problems and the stuttering. When it DOES work, it's great but it still feels like a beta somehow. The biggest problem remains OOMs. (BTW I didn't notice a smaller autogen cone!) Not being able to fly east from Lilydale for longer than 20 minutes isn't good, even though I use FTX AU and autogen at Very dense. It's certainly better than it was but it remains problematic.

 

The next thing I will be doing is flying around with vegetation autogen at Dense and see where that gets me (with stutters and OOMs).

 

We still have a long way to go. One thing I do know, though: unlike the last few years I will be spending more time playing other games. I've been disappointed with flightsimming too often by now and I sometimes don't feel like flying at all anymore. But of course that also might have happened if I had stuck with FSX... ^_^

Where did you find a Triple 7 to work and certified in P3DV2?

 

 

The CS T7 does work in P3D2, if you use EMT's legacy mode...

 

But you misread the implication of what I said, they're AI flightplans, and it's just the Fruit Shack AI model... I was flying around South Korea a bit, and wanted some AI that wasn't an A321.

Damn... Had to repair Simconnect AGAIN just now. I really don't hope this is something I have to do everyday...!