Neon uses its own rendering engine in all cases. What it does is to support (as far as it can) the current "Renderer" as far as features. So if RhinoRender is current, it will support basic materials, environment, decals, sun and sky and so on.
When you switch to Brazil, Neon will now support all of the Brazil materials and settings (as far as possible - which is about 80% right now)
so we can consider NEON as another altervative rendering engine for rhino!
but,to work,it need to use brazil material editor(or Rhino material)
congrats for this NEON rendered image
i think has "realistic quality"
I prefer to think of Neon as a viewport mode that is capable of previewing either RhinoRender or Brazil using real-time raytracing.
just a quick question about NEON and the Brazil env editor compatibility!
when i use a simple env as studio or a gradient env,all goes OK,the NEON viewport runs great and renders all mats and env in the right way!
but,if i create a brazil advanced env
and i put inside it a Jpeg,neon has problems with materials,because all are semi-trasparent,why?
see image below
sorry i cant upload the whole model,cause i'm not using a speedy connection(i'm under 3G) and it's hard upload heavy files!
but i can modify the scene ...and upload a simple example to let you understand!
(but,how can i send you a zip file?)
Thanks - we're looking into it now.
send picture please.
Will future iterations of Neon / Brazil take advantage of GPU tech - NVIDIA GeForce CUDA cores?