hi there i was the same i always had a ctd flying in canada and anywhere in where in pnw this is a known bug in the ftx forum and there going to be a sp1 to fix this bug if you remove these two files from your orbox folder ftx_na you should be good to go since when i removed them i havnt had a ctd yet

 

cvx_300_FTX_NRM_LCpoly_1712_Edmonton_cutblocks.BGL

cvx_300_FTX_NRM_LCpoly_1613_Jasper_cutblocks.BGL

 

 

found this help in the fscrew2 forum so it helps to view other forums as well

Thanks for that Pete. Will put it back on and see what happens.

 

Good find... Pete forgot to document that feature, but it should be in the next Doc update.

You can also monitor, and get an ON-SCREEN display of memory usage, with FSUIPC.

 

See Pete Dowson's Support Forum ..

 

http://forum.simflig...iven-by-fsuipc/

If it was not for Pete Dowson, think I would have binned FSX. :)

I have found out that alt tabbing, switching between fullscreen and windows mode and minimizing fsx too many times causes fsx to use more memory. and once it's above ~2,8gig there is no point of continuing the flight, cause it will continue to increase and will most likely crash on arrival or landing phase

MS owe Pete a cut of whatever they made from FSX for making it flyable and fixing some of their stupid bugs and adding some very nice functionality.

 

I don't get OOME errors either, and I didn't tweak FSX.cfg (except for HIGHMEMFIX=1), because I avoid the things I mentioned in my post further up.

 

Best regards,

Robin.

Hello, i do use fps limiter i am not sure how it's called, but it's the first time that it happan for me, how can i know the name of the fps limiter? thanks for all. cheers.

You have to go to your root fsx folder, and check for the files "d3d9.dll" and "antilag.cfg". If you have them, try deleting them and you'll see your OOM's will go away.

 

I have found out that alt tabbing, switching between fullscreen and windows mode and minimizing fsx too many times causes fsx to use more memory. and once it's above ~2,8gig there is no point of continuing the flight, cause it will continue to increase and will most likely crash on arrival or landing phase

This used to occur to me with the d3d9.dll fps limiter; like I have said, removing it cured these issues for me (I can alt+tab, or switch from full to windowed mode, and FSX never has an OOM).

You have to switch FSX about 10 times to crash it. I can kill it in about 30 seconds doing that, and memory usage is not the problem - it corrupts memory each time you do it. You may get away with it, or you may not. 10-15 times is the limit here. Needless to say I don't do it. I run fullscreen and stay there. I don't minimize it either - leaving it minimized crashes it in about 5 minutes.

 

Best regards,

Robin.

hi there i was the same i always had a ctd flying in canada and anywhere in where in pnw this is a known bug in the ftx forum and there going to be a sp1 to fix this bug if you remove these two files from your orbox folder ftx_na you should be good to go since when i removed them i havnt had a ctd yet

 

cvx_300_FTX_NRM_LCpoly_1712_Edmonton_cutblocks.BGL

cvx_300_FTX_NRM_LCpoly_1613_Jasper_cutblocks.BGL

 

 

found this help in the fscrew2 forum so it helps to view other forums as well

Those files are in Orbx Northern Rockie Mountains, not PNW. I don't have NRM. Thanks anyway Pete.

Those files are in Orbx Northern Rockie Mountains, not PNW. I don't have NRM. Thanks anyway Pete.

ah k worth a try but most likely it be a similiar thing have you tried posting it in the ftx forum at all

Never mind. There has been several posts, but with the NGX, sliders need to come down a bit. This is not an issue with NZSI, or AU SP4, just PNW. Maybe it is more for the GA flyers.

Never mind. There has been several posts, but with the NGX, sliders need to come down a bit. This is not an issue with NZSI, or AU SP4, just PNW. Maybe it is more for the GA flyers.

do you get the ctds at the same area all th time or was it ramdom since in my case it was always the same area so it was probably easy to find the cause of it rather than ramdom.

Normally around Portland Oregon, on approach to KPDX. and sometimes I get an APPCRASH near Klamuth Falls. Thinking that having UTX installed might be a issue.

Do you disable UTX ?

Normally around Portland Oregon, on approach to KPDX. and sometimes I get an APPCRASH near Klamuth Falls. Thinking that having UTX installed might be a issue.

Do you disable UTX ?

no srry havnt got utx but i heard it has caused crashes before in other forums in this area but not sure though so you mite be on the right track there in utx

You have to go to your root fsx folder, and check for the files "d3d9.dll" and "antilag.cfg". If you have them, try deleting them and you'll see your OOM's will go away.

 

 

This used to occur to me with the d3d9.dll fps limiter; like I have said, removing it cured these issues for me (I can alt+tab, or switch from full to windowed mode, and FSX never has an OOM).

i do have these, are you sure it what causes the OOM? i will definitely delete them if so, BTW can some one recommend me of a good fps limiter? thanks!

no srry havnt got utx but i heard it has caused crashes before in other forums in this area but not sure though so you mite be on the right track there in utx

Thanks for your help Peter, will have a play with it tomorrow.

i do have these, are you sure it what causes the OOM? i will definitely delete them if so, BTW can some one recommend me of a good fps limiter? thanks!

Yes, try deleting them and I am almost 100% sure your OOM's will go away. As I explained before, this doesn't cause FSX to crash per se, but it almost creates a memory leak, where, despite the fact you've already left an airport, it still remains loaded in the background. So, when you are loading another scenery, rather than it itself being loaded, it is loaded on top of your original airport, and do, your VAS gradually increases and never goes back down. As for a good limiter, you can either use the batch file fps limiter, or you can use the fps limiter which comes with newer nvidia drivers (this is the one I'm currently using). I'm not at my main machine now, but you need the nvidia control panel, and there is an option there to limit your frames.

Just to let you guys know. I had been getting OOM issues recently. I found the fix was just to delete my fsx.cfg and let it rebuild itself. Maybe there was duplicate entries in there.