Multiloaders for C4D

Logging on behalf of user (more info in comment).

At the moment, Corona relies on a fixed installation path and registry-based discovery, which makes parallel installs and version switching difficult to manage cleanly.

What we would like to request is support for a simple environment variable, for example CORONA_ROOT or similar, that allows defining the Corona installation path at runtime. This would allow us to:

  • Run multiple Corona versions side by side
  • Switch versions per job or per host application
  • Avoid junctions or filesystem workarounds
  • Keep deployments predictable and automation-friendly

This kind of mechanism would greatly simplify large-scale and render farm workflows while remaining fully backward compatible.


Submitted on AHA Ideas (CC4D-I-62).

Originally reported by jw@dropandrender.com

https://dropandrender.com/

It’s a commercial render farm and that would streamline their workflow.


Submitted on AHA Ideas by Marcin Miodek.

AHA Ideas status: Pending.
Set during AHA Ideas to Discourse migration.