Sesquashtoo,

 

Good post, the problem is when peoples try to run bloated add-on (that would run best on a 64-bit) with FSX 32-bit and try to find a magic tweak to make them work without blurries, OOM or stutters free at max settings, and by doing so are probably screwing something else in the process.

 

Sure, if you don't mind getting O.O.M after 15 > 30 minutes, seeing blurries, stutters in a flight who am I to tell you not to do it, try to tell that to a guy who fly big plane on a long trip....but don't try to tell some of them that their bloated FSX is the cause of their O.O.M problems when trying to land at a big airport...hell no, they want a fix, they will make it work at max settings no matter what...and that is where what you see below happen..

 

Alain, when the tweak-dust is allowed to settle, the only true 'fix' for any or all complaints...is FSX converted to 64 bit.  Most 'complaints' would be in the rear-view mirror.  Until this happens, everybody knows, you crank up your graphics demand, and pay-your-money, and see what happens. We all know what happens at high graphic settings and ORBX and airport fly-overs.  People need to acknowledge that, suck it up, and enjoy the flight until memory constrictions says different. There will be no magic pill for this one....  All the tweaks from all authors did bring me to 30 fps in high system demand, and I thank everyone to date for that. YOU did make a difference, with those published tweaks!  I know that there is no 32 to 64 bit conversion 'tweak'.  So...crank it up, baby!  Fly in a world as close to reality as I can!  Keep bringing on those programs and tweaks, and textures....and, and......................................and I will fly those glorius 35 or so minutes...right down to the desktop!

 

It is.....what......it.....is........

 

Reality-Check Mitch

Sesquashtoo

 

+1

I want to use FSX Ground scenery shadows when flying, I want buildings shadows to follow the sun as this is to me a more immersive experience, how do I do that with their sceneries I paid for? Maybe that's where some of the performance you see come from, that's where this saying "Rob Peter to pay Paul" may apply here.

I have no idea what you are even talking about at this point.

 

I'm gonna assume this is another XP troll post because they have dynamic shadows?

 

And no, that's not what Nick meant by "robbing Peter to pay Paul."

 

Alain, when the tweak-dust is allowed to settle, the only true 'fix' for any or all complaints...is FSX converted to 64 bit. Most 'complaints' would be in the rear-view mirror. Until this happens, everybody knows, you crank up your graphics demand, and pay-your-money, and see what happens. We all know what happens at high graphic settings and ORBX and airport fly-overs. People need to acknowledge that, suck it up, and enjoy the flight until memory constrictions says different. There will be no magic pill for this one.... All the tweaks from all authors did bring me to 30 fps in high system demand, and I thank everyone to date for that. YOU did make a difference, with those published tweaks! I know that there is no 32 to 64 bit conversion 'tweak'. So...crank it up, baby! Fly in a world as close to reality as I can! Keep bringing on those programs and tweaks, and textures....and, and......................................and I will fly those glorius 35 or so minutes...right down to the desktop!

 

It is.....what......it.....is........

 

Reality-Check Mitch

FSX doesn't have to be 64bit to get rid of the vast majority of OOM issues, if not all of them.

 

There's a reason DX10 mode leads to less OOM crashes. The more efficently the graphics card is put the work, the less strain on your memory and CPU. And that's just a taste of what could be if the engine was optimized to use today's graphics cards to their abilities. Most modern games aren't 64bit bit but they do put the lions share of the load on the graphics card and they run blazing fast.

 

This is probably the reason LM isn't rushing to make P3D 64bit. Moving to DX11 and putting the load onto the graphics card will create a ton of headroom in the application.

I have no idea what you are even talking about at this point.

 

I'm gonna assume this is another XP troll post because they have dynamic shadows?

 

And no, that's not what Nick meant by "robbing Peter to pay Paul."

 

FSX doesn't have to be 64bit to get rid of the vast majority of OOM issues, if not all of them.

 

There's a reason DX10 mode leads to less OOM crashes. The more efficently the graphics card is put the work, the less strain on your memory and CPU. And that's just a taste of what could be if the engine was optimized to use today's graphics cards to their abilities. Most modern games aren't 64bit bit but they do put the lions share of the load on the graphics card and they run blazing fast.

 

This is probably the reason LM isn't rushing to make P3D 64bit. Moving to DX11 and putting the load onto the graphics card will create a ton of headroom in the application.

