This is someone who does not understand alot about systems, so will PD3 work w/ a W7 64 Bit system or are you speaking of add-on's using 64 bit, I know it says 32 bit OS but I have FS9 a 32 bit program running on a 64 system. There is no such thing as a dumb question LOL

P3D is a 32bit app. But it will run on a 64 bit OS as they have capabilty to run both. Program Files X86 (32 bit) and Program Files (64).

I never used more than default LOD and textures larger than 1024 and never use higher settings than max default cloud density, but still get OOMs sometimes at complex sceneries with complex planes and such at moderate settings, but I guess FSX was never designed to use hundreds of complex sceneries and planes either...

Thats the thing, you say your not running textures larger than 1024 then a few words later say your running complex scenery addons. If you look in your scenery addon texture files I would be willing to bet the house that they are littered with over sized HD textures that you never bothered to resize yourself and thats the problem. Combine that scenery with AI, weather, complex a/c that comes with larger textures and your going to push the limits.

 

Now you can say that your TML is set to 1024 so it fixes it. Wrong, all that does is keep FSX from displaying the largest size texture map, be it the 2048 or 4096 that is in your addon scenery, but the whole size of the texture still gets loaded into memory, just not displayed at the largest size.

 

If you own a lot of addon scenery like I do from FlyTampa, Flightbeam, Orbx, LatinVfr, Taxi2Gate, etc., you'll find lots of textures larger than 1024, so if you didn't resize them yourself, you are indeed running textures larger than 1024 even if you think you weren't or what your TML is to.

 

So you say FSX isn't designed to run lots of complex scenery. It is, I do it all the time with no problem, but its up to you to check the developers work and make the texture adjustments yourself. The good news is some developers like FSDT with Vancouver give an option in the installer to install 1024s or FlyTampa with Montreal give that option in the installer. All the other devs, your on your own to do the resizing.

Thats the thing, you say your not running textures larger than 1024 then a few words later say your running complex scenery addons. If you look in your scenery addon texture files I would be willing to bet the house that they are littered with over sized HD textures that you never bothered to resize yourself and thats the problem. Combine that scenery with AI, weather, complex a/c that comes with larger textures and your going to push the limits.

 

Now you can say that your TML is set to 1024 so it fixes it. Wrong, all that does is keep FSX from displaying the largest size texture map, be it the 2048 or 4096 that is in your addon scenery, but the whole size of the texture still gets loaded into memory, just not displayed at the largest size.

 

If you own a lot of addon scenery like I do from FlyTampa, Flightbeam, Orbx, LatinVfr, Taxi2Gate, etc., you'll find lots of textures larger than 1024, so if you didn't resize them yourself, you are indeed running textures larger than 1024 even if you think you weren't or what your TML is to.

 

You make some good points offcourse and I have never lowered the TML to 1024, only lowered cloud textures to 1024 in the FEX program(clouds)and where an easy to use GUI available lowered textures in my complex planes, you got me. So I guess I run all airports at the 3party's settings, also I wouldn't like to have lower res on them as I like the detail. And I have to say manually resize all the textures in my hundreds of scenery's would be to much work even if I knew how to do it and Im lazy

 

Learned something new today :rolleyes: I'll admit that I may gotten over my head when I quoted you and your right, I may not know enough to run this program properly....

 

But all that doesn't explain why FSX can't reset the VAS when leaving the area where these textures are but let it "remember them even when the program don't need them" and let it keep growing and growing the longer time we fly, and that scenery not even used at the moment nibble off the VAS limit? Did they design it that way on purpose? Are we gonna get into the same issue with prepar3dv2? Is it impossible to solve without going 64 bit?

 

Enlighten me B) Excuse my ignorance..

So you say FSX isn't designed to run lots of complex scenery. It is, I do it all the time with no problem, but its up to you to check the developers work and make the texture adjustments yourself. The good news is some developers like FSDT with Vancouver give an option in the installer to install 1024s or FlyTampa with Montreal give that option in the installer. All the other devs, your on your own to do the resizing.

 

