#TSE Out of Memory ???
5 messages in this thread
I have written a pxp script for the Script Extension where I am creating an
object having about 1000 faces. During execution TSE errors out on me telling
me that one of my variables has one subscript (it is actually a line that says
"objectfaces.caline(129) = 1" which of course should have the subscript 129 ).
I'm guessing this is an error caused by TSE running out of memory.
At this point I am stymied. I have invested a solid week in programming a
general purpose translation program to generate p3d files and now I discover
that when the data starts to get interesting (around 1000 faces) the Script
Extension is letting me down.
What's a programmer to do ???
>> I have written a pxp script for the Script Extension where I am creating
an object having about 1000 faces. During execution TSE errors out on me
telling me that one of my variables has one subscript (it is actually a line
that says "objectfaces.caline(129) = 1" which of course should have the
subscript 129 ). I'm guessing this is an error caused by TSE running out of
memory. <<
I'd be surprised if TSE was running out of memory, but I can't really help you
unless I have more of your script to work with. The most helpful approach would
be to email me the faulty script; that way the programmers and I can examine
the problem.
As a stupid question <g>, do you get this error message the _first_ time you
run the script? Also are you writing information to the console screen
(PWindow)? I've had wierd problems like this when I do a Gfx_SetGas, and later
open PWindow via a "?". Doesn't effect the first execution of the script, it's
the second time around that things sometimes get wierded out.
LAM
: As a stupid question <g>, do you get this error message the _first_ time you
: run the script? Also are you writing information to the console screen
(PWindow)? I've had wierd problems like this when I do a Gfx_SetGas, and later
open PWindow via a "?". Doesn't effect the first execution of the script, it's
the second time around that things sometimes get wierded out.
REsponse:
Yes, I get this error the first time I run the script. I am not using any Gfx
commands. I am only using commands that establish vertex coords, and then build
Meshes out of them and the face declarations. I am doing this on a 4 megabyte
file though.
Well, it sounds like you better take Martin up on his offer <g>.
Sorry I couldn't be of more help.
LAM