-
-
Notifications
You must be signed in to change notification settings - Fork 452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raising the GTASA 3gb memory limit #3928
Comments
GTA:SA was released as a 32-bit (x86) application, which comes with limitations, including the 3GB memory barrier, and it cannot be bypassed, regardless of any modifications or workarounds |
IIRC many years ago the fastman92 limit adjuster was considered but it wasn't implemented because of licensing issues or something weird like that. |
Or just split your IMG's. The current internal HTTP server works poorly with big files, so smaller files are efficient. nginx is mandatory if you have big (>0.5 GB) files |
is there an ideal file size for IMG archives? |
it's about memory not file size |
To send a file to a player, the server reads the entire file into memory. This is the worst part.
Nginx can handle any file. Check how many requests the internal http server can handle on your host. |
@TheNormalnij fastman92 limit adjuster has nothing to do with memory. |
Silent made a tool that makes old GTA games recognize up to 4GB of RAM, might be worth trying https://www.mixmods.com.br/2016/09/iii-vc-sa-largeaddress-reconhecer-3-4-gb-de-ram/ |
That's already enabled. |
Only HTTP server and CRC32 check block big files.
|
I know that he wrote the word Not to speak about that MTA has 64bit version of server where there is no memory limit at all. The blocking of big file is true, and you have a point on that but I think OP didn't want to talk about that. Even if he splits up his images he can't exceed the 3/4GB RAM memory limit on clients. Keep in mind that normal people often talk about server crash when technically its a client crash. They say server because its not the base game, its the server client. But this is only my guess and sorry if indeed his problem was the one you described to him. |
I completely agree with your analysis. The initial confusion around "server" versus "client" is understandable, but the visual evidence is clear: the problem lies with the game client, which is already consuming a significant amount of RAM. |
See also #2336 |
very well said on everything, and yes it's the client starting to lag when reaching 3gb and then crashing |
Well as botder said the memory limit already been raised to 4GB, I think it consists of 1GB VRAM + 3GB RAM. This is the max. Sadly the game is too old, it is a 32bit application, uses only 1 core. (if someone has Intel CPU with HT 'on' he might set it 'off' to get more one-core efficiency) The best you can do is to minimize texture sizes, quality and unload them if they are not nearby etc. The game cannot be updated to 64 bit |
damn that's sad |
Is your feature request related to a problem? Please describe.
Yes, the 3GB memory limit in GTA:SA causes frequent client crashes. This makes it hard to host large servers, especially for my 3.5GB server that uses a lot of GTA's memory, and affects stability.
Describe the solution you'd like
Raise the 3GB memory limit. or allow the use of smth like 'SA.Limit.Adjuster' this would improve server stability, allow for larger servers, and make it possible to add more creative content.
Describe alternatives you've considered
There are no real alternatives. The only solution is to raise the 3GB limit for all clients.
Additional context
Security Policy
The text was updated successfully, but these errors were encountered: