Indigo Renderer 3.2.2

[dag]

Alright, sounds like fishy business.
BTW FoV should probably be called Angle of View since it's a degrees measurement and not distance.

[CTZn]

Is sss working as it should?
In the material with red scattering under 90.3 only bidir modes render red, but above 90.4 all modes render red.

Confirmed, could be that something gets inverted below 90.4 (red) scattering. Inverting absorbtion should be an exporter/GUI feature imho.

[Zlaty Lev]

3.2.2
* Fixed node licenses not being recognised properly

When selecting "Network Rendering" manually within Indigo once render has started I get the following messages :
Starting Render Master Server on port 7777
Master Discovery Listener started

On Slave, I get
Waiting for a master.
ClientDiscoveryPacketSender thread started.
Listening on port 7100

But that's it, nothing happens, no connexion. On 3.2.0, I was getting a connection (even though slaves licenses were not recognized).

License is recognized correct now. But as discribed the connection to the slaves fails when starting the network rendering manually.
And because blendigo still has no button for network rendering ( or it is well hidden somewere or I´m blind) you can not use network rendering at all with blender.

[everwind]

Alright, sounds like fishy business.
BTW FoV should probably be called Angle of View since it's a degrees measurement and not distance.

FoV has never been a distance, it's angular :). Angle of View is just the name of Field of View in photography, but it's exactly the same

[Ryouta Sumeragi]

Because Slave does not reply, network rendering cannot start...
Slave was started with "Network Rendering" button in Indigo3.0.14.


-----------------------------
C4D R10.5 (64bit)
Indigo 3.2.2, Cindigo 3.2.1
Windows 7Pro(64bit), MEM 8GB
-----------------------------
I used machine translation ...

[dag]

Alright, sounds like fishy business.
BTW FoV should probably be called Angle of View since it's a degrees measurement and not distance.

FoV has never been a distance, it's angular :). Angle of View is just the name of Field of View in photography, but it's exactly the same

Most people speak of field of view when in fact they mean angle of view. Field of view is the distance covered by a projection at a certain distance. So if an image exactly shows a 2 meter wide object at 1 meter distance, then the field of view is 2 meter (and the angle of view is 90°). Angle of view is also known as angle of coverage.

but... no big deal.

[everwind]

Alright, sounds like fishy business.
BTW FoV should probably be called Angle of View since it's a degrees measurement and not distance.

FoV has never been a distance, it's angular :). Angle of View is just the name of Field of View in photography, but it's exactly the same

Most people speak of field of view when in fact they mean angle of view. Field of view is the distance covered by a projection at a certain distance. So if an image exactly shows a 2 meter wide object at 1 meter distance, then the field of view is 2 meter (and the angle of view is 90°). Angle of view is also known as angle of coverage.

but... no big deal.

This definition applies only about PROJECTIONS (ex : in cinema). FOV is also used in photography/biology (FOV of human beings etc.) and other fields where it's not about projection but about optical systems. In these situations, FOV = Angle of View.

You can check in encyclopedia universalis or wikipedia or any encyclopedia ;)

[OnoSendai]

3.2.2
* Fixed node licenses not being recognised properly

When selecting "Network Rendering" manually within Indigo once render has started I get the following messages :
Starting Render Master Server on port 7777
Master Discovery Listener started

On Slave, I get
Waiting for a master.
ClientDiscoveryPacketSender thread started.
Listening on port 7100

But that's it, nothing happens, no connexion. On 3.2.0, I was getting a connection (even though slaves licenses were not recognized).

This bug is fixed for next release. Thanks for bug report.

[CTZn]

The blackbody gain parameter is tested even though emission scale is used, leading to a non emissive material if gain is zero. Knowing that the value will be ignored it may happen to set it to zero.

When using the sum material, the sky from sunsky is forced to the background material's light layer:

Code: Select all

