Archived

This topic is now archived and is closed to further replies.

BrzI

Does Pepar3D work in 64-bit mode ?

Recommended Posts

I am quite happy with FSX so far....don't think I would switch unless it is a 64-bit application... Does anybody know ?

 

Thanks

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Prepar3D v2.0 is not a 64-bit application. It might be done further down the road but it's a tremendous amount of work and will break all existing add-ons from working.

 

Since you are happy with FSX so far I'm not sure why you would be looking to see if Prepar3D is a 64 bit application or not. The most obvious benefit would be virtual elimination of OOM's which you don't appear to have issue with. The new DX11 engine in P3D v2.0 seems to be doing a satisfactory job of reducing this issue in the interim, which in its self will be a large benefit to current users with this problem. If OOM errors are virtually a thing of the past, will anyone really be caring at the moment if it's 32 or 64 bit? I don't believe so. We just want performance first and foremost, and it appears v2.0 will be delivering in many ways that which we have wished for of FSX over the years.

Share this post


Link to post

Interesting.  I have a robust FSX setup.  100s of planes, commercial and freeware, 650 layers of scenery and airports and with the usual tweaks. 

 

I have never had OOMs, not sure what causes it but I hear lots of guys talking about it here.  If this is the only thing I'm going to gain by upgrading to V2, then what would be the point.

 

I understood that there are some newer features and most likely will get a smooth ride without any micro stutters etc.

Share this post


Link to post

If this is the only thing I'm going to gain by upgrading to V2, then what would be the point.

 

 

 

I understood that there are some newer features and most likely will get a smooth ride without any micro stutters etc.

 

It's not the only gain, you get volumetric fog, realtime shadows, DX11, HDR, 3D water that moves depending on the weather conditions, no more autogen "popping" and a lot better performance and it also support new hardware. If that is not good reasons for switching then what is?

 

The reason you haven't had OOM's is probably because your hardware specs doesn't allow you to have high settings in FSX. The day you upgrade your hardware and start pushing the settings higher you will eventually hit the VAS limit ^_^ I had the same view like you before I got better hardware and started getting OOM's...

Share this post


Link to post

 

 


The reason you haven't had OOM's is probably because your hardware specs doesn't allow you to have high settings in FSX. The day you upgrade your hardware and start pushing the settings higher you will eventually hit the VAS limit ^_^ I had the same view like you before I got better hardware and started getting OOM's...

 

Look at my specs and explain your reasoning why I have never had an OOM?

Share this post


Link to post

Look at my specs and explain your reasoning why I have never had an OOM?

 

I said it was "probably" as in "most likely" the reason he didn't get OOM's. When maxing settings, pushing the LOD radius and using complex planes and scenery it's more likely that it may happen, maybe you have balanced your settings well and disabling scenery u don't fly over etc etc, I don't know, only talking from my own expirience with OOM's :rolleyes:

 

I don't get OOM's either because I have balanced the settings so I don't get them, I could have had higher settings and a smooth flight but the VAS limit doesn't allow me too do that in certain areas...

 

Anyway, If Prepar3dV2 removes the OOM problem it would give "most" of us great benefits...and that in itself is a huge gain...

Share this post


Link to post

It's not the only gain, you get volumetric fog, realtime shadows, DX11, HDR, 3D water that moves depending on the weather conditions, no more autogen "popping" and a lot better performance and it also support new hardware. If that is not good reasons for switching then what is?

 

The reason you haven't had OOM's is probably because your hardware specs doesn't allow you to have high settings in FSX. The day you upgrade your hardware and start pushing the settings higher you will eventually hit the VAS limit ^_^ I had the same view like you before I got better hardware and started getting OOM's...

 

 

Yes I can see there are some reasons for switching, and am planning on it, I will have a dual setup first before I stop with FSX.

 

Not sure what you mean about the high settings...I have everything at max, I run 4096 on textures, I run on LOD=6, I turn down autogen to dense, I have AI traffic for planes trains and automobiles, I have water turned down a notch - don't need it high and I use FSWC for effects and colour, use ENB series.  I don't know what may be the issue but I fly for hours, sometimes just pause the flight and pick it up the next day. I use REX HD clouds and weather.  All FSX display setting for texture etc are set at max.

 

I almost always have other stuff active on my desktop but then again I have 16gigs of RAM to take care of business.  I just don't know as I run at very high settings. I guess lucky me.

Share this post


Link to post

Are you running any Orbx or FSDT airports near coastal areas Bryan?

 

I only get OOM's around dense areas along coastlines (known culprits), with FSDT airports, Orbx regions, REX weather if really cloudy, and a demanding aircraft in for good measure. CYVR is a prime example. I've yet to get anything above a Carenado aircraft into there from any outside location without the OOM error occurring the moment CYVR loads in. Your "luck" as you put it may have more to do with where you fly mostly, what you fly, and not having so many complex add-ons running at once. Its just my guess.

