Jump to content

ad_verbum

Members
  • Content Count

    99
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender
    Male
  • Location
    Poland, EPGD

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No
  1. That is easy to check isn't true that whole video memory range must be duplicated in the application's space. Only you need is FSX running with simple scenery and low settings, graphics card with 1GB or more video memory and Sysinternals Process Explorer to check size of FSX's allocated space (Virtual Size). FSX (low settings and simple scenery) run on GTS450 with 1GB video memory is reporting total used virtual address space below 0,9GB. According to your claims total used virtual adress space should be significantly bigger than 1GB as a sum of memory allocated for FSX program, data and 'duplicated' 1GB of video memory. Applications that use graphics APIs that are earlier than DirectX10 and that target GPUs that have large amounts of video memory can easily exhaust their virtual address space, but isn't true that size of allocated virtual address space for graphics resources must be equal of installed video memory of graphics card. It may be smaller or even bigger due to duplication by WDDM video memory manager virtualized range in addition to the application’s copy of used resources while working under DirectX 9. In such case data is stored in application's virtual adress space twice. With your idea of "duplication' allocated space according to video memory size of graphics card it would have tragic consequences for applications without LARGE_ADDRESS_AWARE flag set, beeing able to use only 2GB of virtual address space.
  2. Are you sure that full linear address space of graphics card is duplicated in virtual address space of 32bits process while using DirectX9.0c? What in case of cards with 2GB of video memory working under control of 32bits OS? In this case virtual adress space avaliable for each process is equal to video memory size. What about space for the process itself? I know D3D enviroment slightly, but I was thinking that under D3D communication between application memory and video memory placed on graphics card is done by using buffering technique managed by D3D via WDDM (Vista and Win7), so what is the reason for duplicating whole memory of graphics card in application memory? Can you point me where I may read about that? For any application, without LARGE_ADDRESS_AWARE flag set, working on system with modern graphics card equipped with 1GB or more RAM it could be reason to easily get OoM error.
  3. Prepar3D is using its own up to 4GB virtual adress space which is allocated in total memory area avaliable for OS. Video memory buffer is allocated in OS adress space, not in Prepar3D adress space. As long as Ost's computer has installed Win7/64 bits and 8 GB of RAM, video memory buffer with maximum size of 1.5 GB can't be significant problem.
  4. Prepar3D is 32 bits application running in your case in 64 bits system. That error you got means P3D used all memory allowed to use for it as 32 bits application - 4GB. As P3D is complied with LARGE_ADDRESS_AWARE flag it may use up to 4GB of virtual adress space. You saw in Task Manager that used memory was around 3 GB. Task Manager doesn't show size of used virtual adress space but only allocated physical memory. Applications under normal circumstances always are using more virtual adress space than physical. To check how much of virtual adress space is using FSX in your case, you need to get Process Explorer, ( http://technet.microsoft.com/en-us/sysinternals/bb896653 ) run it and right click on the "Process" table header > Select Colums > Process Memory Tab > and mark "Virtual Size" than run P3D with the same plane and scenery as eailer. Memory and Address Space Limits: 32 bits process on 32-bits Windows OS: 2 GB or up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT 32 bits process on 64-bits Windows OS: 2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default), 4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set source: http://msdn.microsoft.com/en-us/library/aa366778%28v=vs.85%29.aspx#physical_memory_limits_windows_7 PS. you won't get any benefits from adding more memory over 8 GB you have now.
×
×
  • Create New...