Indigo Renderer Forum

can you try rendering via indigo_console?! That should give at least some verbose info about "discovery packets", maybe there is some more info there:

The behavior seems identical to the slaves not running:

"
Starting Render Master Server on port 7777.
------------------------------------------------
Total render time elapsed: 10 s
Done 0k samples (0 samples per pixel)
0 samples / second (Inf micro-seconds / sample)
------------------------------------------------
Total render time elapsed: 20 s
Done 0k samples (0 samples per pixel)
0 samples / second (Inf micro-seconds / sample)
------------------------------------------------
Total render time elapsed: 30 s
Done 0k samples (0 samples per pixel)
0 samples / second (Inf micro-seconds / sample)
------------------------------------------------
etc...
"

Ubuntu and Indigo upgrade are only changes to the setup.

when run as working master: the master adds samples but no frames/packets are received

del

Since the introduction of the exponent/roughness switch I can't get texture maps to work as intended. First, the exporter from the C4D is obsolete, preview meshes/system will not give the same results, and gamma value is 1.0, while in Indigo's standalone is 2.2. And there seems to be a problem, I don't know where exactly, but just try exporting a simple scene, for example a sphere with Phong material and a texture map in exponent channel. Set the value to, for example 1, leave the gamma at 1 too. Sun system, position is not important. Once in Indigo, go into roughness channel, select any of the value and just hit enter. Boom! Shiny, whereas the previous state was completely flat. You don't even have to change any value, just "refresh" the channel info by ticking on the box, and you'll get the same results. This gives a really awkward, unstreamed feeling between these two apps, and I urge you too update exporters asap, since a lot of things happened, including new material types. It's hardly even usable atm.

I imagine this "refreshing" problem has the same root as the Z.'s problem above. Once you check/uncheck the box, it refreshes the information from the input fields from the Indigo itself (=new value/state). The exported scene itself, without any change in the information retains the exported/converted data.

I've improved the automatic conversion from exponent textures to roughness textures.
That said we will update the exporters to handle this as well.

GPU not recognized in windows 10 (nvidia 980GTX).
In windows 8 works fine.

http://www.indigorenderer.com/materials/materials/265

Patch tracing GPU http://www.indigorenderer.com/materials/materials/966

Patch tracing GPU http://www.indigorenderer.com/materials/materials/266

Patch tracing GPU ||||||||||||||||||||||||||||||

http://www.indigorenderer.com/materials/materials/268 GPU OK
http://www.indigorenderer.com/materials/materials/267 GPU OK
http://www.indigorenderer.com/materials/materials/287 GPU OK
http://www.indigorenderer.com/materials/materials/272 GPU OK

yonosoy wrote:GPU not recognized in windows 10 (nvidia 980GTX).
In windows 8 works fine.

Have you updated to the latest drivers on Win 10?

Zalevskiy wrote:http://www.indigorenderer.com/materials/materials/246

1. open material

1.png

2. click to bump off

2.png

3. back to press to activate bump

3.png

as a result of reflection of the material is lost

this "bug" figured
Roughness convert a value of 800.0 to 0.8 and reflection work

I reinstall the last nvidia driver and all works fine in windows 10, thanks lycium.

del

Seems that physical aperture difraction don´t work for this release.

Zalevskiy wrote:http://www.indigorenderer.com/materials/materials/1513

Fixed for next release.

del