I was wondering if the author could give us some clues as to whether any of the config file settings or in-game settings can be used to decrease the game's memory footprint a little? I only ask as I'm running a 256MB Pi with a 128/128 memory split that throws segmentation faults with many Quake I mods. Am I right in guessing that lack of RAM is my problem?
This isn't a complaint by the way. I still think it's amazing that the original pak files work just fine on my little box of wonders.
Yes, you are correct that the issue is most likely due to lack of memory, particularly if the errors occur when loading a map. Some mods are designed to run only on a gaming pc and simply won't run on a RPi with 512mb not to mention models with only 256mb. If you are able to run mods successfully on a 256mb RPi, please share the results!
A list of working mods along with installation notes is being compiled here:
https://github.com/autonomous1/darkplac ... places-RPi
Reducing texture memory
The following parameters reduce the amount of memory allocated to textures:
gl_max_size - maximum allowed texture size, can be used to reduce video memory usage
gl_picmip - reduces resolution of textures by powers of 2, for example 1 will halve width/height, reducing texture memory usage by 75%
These parameters will affect the visual appearance. Here is an example of config.cfg parameters that will reduce texture memory:
Reducing display memory
Code: Select all
Reducing the resolution from 1080p to 720p or less may free up a few megs. Another option is to change the number of bits allocated per pixel:
vid_bitsperpixel - how many bits per pixel to render at (32 or 16, 32 is recommended)
Reducing other memory use
After a map has loaded you can examine memory allocations. The console command memstats displays total memory allocated to textures and vertices. The console command memlist prints a detailed list of allocated memory. Sometimes large amounts of memory may be allocated to sound and it may be possible to remove pak files containing audio files.
Recommended memory split
Model B: 256/256
Model A (or 256mb models): 128/128
The default allocation of 64mb GPU memory does not work, as well as allocating 64mb to the Arm.
The next release will include improved bounds checking to avoid segmentation faults or lockup issues. The engine has these types of checks built-in but again it is configured for a gaming pc. The RPi is stressing memory limitations to the max.