RDK Bugs

[merlik585]

Re: RDK Bugs

I was more talking about the position.

1)set the sunlight manually
2)click ok
3)modify it via the object light properties,you have to select manually again,and this is where the problem is,the graphic representation doesn't show the position where it is,if I only want to tweak it a little bit,I have to remember the previous azimut and altitude,it should represent the orientation of the sun as it is.

Is it clear ? Kind of hard to explain....

Renee

[Micha_cg]

Re: RDK Bugs

Did you mean, you can not change the geographic position of a previous placed sun?

[joe_b]

Re: RDK Bugs

3)modify it via the object light properties,you have to select manually again,and this is where the problem is,the graphic representation doesn't show the position where it is,if I only want to tweak it a little bit,I have to remember the previous azimut and altitude,it should represent the orientation of the sun as it is.

Is it clear ? Kind of hard to explain....

Yes - I believe I understand. You want the dialog to be populated with the information from the light you are editing. At this time its not possible through the RDK to send any information to that dialog - we only get information back from it. I'll see what Andy has to say about that.

[merlik585]

Re: RDK Bugs

Did you mean, you can not change the geographic position of a previous placed sun?

Yes I can Micha,but the graphics that allow us to choose the position manually,does not stick between modify session,the sun itself is positioned correctly.
May be there is something I am not doing correctly.

For example if I set the sun with the location and hour,and I go back to modify the location or the time of day,what I see is the position where I was,from there I can tweak.That is what I want for manual setting,having the graphic representation of the position remember the state it is.

Renee

[Micha_cg]

Re: RDK Bugs

Ah, I see it here too. It's not possible to modify a previous manual set position.

[Micha_cg]

Re: RDK Bugs

Assign a box mapping to an object -> set the mapping box to a cube (f.ex. 10x10x10). Now scale the object in one direction. The mapping is scaled, the widget too, but the numbers at the widget size options are at the old values. If I scale the widget to the right size, the numbers are wrong. I find now way, that widget size and numerical size match again.

[Micha_cg]

Re: RDK Bugs

The Mapping UI is much to big, only a few options but it's soooo big. But this is not the bug I want to report now.

Bug: if I want to set a the texture repeat, than I must scroll down to the repeat options and if I type in the x repeat and want to go to the y repeat option, than the UI jump back to the top and I must scroll down again and search for the right field. Box mapping -> three times scroll down.

The mapping tool could get more attention.

[crazygreg]

Re: RDK Bugs

I have a mapping problem
(click on it to see the full size image)
Here a screen capture, with material setting,
View port view is correct, but rendering is bad, tried on two different files (two different keyboard), but same probleme. , tried also with box mapping, but same effect as planar.

This is a png file, tried with png 8bit and 16 bit...same effect :-[

I also realise, that if you change the "repeat" amount in the texture properties, the texture preview in the viewport rendering view become crazy, you need to change the uvw repeat in the mapping option...
Thanks

Greg

Update: I try with any png, and vray seems that it dosn't like this kind of file.
If I just resize the texture with photoshop, I have some other rendering glitch. (even in the preview of the material)

[crazygreg]

Re: RDK Bugs

I just find the solution :
Make 2 diffuse layer
first one: diffuse color with bmp texture with colors, and same texture size but in transparency mask (so black and white texture)
Second one: with "touch" color

I hope my explenation is not too complicate...because my english is kind of bad. :

[Micha_cg]

Re: RDK Bugs

I'm working on a keyboard too and I use the button letter texture for trancparency only too. The color of the letters and the basic color are Vray colors at different layers and no textures. I never got a problem.

[Micha_cg]

Re: RDK Bugs

No texture control of repeat, rotation and offset at "surface" mapping.

Joe, are you in contact with Andy or the other developer of the mapping tool? No changes since a very long time.

[ALTO]

Re: RDK Bugs

No texture control of repeat, rotation and offset at "surface" mapping.

Micha, Surface Mapping works right only with surface objects, to use it with polisurfaces you should digit UnpackTextures in command line.

[Micha_cg]

Re: RDK Bugs

Thanks!!!

[joe_b]

Re: RDK Bugs

Joe, are you in contact with Andy or the other developer of the mapping tool? No changes since a very long time.

I talk with him from time to time but the suggestions we present to him are just that - suggestions. The development of it is his call.

Didn't they just release a new RDK beta last week? I haven't played with it yet. Also - keep in mind that RDK is not just the mapping tools. He's been adding the sun stuff, displacement, and other things.

[Micha_cg]

Re: RDK Bugs

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