#Can't create Flic file
14 messages in this thread
As John says, it sounds like you're running out of disk space. Are you using
the High palette mode, by any chance?
– G
I encountered the same problem saving a 10-frame flic in low pallette mode. I
could save as sequential TGA frames, but not as a flic. I suspect it was a
path problem in 3ds.set, but I never nailed it down.
I worked around the problem by resetting 3ds and merging everything from the
offending file. I also rendered on the local machine, since the problem
occurred mainly during "NET ASAP" renders.
I've also seen a "can't save last image file" message occassionaly. I wonder
if this is related in some way.
I don't think Peter mentioned anything about net rendering, David.
Re "can't save last image" messages… whenever I've seen that, it's because I
had a .prj file from another machine with a different path structure. That'll
do it every time.
– G
>> I don't think…
Oops, sorry. I didn't intend to confuse the issue.
>> .prj file from another machine with a different path structure.
Could that also be the source of the "Can't create flic" message? I tend to
move projects back and forth between machines without always checking the paths
in the configuration box. I don't do flics that often, but I was surprised to
run into that message. TGA frames always saved fine.
Without seeing your exact configuration(s), I couldn't tell.
– G
Near the end of this week, I expect to have some time for "sleuthing". I will
be swapping some hardware around at the office and I plan to work my way
through my list of "gee, why doesn't that work" items. I'll post any
interesting findings here, and if the "can't create flic file" shows up again,
I'll properly document my methods and configurations for your review.
Gary, David, and John:
Thanks for replying. I'm sure I'm not running out of disk space. My system is
standalone – no network.
An interesting point is that the problem can be fixed, temporarily at least, by
resetting 3DS and merging everything from the bad project. David mentioned
this worked for him, too.
The error always occurs at the end of the "Encoding 256-color image…" stage
on the first frame. I haven't been able to identify any pattern to when it
works or doesn't work.
Pete
You have no idea how much disk space High can use. For example, if you're
making a 640×480 flic that's 200 frames, it would create a 921K 24-bit temp
file for each frame, or about 184 MEGABYTES of temp disk space.
What palette mode are you using?
Regardless, if the error is occuring at the end of the first frame, storage
space is definitely not your problem. If this only happens with one project
file, it sounds like something's wrong with that specific file.
– G
I have never used High palette. I always use Medium or Custom. Also,
I have been using 320×200 exclusively to save time.
If it only happened with one project file, I wouldn't be bothering you
about it. Unfortunately, it has happened with most projects lately.
I still can't predict when it will happen next, but I will keep
trying to detect a pattern.
>> The error always occurs at the end of the "Encoding 256-color
>> image…" stage on the first frame. I haven't been able to identify any
>> pattern to when it works or doesn't work.
This is exactly when it occured during my animation as well. I am planning to
spend some time on this "problem" later this week (when there's some free time
in my schedule) and I'll post my findings here. It wasn't terribly high on my
priority list, since I normally record single frames to tape, rather than flics
to disk. Please keep me posted if you make any discoveries.
David (et all.. )
<< can't create flic.. >>
Any other comments from anyone about this? Since the wishlist
season is almost over I'm now on a bug hunt….
jonas[adesk]
>> I'm now on a bug hunt….
Check under your desk, or in the lunch room <g>. But seriously, I don't think
the "can't create flic" message is a bug. It is more likely a mistake that I
made in setting paths properly. Because I've had work to get done, I put it
aside to be "checked out later". That pile also includes a Lantastic/Diaquest
conflict I haven't figured out yet. As long as there are work-arounds to my
problems, I tend to note them and go about getting my work done, rather than
spending time (sometimes days) to find the source of the problem.
"I don't think the "can't create flic" message is a bug."
I'm inclined to agree, although the usual suspect doesn't seem to be
guilty! (Disk space). It seems that Project files might be
involved. If you are switching files from one machine, where they
are created, to another, where rendering them produces the error, it
makes sense that the original machine would work fine, and that the
second machine would be able to create a fresh file and render
correctly.
I was told by a dealer that although he couldn't explain it, he ran
into similar rendering problems until he removed a project file that
was "just sitting there" in his Projects directory. On this theory,
you could move all your projects to a location that 3D Studio
wouldn't see, and render your flic file and not have this error. (I'd
say *that* would be a bug!). I cannot duplicate the dealer's claim
however.
>> I cannot duplicate the dealer's claim however.
I was planning on investigating later this week, but a rush job just came in
that should keep me going crazy until April 10 or so. I will post my findings
when I get into "test mode" after that.