#Wierd goings on
7 messages in this thread
Well, this is a call for help from a dealer who is not as up to speed as he
needs to be!
Our customer upgraded from Rel 2 to Rel 3.0A, via upgrade kit (lot # 942400).
Since this upgrade, strange things happen while using 3D editor. For instance
– add a light, save the file, recall the file and adjust the light – and the
light values are out of limits. The Multiplier value is shown as "NAN", rather
than a number, etc. Rendered output will contain garbage at times, and the
program will hang-up the computer.
On one occassion, the HLS values for a light which was being adjusted were each
"271", illegal numbers. They were displaced to the right of where they should
have been, too. The pgm seems to have a conflict with display memory.
Here's the system config:
Taiwan mainboard clone, 486DX66, 32MB RAM, with Adaptec SCSI I/F and Quantum
1.8GB drive. We have tried both Trident and Cirrus VGA cards, using Vibrant
set-ups – both same results. Render O/P is to VMAXX-10 board, YUV output. All
memory management is by 3D Studio. Even taking out HIMEM doesn't help.
We reloaded Rel 2, and everything works well.
Any suggestions, or further questions?
Ron Koyich
Hintak Limited – Hong Kong
(Customer's s/n = 660-60000039)
<< The pgm seems to have a conflict with display memory.>>
From your description this sounds likely. You are conflicting with something. 2
things to try:
Completely strip the system. This means only loading files, buffers, prompt,
and mouse. Nothing else. Reconfigure 3DS for just VGA. Does it work?
More likely:
You need a memory manager like QEMM that will allow you to identify and exclude
the region of memory that your video and output baords are using. Exluding the
memory ranges will avoid many conflicts.
-Brian
Thank you for your quick reply, Brian. Your comments on QEMM seem to be at
odds with the advice we've received from Autodesk Far East. The technician
there told me to not use any memory manager, that your product had its own
inbuilt.
Will try exclusions in EMM386. Do you have any reason for suggesting QEMM over
EMM386?
Does your company have any comment on the statement from our frame buffer
manufacturer that says, "3D-Studio people did not adhere exactly to the ADI
spec in release 3, and will not talk to the ADI people to give them the
necessary info to allow drivers to be modified." They go on to report there
are problems in release 3 reported by their customers.
All I want to do is get the customer up and running, not to get embroiled in
another finger pointing excercise.
Thanks again, Ron
<<. Your comments on QEMM seem to be at odds with the advice we've received
from Autodesk Far East. The technician there told me to not use any memory
manager, that your product had its own inbuilt.>>
3D Studio does have it's own memory manager built in, and on most computer
setups you would not need to run any other memory managers.
However, some periferals or output devices require the exclusion of a certain
range of memory. (For example the Targa cards often require a section of memory
where video drivers are to be loaded.) In these cases, you need a memory
manager to perform these exclusions when you boot your system. EMM386, or QEMM
would do this.
<< Do you have any reason for suggesting QEMM over EMM386?>>
QEMM gives you a number of memory optimization and diagnostic features that are
not present in EMM386. It makes diffucult memory management much easier. I
personally prefer it.
<<Does your company have any comment on the statement from our frame buffer
manufacturer that says, "3D-Studio people did not adhere exactly to the ADI
spec in release 3, and will not talk to the ADI people to give them the
necessary info to allow drivers to be modified.">>
I do not understand this comment. How can we not adhere to the ADI spec? We
developed it. Also, registered ADI developers have direct telephone support
from Autodesk, so the comment that we will not talk to developers is wrong. It
is in our best interest to promote as much 3rd party development as possible.
If they are an ADI developer, then they have a direct line into 3DS.
<,All I want to do is get the customer up and running, not to get embroiled in
another finger pointing excercise.>>
We appreciate your efforts. Let us know the results, and keep us informed if we
can offer more suggestioins.
-Brian
Thanks for your clarifications, Brian.
Going through the machine in question, and excluding the VMAXX-10 area, and the
Cirrus VGA, using EMM386, I still have problems (including in Rel 2.0). While
drawing a circle, for instance, in 2D, when I try to open up the circle, I get
a four sided thing, instead of a circle. Another time we launched, the circle
was OK. When rendering to the VMAXX we're getting breakup in the rendered
surfaces.
On reflection, and much discussion with the customer, I find that all his
problems started when he installed the Quantum 1.8GB drive and Adaptec SCSI
controller. We are using the BIOS on board the ADAPTEC card, with the card at
base addr 330. Is there a chance of a conflict here?
Thanks again – Ron
<< While drawing a circle, for instance, in 2D, when I try to open up the
circle, I get a four sided thing, instead of a circle.>>
Well, A circle IS a four sided thing. In the shaper, a circle and a square are
exactly the same entity, except on one the line segments are curved. Check the
shaper settings, especially the number of steps you are using to create
objects.
<< I find that all his problems started when he installed the Quantum 1.8GB
drive and Adaptec SCSI controller. We are using the BIOS on board the ADAPTEC
card, with the card at base addr 330. Is there a chance of a conflict here?>>
Always a chance of a conflict. Make sure you add the /SAVEREGS switch to the
device= line for the SCSI card. Beyond that, you probably need some more
advanced memory diagnostic tools, like Manifest, to identify exactly what the
SCSI card is doing in memory.
-Brian
<<Well, A circle IS a four sided thing. In the shaper, a circle and a square
are exactly the same entity, except on one the line segments are curved. Check
the shaper settings, especially the number of steps you are using to create
objects.>>
Brian, the problem is variable. One time it might be a four sided whatsit, and
the next a circle. Remember, this is a setup that was working perfectly well,
and still does except when the conflicts come.
Haven't heard of the the "/SAVEREGS" switch, but will investigate it.
Again, thanks for your help. Ron