RDK Bugs

[dalomar_cg]

Re: RDK Bugs

As far as I've seen the new RDK doesn't really have too many new things. It may have some fixes behind the scenes, but there isn't to much of a difference from the users standpoint.

[joe_b]

Re: RDK Bugs

Do you recommend to install new releases of the RDK? Do it improve the mapping tool?

I don't know if there are any improvements to the mapping tool in the latest RDK. But I don't see any harm in having the latest version of RDK. If it causes any conflicts with VfR you can always just reinstall the version we ship with our installer.

[ALTO]

Re: RDK Bugs

Do you recommend to install new releases of the RDK? Do it improve the mapping tool?

From what i know, mapping in Rhino 4.0 is not a part of RDK but it's an internal feature.

Also in the last version, Displacement is no more available with RDK but as a separate plugin: LINK

[joe_b]

Re: RDK Bugs

From what i know, mapping in Rhino 4.0 is not a part of RDK but it's an internal feature.

Yes - you're right. The mapping is only done by RDK in Rhino3. That always slips my mind since they are both, essentially, the same thing

[Micha_cg]

Re: RDK Bugs

* Allways if I open a Rhino file, the "unpacked" texture of a tube is "pack" again. The surface settings are disabled, but the old values are grey out visible. After _unpacktexture it works fine again.

* I copy a model from one file to an other and the mapping is lost. I can set all mappings again. (I start to set the mapping again, but than the jumping interface bug makes me crazy.)

[dalomar_cg]

Re: RDK Bugs

RDK apparently causes the viewport/render settings to always revert back to the default settings. Discussed in this thread here

[alex321]

Vray For Rhino 4.0 bug

Hi

I am unable to see my mapping widget I used to be able to see it before

thanks

Alex

[dalomar_cg]

Re: Vray For Rhino 4.0 bug

There is a bug with RDK that the mapping widgets are created on either the Default Layer or the Top-Most layer. So that means that if that layer is hidden or locked, so will the mapping widgets.

Unhide either the Default or the Top-most layer and that should take care of it for you.

EDIT: I've moved this to RDK bugs thread

[Micha_cg]

Re: RDK Bugs

* Vray Bug: sometimes the mapping of the rendering dosn't match with the mapping of the widget/viewport. The Rhino renderer show the right placement, so I suppose it's a VfR bug. It's a very confusing bug.
Damien, did you get my "crazy reflection" email with the same problem.

* Rhino bug: If I jump from VfR to Rhino renderer, than the mapping interface don't show any previous assigned mapping, but the mapping is still activ. If I assign a new mapping, the same channel is used, but with a fresh mapping. If I jump back to VfR, the old mapping is back again. Is it a feature or a bug? It's confusing, to get render engine dependent mapping widegets. For example I can not edit the VfR mapping if I enable the Rhino renderer.

[dalomar_cg]

Re: RDK Bugs

I've noticed that sometimes the mappings don't match the actual widget...My solution, delete the mapping channel, assign random material, reassign original material, redo mapping. I know it sucks, but thats all I got.

I did get the crazy reflection email, but I still have to look at it (yesterday was a holiday over here)

As for the v-ray/rhino render material switch thing, remember that we are the only ones reading our v-ray material, so as far as rhino is concerned the object has a mapping widget with no map. Once you assign it a map as a rhino material, then everything is fine and dandy with the rhino renderer, and once you go back to v-ray all we do is read the mapping widget again, not the map.

[merlik585]

Re: RDK Bugs

I've noticed that sometimes the mappings don't match the actual widget...My solution, delete the mapping channel, assign random material, reassign original material, redo mapping. I know it sucks, but thats all I got.

I also have the same thing,and this is also my solution.One thing if I managed to map a roof,and know that I have to rotate the map lets say 90d,if I do it before actually do a test rendering it is fine,if I map it and don't do the rotation,do a test render,notice my error,rotate the widget then it does not work,no matter what I do.That is when I need to delete the mapping and start again.

Renee

[Micha_cg]

Re: RDK Bugs

As for the v-ray/rhino render material switch thing, remember that we are the only ones reading our v-ray material, so as far as rhino is concerned the object has a mapping widget with no map. Once you assign it a map as a rhino material, then everything is fine and dandy with the rhino renderer, and once you go back to v-ray all we do is read the mapping widget again, not the map.

The problem is, if you set a mapping, than it is editable in the original renderer engine only. If you set a mapping in Rhino render mode, than in Vray mode you can not edit. Same in the other direction. And if I jump to Penguin, than the mappings of Vray and Rhino are not editable. It makes no sense, that the mapping can not be edited -> bug or?

And the other problem: the workaround help, but did you mean, it is on the bug list now?

[Micha_cg]

Re: RDK Bugs

Today I got an old bug again: if I turn a box mapping 90°, than one side of the box mapping looks complete stretched (viewport and all render engines -> Rhino bug). To bad, that I'm in the middle of a project and so I lost much time.

It's hard to use this McNeel mapping tool for a professional work with tight deadlines.

[Micha_cg]

Re: RDK Bugs

Latest news from Andrew (McNeel) - no fixes befor SR2.

http://news2.mcneel.com/scripts/dnew...m=262690&utag=

[dalomar_cg]

Re: RDK Bugs

Not that I really like to hear that any fixes won't come until SR2, Brian (Gillespie of McNeel) did say the SR1 is pretty much out the door (see quote below). It be pretty tight to try and fix it for something thats almost already released. It would be nice if the fixes could be bundled with RDK even though mapping technically does handle the mapping anymore. But there's also no guarantee that the next RDK release will come before SR2. Either way, it looks like we're floating adrift for a little while longer :'(.

This is the final Release Candidate for SR1; we'll make it official next week unless you report critical bugs