yang686526

odgimaterial issues

odgimaterial issues
thanks to sergey's help i'm able to use odgimaterial.
but there are some remaining questions:
1.) if i set the material traits to
tmaterial->setmode(odgimaterialtraits::kadvanced);
autocad says the materialmode would be an advanced metal.
did i forgot something?
2.) in objectarx i can say something like
tmaterial->setdiffuse(tcolordiff, acgimaterialmap::knone);
thus setting up an material using a diffuse color instead of using an texture.
why isn't that possible with opendwg?
3.) is there a good example setting up materials? i've done this before in objectarx ... but opendwg seems to behave pretty ... uhm nasty/different.
cheers
psy

psy
# 23rd october 2007, 09:58 am

moderator join date: mar 2002
posts: 2,994
materials in dwgdirect are expected to work as in objectarx (2008). but this code is poorly tested because was not used intensively yet.
it would be great if you having experience with materials in objectarx would reports differences in their behavior in dd and arx.
1. where are only 2 modes defined in arx headers (realistic and advanced). where does autocad report "advanced metal"?
maybe you forgot to setilluminationmodel()?
2. what is the difference in setdiffuse() behavior in dd and arx?
3. we have no dbmaterials sample. the client code is expected to be the same as in arx. we hope to improve our materials implementation with your help.
sergey slezkin

sslezkin
# 24th october 2007, 12:22 am

registered user join date: mar 2007
posts: 12

quote:
originally posted by sergey slezkin
materials in dwgdirect are expected to work as in objectarx (2008). but this code is poorly tested because was not used intensively yet.
it would be great if you having experience with materials in objectarx would reports differences in their behavior in dd and arx.
1. where are only 2 modes defined in arx headers (realistic and advanced). where does autocad report "advanced metal"?
maybe you forgot to setilluminationmodel()?
if i open the "materials"-tab in autocad 2007 sp1, it says advanced metal.
maybe i'm setting some other properties that affect the material mode.
the complete initialization is done as in this block:
code:
oddbmaterialptr tmaterial = oddbmaterial::createobject();
tmaterial->setmode(odgimaterialtraits::kadvanced);
tmaterial->setilluminationmodel(odgimaterialtraits::illuminationmodel::kblinnshader);
tmaterial->setchannelflags(odgimaterialtraits::kusediffuse);
tmaterial->setchannelflags(odgimaterialtraits::kusespecular);
quote:
originally posted by sergey slezkin
2. what is the difference in setdiffuse() behavior in dd and arx?
the signature of the function is the same as far as i can tell. the problem is the missing odgimaterialmap::knull ... only kscene, kprocedural, kfile are declared.
in objectarx i can write:
code:
tmaterial->setdiffuse(tdiffuse, acgimaterialmap::knull);
quote:
originally posted by sergey slezkin
3. we have no dbmaterials sample. the client code is expected to be the same as in arx. we hope to improve our materials implementation with your help.
since i need material support for my project which is identical to autocad 2007 (texture orientation and such things are very very important) i might be able to find some of the bugs ;-)
cheers
psy

psy
# 24th october 2007, 07:21 am

