I run my 2.5 "out of the box" and just test different settings for the sliders and it runs like a dream EVEN with PMDG 777. But I guess some people never learn and every time they see a posted tweak on the net, they have to add it to their .cfg even if the don´t understand anything.

Well observed and well stated. Like you, I've run it as it is, with the PMDG7777+FSDT+ with all my sceneries from FSX, other than Orbx,and managed over 9-hour flights without any OOMs.

I am in line with Jack and Lyn here, I would leave this out of the cfg

 

I have tried a lot of the tweaks as they are presented here in the forum, but after a while I always come to the conclusion that P3D runs best without tweaks.

 

On the fragile balance scale -performance/smoothness- in my humble opinion no tweaks is the best balance. The Lockheed Martin devs did an amazing job in optimizing this thing. I am still on 2.4 but I guess it is the same (or better) for 2.5

 

 

greetz,

 

 

I have absolutely no sympathy for you Pedro.  You caused the predicament and consequent frustration yourself by installing 2.5 before all program updates have been released. :mad:

 

If you had cared to investigate this forum you would have happened upon many warnings/cautions as to what was likely following the release of a new version of P3D. 

Appliance: To be honest with you I personally dont have too much time to sit and read every single post in this forums..I have the money. I get the stuff and have my expectations..now are u going to tell me that P3D was announcing "HEY GUYS WE WILL CHANGE THE ENTIRE STRUCTURE OF OUR NEW 2.5..SO IF YOU HAVE ADDOS GUESS WHAT THAT'S U PROBLEM"...... or just go back to college and register in one of their computer programming curses so you can TRICK this and this.....they mentioned improvements of this and that ..fixes will be improve etc...but in case they mentioned,,hey I dont read line by line I just trust them ...and hey, I am not going back to FSX neiher Xplane.......and last the last thing I need in my life is you sympathy SR....

Dont waist my bandwidth connection with you responses.....

Pedro

 

 

