PLAN8

This flags up my previous repeated requests for the V3D export locally option to ONLY export the essential required HTML app files and none of the V3D, Blender and other unused files –

As a non-coder, the export locally option is very un “Artist Friendly”, as there is no clear explanation as to which files are required for the HTML app only – it is not an easy task at all to go through the exported files and try and work out what are the actual HTML app files, and what are the puzzle files and blender files etc –

PLEASE can you make the export locally option respect the option that is made checkable in the app manager “general settings”? I really don’t understand why this hasn’t been done – it makes no sense at all, and now with this vulnerability issue, it would help resolve this if the upload app manager in WordPress was only uploading a known set of file types because the exported app locally only contains the required files for a website. If that makes sense?

Ahh, so it is! My mistake, sorry!

I can confirm that the emission shader in BSDF is now working for me! thank you!

OK, thanks – I understand.

But technically, would it be possible to have a list of multiple collision materials? because that would save the work of making a collision mesh and its own material.

Ah, OK, I didn’t think about adding an invisible mesh – however, that still would require duplicating everything which is quite time consuming and adds extra data to be transferred for the web delivery which makes it less efficient all round?

Dragging this up again as it seems a must to me –

A button to export only the required HTML/web based set of files only that doesn’t include files that are not required for the web version (ie all the Verge3D and blender files as well as unused textures etc).

Or, make the Verge3D folder hierarchy keep the exportable HTML files separated from the design and backend files in the first place so that manual export or copy of the web ready files is a simple case of copy and paste.

It really does seem like this should be a standard part of the workflow to me, given that the whole point of Verge3D is to enable Blender to Web processing.

• This reply was modified 11 months, 3 weeks ago by PLAN8.

Note – I am only seeing the AO through the “backside” of the material – IE it’s a thin surface with no thickness, from the frontside, the material renders correctly, through the backside (with double-sided faces enabled) you can see the AO through the material.