0
PBR - you must include basecolor, metal, normal, occlusion & roughness. Simple as that. Even if some of your textures are pure white or black it doesnt matter, its the requirement as per the standard (not just for CGT). This way the material behaves correctly in real-time. Dont worry about the resources since a black metal texture is like 10kb so it doesnt use much really.
Also remember for ORM workflow (occlusion, roughness, metal packed into a single texture) it needs something to pack, otherwise you end up with a blank channel which should not be an alpha but a 0-255 value. Lots of real-time packages and platforms can package your ORM for you but without one of them you are missing a component, thus you throw errors. Its a standard for a reason.
Wow man your comments are really insightful, So packing PBR textures for example UE packed textures can pass as PBR textures ?
I also provided Textures that are compatible with Blender with all the channel you have mentioned above.
Is there any other thing I need to be careful for?
Thank you for your time!
Interesting! what if the models are high poly and PBR that's for prerendered engines, that doesn't use Occlusion, and metal is always black by default and doesn't need to be packed? I think PBR is not quite a "game ready" term anymore
@RedoyRajoan - if you want to provide ORM then also provide the originals (unpacked). Just gives the customer more flexibility in their workflow. @kremiansky PBR is just Physically Based Rendering, game or real-time call it what you want but those are the specs. If your specific engine enables you to omit metal or occlusion great (for example not required in vray/corona), but GLB/GLTF do require those textures and its the safest way to ensure your customers have everything they need from day 1.
