Got mine set to 4.5(should it be higher or lower)

 

4.5 is default. With higher we are forcing FSX to run outside of its normal operating parameters...

 

Really the OOM's are our fault hehe...

This is why I love Avsim all you guys test this stuff for me so I don't have too! Ill wait and see if it get any better.

Finally solved my oom problem with my previous settings as mentioned in my previous thread departed cyvr went to vor pae and returned back to cyvr all the time i stayed in vc view fps dint go below 15 on the ground in the air went to 35. all i had done is went to dx10 view in the fsx settings now am a happy camper

 

Randy

Maybe you be the lucky ones that it will work for you straight away have you tried the trial version at all

Guys,

 

I am getting massive fps issues when looking into the centre of the airport at low level only. Below are some pics, 29.x is smooth as butter, when it hits 19, it fluctuates from 30, which causes the issue

 

http://i293.photobuc...ISSUE/th_10.jpg

 

http://i293.photobuc...SDT ISSUE/1.jpg

 

 

Spot and wingviews for me, never go below 30.. I feel it's linked to the oom issues.

 

No AI traffic etc. can run Flytampa dubai and hundreds of other sceneries [minus certain aerosoft ones ] without issue

 

Alex

 

Hi saw the photos as another user had picked up you have a duplicated scenery as well, you notice that you have 2 control towers like i had at one stage till i removed the duplicate scenery package.

 

use the Free FSX Airport Scanner, to search for afcad duplicates, and remove all the extra.

And 2 hangers for the air Canada hanger.

yup hes got 2 of everything by the looks of it probably why his having low fps

If you are using FSX in full screen and you hear the Ding Dong via FSUIPC to warn you of an impending OOM, go into window mode briefly, and then back to full screen. It gives me another 10 or 15 mins. Which in most cases allows me to land and taxi etc. If it ding dongs again, I just repeat going in and out of window mode. Never lost a flight yet. (DX9)

DX10 is great. However it should be mentioned that you need to have it enabled for this product. OOM on touchdown. I do not currently have the time to start another tweak fest with DX10. Please patch this product so that it works with PNW, PMDG, REX, UTX. This should perform the same as KLAX not worse

 

This airport should work on today's hardware and DX9. There is no reason why I should purchase a product that's unusable in DX9 with complex add ons. I'm on a 2700k over clocked to 4.55 and I am unhappy that I purchased without demo. Normally FS Dreamteam stuff works great. This is not ok...

So Umberto is basically saying that we have to use dx10 now to run their stuff? Gimme a break! ! There is no way I am going to start having to go to that dx10 forum on here and stay switching a bunch of stuff in the sim just so I can fly into one airport. Umberto, fsdt is now reached a level were people cannot use your scenery without having to worry about constant OOM errors. Your scenery design has gone past the capabilities of what fsx and dx9 can handle. If fsdt's position going forward is use dx10 or suffer OOM then I am done with your company. I could care less about dynamic shadows. I am just thankful Fly Tampa and Flightbeam have not gone your route.

 

Sent from my Samsung Galaxy Note 2

 

 

So Umberto is basically saying that we have to use dx10 now to run their stuff? Gimme a break! ! There is no way I am going to start having to go to that dx10 forum on here and stay switching a bunch of stuff in the sim just so I can fly into one airport. Umberto, fsdt is now reached a level were people cannot use your scenery without having to worry about constant OOM errors. Your scenery design has gone past the capabilities of what fsx and dx9 can handle. If fsdt's position going forward is use dx10 or suffer OOM then I am done with your company. I could care less about dynamic shadows. I am just thankful Fly Tampa and Flightbeam have not gone your route.

 

Sent from my Samsung Galaxy Note 2

 

I agree dude,

 

I am on the FSDT forums, and I am banging my head against a wall here.

So Umberto is basically saying that we have to use dx10 now to run their stuff?

 

Obviously not. I'm saying that if you want to use many add-ons at the same time, you'll have to switch to DX10. What you guys don't seem to understand, is that this situation, sooner a later, would have happened in ANY CASE.

 

It doesn't have anything to do with FSDT products. It just happened here, because there are many available add-ons in this area, but it might happen again with any other scenery in a different area, or it WILL happen when the next great weather/texture/airplane product will come out, and everybody will want to use it together with ALL the other add-ons, forgetting that those 4GB are a FINITE resource, and it WILL be filled up someday.

 