If it was, shouldn't it be able to handle the complex addons without me as a user have to be a computer "wizkid" and rocket scientist to be able to use them without manually edit hundreds of addons just because they designed it only to use 1024 res textures and whatnot. Shouldn't they maybe fixed that when they knew that most devs would break that limit? Or is it impossible and only way to make it work would be to make it a 64 bit SIM?

You make some good points offcourse and I have never lowered the TML to 1024, only lowered cloud textures to 1024 in the FEX program(clouds)and where an easy to use GUI available lowered textures in my complex planes, you got me. So I guess I run all airports at the 3party's settings, also I wouldn't like to have lower res on them as I like the detail. And I have to say manually resize all the textures in my hundreds of scenery's would be to much work even if I knew how to do it and Im lazy

 

Learned something new today :rolleyes: I'll admit that I may gotten over my head when I quoted you and your right, I may not know enough to run this program properly....

 

But all that doesn't explain why FSX can't reset the VAS when leaving the area where these textures are but let it "remember them even when the program don't need them" and let it keep growing and growing the longer time we fly, and that scenery not even used at the moment nibble off the VAS limit? Did they design it that way on purpose? Are we gonna get into the same issue with prepar3dv2? Is it impossible to solve without going 64 bit?

 

Enlighten me B) Excuse my ignorance..

 

If it was, shouldn't it be able to handle the complex addons without me as a user have to be a computer "wizkid" and rocket scientist to be able to use them without manually edit hundreds of addons just because they designed it only to use 1024 res textures and whatnot. Shouldn't they maybe fixed that when they knew that most devs would break that limit? Or is it impossible and only way to make it work would be to make it a 64 bit SIM?

1. The FSX SDK never said that you could use larger than 1024 texture sheets. If i recall it was ******* aka Bojote, you must have heard of him from his tweaking tool, that made the discovery that you could go up to 4096 texture sheets. Then the developers took it and ran with it, bu this wasnt how Aces intended for FSX to be used, hence the problems people are having now. Years ago before the HD revolution you didnt hear of as many OOM problems until REX, Orbx and other devs started pushing HD textures and sceneries.

 

2. I've told you how you can fix it, its your choice to not be lazy as you said, not me, and learn to do it a little at a time or just wait for a 64 bit version of P3D. While the new version of P3D might help a little, but its still a 32 bit program.

 

3. Running airports with 1024 textures doesnt look all that much different than 2048 or 4096 unless you get real close to a building. If you fly airliners its perfect because you normally dont get real close except when you park, otherwise you probably wont notice a differenc. Most of all the older FSDT sceneries as well as Aerosoft are 1024 and no one is complaining that its not detailed enough.

 

I've learned a lot about this stuff thru the years from various people here at Avsim. One guy who goes by cmpbellsjc has posted some stuff in the PMDG forums with instructions on resizing textures as well as what formats to use, ie DXT5,3, or 1 depending on the type of texture and composition.

 

The only other thing you can do is lobby developers to stop using large texture that kill memory or at leat offer a choice of which ones to install via the installer.

 

It is what it is. As they say, theres no free lunch in FSX regarding performance. You can fix it yourself one scenery at a time like I do, or lower your settings considerably, not use your addons, or just fly less demanding aircraft that dont consume a lot of resources. Your choice, but I prefer to make mine work good by putting the effort. Once its done its done. As edetroit the screen shot master once said, you contol the sim, dont let it control you. Wise words.

Now you can say that your TML is set to 1024 so it fixes it. Wrong, all that does is keep FSX from displaying the largest size texture map, be it the 2048 or 4096 that is in your addon scenery, but the whole size of the texture still gets loaded into memory, just not displayed at the largest size.

 

 

 

Well, if that were the case, lowering TM to 1024 should also cause an OOM but - in my case it least - it does not.

 

The only thing I change is TML in the PMDG777/CYVR and with 1024 I get no OOMs...but I do get them with 2048 and 4096...

