#Flic Rendering Problem
6 messages in this thread
We are having a problem while rendering a flic file in 3ds. We have had the
problem with version 3 and are now experiencing it in our new 4 upgrade.
While rendering a flic we get the following message:
Cannot Create Temp File:
C:\3ds4\temp\$fliwi$.tmp
Error # -6 in making post_med
The system we are using is a Pentium 90mhz with 24mb RAM and 300mb open on the
hard drive. Thanks in advance for any help.
John M. Hester
Digital Sight and Sound, Inc.
It sounds like you've run out of disk space on your hd partition. Since you've
got 300mb free, it most likely means that you've got a flakey hd controller.
What kind of controller do you have in that machine?
– G
I don't know really. The machine is a Packard Bell P90 with all the bells and
whistles but that means nothing really. Could there be a setup problem
(autoexec,config,etc.) that might cause a problem like this?
Sure could. Perhaps Jonas or Brian can help you diagnose it further.
– G
John,
Even with 300MB free, it is possible to run out of hard disk space. What
resolution are you rendering to? What palette mode? Do you have a lot of
shadows and texture maps? Can you render the exacat same animation but at a
lower resolution?
<<Could there be a setup problem (autoexec,config,etc.) that might cause a
problem like this?>>
Absolutely. The way to find out if that is the problem is to strip the system
and diagnose. I have included detailed instructions for this at the bottom of
the e-mail.
-Brian
Title: Clean system boot; diagnostics for memory conflict…
Description:
To confirm that the problem is caused by a memory conflict, re-start the
computer with simplified settings (a 'stripped system') and see if the problem
goes away.
For DOS-only computers, a stripped system means that the computer is rebooted
without terminate and stay resident (TSR) programs nor device drivers that are
not absolutely necessary for the operation of the operating system and
computer. The Autodesk program should also be configured for VGA display if
possible, to rule out display driver conflicts.
To reboot into a stripped system for 3D Studio and Animator Pro, change the
system files as follows:
CONFIG.SYS should contain only:
FILES=40
BUFFERS=20
AUTOEXEC.BAT should contain only:
PATH=<your path>
PROMPT=<your prompt>
You may want to use the DOS SYS command to create a bootable floppy for this
trouble-shooting exercise and place these simplified system files on the
diskette. Or, you may edit the existing CONFIG.SYS and AUTOEXEC.BAT files
currently on the hard disk (make back-up copies first). Make sure you have a
bootable DOS floppy on hand, just in case the computer has trouble rebooting.
Note: Quarterdeck QEMM users may find it helpful to review the QEMM
trouble-shooting documentation and use the Analyze utility to track down memory
conflicts.
Trouble-shooting:
If the program now operates correctly, the next step is to determine which
program or driver in your system files is causing the conflict. Edit the
CONFIG.SYS and AUTOEXEC.BAT files, adding one device driver or TSR command at
a time, rebooting, and starting 3D Studio/AAPRO until the error reappears.
When the error happens, the last item you added to the configuration is
probably the trouble maker. Once we know which drivers are conflicting, we can
determine the proper course of action.
If you are using special display adapters (for example, a Targa frame buffer),
you should check the documentation that came with the display driver to see if
special memory settings or EMS exclusions are needed.
Thanks so much Brian. I can indeed render the same image at lower resolutions
and as a shorter flic. We are rendering at 256 color. Maybe this is a
work-around situation? Anyhow, I will try some of your suggestions and mail
back if I need some more help. Thanks again for everything.
NRN
John M. Hester
Digital Sight and Sound, Inc