Tweet
Hi richard_aubin,
I see your point, but for the time being we will only support global material override, as I explain already. It will look like what paul showed. That was our idea as well.
If we decide to go with per-geometry override, the way you suggested will only work for the regular VGeo. That component is the only that outputs a geometry. All the rest of them: Scatter, Instancer, Cosmos, Proxy scene and Proxy mesh, have "VGeo" only as a hint where to connect it, they do not output actual geometry (e.g. V-Ray Node plugins). For example the proxy scene outputs a string - the .vrscene path.
I know it looks like simple and clean enough on the surface, but it is not such in code.
I see your point, but for the time being we will only support global material override, as I explain already. It will look like what paul showed. That was our idea as well.
If we decide to go with per-geometry override, the way you suggested will only work for the regular VGeo. That component is the only that outputs a geometry. All the rest of them: Scatter, Instancer, Cosmos, Proxy scene and Proxy mesh, have "VGeo" only as a hint where to connect it, they do not output actual geometry (e.g. V-Ray Node plugins). For example the proxy scene outputs a string - the .vrscene path.
I know it looks like simple and clean enough on the surface, but it is not such in code.
Comment