We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Feat Req: Create a Verge3D Output node (or option along with EEVEE & Cycles)

Home Forums Bug Reports and Feature Requests Feat Req: Create a Verge3D Output node (or option along with EEVEE & Cycles)

Tagged: 

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #22929
    mcolinp
    Customer

    I feel this would be a huge benefit; to have specific node setups that only output to Verge; so I can have other node outputs that are used strictly for EEVEE or Cycles. In the current material ‘output’ node; it is set to ‘All’ by default. but you can select the drop down menu and change it to only be used for either engine.

    Allowing the same behavior for Verge3D materials would be very liberating.

    Another thing I have asked for in the past; is a way to flag certain nodes that do not generate usable data to Verge3D. It could be as simple as clicking a button on the header of the node editor that would put a red outline around nodes that are not recognized by the Verge3D engine. This would be so helpful in trouble shooting problematic materials. And at the rate new nodes are released; this seems like the most reasonable approach to quickly determine what is or is not working.

    #22938

    Thank you for the thoughts! We’ll discuss this among the developers. :good:

    Chief 3D Verger | LinkedIn | Twitter

    #22953
    mcolinp
    Customer

    Thank you! This would be a huge productivity booster. Upon reading my initial post again; perhaps an easier way to enable the debugging mode, (Highlight nodes that are not working, etc), would be to just make a checkbox on the Verge3D output node itself. Of course this is dependent on if you create a new node vs just adding Verge3D to the existing output node. I am not sure if you can add it to the default output node; (only being an option if the plugin is installed, etc.) Perhaps if you can do that; the ode could also reveal the ‘debug’ checkbox when selecting the Verge3D output.

    I have no idea how feasible these suggestions are; but just sharing my thoughts on how it might work for the user.

    #22964

    Thanks again for the suggestions! In the meantime, you can check your node setups against this reference.

    Chief 3D Verger | LinkedIn | Twitter

    #22987
    mcolinp
    Customer

    Thanks again for the suggestions! In the meantime, you can check your node setups against this reference.

    Wonderful! I had taken a break from following your specific updates for a few months. This is very helpful.

    Thank You!

    #22994

    Sure! :bye:

    Chief 3D Verger | LinkedIn | Twitter

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.