[Tyrone Marshall]

Now, the thread Tyrone referred to, doesn't explain how to map images in Cinema or did I overlook something? I did not manage to make any image textures work till now.

Check the message reference above, and if you are still not sure how to make this work. Put in a request for a tutorial and I will see what was not covered in the tips and techniques section.

[cri3d]

you mean this?

4/29/2005 Maxwell Plastic Material Tag

For Plastic Material:

Specular Color - controls the glossiness (From Black to Grey to White)

-Black means no gloss
-White full gloss
-Grey values : Anything inbetween is moving towards less gloss or more
gloss

we know it.
but with cinemaxwell+R1+textures doesn't work.

[mashium123]

Hi all.

It seems to be possible to join plastic tag with tex in c4d.
(Sorry, if this issue already was solved)


-Do your c4d-thing as known. (Add tex to obj + MRplasticTag)
-Render in Mxcl and you'll see (at least I saw):


-now open your mxs scene that the plug gave you and open the mat that should have plastic and tex together.
-there you'll see two layers. try and swap their roughness value.
(Goal is: the layer with the tex in it should have Lambertian on or a high roughness if you wish, the layer with no tex in it should have no lambertian or no/low roughness)

-after that you should see this (at least I saw):



For me, this looks like a plastic-shiny-textured thing. What do you think?

Bye. Mesut.

[spekoun]

Yes. You are right. Cinemaxwell wrongly translates plastic shader... I have same experience... So we have to use custom mxm.. Only diffuse seem to work properly...

So again I must complain. Very small work was done on Cinemaxwell...

[kmwhitt]

Sure, but that defeats the purpose of having a plug-in. I want to do all my work in Cinema without opening Studio and the stand-a-lone Material Editor makes Cinema freeze up. I want a working V1.0 + plug-in without all these aggravating work arounds. Just curious, how many A-Team members were trouble-shooting the Cinema plug-in as it is really less effective than it was with RC5.

[mashium123]

Hm, i see your point.

Plz excuse me, if I act maybe a little naiv (is that the right word?), but I am a bit new to this thing.

Just for commenting: It seems to me, as if c4d is there for preparing data so that the "main thing" (mxst) has something to handle and work with and not the other way round. At least from my few day experience with mr.

When I think about it, it would surely be an unbelievable situation if mr was a module like lets say mocca, hair, ar or all the other modules in c4d.
Some kind of killer-application-thing going on then.

But isnt it lets say similar with other 3rd party renderers in other 3d packages? the lighting, the mats, the whole scene, all this stuff is to be prepared differently for one renderer than for the other?

Just guessing. Don't know about these things for sure. Just reading here and there.

Greets. Mesut.

[kizo]

mashium123 you re right about other renderers, but NL stated seamless implementation of their render engine via plug ins, there was no mentioning of an external app at the time I bought it, so they should provide a working plug for all packages, and not only work on some of them (like the max plug)

c4d plug is very poor in terms of using all the features of the render engine
while in max ( not perfect) more options are available

...and i bet that no a-tem member tested the c4d plug, thats why works so well

[mashium123]

Hi kizo.

I see. So everyone is so angry about NL because of expactations that were not being fullfilled?! Just trying to understand, what get people into such a rage...

You know, I bought mr just one day before release, so i dont have all the long hard way behind me that all the others seem to have. So, from my point of view everything I get from this renderer is purely unbelievable. And everything better to come is just more unbelievable and fascinating for me. I guess it would be different if i had a way behind full of promises...

If promises and announcements would have been a bit more moderate, everyone would be happier now? With the same piece of software? Hm.

P.s. Did I already mention that I LOOOOOVVVVEE the -ml.

Mesut.

[cri3d]

kmwhitt, did you solve our problem?

I didn't yet.

Can somebody post an image with a reflective texture using only a plastic tag (no mxm), please?

[Kabe]

I see. So everyone is so angry about NL because of expactations that were not being fullfilled?! Just trying to understand, what get people into such a rage...
...
If promises and announcements would have been a bit more moderate, everyone would be happier now? With the same piece of software? Hm.

Well, some people here (me included) have Maxwell for over one year. And
considered the promises that were made over a year ago (animation,
motion blur, to name two of them) the progress is indeed very slow.

Also there are long standing bugs with Cinema basics like tag and flag propagation
or even crash bugs that are unfixed since the first Cinemaxwell release.

Tyrone obviously was the only A-Team tester using Cinema, and he didn't
even have time enough for testing to write a few tuts about the new
features upfront.

Under these circumstances nobody expected a stable release. In terms of
software design this still is a public beta (if you consider it as basically
feature complete...).

Kabe

[kmwhitt]

No, I didn't solve the problem. I did find out that the plug-in will export the textures to Studio using the plastic tag, but you must tediously change their properties within Studio for them to show up in the render. It seems the "plastic coating layer" is weighted so high that it obscures the image map. I spent almost two hours last night changing material properties within Studio that would have taken me no longer than 3 minutes in Cinema so that I could produce this (still rendering):

http://home.comcast.net/~kmwhitt/try.jpg

I tried different techniques to make the process efficient to no avail. I tried using the Material Editor within Cinema via a custom .mxm, but you can not map images this way using even simple planar mapping. I tried selecting multiple materials in Studio in the hopes of changing all of the textures at once - no such luck. Now that the plug-in is damaged, the work flow is impossible.

This will be my last render until the guys at NextLimit get their act together. Again, I must ask how many people actually worked on the Cinema plug-in prior to its release and why did they release it knowing that these problems exist? Tyrone, you stated that this works for you - I would love to know which version of the plug-in you have and please do not patronize me again by pointing me to a tutorial that is not even related to the problem. I have been using Maxwell for almost 1 year and this is definitely a bug........

Kevin

[lllab]

i am fighting too with the "v1" plugin.

rc5 plugin was not perfect but stable and it did what i was expecting.
rc5 plugin was in use everyday here,

i fear i will not be able to do my work with v1plugin. so i might go back to rc5, which is very sad for me becuase maxwell1 seems very nice indeed.

just we cinema users are lefta bit behind, please dear programmer of the plugin, give us bugfixes and all missing features.

respectfull but not happy,
stefan

[cri3d]

kmwhitt try this now!

REFLACTANCE COLUR : ALWAYS BLACK (0,0,0)

specular colour : from white to black (as you know)

It works!

[Tyrone Marshall]

kmwhitt try this now!

REFLACTANCE COLUR : ALWAYS BLACK (0,0,0)

specular colour : from white to black (as you know)

It works!

Thanks Cri3d!

Please use the tutorial request sticky and I will see what I can do for you all!

[kmwhitt]

kmwhitt try this now!

REFLACTANCE COLUR : ALWAYS BLACK (0,0,0)

specular colour : from white to black (as you know)

It works!

No, it doesn't. Care to try with this scene?

http://home.comcast.net/~kmwhitt/Maxwell_Test.zip

Kevin