#Object color creation
16-Nov-93 18:19:29
Sb: #66537-#Object color creation
Fm: David Stinnett 70214,774
To: Yost Group 76702,413
Jack,
Well, I set the Vibrant drivers to 8x6x256 VESA and the create color
swatch works fine, went back to Chrome 8x6x24bit and the swatch will only stay
white. I have to stick with the chrome, because the VESA drivers are just too
slow.
I've also run into another problem, although I've noticed this in R2
also. In certain files, not very many, but some, when moving the camera in the
keyframer, the camera and fov cone will dissappear and not appear again until
the mouse is clicked to complete the move. The cone will flash here and there
but once you click to move it, it can't be seen clearly until you drop it. When
moving objects in the same scenes, the bounding box of the object can't be seen
unless the mouse is still. If an object is picked up and moved, you can't see
anything until you stop moving the mouse, or until you drop the object. These
things do not happen in the 3d editor.
Here is something you might try out yourself. Run 3ds using the VESA
compatable driver w/256 colors. As in tutorial 20, load office.dxf.
Create a camera near the office door. Enter the keyframer and set total frames
to 600, then create a dummy near the door. Get the path from disk in
office.dxf. Show the path and then move the camera. While moving the camera on
my system the cone will flash in and out until you click the mouse. The same
happens while moving objects.
While using the chrome drivers, this effect is much worse, the camera
being virtually invisible until you drop it. And also (no, I'm not done yet),
when loading a file the info bar at the top of the screen reads "EASE WAIT" and
when loading the office.dxf, the status line on top will flash for a split
second (almost subliminal) for each step it goes through, as opposed to a line
staying on screen long enough to read, then being replaced by another. This
problem only happens with the chrome, but not the ATI with VESA.
Another interesting thing, on the chrome the camera cone is black while
being moved and in VESA it is white. Shouldn't the colors be the same, as long
as Vibrants drivers are being used for both?
Will Vibrant directly support the built in drivers through thier tech
support? If so I think I'll be giving them a call in the morning, if for
nothing else then at least to officially report the problems I'm having. I'm
just now starting on my first 3ds3 project, so I hope I don't find anything
else!
Thanks,
David