#Object color creation
16 messages in this thread
I have a related problem. Isn't the object color box supposed to be
the current color? I can click on the box, have the color selection
dialog come up with 64 colors, pick a color, hit OK, but the color
button is still white. I'll make a object which will appear in the
selected color, say red, but the button is always white. Any Ideas?
Thanks,
David
The color box on the icon panel is the "create color," which is the
color an object is _created_ in. This is not the same as the active
color in the Change Color dialog box. The active color is simply the
default color used when you invoke Modify/Object/Change Color.
Jack,
I'm not talking about changing colors. I open 3ds, click on
the create color icon, the create color dialog comes up, I pick red,
click OK, and the create color icon is still white even though all
new objects created are red. Page 4-10, second paragraph says "Click
to select a new create color, and then click on OK. The new color
appears in the Create-Color swatch, and…". Shouldn't my create
color swatch icon now be red, not white? Or am I mistaken?
David
I can't duplicate your problem on my system. Anyone else out there have this
problem? If so, please include the name of your main display drivers. That's
the only thing I can think of that might cause something like this.
– J
I am using the built in vibrant drivers at 800x600x24 bit with
a Hecules chrome. I can't drop to 256 colors because the Chrome only
supports 24 bit. When I get the chance I'll set 3ds to run VESA
8x6x256 on an ATI and see if it does the same thing. I'll let you
know.
When the built in display drivers are updated by Vibrant, how
is that distributed? Will it be in the form of 3ds3.01, or can it
just be a single upgrade disk from Vibrant that will replace just the
drivers?
I believe it will either be a patch or a replacement for the
vib3ds.vlm file. The plans call for it to be uploaded to CompuServe
and distribute through other familiar means. (Dropped from airplanes,
etc.) Don't hold me to this, though, because I haven't seen an
upgrade yet.
I have been able to duplicate this problem when using the Vibrant driver for
the Tseng 4000 with any rez with >256 colors for the Main Display.
Not a problem. I don't really need >256 in the Main Display anway.
— James —
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
Display anomalies, such as the ones you're describing, should really be
addressed to Vibrant. I've only got one display card, so it doesn't do me much
good to try to troubleshoot display problems. Brian Massey is on the forum here
representing Vibrant. You might try him at ID# 71034,2611.
– J
(PS – Don't worry about your project. It'll come out fine.)
Thanks, I think I'll call them today. After starting some work
yesterday, I realized the problem was more widespread than I thought, placing
polygons in the 2d shaper accurately is next to impossible because once I pick
it up, I can barely see where I move it until its dropped. So I've switched to
the VESA drivers. They're a little slower, but at least they work properly.
David
"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."
David,
We (Autodesk and Vibrant) have not been clear about support for their drivers.
In fact, we're still sorting it out!
We entered an agreement with Vibrant that states that Autodesk can call Vibrant
for support problems (no, not unlimited support). Customers were to call their
dealers for support on problems, and dealers call Autodesk for help.
Vibrant's phone number on the VIBCFG screen was intended as a sales tool for
3DSers who wished to follow up with Liquid Speed, etc. Unfortunately, Vibrant
has been flooded with support calls from 3DSers and we're trying to come up
with a solution so that they don't feel they're passing the buck when called.
Also, they don't have the resources to handle all the tech support issues
surrounding their drivers. We're lucky to have Brian Massey on board in the
forum.
So for now, report bugs as if it were an Autodesk product. We don't know all
the answers and will pass info to Vibrant. Vibrant's contract states that they
will come up with fixes or workarounds to documented reproducible bugs.
Nik
Nik,
I just called Vibrant this morning and dicovered thier aversion to
dealing with 3ds users directly. They told me I had to go through my dealer
with any display problems. He took down a brief description of the problem
(probably just to get rid of me) and admitted they've been having some TIGA
problems. I luckily have a workaround to the problems for now, but if I had to
notify my dealer, who then goes to Autodesk, who tries to verify the problem
and then goes to Vibrant, who checks on it, then gets back to Adesk, then my
dealer, then me again, I'm worried I'd be old and gray before I found anything
out.
I understand thier concern about being flooded with calls on a
product they're not obligated to support directly, but I'd love to
cut out a few steps in reporting some display problems. Can I E-mail
you or Brian Massey a discription of the problems and my system info?
This way I can be sure Vibrant is aware of the problem and the info
is not lost somewhere in the long chain it would otherwise have to
travel.
Yes, please email Brian Massey or better yet both of us. Vibrant has
agreed to fix bugs submitted by Autodesk, but it will probably help
to have Brian Massey concerned about the bug too.
Thanks. The bug would be easier to replicate and record if you can
include your config/autoexec/*.bat you run before starting 3D Studio.
I'm sorry that we're having a problem with this "middleman" approach.
Product Support at Autodesk and Vibrant have been on the phone
several times this week trying to make sure that we have the right
communication to keep people happy and confident.
Nik
Nik,
Thank you. I'm using the VESA drivers now, so I'll be ok for the time
being. I will try to E-mail you and Brian at the end of the week with the
details.
David
David, PMJI Did you try and leave me a message on our phone system?
I thought I got the name but the Phone Number was not complete.
Oh..Ya!!! >> I'm worried I'd be old and gray before I found anything
out.<< What's wrong with being old and Gray!!!!!. Murph'
James,
>>Did you try and leave me a message on our phone system?<<
Nope. Wasn't me.
David