Not sure its the exporter or Indigo, but something seems horribly broken when GPU rendering on my system: Another older scene renders fine, yet another one after the first "flash" of an image, it only renders the environment HDRI.

@Zalewsky Can you elaborate on the intention of your post ? I would believe that all or at least the vast majority of the models in this thread were created with mesh modelers. My models in this thread were created as Sub-D meshes with Blender. Why would you say that the caustics in your images are ...

Simple BIDIR (without Metropolis Light Transport) also renders this effect. That isn't surprising! Brute force path tracing almost never "finds" the very small laser light source. The max path depth effects GPU only. When I open any of the test scenes that ship with Indigo with an XML editor, I can ...

I have to say that I am not 100% sur anymore if max_path_depth relates to GPU use only. The images below all use a value of 99, just to be sure. In GPU mode max_path_depth is limited to 100. Not sure that is part of the documentation (could not find it in a quick search) , o if I red it in a forum p...

LOL, yes not a surprise. What render mode did you use for that image ? The mention of max path depth indicates GPU use. But I would have imagined that the bidirectional path tracing, perhaps even with MLT converge much faster than brute force path tracing on the GPU. I've got a number of renders whe...

The link I provided in step #3 describes what happens after you initially purchased Indigo. The process is the same, whether you just purchased a license or want to transfer an existing license to a new machine. You should have received an email with a link to the order page for your specific licens...

@noelyone I transferred my Indigo license to a new computer 2 weeks ago without a problem following the instructions on this help page . The help page refers to an email you should have received with the original order (mine is from 2009). Here's a screenshot of it. Indigo_order.png I requested the ...

Very nice!

I've asked myself the same question. I sent an email with that question about 2 weeks ago to contact@glaretechnologies.com
and so far have not received a reply.

Just to be clear, I am not moving away from Indigo, unless it just stops being and I am forced to. That does not mean, however, that I don't look over the fence and evaluate other tools and if suitable, add them to my arsenal of tools. CyclesX is certainly interesting but is a tool that serves a som...

I have hoped for a long time that the Blendigo exporter would see some development time, but I believe that is unlikely to happen. My Python skills are rudimentary at best - in the past I've added missing buttons to the Blendigo UI - but even if they would be up to snuff, at this point I am not sure...

Bendigo 4.3.3 works with Blender 2.9.7 [LTS]

Installation isn't as simple as downloading the zipped file and installing it through Blender's preference->Addon "Install" menu.

macOS 11.6.1 (Big Sur) Blender 2.93.7 [LTS] Blendigo 4.3.0 Where did you obtain Bendigo 4.3.3? I also run a win10 installation on Bootcamp and the .msi Installer for the stable release only offers Bendigo 4.3.0 installation. On macOS, Bendigo isn't part of the Indigo install. It has to be downloaded...

This is all I get...
I also have BlendLuxCore installed, but that should not be an issue.

It looks like there is a update needed soon for Blendigo, as it does not appear to be compatible with Blender 2.93LTS and up.
This would be an opportune moment to add settings there were already missed in the last update.

1. The max path depth is missing
2. Optimize for denoising is missing