1. The FSX SDK never said that you could use larger than 1024 texture sheets. If i recall it was ******* aka Bojote, you must have heard of him from his tweaking tool, that made the discovery that you could go up to 4096 texture sheets. Then the developers took it and ran with it, bu this wasnt how Aces intended for FSX to be used, hence the problems people are having now. Years ago before the HD revolution you didnt hear of as many OOM problems until REX, Orbx and other devs started pushing HD textures and sceneries.

 

You're probably right B)

 

 

 

2. I've told you how you can fix it, its your choice to not be lazy as you said, not me, and learn to do it a little at a time or just wait for a 64 bit version of P3D. While the new version of P3D might help a little, but its still a 32 bit program.

 

I will continue being lazy

 

 

 

3. Running airports with 1024 textures doesnt look all that much different than 2048 or 4096 unless you get real close to a building. If you fly airliners its perfect because you normally dont get real close except when you park, otherwise you probably wont notice a differenc. Most of all the older FSDT sceneries as well as Aerosoft are 1024 and no one is complaining that its not detailed enough.

 

To me it does, and I can see the difference quite well comparing the old aerosoft sceneries with some of the jaw dropping detail at certain Orbx airports, but I guess it's a matter off taste.

 

 

 

The only other thing you can do is lobby developers to stop using large texture that kill memory or at leat offer a choice of which ones to install via the installer.

 

I would never do that, I like the way they do things and want those HD textures on buildings and ground textures.

 

 

 

It is what it is. As they say, theres no free lunch in FSX regarding performance. You can fix it yourself one scenery at a time like I do, or lower your settings considerably, not use your addons, or just fly less demanding aircraft that dont consume a lot of resources. Your choice, but I prefer to make mine work good by putting the effort. Once its done its done. As edetroit the screen shot master once said, you contol the sim, dont let it control you. Wise words.

 

I know the situation is what it is, my question was only did it need to be this way or could ACES have prevented it and you have given me the answers too that :rolleyes:

Thanks for your Insight and explaining alot of things, appriciated, and sorry for getting over my head in this discussion,

 

I have worked my way around most OOM issues with balancing my settings and can live with that and rarely get into OOM's, if I do Im asking for it too happen and I know FSX current limits and what I can do and not do (flying into Manhatten X with a complex plane, with FTX Global and UTX enabled is one of the things I avoid, can't even take off from there without an Instant OOM) It's all about give and take with FSX and making comprimises, that I have learned along time ago.

 

But all that aside the FSX limits bugs me alot so I still keeps my fingers crossed hoping that P3DV2 will improve things a little so that I maybe able to e.g fly into that beautiful Manhatten X scenery with a complex plane and not only limit it to GA flying. Maybe Im hoping for too much

 

End of discussion ^_^

I think this was a good discussion so far

....so....

is there anybody out there that has any insight into how P3D V2 manages memory...specifically does it unload textures that are no longer needed...

 

Thanks

I think this was a good discussion so far

 

Yes it was, but when I said end of discussion I ment from my part, as my knowledge is limited so I don't really have anything more too say. So the rest off you may continue it as you like :lol:

 

 

 

is there anybody out there that has any insight into how P3D V2 manages memory...specifically does it unload textures that are no longer needed...

 

I belive only LM devs could answer that question...

P3D is a 32bit app. But it will run on a 64 bit OS as they have capabilty to run both. Program Files X86 (32 bit) and Program Files (64).

Thank you, I was alittle confused but I understand now. I learned something new w/ your comment about program files, that's interesting, I did not know that. Been doing this since FS2000 but never learned about windows just siming and that's how I have learned about computers. That's the way it is w/ us older types..ha ha

 

is there anybody out there that has any insight into how P3D V2 manages memory...specifically does it unload textures that are no longer needed...

 

 

I sincerely hope that it does. In fact, it's probably the most important aspect of P3DV2 as far as I am concerned. I will be astonished (and very disappointed) if LM has not corrected this.

Switching to DX11 should definitely free up more VAS space but with  more eye candy options it may be a wash if you then turn up the new shadows etc. Time will tell. I know it will be one of the first things I'm looking at as I set about to tweaking for eye candy/performance,

I was thinking more about the ability to clear memory/VAS of complex scenery that is no longer required. FSX has a nasty habit of not doing this.