Share this post


Link to post

Not sure what you mean about the high settings...I have everything at max, I run 4096 on textures, I run on LOD=6, I turn down autogen to dense, I have AI traffic for planes trains and automobiles, I have water turned down a notch - don't need it high and I use FSWC for effects and colour, use ENB series.

 

What plane do you use and what scenery do you fly over and are you using Sparse Grid Supersampling AA? Hmmm, you lucky son of a bi... :P

 

E,g, when I load up Majestic q400 at La Guardia with Manhatten X scenery, FTX Global and UTX, even with default LOD settings it results in a instant OOM. In that area I can only fly GA planes. The performance is good and I get 30FPS with GA planes but with complex planes I can't even take off...

 

Another example would be in the Vancouver area, I use Extreme autogen when flying GA all over the world, but in the Vancouver area with Vancouver+V3 scenery and Orbx PNW it results in a OOM after 5 minutes in the flight even though everything runs smooth with constant 30 FPS, I have to lower my autogen settings down to very dense to be able to fly in that area without OOM's

Share this post


Link to post

Ha ha ha. Throw in FSTD CYVR and watch the carnage begin!

 

I agree, Vancouver, Seattle, New York, and even sometime Honolulu and LAX are high culprits to offend. I'm looking so forward to being able to fly again into these regions without castrating my settings to maybe get a successful attempt in V2.0.

Share this post


Link to post

 

 


Ha ha ha. Throw in FSTD CYVR and watch the carnage begin!

 

:lol: I have tried but for some strange reason CYVR won't install properly on my system, I get only black ground textures :mellow:

Share this post


Link to post

Are you running any Orbx or FSDT airports near coastal areas Bryan?

 

I only get OOM's around dense areas along coastlines (known culprits), with FSDT airports, Orbx regions, REX weather if really cloudy, and a demanding aircraft in for good measure. CYVR is a prime example. I've yet to get anything above a Carenado aircraft into there from any outside location without the OOM error occurring the moment CYVR loads in. Your "luck" as you put it may have more to do with where you fly mostly, what you fly, and not having so many complex add-ons running at once. Its just my guess.

 

 

I have almost all of Orbx scenery (you can see my list over at FTX forums).  I have FSDT airports for Hawaii...fly these areas mostly.   I have FSAddons for CYVR coverage.  I must say the Vancouver + with stuff turned on does cause my machine to "slow" to 16 fps so I have to turn back setting in the area of the city only.  The same goes for KSEA area I do drop from my 30fps to 15 in that area so it help if I temporarily shut off AI and drop the autogen to normal.  But I never have any crashes with or without turning down those things.

 

And perhaps your right I do not fly for long periods in the big city areas, NE corner of US and LA for instance.

Share this post


Link to post

:lol: I have tried but for some strange reason CYVR won't install properly on my system, I get only black ground textures :mellow:

 

Hmm, odd. Perhaps your VAS memory is maxed out before FSDT CYVR can even fully load up. Perhaps Vancouver +3 is the tipping point as I do not have that package due to problems as they stand. First visual signs I get of running out of VAS is black texture squares appearing on the ground. You should bring this issue up with Umberto on the FSTD forums if it won't install properly. First I would disable the Vancouver + scenery and see what happens, just to eliminate that variable.

Share this post


Link to post

I have a good rig. Performance is not an issue. OOMs started happening when I tried the PMDG 777 in CYVR. The FPS would still stay high but monitoring VAS usage I hit 3.2 GB very quickly. I could maybe do a takeoff but coming back for an emergency landing would OOM on me. This is not a hardware issue - it is a limitation of the 32-bit environment. Don't get OOMs with the NGX - or any other add-on. Of course, if I have clear weather, it will not happen - but Vancouver is one rainy city....

 

The only surefire method of eliminating OOMs with the 777/YVR combo for me is to reduce TML to 1024 (even 2048 will OOM on me).

 

This is why I will not be buying P3D - at least not for now...

Share this post


Link to post

You could always splash out $10, if the pricing ends up being similar to 1.4, to get a one month subscription and just see how it goes.

 

    We really dont know how bad the coding and freeing of memory was in FSX and how much of an improvment p3d v2 could be on that in a 32 bit environment.   

 

     64 bits is good when you need a lot of memory but if for all intents and purposes it behaves like a 64 bit app in a 32 bit environment due to much better internal memory management then it could be a moot point.

Share this post


Link to post

Even if P3D was 64 bit, you would have to give up your PMDG 777 to get the benefits. It is designed not to work in Prepar3D so you will be stuck with your issue.

 

P3D with it's new DX11 engine and vast VAS memory usage improved would likely fix the problem around Vancouver but it's moot as PMDG will not allow you to benefit from it.

Share this post


Link to post