moderator join date: mar 2002
posts: 2,994
quote:
tmaterial->setchannelflags(odgimaterialtraits::kusediffuse );
tmaterial->setchannelflags(odgimaterialtraits::kusespecular) ;
maybe you mean
code:
tmaterial->setchannelflags(odgimaterialtraits::kusediffuse | odgimaterialtraits::kusespecular);
else the second call resets the flag set by the first one.
kscene, kprocedural, kfile are members of source enum and knull is static const acgimaterialmap object.
it makes sense to add it to dwgdirect but for now you can use
setdiffuse(...., odgimaterialmap());
instead of
setdiffuse(...., odgimaterialmap::knull);
this only effects efficiency (no need in constructing object if knull is used.
sergey slezkin

sslezkin
# 5th november 2007, 11:31 pm

registered user join date: mar 2007
posts: 12

hi sergey ...
i've solved most of my material problems but one seems to be a bug in version 2.3.0 and the actual 2.4.02.
code:
tmaterial->setmode(odgimaterialtraits::krealistic);
tmaterial->setilluminationmodel(odgimaterialtraits::illuminationmodel::kblinnshader);
this actually works like a charme, whilst:
code:
tmaterial->setmode(odgimaterialtraits::kadvanced);
tmaterial->setilluminationmodel(odgimaterialtraits::illuminationmodel::kblinnshader);
gives me the described "advanced metal" in the autocad material-properties in autocad 2007.
to me it seems that the enums for advanced and the offset of blinnshader somehow don't express the correct mode. can you second this?
this is really important to me.
cheers
psy

psy

none
? | ?
thread tools



display modes
linear mode


search this thread

rate this thread
excellent
good
average
bad
terrible

posting rules
you may post new threads
you may post replies
you may post attachments
you may edit your posts
is on
are on
code is off
html code is off
forum jump
user control panel private messages subscriptions who's online search forums forums home general topics news questions and remarks business issues industry commentary general software issues documentation issues future directions dwg libraries dwgdirect.net dwgdirect, c++ version dwgdirectx, activex version adtdirect/c3ddirect opendwg toolkit/viewkit dgn libraries dgndirect, c++ version (2.x+) dgndirect libraries (legacy 0.99xx)
all times are gmt -7. the time now is 09:28 pmfff">.
- - -
copyright ?2000 - 2009, jelsoft enterprises ltd.
copyright 1998-2008 open design alliance inc.
materials in dwgdirect are expected to work as in objectarx (2008). but this code is poorly tested because was not used intensively yet.
it would be great if you having experience with materials in objectarx would reports differences in their behavior in dd and arx.
1. where are only 2 modes defined in arx headers (realistic and advanced). where does autocad report "advanced metal"?
maybe you forgot to setilluminationmodel()?
2. what is the difference in setdiffuse() behavior in dd and arx?
3. we have no dbmaterials sample. the client code is expected to be the same as in arx. we hope to improve our materials implementation with your help.
sergey slezkin

quote:
originally posted by sergey slezkin
materials in dwgdirect are expected to work as in objectarx (2008). but this code is poorly tested because was not used intensively yet.
it would be great if you having experience with materials in objectarx would reports differences in their behavior in dd and arx.
1. where are only 2 modes defined in arx headers (realistic and advanced). where does autocad report "advanced metal"?
maybe you forgot to setilluminationmodel()?
if i open the "materials"-tab in autocad 2007 sp1, it says advanced metal.
maybe i'm setting some other properties that affect the material mode.
the complete initialization is done as in this block:
code:
oddbmaterialptr tmaterial = oddbmaterial::createobject();
tmaterial->setmode(odgimaterialtraits::kadvanced);
tmaterial->setilluminationmodel(odgimaterialtraits::illuminationmodel::kblinnshader);
tmaterial->setchannelflags(odgimaterialtraits::kusediffuse);
tmaterial->setchannelflags(odgimaterialtraits::kusespecular);
quote:
originally posted by sergey slezkin
2. what is the difference in setdiffuse() behavior in dd and arx?
the signature of the function is the same as far as i can tell. the problem is the missing odgimaterialmap::knull ... only kscene, kprocedural, kfile are declared.
in objectarx i can write:
code:
tmaterial->setdiffuse(tdiffuse, acgimaterialmap::knull);
quote:
originally posted by sergey slezkin
3. we have no dbmaterials sample. the client code is expected to be the same as in arx. we hope to improve our materials implementation with your help.
since i need material support for my project which is identical to autocad 2007 (texture orientation and such things are very very important) i might be able to find some of the bugs ;-)
cheers
psy
quote:
tmaterial->setchannelflags(odgimaterialtraits::kusediffuse );
tmaterial->setchannelflags(odgimaterialtraits::kusespecular) ;
maybe you mean
code:
tmaterial->setchannelflags(odgimaterialtraits::kusediffuse | odgimaterialtraits::kusespecular);
else the second call resets the flag set by the first one.
kscene, kprocedural, kfile are members of source enum and knull is static const acgimaterialmap object.
it makes sense to add it to dwgdirect but for now you can use
setdiffuse(...., odgimaterialmap());
instead of
setdiffuse(...., odgimaterialmap::knull);
this only effects efficiency (no need in constructing object if knull is used.
sergey slezkin

hi sergey ...
i've solved most of my material problems but one seems to be a bug in version 2.3.0 and the actual 2.4.02.
code:
tmaterial->setmode(odgimaterialtraits::krealistic);
tmaterial->setilluminationmodel(odgimaterialtraits::illuminationmodel::kblinnshader);
this actually works like a charme, whilst:
code:
tmaterial->setmode(odgimaterialtraits::kadvanced);
tmaterial->setilluminationmodel(odgimaterialtraits::illuminationmodel::kblinnshader);
gives me the described "advanced metal" in the autocad material-properties in autocad 2007.
to me it seems that the enums for advanced and the offset of blinnshader somehow don't express the correct mode. can you second this?
this is really important to me.
cheers
psy