No, it does not do that automatically. You kind of wrote it yourself, like more memory is *supported* and the processor *can* perform more calculations per second. This is does not mean that this will happen automatically just because the software is 64-bit. For example, if a 32-bit software runs out of memory because of memory leaks and bad coding, adding the double amount of memory is not the solution. It will just make things worse.

You got it wrong Tolip2. 32bits apps often (including FSX) run out of memory beacuse of the simple physial address limit (https://en.wikipedia.org/wiki/3_GB_barrier) and FSX/P3D allows custom 4K textures, custom dll addons etc, etc you can easily run into OOM issue (not error) and YES, 64bits apps solve the problem automatically - I mean you still need to adapt your app to 64 bit but you do not necesssarily neeed to fix all memory leak issues. As explaind, OOM in FSX/P3D happens just because it allows custom textures and addons and each of them consumes RAM in the FSX/P3D address space unless they are separate EXE files and communicate with FSX/P3D using IPC or other technique - in that case your RAM and Virtual Memory (if needed) is the limit.

If you suggest that this software (which is based on historical code infamous for its bad performance, memory leaks and bad memory handling) is so perfect that it can't be optimized any further, and that it is running out of memory just because of the hardware limit and not because of non-optimized programming, then yes, you are absolutely correct...

 

Going 64-bit without fixing the cause of the issues will make us very unhappy simmers.

 

is so perfect that it can't be optimized

No, I did say that. I just said, that making it x64 would solve OOM issue without any particular effort on optimisation, fixing leaks, etc. That does not mean it should not be addressed in 3.X version, in fact such issues should be fixed anyway no matter if 3.0 is going to be x64 or still 32 bit app.

Isn't the out of memory due to graphics memory and not system memory?

Isn't the out of memory due to graphics memory and not system memory?

 

here's nice explanation of the subject:

 

https://#####.wordpress.com/fsx-oom-and-addon-vas-usage/

 

of course smart memory management in P3D could partially solve the issue, however the ultimate solution is going x64 which would leave a lot of space for memory leaks and bugs

 

Please note, the memoy leaks & bugs could be not only due to FSX/P3D but also bugs from add-ons loaded as DLL (e.g. complex gauges of custom aircrafts)

Isn't the out of memory due to graphics memory and not system memory?

In a word, no. OOM has nothing to do with either one, truth to tell. Word Not Allowed's explanation is excellent, and you can get the full 411 just by reading the first few paragraphs.