Indigo Renderer Forum

Behrendt wrote:When creating Materials - I always sort my materials in layers. If I'm currently in an active layer and create a material usually the material should be created in the active layer, instead it is created without a layer - is it possible to fix this?

fused wrote:

andeltoz wrote:In Cinema 4D on OS X, the plugin does not automatically start the application Indigo Renderer, as is the case for Windows users. You can do this?
Regards

Hi andeltoz,

that should be working. There was a bug tho which was preventing the starting of Indigo in some cases that was fixed in Indigo for C4D 3.4.8: http://www.indigorenderer.com/forum/vie ... 10&t=11905

ejanne wrote:Hi there, might I just say: I've tried most of the GPU renderers out there, and Indigo is really ahead of everyone in terms of integration and cross-platform support. Kudos.

ejanne wrote:Would it be possible to make it optional to kick off the Indigorenderer locally? I work on Mac, but have a nifty linux box with a spanking new Titan (I'm getting 800k samples/second, but alas, no C4D, booo). I'd like to be able to just export my igs scene file sequence and upload it to the PC for rendering rather than render locally on my Mac. You might suggest that I use the network rendering ability; however, the Indigo renderer doesn't allow me to specify the remote GPU.

To this end, would it also be possible to modify Cindigo to export relative pathnames to the mesh/texture/material files, as well as to provide a simple UI that would allow me to override the target render device and CUDA vs OpenCL?

I'm hoping that such options should be quite simple to implement, but would simplify my workflow tremendously.

Thanks in advance.

<?xml version="1.0" encoding="utf-8"?>

<config>
	<renderer_settings>

		<!-- .... all the other default settings ... -->

		<selected_gpu_device>
			<device_name>GeForce GTX 670</device_name>
			<subsystem>CUDA</subsystem>
		</selected_gpu_device>
	</renderer_settings>
</config>

fused wrote:For transferring scene files to another computer (without network rendering) I'd suggest to package the scene into a .pigs. You can do this in the Indigo standalone UI under "Tools" > "Pack Indigo Scene...". This should take care of the issue with the absolute pathnames.

I could add a "pack scene file" option to the exporter, so you don't have to do it manually.

fused wrote:Regarding the manual override for the target GPU and mode, it's possible to set a default/fallback in the inifile.xml (which you can find in the Indigo Renderer directory). Just add this to the <renderer_settings> element:

Code: Select all

<?xml version="1.0" encoding="utf-8"?>

<config>
	<renderer_settings>

		<!-- .... all the other default settings ... -->

		<selected_gpu_device>
			<device_name>GeForce GTX 670</device_name>
			<subsystem>CUDA</subsystem>
		</selected_gpu_device>
	</renderer_settings>
</config>

Of course you need to change the device_name of your GPU and also your preferred subsystem.

Cheers!

Zom-B wrote:I would prefer to see the development power gets focused on Real Time preview instead