#eXternal
8 messages in this thread
I too hnave a problem with the eXternal command. I load in the object
(using eXternal, of course!) and make some changes to the object (ie. color
reflection etc) then I close the attributes requester and go to re-save the
object. The screen flashes BUSY for about a half -second and everything
seems ok.then I Delete the object and try to load it ihn again (using
eXternal). I get an error message about some 'INFINITE RECURSION' in the
object and the object WILL NOT LOAD> It has gone bye-bye. If I look in the
directory it came from (Usually I keep it in the CEL dir) The file is there
but instead of being 17k long it is now 128 and if I try to read the file
all I get is: FORM What (if anything am I doing wrong ?? I am using a 2000
with a 2620 (2 megs) and a HardFrame controller. Also have the new Agnes
chip and a 2 meg (16-bit) board. Any Ideas??? thanx eli t
Eli, this is a known bug in Turbo. The external command has never worked
to my satisfaction and it continues to have problems. When you save an
object, immediately try to reload it to the screen. If it loads properly,
just delete it again. If it doesn't load properly, try renaming it and
saving your object again. Sometimes I have found that I have to exit the
program before I will get the 'infinite recursion' message to go away.
I have tried re-naming it, and also I run machII with Tsilver, that way I
can press Amiga-M and push the silver screen to the back (even while in the
object editor) and check the file length in the background. Well, at least
this is an 'expected' problem, Is there anyother method you can offer ?? I
mean, even with a HardDisk if I do an Overscan20 Interlace HAm image for 60
frames each CEL is 100 k or so !! thanx again for your quick reply… eli
ok here's the thing… I just tried it again and it seems the problem
lies in the SAVE command in the object editor. That is when the corruption
occurs not whenI try to get the object back with external! I eem to have
stumbled onto a workaround tho'… 1- USing eXternal load your object
2-Change any/all parameters in the object 3-exit the (key) celland go to
the main screen 4-SAVE the 'changed' cell (even tho' there really is no
change, as the change was to the eXternal object) 5-re-enter the cell and
click on the object 6-SAVE the object, now the BUSY pointer stays up for a
reaonable amount of time 7-delete and load (using eXternal) the modified
object and voila! it work !! Like I said though it seems the problem
happens when you AVE the object, not when you use the external thingy..
Lemme know if this works for you.. eli
Eli, I've encountered the problem both with saved and external objects.
Like I said, the problem seems entirely random. You can tell with a hard
drive though, because the drive light will flash far too briefly to have
saved anything like an object.
rick, alas…you are correct. It Is entirely random (sigh) well, when I
have gotten the savew to work and have reloaded the object with external it
seems that my animation path (tho still there in STORY) don't work. Only
when I waste the disk pace with full objects in each frame (about 3 megs
worth!!) then the story works !! What about the new designer and renderer
pgms? How do they work that way ?? eli
Your path should still function correctly. You MUST save the object AFTER
assigning it a story . Then when you reload it as an external object, it
will follow the proper path. Don't know much about the new programs, but
the bugs will be fixed. –Rick
Eli, in my experience the problem is entirely random, but I wouldn't
abandon external files entirely because of it. Try quitting Silver, maybe
even reboot. I can't tell you the exact sequence I've used, but I do get
the external files to load and save correctly. If the save didn't happen
properly you'll know it right away.