<material>	<name>SunShape</name>
<sunsky>
	<sundir>-0.5 -0.5 0.7071067812</sundir>
	<sun_layer>0</sun_layer>
	<sky_layer>1</sky_layer>
	<turbidity>2</turbidity>
</sunsky>	</material>

<material>
	<name>lambert2SG</name>
	<diffuse>
		<albedo>
			<constant>
				<rgb>
					<rgb>0 0 0</rgb>
					<gamma>2.200000048</gamma>
				</rgb>
			</constant>
		</albedo>
		<layer>3</layer>
		<base_emission>
			<!--indigoSpectrum indigoSpectrum1-->
			<constant>
				<blackbody>
					<temperature>6500</temperature>
					<gain>9.999999747e-006</gain>
				</blackbody>
			</constant>
		</base_emission>
		<texture>
			<uv_set_index>0</uv_set_index>
			<path>OpenfootageNETStallersattel_small.exr</path>
			<exponent>2.200000048</exponent>
 			<tex_coord_generation>
				<spherical>
					<rotation>
						<axis_rotation>
							<axis>0 0 1</axis>
							<angle>0</angle>
						</axis_rotation>
					</rotation>
				</spherical>
			</tex_coord_generation>
			<b>1</b>
 			<c>0</c>
		</texture>
		<emission>
			<texture>
				<texture_index>0</texture_index>
			</texture>
		</emission>
	</diffuse>
</material>

However the layer 1 will be empty and both the sky and the environment will be found on the third layer (2).

[Pibuz]

Displacement maps are not working properly here: seems like the changes done in the GUI do not affect the render at all (Indigo doesn't restart the calculation of the image either).

The exported values turn out to be 0.0000000, while in SU is obviosuly different from 0.

[zeitmeister]

You got to click on the texture button in the displacenent slot of the material in the Indigo GUI; then you'll reach your value from Skindigo.

Nethertheless, Displacement causes nasty black borders on UV-mapped objects where applied. :-(

[CTZn]

A camera using a keyframe is saved incorrectly, 3.2.0 is okay in this regard.

[solarray]

I got the following error when loading a scene similar to the material scene and playing around with materials (assigning new ones to objects, changing settings, assigning again new ones) (using gpu for rendering):

Code: Select all

A problem occurred with the scene:
Error initialising GPU ray tracer: cuMemAlloc of 33554432 B failed: CUDA_ERROR_OUT_OF_MEMORY
Indigo version: Indigo Renderer v3.2.2, Windows 64-bit build.
Exporter: 
Platform: 
Author: 
Description: 
Date created: 

I also recognized that when the scene is loaded, indigo fills around 700 MB on RAM after playing around with materials and this error indigo has around 3.1 GB in RAM. Never forget 'delete' when allocating with 'new' :-P

By the way a button 'delete material' would be nice too.

[Jeff Hammond]

i've seen this behavior in the last few builds :

i don't think the 'Update Image' button is working anymore.. I used to be able to click it and the image would update visually and the 'next image update in' clock would also reset itself..

previously, if i had a render going overnight, in the morning it might say something like 'time elapsed: 14hrs, next image update in 4hrs' when it's been 5hrs since the last update.. at this point, i'd update then save my file but now it seems as if i have to wait the additional 4 hrs to get another update..

..or maybe i'm missing something?
thanks


osx 10.7.2 indigo 3.2.2

[Voytech]

i've seen this behavior in the last few builds :

i don't think the 'Update Image' button is working anymore.. I used to be able to click it and the image would update visually and the 'next image update in' clock would also reset itself..

previously, if i had a render going overnight, in the morning it might say something like 'time elapsed: 14hrs, next image update in 4hrs' when it's been 5hrs since the last update.. at this point, i'd update then save my file but now it seems as if i have to wait the additional 4 hrs to get another update..

..or maybe i'm missing something?
thanks


osx 10.7.2 indigo 3.2.2

Based on my experience, pressing the update image does update the image but does not reset the clock as it used to. Everything works on my end.