This topic contains 4 replies, has 4 voices, and was last updated by 
AdamStrange
1 year, 5 months ago.
-
Posts
-
Title says it all.
So far loading 3,000kb files works fine but loading anything too big can result in an error.
Just curious what the max amount of data Monkey’s DataBuffer class can load/handle.Probably 2Gig, ie: 2^31. Need to convert some ints to longs (or maybe add a size_t type thing) before it can go full 64 bit.
This will also be a problem in Windows as it will really require a new target, ie: separate Windows32/Windows64 targets.
Yes, that 64bit idea would be great for heavy data, especially in intense games. I hear memory mapping is a thing but that seems a bit too advanced. Thank you!
EDIT: Now that I think about it, I think that’s why ‘#Define’ came into the picture for C if I’m not mistaken. So you could using the same source code and generate two different Binaries based on not only the architecture, but in a host of scenarios when building.
#define with #if
12345#if win64#define size_t long#else#define size_t int#endifisn’t an int usually 32 bit with longint being 64 bits?
be careful of changing how an int works (from current) as something might break. E.G. readint, writeint which are definitely 4 bytes.
Macos compiles are already 64bit with no internal int changes, so shouldn’t windows be the same?
just a thought
You must be logged in to reply to this topic.