Note that, switching to DX10 will not be the end of the troubles, this will save about 300MB, that with some stuffed systems and/or too high settings that are OOM-ing now, might just be what saves from a crash, but that won't last long. There will be add-ons coming out that will keep filling memory, and we'll surely discuss about this situation even with DX10, maybe the next year, maybe about the next scenery from someone else.

 

This is not a matter of FSDT, we just made one additional scenery, which runs perfectly well, that's just happened to be (and of course only for some users, because you see plenty of comments that don't have any problems with it) the last straw that broke the camel's back, but it happened to be in an area with many add-ons available, in a post-PMDG NGX world, in a place when it's *almost* always raining to begin with, so users with hi-res cloud textures and 3rd party weather engines, might noticed it even more.

 

As I've said, if we released CYVR a couple of years ago, before PNW and the NGX, this discussion would be about other products, OOM-ing an "airport that worked up to the day before". And it would have been wrong nonetheless.

 

It's a matter of understanding there are limits to what you can do with FSX and 4GB. And understanding that, you WILL have this problem with something else entirely (as if OOM didn't existed before CYVR...really ? ), sooner or later, because the more add-on will be released, especially those that could be possibly used together, the more the issue will hit you, because those 4GB limit will always be there, you have to learn how to MANAGE your stuff and make choices, either in the number of add-ons to use together OR in your settings.

Obviously not. I'm saying that if you want to use many add-ons at the same time, you'll have to switch to DX10. What you guys don't seem to understand, is that this situation, sooner a later, would have happened in ANY CASE.

 

It doesn't have anything to do with FSDT products. It just happened here, because there are many available add-ons in this area, but it might happen again with any other scenery in a different area, or it WILL happen when the next great weather/texture/airplane product will come out, and everybody will pretend want to using it together with ALL the other add-ons, forgetting that those 4GB are a FINITE resource, and it WILL be filled up someday.

 

Note that, switching to DX10 will not be the end of the troubles, this will save about 300MB, that with some stuffed systems and/or too high settings that are OOM-ing now, might just be what saves from a crash, but that won't last long. There will be add-ons coming out that will keep filling memory, and we'll surely discuss about this situation even with DX10, maybe the next year, maybe about the next scenery from someone else.

 

This is not a matter of FSDT, we just made one additional scenery, which runs perfectly well, that's just happened to be (and of course only for some users, because you see plenty of comments that don't have any problems with it) the last straw that broke the camel's back, but it happened to be in an area with many add-ons available, in a post-PMDG NGX world, in a place when it's *almost* always raining to begin with, so users with hi-res cloud textures and 3rd party weather engines, might noticed it even more.

 

As I've said, if we released CYVR a couple of years ago, before PNW and the NGX, this discussion would be about other products, OOM-ing an "airport that worked up to the day before". And it would have been wrong nonetheless.

 

It's a matter of understanding there are limits to what you can do with FSX and 4GB. And understanding that, you WILL have this problem with something else entirely (as if OOM didn't existed before CYVR...really ? ), sooner or later, because the more add-on will be released, especially those that could be possibly used together, the more the issue will hit you, because those 4GB limit will always be there, you have to learn how to MANAGE your stuff and make choices, either in the number of add-ons to use together OR in your settings.

 

Umberto, this is like hitting a brick wall over and over..

 

I get the OOM'S with no ORBX scenery and running a microsoft default plane.. Explain explain explain please

Again and again I'll mention it;

 

Google 'Word Not Allowed OOM'

 

Theres a direct link to a MICROSOFT fix.

Again and again I'll mention it;

 

Google 'Word Not Allowed OOM'

 

Theres a direct link to a MICROSOFT fix.

 

Doesn't work in this Case 'Flying Bliss' [real name required]

Umberto, this is like hitting a brick wall over and over..

 

You mean I'm hitting a brick wall, which is you. There are several users here that pointed you out about your duplicate scenery, which was obvious in your screenshot.

 

I'll reply you here, which of course it's a waste of time, but anyway:

 

As I've said already, it's possible it might not show up now, but is still slowing down fps. There are cases when you HAVE a duplicate AFCAD, when there's NOTHING on screen, and that is CAUSED by the duplicate too, but even if you don't see anything, it still slows down the fps.

 

And, since you obviously HAD a duplicate in your previous screen, either you FOUND IT and remove it, and you haven't said you did, or it's still there. Since you just ASKED "How can I check if there is duplicate scenery ?", I can assume you haven't removed it, so it's likely still there.

 

This is not FSDT support forum so, please, don't reply here and there. Continue there, we'll find your duplicate scenery, and if you manage to reply to my question about your fps, other possible causes (you might have multiple issues at the same time, with the duplicate scenery being just one of them ).