Well,...I hope you are right, for the end result for all of us...in one way or another, is to max out the graphics within FSX, with 3PD onboard...and not seeing the desktop before the user decides to...  Let's hope that somebody can put the OOM issue to sleep, once and for all!

 

 

Let's hope that somebody can put the OOM issue to sleep, once and for all!

 

But XP shouldn't have any OOM issues. They don't have any Orbx scenery or PMDG aircraft so no stress whatsoever!

Well,...I hope you are right, for the end result for all of us...in one way or another, is to max out the graphics within FSX, with 3PD onboard...and not seeing the desktop before the user decides to...  Let's hope that somebody can put the OOM issue to sleep, once and for all!

 

I personally don't have them and I run LOD 6.5 in Orbx regions with full autogen so I'm lucky I guess.

 

What I do get every now and then is those stupid menu crashes.

yeah that's the big problem I have with Nick's rantings.  From what a poster said above, nick is very good at support and very helpful, I'm not trying to  demean him personally.  the problem that I have is twofold:

 

His FSX advice is VERY dogmatic, it's Ironic, in fact that he's calling this his "bible"  again not that he's totally off base, but he presumes that what's important to him should be the only things important to anybody else, and he's completely averse to pushing the envelope.

 

and the biggie:  I already have what he tells me I must not have, and I got it by not following his advice.  are there prices for that that Nick was not willing to pay?  sure,  but they are prices I was willing to pay.  to say that BP=0 is a nonsense tweak like he did for so long is a little telling,  yes it's less stable on the wrong hardware, and yes, I don't agree that *******'s online config tool is the best thing in the world.  It's still a game changer.   oh, and DX10 has many more benefits than he mentions on his site. although he's spot on about the downside.

 

 

I don't think nick has any more agenda against orbx than anyone would in his position.  If I was nick I'd probably be at least a little anti-orbx this week.  but that highlights another point:  nick has explained for years about asian textures and what MS did to the landclass table, and JV realized the same problem when developing global,  Nick shrugged his shoulders and said "nothing we can do"  JV tried to find a solution, and apparently did.

Nicks helped me a lot with FSX, even one to one by email.

 

In all the time I have known him I have never once felt he was pushing me to buy GEX/UTX over ORBX products.

 

I believe his assistance to all with hardware and settings is a genuine willingness to help others.

 

Cheers Dave

Yes, I've never needed direct support from Nick, but I've certainly seen him offer world class support to his customers and the community. I'm sure he believes every word that he's wrIting, I think he's got a lot of wisdom to offer, he makes some good points, I just don't buy some of his biases and assumptions. Enb is not the devil, the Sdk is not the final arbiter of what you can do with fsx, there are definite and measurable advantages in DX10 mode. Immersive scenery details are worth it to most simmers.

But XP shouldn't have any OOM issues. They don't have any Orbx scenery or PMDG aircraft so no stress whatsoever!

Oh no, my friend...XPX can suck up the memory just as well as FSX can with 3rdP add-ons. I have installed a ton of airports, overlay, scenery galore, and at my max XPX settings, I am running out on occasion in XPX 32 bit mode after about a hour of flight, or pretty well double the time where the desktop shows up in FSX. This has happened only twice since having bought it 8 weeks ago...but it still has.

 

In 64 bit mode? XPX running my full 12 GB's, outlasts the pilot....Zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz! ))))))

I personally don't have them and I run LOD 6.5 in Orbx regions with full autogen so I'm lucky I guess.

 

What I do get every now and then is those stupid menu crashes.

Add along with that 6.5 LOD setting, every graphic slider full to the right, A.I. at 25 percent, and ground vehicles at 20 percent. Water at full max. Clouds at 70 miles. Go to ORBX PNW at KORS. Stay in that area, flying over and around the islands, doing a few touch and go's, and then head towards Vancouver and the mainland...head north along the coast. See how long your flight lasts... Report back.

I'm going to do exactly what you suggest and see what happens.  The only time I've gotten ooms is when flying the NGX into an fsdt or flytampa airport with a lot of ai traffic.  And that's because the NGX sucks 700 mb alone.  I've never had an oom in a carenado or realair GA plane.

I personally don't have them and I run LOD 6.5 in Orbx regions with full autogen so I'm lucky I guess.

 

