-nomap: Difference between revisions
Jump to navigation
Jump to search
m (removed categorization) |
m (Added links) |
||
| Line 1: | Line 1: | ||
[[Category:Operation Flashpoint: Startup Parameters|N]] | [[Category:Operation Flashpoint: Startup Parameters|N]] | ||
'''-nomap''' is an '''Operation Flashpoint Startup Parameter''', which forces OFP to avoid memory mapping for file access. | '''-nomap''' is an '''[[:Category:Operation Flashpoint|Operation Flashpoint]] Startup Parameter''', which forces OFP to avoid memory mapping for file access. | ||
''Flashpoint only. This 'switch' has no effect for Armed Assault and is not relevant for, Armed Assault. Potentially, use -maxmem for similar intended results.'' | ''Flashpoint only. This 'switch' has no effect for Armed Assault and is not relevant for, Armed Assault. Potentially, use -maxmem for similar intended results.'' | ||
Revision as of 13:41, 26 November 2018
-nomap is an Operation Flashpoint Startup Parameter, which forces OFP to avoid memory mapping for file access.
Flashpoint only. This 'switch' has no effect for Armed Assault and is not relevant for, Armed Assault. Potentially, use -maxmem for similar intended results.
While memory mapping is very efficient from a performance point of view, it can quickly fill all available virtual space, causing various memory allocation errors or even driver crashes or freezes.
This switch is especially important for users with display adapters with large amounts of VRAM (128MB or more), which reserves a lot of virtual addresses in the application address space for themselves.