Back to the Vavoom Forum Archives


Forum

[Works for me] 0K Light Mem (???)

Sat, 24 Aug 2002 13:44:53

roy5050

When I attempted to execute the following command: map map16 I got the following message 0k Light Mem Host_Error: Can't Find State Name After that I reentered the map map16 command and got the following Stack Trace: Stack Trace <- LoadBaseLevel <- LoadLevel <- SV_SpawnServer <- COMMAND Map <- Host_Frame What does this mean? Thanks, L.H.
Sat, 24 Aug 2002 16:05:31

roy5050

The error type is a "floating point exception"<br><br>what casuses them &<br><br>how can thay get fixed<br><br><br>Thanks <!-- s:) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" /><!-- s:) --> A Million<br><br>L.H.<br><br>ps<br><br>can u put in bignum and/or fixnum support--<br>these should elim. floating pointer exeptions<br>and underflow/overflow errors @ a cost of<br>a larger memory space needed for larger<br>numbers.<br><br>(representing the numbers as a linked structure such as a list and/or tree is one way of doing this.)<br><br>this is not a demand it's just FYI (4 your |nf0mat10n)
Sat, 24 Aug 2002 17:17:27

Janis Legzdinsh

When I attempted to execute the following command:<br><br>map map16<br><br>I got the following message<br><br>0k Light Mem<br>Host_Error: Can't Find State Name<br><br>After that I reentered the map map16 command<br>and got the following Stack Trace:<br><br>Stack Trace <- LoadBaseLevel <- LoadLevel <br><- SV_SpawnServer <- COMMAND Map <- Host_Frame<br><br>What does this mean?<br><br>Thanks,<br><br>L.H.
<br><br>From topic name I understand you are worying about "0k Light Mem" message. Well, it simply says how much memory is taken by lightmaps, amd 0 means that you don't have any static light sources. The FindState error is quite strange, I'll check it out.
Sat, 24 Aug 2002 17:22:54

Janis Legzdinsh

The error type is a "floating point exception"<br><br>what casuses them &<br><br>how can thay get fixed
<br>There can be many reasons. Can't tell anything right now.<br><br>
can u put in bignum and/or fixnum support--<br>these should elim. floating pointer exeptions<br>and underflow/overflow errors @ a cost of<br>a larger memory space needed for larger<br>numbers.<br><br>(representing the numbers as a linked structure such as a list and/or tree is one way of doing this.)<br><br>this is not a demand it's just FYI (4 your |nf0mat10n)
<br><br>I spent a lots of time in switching from fixed-point to floating-point and I'm not gonna to switch back. And it's fixed points that overflows/underflows, floats doesn't have such limits. And if more precision is needed, double is used.

Back to the Vavoom Forum Archives