• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSXA default 747

But 4Gb is only available on 64-bit Windows

You know that is correct but not entirely. Some X86 or 32bit is limited to 2gb physical with another gig or 2 available in virtual memory, however on win XP/vista 32bit you could get 4gb physical memory with additional virtual memory. With 64bit you expand to 190 something gig physical for the higher releases, under 20 for home or stater editions.

The same holds true for other operating systems. 32bit can use 4gig physical and more VRAM, 64bit can run up to 190's plus vram.
There is a formula to make the calculation to determine the limit of the processor memory, I cant recall it right now but its like 64 to the 2nd power or something, similar for 32 bit

There is a Microsoft table that shows this somewhere, let me try to find it.

Update:
Found it
http://msdn.microsoft.com/en-us/lib..._cards_and_other_devices_affect_memory_limits

In my venture to find the actual formula, I came across another term and page.
Yottabytes
May the numbers be with you.
http://www.csgnetwork.com/memconv.html
 
Last edited:
That's what I was expecting a 512mb videocard will do that. I had the same experience until I upgraded to a 1GB videocard. now have a 2GB card.
 
The table shows that 4Gb is only available in 64-bit Windows, just as I said.

4gb is available in x86 platforms, AKA 32bit, whether or not it can all be used by one software is another story.
This isnt factoring virtual memory or paging. Its physical.
64bit physical limitation is above 4gb.

Physical memory is not the same as video/graphics memory nor virtual memory.
 

Attachments

  • memlim.png
    memlim.png
    8.5 KB · Views: 425
  • memlim2.png
    memlim2.png
    11.9 KB · Views: 302
  • mrmlim1.png
    mrmlim1.png
    12.7 KB · Views: 385
The attached figure (from your link) shows that a 32-bit application on a 32-bit system has only 2 Gb of addressable memory VAS (which is what this sub-thead is about) unless IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT are set when it can have up to 3 Gb (still less than 4 Gb) provided the remaining 1 GB isufficient to allow the system to run.

It also shows that a 32-bit application on 64-bit still only has 2 Gb unless IMAGE_FILE_LARGE_ADDRESS_AWARE is set to give it 4 Gb. By default, IMAGE_FILE_LARGE_ADDRESS_AWARE is not set, so that 32-bit applications' .exe files have to be patched before they can use 4 Gb.
 

Attachments

  • Capture.JPG
    Capture.JPG
    76.3 KB · Views: 391
FSX is made with large adress aware flag set. I imagine HIGHMEMFIX actually triggers the functionality.
 
The attached figure (from your link) shows that a 32-bit application on a 32-bit system has only 2 Gb of addressable memory VAS (which is what this sub-thead is about) unless IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT are set when it can have up to 3 Gb (still less than 4 Gb) provided the remaining 1 GB isufficient to allow the system to run.

It also shows that a 32-bit application on 64-bit still only has 2 Gb unless IMAGE_FILE_LARGE_ADDRESS_AWARE is set to give it 4 Gb. By default, IMAGE_FILE_LARGE_ADDRESS_AWARE is not set, so that 32-bit applications' .exe files have to be patched before they can use 4 Gb.

This is a statement of Semantics, granted I am no expert nor do I claim to be, Ive been around pc development for a number of years, all the way back to the early days of alphabet Basic. I do see where you are coming from though. I was referring to limits, you were referring to usability determined limits.

I am not trying to nor do I want to argue over this, as we are both right. Your statement was 4gb is not available on 32bit systems. Whether fixes or patches applied or not, it is capable, which was my point.
You wouldn't say you dont have a car if you have one sitting in the driveway with a flat tire that cant be driven without minor repair.

With all that said, I do appreciate your comments. They are well intentioned and I am sure someone has or will learn something by reading this, I know I have learned I need to be like GaryGB and include ALL relevant information, not just the primary parts.

We both have great knowledge to offer the community, let this one end here and a truce be called so we can all work to better ourselves and our sims.

My apologies to anyone who may think this was a hijack. It is not, just tried to cover all bases and it skewed outside the line a little bit.

BTW, back on topic, the GTX550Ti Nvidia card actually has a minimum of 1gb. There are other versions that have higher I think. Apparently there is a flaw/defect in the makeup of the card. Something about it can only use 768mb of its memory. I havent researched much on it, but here is one tech-review I saw on it with more.
http://techreport.com/review/20573/nvidia-geforce-gtx-550-ti-graphics-processor
 
Last edited:
FSX is made with large adress aware flag set. I imagine HIGHMEMFIX actually triggers the functionality.

My understanding is that HIMEMFIX only deals with a graphics problem in FSX and doesn't incease VAS.

The IMAGE_FILE_LARGE_ADDRESS_AWARE flag indicates the application is aware that large addresses exist and won't crash if it is given an address above the 2GB boundary. However, it will never be given such an address on 32-bit windows unless the 4 Gigabyte Tuning (4GT) is enabled for Windows. This makes up to 3Gb available to the application. The downside is the reduction for Windows which can cause it to crash so it's possible to give the application less than 3 Gb. The user needs to set 4GT on 32-bit Windows. IMAGE_FILE_LARGE_ADDRESS_AWARE flag is all that's needed on 64_bit Windows.

FSX SP2 sets IMAGE_FILE_LARGE_ADDRESS_AWARE flag in FSX
 
My understanding is that HIMEMFIX only deals with a graphics problem in FSX and doesn't incease VAS.

I asume the same.

FSX SP2 sets IMAGE_FILE_LARGE_ADDRESS_AWARE flag in FSX

I thought it did but wasnt 100% sure. I know I mentioned somewhere FSX SP2 fixed that issue with memory management.

Do we know if the issue is still occuring or has a solution been found other than hardware replacement and lower sliders?
 
Last edited:
I don't think FSX has been changed since SP2/Acceleration.

It hasnt; Acceleration is SP2, and was released a few years back after FSX was initially. FSX Gold is just Deluxe and Acceleration bundled.
ACES was released in 2009 and the team formed Cascade Game Foundry. They release a scuba simulator some time ago but IDK what their future projects are.
Some aces guys went elsewhere in the industry.

Regarding my statement,
"Do we know if the issue is still occurring or has a solution been found other than hardware replacement and lower sliders?"
It was referring to jterr, whether he/she got a fix or still has issues with it. Not if FSX still has issues. I probably could have worded it a little differently as it did leave room for misinterpretation. Entirely my fault.

My understanding that P3D is basically FSX, and Lockheed Martin has licensing to modify and update upon P3D but they can not do anything to FSX as MS still holds the rights to it and LM modifying or building upon FSX would violate contractual, copyright, and trademark restrictions. Building upon P3D and converting, non-commercially, to FSX would be ok but LM can not without MS approval.
 
Last edited:
Back
Top