Most Wanted - Poll

[smicha]

IMO nodal approach means skatter support (via scatter node) and working proxies (via import ocs/obj same as in the standalone). So first three questions/requests are equivalent to the nodal approach that we have in the standalone

Q: when can we expect to have the nodal approach?

[resmas]

IMO nodal approach means skatter support (via scatter node) and working proxies (via import ocs/obj same as in the standalone). So first three questions/requests are equivalent to the nodal approach that we have in the standalone

Q: when can we expect to have the nodal approach?

+1

Whith nodal aprouch i think we be able to do almost everything...

if we can "copy/paste" nodes...similar to the way Mobo works....teh sky is the limit

we can even make a animation path in blender....export as orbx alembic file...and usit in sketchup....


or i may just be dreaming

cheers to all

[smicha]

IMO nodal approach means skatter support (via scatter node) and working proxies (via import ocs/obj same as in the standalone). So first three questions/requests are equivalent to the nodal approach that we have in the standalone

Q: when can we expect to have the nodal approach?

+1

Whith nodal aprouch i think we be able to do almost everything...

if we can "copy/paste" nodes...similar to the way Mobo works....teh sky is the limit

we can even make a animation path in blender....export as orbx alembic file...and usit in sketchup....


or i may just be dreaming

cheers to all

Completely agree. We could even replace geometry nodes with let's say zbrush geometry - so powerful! Let's hope the team will not disappoint us.

[smicha]

PS. Sorry if I keep repeating myself buy this is the key for full success
viewtopic.php?f=31&t=41560&hilit=search ... t+exporter

[-rb-]

Would be great to tune up basic functionality bugs before anything surely?

ie. Copying materials, changing their basic properties (Diffuse, Glossy) - Scenes keeping their properties, Menus not failing sometimes, etc.

- Rich

[smicha]

Would be great to tune up basic functionality bugs before anything surely?

ie. Copying materials, changing their basic properties (Diffuse, Glossy) - Scenes keeping their properties, Menus not failing sometimes, etc.

- Rich

I agree - fix bugs and keep the development.

[resmas]

Would be great to tune up basic functionality bugs before anything surely?

ie. Copying materials, changing their basic properties (Diffuse, Glossy) - Scenes keeping their properties, Menus not failing sometimes, etc.

- Rich

I agree, but this bugs probably come from the caos that is the node graph setup .....

if this struture gets more organized...probably many bugs will be gone....if every change we make in the model is updated in that estructure.....i can only imagini the caos the software need to embrace just to reconfigure the nodas....

Lets organize this....i might be wrong....but lets think....

that may be the reason to materials gets messed up....textures gone...etc etc.


Node Graph all the way

cheers

[-rb-]

Possibly - though this plugin was quite famous from the start as being based on a 'crappy' (dev's words not mine) UI!

I guess it depends for me whether the node graph has an ease-of-use factor - otherwise hide all the unnecessary stuff under the hood (that's what a 'plug-in' should do - integrate simply enough with the host program!)

- Rich

[-rb-]

But for me - yes - bug fixes before v3 integration. I can't exactly see what the massive advantages of v3 are in terms of a SU pipeline (apart from scatter and volumetric) versus the problem of having to restart SU 9-10 times across a project because of menu failures

[Cosoli]

I want to have "batch render tool".

Just like Thea Render,user can batch all the views they saved easily.

It is really useful!