Scriptsize: Difference between revisions

From EDukeWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 1: Line 1:
'''scriptsize''' <integer>
'''scriptsize''' <integer>


scriptize allows the user to enforce a solid buffer limit for complied code size without any progressive buffer increases up to that point that normally occur during start up.
''Scriptsize'' allows the user to enforce a solid buffer limit for compiled code size without any progressive buffer increases up to that point that normally occur during startup.


Example of normal buffer setup would be from 16384 to 32768 to 65536 [and doubles for each normal increase to buffer size].
Example of normal buffer setup would be from 16384 to 32768 to 65536 (and doubles for each normal increase to buffer size).


Using "scriptsize #" can bypass this if you're having problems in-game that you suspect are linked to the normal method of code-buffer increases.
Using ''scriptsize'' can bypass this if you're having in-game problems that you suspect are linked to the normal method of code-buffer increases.


[[Category:EDuke32 specific commands]]
[[Category:EDuke32 specific commands]]

Latest revision as of 09:57, 9 July 2010

scriptsize <integer>

Scriptsize allows the user to enforce a solid buffer limit for compiled code size without any progressive buffer increases up to that point that normally occur during startup.

Example of normal buffer setup would be from 16384 to 32768 to 65536 (and doubles for each normal increase to buffer size).

Using scriptsize can bypass this if you're having in-game problems that you suspect are linked to the normal method of code-buffer increases.