Incorrect amount of total memory listed

LogMemory: Memory total: Physical=15.9GB (16GB approx) Virtual=8192.0GB
LogMemory: Physical Memory: 4006.73 MB used, 16276.83 MB total
LogMemory: Virtual Memory: 236.46 MB used, 8388608.00 MB total

How is that “8388608.00 MB total” ?
I have 2 hard drives (1º 250GB / 2º 3TB)

And in video card:
LogD3D11RHI: Adapter has 2994MB of dedicated video memory, 0MB of dedicated system memory, and 7882MB of shared system memory, 1 output[s]
LogD3D11RHI: Chosen D3D11 Adapter Id = 0
LogRHI: Texture pool is 1361 MB (70% of 1945 MB)

(70% of 1945 MB) ? the vram is “2994mb”, from where are the 1945 MB ?

Hi Hgdavidy,

Could you post a copy of the full logs so we can have a look as well as your dxdiag? Thank you!

Hi Hgdavidy,

Are you seeing this from a specific project or does it happen in a blank project with no additional content?

Generate the same number in new and old projects from the same and other versions, you create a new BP FPS and give the same number in virtual memory

Are you seeing this in the task manager window or where is this memory information being shown?

In the ue4 logs of all projects “Saved\Logs*.txt”

8388608 MB = 8192.0 GB (8388608*1024)

Virtual memory is just a % of a disc set by the system, not the whole drive. You can change it in Computer properties > Advanced System settings > Advanced > Performance Settings > Advanced

As for “1945”, isnt it the Texture pool streaming?

Hi Hgdavidy,

I was able to reproduce these exact numbers on my pc here with a clean project. I am getting confirmation as to whether this is a bug or intended functionality and will let you know when I have more information available. Thank you!

News about this ?, in 4.6 still broken…

Hi Hgdavidy,

I did a lot of digging and finally found out what this information is. It is the limit of virtual memory available for Windows 64 bit. This is erroneous data that you won’t have to worry about and will have no bearing on your project!

No is a problem but why report the limit and no the real/actual size/amount ?

This is something we are looking into altering. If it does not get removed entirely it may be altered to show actual virtual memory size instead of the maximum allotted.