Verge3D engine or Cycles Render engine ?

This topic has 2 replies, 2 voices, and was last updated 6 years, 9 months ago by brice.

Viewing 3 posts - 1 through 3 (of 3 total)

Author

Posts
2018-02-25 at 8:13 pm #2381

brice
Participant

Hello,
i’m a bit confused with the materials setting workflow…
in a hand we have Verge3D ( ok it’s “the name of the software” so i think i should stay with that..) but no, in the other hand if i want to use the Suzanne PBR nodeTree i must use the Cycles render engine for seeing it in the viewport and when i switch back to the Verge3D engine the mesh is a shadeless black… (i also noticed the PBR Cycles nodes doesn’t support the “environment Lighting” of the Verge3D->World section ). I have the feeling that if we choose the advantages of one side (Cycles) we recover disadvantages that we had not on the other side (Verge3D)… it could be more friendly if we could stay in the Verge3D Engine with no need to switch out.
I think I did not understand how to use Verge3D well, so for you, what is the best workflow ?

2018-02-26 at 8:07 am #2386

Mikhail Luzyanin
Staff

Yes, workflow may be little bit confusing. If you prepearing model in pbr workflow you need to use cycles mode to export your file if you are using GLSL workflow (Blender Internal nodes) you need to use the Verge3D engine mode. Unfortunaly both are nor supported because they not supported by blender, this will changed when EEVEE comes out in august. We are trying to minimize inconvenience of such workflow. Some of them will be fixed in next release of the engine, some of them little later.

Co-founder and lead graphics specialist at Soft8Soft.

2018-02-26 at 5:13 pm #2500

brice
Participant

Hello Mikhail, thank you for your answer, too bad that the Verge3D workflow is actually splitted … I will be happy to see EEVEE arrive to simplify the workflow
Author

Posts