rod.vfx.td
-
Content count
41 -
Donations
0.00 CAD -
Joined
-
Last visited
-
Days Won
1
-
+ 1 on Instance nodes, with overrides, of couse! other feature request: *when moving nodes to other hierarchies, please make Houdini ask user if need update expression links to point to new locations!!! Is very important feature who Houdini don't have.
-
No man, the result is not same of add a grid on second input, because in Polydraw you not limited to the grid projection when creating new polys (360 DoF). And the reason Polydraw creates a topobuild, is because is a WIP tool, so, internally is using topobuild functionality on UI, but with "extras" on code.
-
Vellum???? Whaaaaattttt????
-
makes absolutely sense Michael! Thanks
-
yeap, i do not get why this is a new context, and not just a improvement to ROP context. But i think sesi have a good reason to do this way. So, let's wait to official announcement brother!
-
Nice!! Thanks for the info Aditya!
-
no PolyDraw videos yet? any news from presentation about H17?
-
Cuda cores is other story, here it's brand new RT cores. The mention to "bind to company" is very well known statement of SESI. "The Turing architecture is armed with dedicated ray-tracing processors called RT Cores that accelerate the computation of how light and sound travel in 3D environments at up to 10 Giga Rays per second"
-
No SideFX or Mantra present on a panel of logos of NVIDIA partnership on turing RTX raytracing accelaration presentation. even blender is present... :/
-
11. Ability on mantra ROP to point candidate/force/matte objects to nodes (like object merge node), and not only at object level path (current situation).
-
Feature request for 17 or 17+ 1. A ISOLATE function on viewport, not at nodes... like XSI viewport Isolate function. 2. Make /img more featured to eliminate necessity of going nuke/natron/fusion to do basic/median composition things. (acutally comp in Houdini do only the very basic, but need improve. 3. Make /img network import live output from mantra to see results direct on framebufer output without needs save/reload from/to disk. 4. A some type of high performance sculpting editor, even open source Blender have it (and is very very good and fast indeed). (this is on same thinking of eliminate necessity of exit from houdini to do the basics). Sculpting in 2018 already can be considered BASICS. 5. Make a more correct HiDPI adjustment to interface. (even in .env granularity on scale, some thinks on interface not adapt, like splashscreen, viewport toolboxes , some menus editors, etc..) 6. Bring Save presets to 21 century, not overriding all parameters! 7. Make all nodes show all attributes/inputs/variables available. (actually only few nodes shows, forcing user manually enter attributes and need remembering whats available) 8. please document everything, so much "new nodes" without any documentation, just a short explanation is available. So many old nodes with new parameters have not updated documentation too. Including very important ones as FEM sutff. 9. A more easy way to create Shape animation, like XSI where proportional editing creates shapes automatically. (or something similar) 10. More intuitive way to create "XSI Link with/Maya Diven Keys" (maybe with a dedicated curve/link editor?)
-
1+ on Sneak Peek!!!
-
Oh yeah, this will be nice... much more Houdini thinking/Methodology. I hope this will be true soon!
-
-1 o this! No Thanks! (this is just IMHO) This is not really more useful than what we already have... A "scene map" is much more interesting to have, where we can see all relations at scene level, "scene assembly" is nothing more than a ICE with exploded nodes! ...and Houdini is much, much, much more advanced and robust than Clarisse. Easy to clutter interface if not take very careful new UI ideas, only because "looks good" in other softwares.
-
What XSI|ICE "Project a vector" equivalent on VOPS?
rod.vfx.td replied to rod.vfx.td's topic in General Houdini Questions
Thanks