What I do get every now and then is those stupid menu crashes.

+1

 

 

Add along with that 6.5 LOD setting, every graphic slider full to the right, A.I. at 25 percent, and ground vehicles at 20 percent. Water at full max. Clouds at 70 miles. Go to ORBX PNW at KORS. Stay in that area, flying over and around the islands, doing a few touch and go's, and then head towards Vancouver and the mainland...head north along the coast. See how long your flight lasts... Report back.

 

It's been a while since I had all that installed but I indeed got lockups in that region. However, the free version of FSUIPC solved that for me. I haven't had a single lock up ever since.

Alright I'm here to report back. No ooms. First I'll start with my computer specs and then FSX.

 

i5-3570K 4.3 ghz

16 gb 2400 mhz ram

580 GTX stock

w7 64 on samsung 256 ssd

FSX on WD raptor 300gb

 

FSX:

 

1920x1080

30 fps locked

Lens flare (usually don't have it but it was on and prolly cost a few frames)

no aircraft shadows (waste of a shader pass)

all scenery sliders to the right except water (high 2.x)

autogen at dense (one notch above what I usually run to test this out)

cloud draw distance 60 mi; density maximum

 

UT2 traffic 30% both commercial and GA

no road traffic (i don't like it and it taxes system)

20% ships and ferries and leisure boats

 

CFG settings:

 

highmemfix of course

usepools=0

no affinitymask (I usually run it at 14 but have been testing without it; seems good; I think it might be best to let FSX use the cores how it wants)

default 1024 textures

LOD=6.5

texture bandwidth mult=40

texturemaxload=30 (normally leave this out and set tbm at 80 but been using this lately)

fftf=0.15 (textures load fine for me; no blurries)

 

Nvidia inspector:

8xS aa

2x sgss

16x aniso

max prerendered frames = 1

standard vsync 1/4 refresh rate (120 hz monitor)

 

ezdok, opus, trackir, Carenado F33

 

All Orbx sceneries PNW and airports

FSDT Vancouver

 

I took off from 2WA1 Diamond Point and flew south down to Discovery Bay and Olympic Field.  Then I turned around and flew over OS9 Jefferson Co.  Then across to KPAE and did a touch and go and circled the airport again to get a look at the 787 Orbx placed there.  Then up to KBVS Skagit; touch and go there.  Then over to Anacortes.  I did a low pass over Anacortes aiport then down to Deception Pass Bridge.  I had a little fun flying under the bridge (shh don't tell the FAA).  Flyover of Whidbey NAS and back to Anacortes for a touch and go.  After that up to KORS.  Quick touch and go and then north to FSDT Vancouver.  I alt tabbed out at this point and checked task manager and fsx read 2.5 gb.  Touch and go at Vancouver.  Performance was better here in Canada than further south in orbx airport land.  Locked at 30 pretty much.  There were maybe 5 planes at the gates with a few taxiing.  Then went over the Vancouver skyline and landed at Pitt Meadows CYPK.  No ooms but fps was a little stuttery and not consistent at 30, especially near the orbx airports.  It wasn't horrible though; down to the teens at the lowest but 75% of the time locked at 30. Opus real weather from yesterday noonish. Clear weather; some scattered clouds but not enough to affect performance.  This is one notch more autogen then I usually run.  Bringing it down to normal would have helped and still looked great.  I flew this at 2000 feet.  Honestly 6.5 lod prolly isn't necessary at that low altitude.  Bringing it down a bit may have helped the fps.  The traffic was totally unnecessary.  I didn't see any traffic at the smaller airports.  I saw several in the distance but the traffic menu was LONG.  Waste of cpu cycles imo.  I think Orbx has some GA traffic for this area we can download. I might try that to give some life to these fields.

 

My point is no ooms.  I think the oom issue is blown way out of proportion.  Yes in the NGX I've had issues occasionally (FSDT lax, dfw, jfk with a lot of traffic) but I'd adjust settings as much as possible to give some breathing room.  Lower lod, very little or no autogen, no GA traffic, 30-40% commercial traffic.  And you do NOT need 2048 or 4096 textures.  Clouds look fine at 1024.

 

Hope this was helpful to some.    Awesome flight btw!  About an hour and a half.  Think I might adjust some settings and do it again and see if I can't keep it locked at 30 fps.

I'm going to do exactly what you suggest and see what happens. The only time I've gotten ooms is when flying the NGX into an fsdt or flytampa airport with a lot of ai traffic. And that's because the NGX sucks 700 mb alone. I've never had an oom in a carenado or realair GA plane.

Ok, that would be great. I'm hoping that you do not...but in this configuration....35-45 minutes and bye-bye for me.

 

As you, I use a Carenado G.A. for most outings.

 

Mitch

Alright I'm here to report back. No ooms. First I'll start with my computer specs and then FSX.

 

i5-3570K 4.3 ghz

16 gb 2400 mhz ram

580 GTX stock

w7 64 on samsung 256 ssd

FSX on WD raptor 300gb

 

FSX:

 

1920x1080

30 fps locked

Lens flare (usually don't have it but it was on and prolly cost a few frames)

no aircraft shadows (waste of a shader pass)

all scenery sliders to the right except water (high 2.x)

autogen at dense (one notch above what I usually run to test this out)

cloud draw distance 60 mi; density maximum

 

UT2 traffic 30% both commercial and GA

no road traffic (i don't like it and it taxes system)

20% ships and ferries and leisure boats

 

CFG settings:

 

highmemfix of course

usepools=0

no affinitymask (I usually run it at 14 but have been testing without it; seems good; I think it might be best to let FSX use the cores how it wants)

default 1024 textures

LOD=6.5

texture bandwidth mult=40

texturemaxload=30 (normally leave this out and set tbm at 80 but been using this lately)

fftf=0.15 (textures load fine for me; no blurries)

 

Nvidia inspector:

8xS aa

2x sgss

16x aniso

max prerendered frames = 1

standard vsync 1/4 refresh rate (120 hz monitor)

 

ezdok, opus, trackir, Carenado F33

 

All Orbx sceneries PNW and airports

FSDT Vancouver

 

I took off from 2WA1 Diamond Point and flew south down to Discovery Bay and Olympic Field. Then I turned around and flew over OS9 Jefferson Co. Then across to KPAE and did a touch and go and circled the airport again to get a look at the 787 Orbx placed there. Then up to KBVS Skagit; touch and go there. Then over to Anacortes. I did a low pass over Anacortes aiport then down to Deception Pass Bridge. I had a little fun flying under the bridge (shh don't tell the FAA). Flyover of Whidbey NAS and back to Anacortes for a touch and go. After that up to KORS. Quick touch and go and then north to FSDT Vancouver. I alt tabbed out at this point and checked task manager and fsx read 2.5 gb. Touch and go at Vancouver. Performance was better here in Canada than further south in orbx airport land. Locked at 30 pretty much. There were maybe 5 planes at the gates with a few taxiing. Then went over the Vancouver skyline and landed at Pitt Meadows CYPK. No ooms but fps was a little stuttery and not consistent at 30, especially near the orbx airports. It wasn't horrible though; down to the teens at the lowest but 75% of the time locked at 30. Opus real weather from yesterday noonish. Clear weather; some scattered clouds but not enough to affect performance. This is one notch more autogen then I usually run. Bringing it down to normal would have helped and still looked great. I flew this at 2000 feet. Honestly 6.5 lod prolly isn't necessary at that low altitude. Bringing it down a bit may have helped the fps. The traffic was totally unnecessary. I didn't see any traffic at the smaller airports. I saw several in the distance but the traffic menu was LONG. Waste of cpu cycles imo. I think Orbx has some GA traffic for this area we can download. I might try that to give some life to these fields.

 

My point is no ooms. I think the oom issue is blown way out of proportion. Yes in the NGX I've had issues occasionally (FSDT lax, dfw, jfk with a lot of traffic) but I'd adjust settings as much as possible to give some breathing room. Lower lod, very little or no autogen, no GA traffic, 30-40% commercial traffic. And you do NOT need 2048 or 4096 textures. Clouds look fine at 1024.

 

Hope this was helpful to some. Awesome flight btw! About an hour and a half. Think I might adjust some settings and do it again and see if I can't keep it locked at 30 fps.

Thanks for the report post. Although you did not set us as I have mine (I have water full to to the right, etc, road traffic, autogen at the highest it can go...) so not apples-to-apples alternate system test, I am going to set up as you have posted later on today, and will report back also if I got an OOM running with your FSX settings. Thanks for your efforts.

 

Mitch