As far as Affinitymask, I would comment it out of the cfg (//) and see what it does. I would trust LM to know what is best for their software and that is: all cores/threads being utilized.

 

Lyn

I am going to just let the sim  the way it is...however the FSdream airports  Addon manager have some stuff there to move and change that I am definitely investigate what is the impact of the sim...but yes sometimes is better to keep our hands away and just fly......

Thanks you

Pedro

I am in line with Jack and Lyn here, I would leave this out of the cfg

 

I have tried a lot of the tweaks as they are presented here in the forum, but after a while I always come to the conclusion that P3D runs best without tweaks.

 

On the fragile balance scale -performance/smoothness- in my humble opinion no tweaks is the best balance. The Lockheed Martin devs did an amazing job in optimizing this thing. I am still on 2.4 but I guess it is the same (or better) for 2.5

 

 

greetz,

 

 

 

 

 

 

 

For sure I will and test...and yes wait a little be..I guess I am just little be anxious here...

Thanks

Pedro

 

 

but yes sometimes is better to keep our hands away and just fly.

I have come to that decision myself,   the hard way of course but its easiest way to remember 

Recently a retired captain, BA, user of Aerowinx PSX ( which I also am a proud user of... ) started an interesting series of tutorial videos and, on some of those videos who will be able to see scenery out of windshield which is not PSX native baseic scenery, but rather, as Peter ( Britfjet ) told us, P3D.

 

He is mainly concerned with the simulation of a Boeing 744-400, pretty much as simmers most probably are when using sophisticated high level add-ons like PMDGs, Majestic Q400... 

 

One this you can easily notice on Peter's videos is how SPARSE the scenery looks in his videos. The airports are more or less complex, probably payware airports, but apart from that you really see what I believe are sliders pushed well into the Left in P3D....

 

That's exactly what I am doing in FSX-SE when flying the PMDG 777 or the PSX 744.... I use ASN for the weather, and that's all!

 

Now, if I want to simulate GA flights, using one of my A2As or RealAirs... then I push the sliders to the right, and try to enjoy ORBS FTX Global with acceptable overall FPS everywhere. There I am flying low & slow, and it pays to have some nice scenery.... 

 

I guess I would follow exactly the same principles should I be using P3D.

Tamper with things you have no in-depth knowledge of, and one pays the devil!

Appliance, on 14 Feb 2015 - 04:49 AM, said:

I have absolutely no sympathy for you Pedro.  You caused the predicament and consequent frustration yourself by installing 2.5 before all program updates have been released.

 

If you had cared to investigate this forum you would have happened upon many warnings/cautions as to what was likely following the release of a new version of P3D. 

Appliance: To be honest with you I personally dont have too much time to sit and read every single post in this forums..I have the money. I get the stuff and have my expectations..now are u going to tell me that P3D was announcing "HEY GUYS WE WILL CHANGE THE ENTIRE STRUCTURE OF OUR NEW 2.5..SO IF YOU HAVE ADDOS GUESS WHAT THAT'S U PROBLEM"...... or just go back to college and register in one of their computer programming curses so you can TRICK this and this.....they mentioned improvements of this and that ..fixes will be improve etc...but in case they mentioned,,hey I dont read line by line I just trust them ...and hey, I am not going back to FSX neiher Xplane.......and last the last thing I need in my life is you sympathy SR....

Dont waist my bandwidth connection with you responses.....

Pedro

Your original post caused a lot of confusion and wasted a lot of people's bandwidth.  When someone upgrades a software package it just is good practice to read the instructions. That is just common sense.

 

 

I have absolutely no sympathy for you Pedro.  You caused the predicament and consequent frustration yourself by installing 2.5 before all program updates have been released.  
 
If you had cared to investigate this forum you would have happened upon many warnings/cautions as to what was likely following the release of a new version of P3D. 

 

Pedro's error was thinking of P3D the way he thinks of other software.  It's not, it's a ongoing beta testing program, except you get to pay to participate.  This is not sour grapes, it's reality, I know it and expect it, so I'm not frustrated.  Name one other piece of software that demands its vast array of 3rd party content developers to which it quite clearly benefits, has to standby ready to update installers with each new twist along the way.  Again, just reality--the core product is being moved in some very good directions and we all like that part.  The 3PD devs see there is real upside in P3D's future, so they I'm sure reluctantly have to play along w/ LM's development strategy.   That they have publicly all but committed to a 64-bit future really helps establish a future for P3D, and so again 3PD's have to think it's all worth it ultimately.

 

My personal solution which I fully still believe in is to avoid 'incremental' upgrades that start breaking some level of compatibility, require patches and new installers for legacy add ons.   Because of this I still use P3D 2.2, and it really works well including w/ PMDG T7.   Make no mistake--all of the trainees here (not simming hobbyists because as you well know P3D is not authorized for entertainment use) are being utilized as contributors to a what amounts to this ongoing beta testing project.  That's fine as long as you're ok w/ it going forward and I think most here appear to be, but my preference is to NOT update w/ every incremental change and make wholesale reinstalls no more often than every year or two.   I think the reason it is ultimately a good thing for LM to do what they are doing, as long as there are folks willing to play along, is that they thankfully see more upside in developing the core product, else they won't be doing this. 

 

If you're ok w/ helping LM move the product along incrementally, have at it.  I will indeed wait for 'all program updates' to be released before touching 2.5, which appears to be worthy of some hassle.  2.3 & 2.4?  Not so sure from everything I've read here.  Thanks in advance to all of you who are willing to be ongoing testing partners for those of us who are less willing.

Your original post caused a lot of confusion and wasted a lot of people's bandwidth.  When someone upgrades a software package it just is good practice to read the instructions. That is just common sense.

here we go now u are wasting my bandwidth again.....incredible....

Its Valentines Day,  lets all Virtually Kiss and make up,  Kixs Kiss Kiss,  See all friends again 

Pedro's error was thinking of P3D the way he thinks of other software.  It's not, it's a ongoing beta testing program, except you get to pay to participate.  This is not sour grapes, it's reality, I know it and expect it, so I'm not frustrated.  Name one other piece of software that demands its vast array of 3rd party content developers to which it quite clearly benefits, has to standby ready to update installers with each new twist along the way.  Again, just reality--the core product is being moved in some very good directions and we all like that part.  The 3PD devs see there is real upside in P3D's future, so they I'm sure reluctantly have to play along w/ LM's development strategy.   That they have publicly all but committed to a 64-bit future really helps establish a future for P3D, and so again 3PD's have to think it's all worth it ultimately.

 

My personal solution which I fully still believe in is to avoid 'incremental' upgrades that start breaking some level of compatibility, require patches and new installers for legacy add ons.   Because of this I still use P3D 2.2, and it really works well including w/ PMDG T7.   Make no mistake--all of the trainees here (not simming hobbyists because as you well know P3D is not authorized for entertainment use) are being utilized as contributors to a what amounts to this ongoing beta testing project.  That's fine as long as you're ok w/ it going forward and I think most here appear to be, but my preference is to NOT update w/ every incremental change and make wholesale reinstalls no more often than every year or two.   I think the reason it is ultimately a good thing for LM to do what they are doing, as long as there are folks willing to play along, is that they thankfully see more upside in developing the core product, else they won't be doing this. 

 

If you're ok w/ helping LM move the product along incrementally, have at it.  I will indeed wait for 'all program updates' to be released before touching 2.5, which appears to be worthy of some hassle.  2.3 & 2.4?  Not so sure from everything I've read here.  Thanks in advance to all of you who are willing to be ongoing testing partners for those of us who are less willing.

This is what i call constructive comment, and I absolutely agree with you on this...for some reason I miss the fact that LM is not for entertainment, To be more clear  I will never go back to FSX not matter how log it will take me to get use to WAIT or just fly instead of tweaking....I will support P3d , in fact is my favor Sim ..love the graphics...and the fact that is a live SIm development structure that I am sure will be better until finally jump to 64bit...at that point I will re-purchase again if necessary.

Thank you for you posting

Pedro

Its Valentines Day,  lets all Virtually Kiss and make up,  Kixs Kiss Kiss,  See all friends again 

jejejjee...yeah I just maybe need a drink...and leave the cfg do his job... :rolleyes:

The best thing that Microsoft did with FS was leave it open to 3rd party addon developers. The worst thing that Microsoft did with FS was leave it open to 3rd party addon developers.

 

 

No DX10 no tweaks in CFG except enablewidescreen=Enable

 

That's the wrong syntax Sidhant.

Should be:  WideViewAspect=True

 

gb.