You can stick to this "arrogance" and ignore all the logical comment/remarks I just made.
Also since we do not know each other, I d avoid characterisations.
Cheers
Moderator: juanjgon
- When something is called "vertex attribute" and accepts "point attributes" is simply wrong UX and super confusing.
- When I have to promote prims to vertex so i get prim attributes
- When i use rppk maps to get attribs (whatever this is called).
When I repeat twice that exposure slider shouldnt be from 1-1000 and i dont even get a reply, what does that say to you?
thanulee wrote: Afaik already the c4d developer is helping rebuild the ipr in H if that says something to you.
thanulee wrote:Also what is "ready solution"?Not having exposed a single color in Dome light ? (which dome light doesnt even exist?)
thanulee wrote:When I repeat twice that exposure slider shouldnt be from 1-1000 and i dont even get a reply, what does that say to you?
thanulee wrote:- When something is called "vertex attribute" and accepts "point attributes" is simply wrong UX and super confusing.
- When I have to promote prims to vertex so i get prim attributes
- When i use rppk maps to get attribs (whatever this is called).
juanjgon wrote:thanulee wrote:Also what is "ready solution"?Not having exposed a single color in Dome light ? (which dome light doesnt even exist?)
The number of possible UX/GUI combinations of all the Octane features inside a single RenderTarget HDA are almost unlimited. Of course, it is possible to add this feature to the included HDA, and of course, it is also possible to include an additional HDA and let it work as a dome light. This is the good news, in the Houdini plugin, almost everything is possible. The bad news is that I add all these features when I can, and they depend on the number of requests about them, so I have added them to my TODO list to try to have them available later this year.
Thanks for your patience,
-Juanjo
Users browsing this forum: No registered users and 17 guests