cloudandy
08-30-2001, 11:31 AM
I'm trying hard to learn how to use FSDS. So far not going to bad but have
struck a strange problem
I am making a structure(about 30 parts) and testing the look of it as I build
it, in FS2000, using Apt 2.6 to compile the scenery.
Suddenly Apt 2.6 stopped compiling, showing a error message about the object
being out of range????
By removing some of the structures parts Apt 2.6 will again compile OK. If I
put the parts back in, same problem.
Does FSDS or APT 2.6 have memory restrictions??. Is this a common problem??
In dire straights,
Clive ( ausie ) Marriott.
Clive
You have exceeded scasmīs linebuffer memory. By default scasm has a certain
limit of code lines for each scenery object. This is a presign that your
object is most likely overdesigned, with too many points and polygons.
Take care that you are defining structures as simply as possible. E.g.
a sphere wonīt always need 32X32 sections, you can make it with 8X8 or
16X16 as well.
A cube wonīt need 8 sections if it has a regular shape. 1 section is enough
then.
Whenever possible, combine parts and points. Select two (or more) parts
and execute "...join selected". Then click "...snap to scale".
There are of course much more ways of minimizing the code size.
But if you really want to ( or need to ) stick with your object size, you
must reedit the macro with wordpad and append the following two lines
to the top of the macro:
Set( areamx 64 )
Set( linbuf 64000 )
That should fix compilation problems in most cases. But Iīd recommend
trying to minimize part and object size first. Think of the frame rates.
Andreas
struck a strange problem
I am making a structure(about 30 parts) and testing the look of it as I build
it, in FS2000, using Apt 2.6 to compile the scenery.
Suddenly Apt 2.6 stopped compiling, showing a error message about the object
being out of range????
By removing some of the structures parts Apt 2.6 will again compile OK. If I
put the parts back in, same problem.
Does FSDS or APT 2.6 have memory restrictions??. Is this a common problem??
In dire straights,
Clive ( ausie ) Marriott.
Clive
You have exceeded scasmīs linebuffer memory. By default scasm has a certain
limit of code lines for each scenery object. This is a presign that your
object is most likely overdesigned, with too many points and polygons.
Take care that you are defining structures as simply as possible. E.g.
a sphere wonīt always need 32X32 sections, you can make it with 8X8 or
16X16 as well.
A cube wonīt need 8 sections if it has a regular shape. 1 section is enough
then.
Whenever possible, combine parts and points. Select two (or more) parts
and execute "...join selected". Then click "...snap to scale".
There are of course much more ways of minimizing the code size.
But if you really want to ( or need to ) stick with your object size, you
must reedit the macro with wordpad and append the following two lines
to the top of the macro:
Set( areamx 64 )
Set( linbuf 64000 )
That should fix compilation problems in most cases. But Iīd recommend
trying to minimize part and object size first. Think of the frame rates.
Andreas