Hmm, odd. Perhaps your VAS memory is maxed out before FSDT CYVR can even fully load up. Perhaps Vancouver +3 is the tipping point as I do not have that package due to problems as they stand. First visual signs I get of running out of VAS is black texture squares appearing on the ground. You should bring this issue up with Umberto on the FSTD forums if it won't install properly. First I would disable the Vancouver + scenery and see what happens, just to eliminate that variable.

 

Don't bother trying to help me on this issue, already have a support thread going on the FSDT forum.... I even tried installing it on a vanilla FSX install(only default FSX), same issue, also tried it with my previous hardware setup(different mobo, GPU and RAM), everytime I have reinstalled FSX I have tried this scenery first, also tried lowering settings to minimal, with tweaks, without tweaks...Pretty much tried all there is to try.

I have stop bothering with this scenery, because it's not worth the time and I'm soon switching too prepar3dV2 so I have pretty much given up on fixing it. :P Umberto suggested helping me with teamviewer but haven't gotten time to do that and since FSX soon is being removed from my computer there is no need to get it fixed..

 

Thanks anyway :rolleyes:

Share this post


Link to post

I have FSAddons for CYVR coverage. I must say the Vancouver + with stuff turned on does cause my machine to "slow" to 16 fps so I have to turn back setting in the area of the city only.

 

Try having Orbx PNW enabled and Vancouver+ and fire up the most demanding GA plane you have, and turn booth autogen settings to Extremely dense and have water on highx2 with decent traffic, bad weather and fly over the city and then tell me you don't get OOM's....

(look away from the FPS as it's not the point what frames you get, the point is to trigger an OOM, I get excellent frames with these settings but the VAS limit is what keeps me away from using them. That's my point with your hardware never gotten you to use such high settings because you say you turn settings down when getting low frames and therefore your less likely to encounter OOM).

Share this post


Link to post

I have FSDT airports for Hawaii...fly these areas mostly.

 

Also may be a reason because If I understand you right you keep away from the areas in FSX notoriously famous for bad performance, e.g Seattle, Vancouver, New York, London etc and that you mostly fly short trips, and not 12 hour + with complex planes like PMDG over complex sceneries and destinations like Seattle, New York, London etc? And you reduce settings in the worst areas?

Share this post


Link to post

Running FSX in DX9 caused me regular OOMs due to its memory model of mapping all the contents of the graphics card memory onto the system RAM, causing it to regularly hit the 4GB code limit in FSX. In DX10 using the fixes, I never get any OOMs at the same close to maxxed-out settings, and FSX RAM usage is greatly reduced and never gets close to the 4GB wall.There is my 2 cents for what its worth.

Share this post


Link to post

With DX11 and the total rework of how P3D handles memory, I believe V2.0 will finally put the smackdown on OOM errors, at least for the foreseeable future anyway.

Share this post


Link to post

I assume that P3DV2 will have considerably better memory management than FSX? You know....clearing the memory of stuff that has been left far behind? I have never understood why FSX is so rubbish at this. I mean, why on Earth would anyone design a flight simulator to retain scenery data in memory that is no longer required? It just doesn't make any sense.

Share this post


Link to post

The Microsoft FS franchise was an evolving product. They likely figured they would just get to the issues at a later date. Seeing how a lot of problematic code got carried through revision after revision its probable the focus was always on the next release.

The fact that is took L.M. over 2.5 years to yield an FSX equivalent that was stable and nearly bug free is a testament of how much was wrong within FSX. That's a lot of man hours and money just to create a version of Prepar3D that ran as FSX should have. It makes one think about how much of a mess it was. They completely ripped out the DX10 preview mode and even somewhat simplified the simulator just in part to achieve this. I'm just glad it's finally cleaned up and for once in many many years we will have a simulator we can spend more time using than time fiddling with. It will also hopefully decrease the amount of time developers need to spend in support forums trying to fix issues that are more at the core of FSX than with the product they created. I have always taken note that most Prepar3D support forums for products are a fraction of the size of the ones for FSX. Coincidence or smaller user base? Perhaps, but there just does not seem to be the same amount of problems. Lets hope this becomes the norm so developers can spend more time making things and fixing real issues in their software than trying to figure out if the problem is on their end or with FSX.

Share this post


Link to post

Try having Orbx PNW enabled and Vancouver+ and fire up the most demanding GA plane you have, and turn booth autogen settings to Extremely dense and have water on highx2 with decent traffic, bad weather and fly over the city and then tell me you don't get OOM's....

(look away from the FPS as it's not the point what frames you get, the point is to trigger an OOM, I get excellent frames with these settings but the VAS limit is what keeps me away from using them. That's my point with your hardware never gotten you to use such high settings because you say you turn settings down when getting low frames and therefore your less likely to encounter OOM).

 

 

I guess i'll have to frustrate the hell out of myself to replicate the OOMs.  I'll skip that.  Life is already got plenty of challenges for me.  Maybe when I get my new computer or when the wife lets me get the new computer...lol.

Share this post


Link to post