HowTo:Fix artifacts - Revision history

SharkD: /* Coincident Surfaces */ use wikilink, main aritcle link

2010-07-26T17:18:01Z

Coincident Surfaces: use wikilink, main aritcle link

SharkD: /* Coincident Surfaces */ mention interior_texture

2010-07-26T17:16:46Z

Coincident Surfaces: mention interior_texture

SharkD: remove unnecessary line breaks, change heading title

2010-07-26T16:31:01Z

remove unnecessary line breaks, change heading title

SharkD: /* Expressions */ present tense

2010-07-26T16:29:17Z

Expressions: present tense

SharkD: bullets are unnecessary

2010-07-26T16:28:37Z

bullets are unnecessary

SharkD: new section

2010-07-26T16:28:05Z

new section

SharkD: /* Coincident Surfaces */ link to section in docs

2010-07-26T16:10:27Z

Coincident Surfaces: link to section in docs

Reactor: /* made sections. Corrected minor spelling error and changed wording. Added links to docs and relevant pages. */

2009-08-16T06:02:27Z

made sections. Corrected minor spelling error and changed wording. Added links to docs and relevant pages.

PlayBunny: HowTo:Fix Artifacts moved to HowTo:Fix artifacts: Capitalisation standard: Initial capital and proper nouns.

2008-04-29T08:28:28Z

HowTo:Fix Artifacts moved to HowTo:Fix artifacts: Capitalisation standard: Initial capital and proper nouns.

PlayBunny: New page: Wierd speckles on a surface may be caused by: *Two or more surfaces occupy the same plane. The choice of which surface gets rendered varies from pixel to pixel according to the whim of PO...

2008-04-26T10:25:10Z

New page: Wierd speckles on a surface may be caused by: *Two or more surfaces occupy the same plane. The choice of which surface gets rendered varies from pixel to pixel according to the whim of PO...

New page

Wierd speckles on a surface may be caused by:

*Two or more surfaces occupy the same plane. The choice of which surface gets rendered varies from pixel to pixel according to the whim of POV-Ray. Shifting one surface by 0.0001 or some such miniscule but significant amount will usually fix this.

*You've rendered the scene with certain textures and at low quality and with no anti-aliasing.

*You've rendered a texture which is supposed to have wierd speckles! ;-)

@@ Line 2: / Line 2: @@
 ==Coincident Surfaces==
-Two or more surfaces occupy the same plane. The choice of which surface gets rendered varies from pixel to pixel according to the whim of POV-Ray. Translating one surface by 0.0001 out of the plane will usually fix this.  This is probably the most common cause of 1px speckles on specific objects in a scene. See [[Documentation:Tutorial Section 2.1#Co-incident Surfaces]].
+:''Main article: [[Documentation:Tutorial Section 2.1#Co-incident Surfaces]]''
-If you are trying to model a single object with both an inside and outside texture, you might try using the [http://wiki.povray.org/content/Documentation:Reference_Section_5.2#Interior_Texture interior_texture] keyword.
+If you are trying to model a single object with both an inside and outside texture, you might try using the [[Documentation:Reference Section 5.2#Interior Texture|interior_texture]] keyword.
 ==Radiosity==

@@ Line 3: / Line 3: @@
 ==Coincident Surfaces==
 Two or more surfaces occupy the same plane. The choice of which surface gets rendered varies from pixel to pixel according to the whim of POV-Ray. Translating one surface by 0.0001 out of the plane will usually fix this.  This is probably the most common cause of 1px speckles on specific objects in a scene. See [[Documentation:Tutorial Section 2.1#Co-incident Surfaces]].
 ==Radiosity==

@@ Line 6: / Line 6: @@
 ==Radiosity==
 In scenes using radiosity, if the artifacts show up only when radiosity is turned on, then they are caused by radiosity sampling errors.  If you haven't already done so, check the [[Documentation:Tutorial_Section_3.7#Radiosity|Official Documentation on Radiosity]] or the [[HowTo:Use_radiosity|HowTo: tutorial on radiosity]].
 ==Transparent and Reflective Surfaces==
 Scenes that many reflective/transparent surfaces may run afoul of the default [[Documentation:Reference_Section_3.1#Max_Trace_Level|max_trace_level]] setting.  Check the messages from the render, as POV-ray will tell you if the max_trace_level was reached during a render.  If it was reached, raise the max_trace_level to a higher value.
 ==Other Causes==
 You've rendered a scene using certain textures with [[Documentation:Reference_Section_1.3#Anti-Aliasing_Options|anti-aliasing]] turned off.  The difference caused by the use of anti-aliasing can be startling, especially with a texture which is supposed to have weird speckles! ;-)  Note that the appearance of speckles on a surface is not only controlled by the pigment statement, but can be the result of a small, bumpy normal, or the use of [[Documentation:Reference_Section_5.1#Crand_Graininess|crand]] in the finish statement.
-==Expressions==
+==Floating-point expressions==
 You've created an expression where some fractional or decimal values are operated upon to create an integer, but the expression doesn't evaluate to the correct amount. This problem is related to the one of [[Documentation:Tutorial Section 2.1#Co-incident Surfaces|co-incident surfaces]], in that floating-point values are cut-off at a level that is less precise than the one you are checking for.

@@ Line 16: / Line 16: @@
 ==Expressions==
-You've created an expression where some fractional or decimal values are operated upon to create an integer, but the expressions don't evaluate to the correct amount. This problem is related to the one of [[Documentation:Tutorial Section 2.1#Co-incident Surfaces|co-incident surfaces]], in that floating-point values are cut-off at a level that is less precise than the one you are checking for.
+You've created an expression where some fractional or decimal values are operated upon to create an integer, but the expression doesn't evaluate to the correct amount. This problem is related to the one of [[Documentation:Tutorial Section 2.1#Co-incident Surfaces|co-incident surfaces]], in that floating-point values are cut-off at a level that is less precise than the one you are checking for.
 The underlying problem is the same as if you'd try to compute 1/3 + 1/3 + 1/3 + ... using decimal numbers with a certain limit in precision; as you can't exactly represent 1/3 this way, you'd get e.g.:

@@ Line 2: / Line 2: @@
 ==Coincident Surfaces==
-*Two or more surfaces occupy the same plane. The choice of which surface gets rendered varies from pixel to pixel according to the whim of POV-Ray. Translating one surface by 0.0001 out of the plane will usually fix this.  This is probably the most common cause of 1px speckles on specific objects in a scene. See [[Documentation:Tutorial Section 2.1#Co-incident Surfaces]].
+Two or more surfaces occupy the same plane. The choice of which surface gets rendered varies from pixel to pixel according to the whim of POV-Ray. Translating one surface by 0.0001 out of the plane will usually fix this.  This is probably the most common cause of 1px speckles on specific objects in a scene. See [[Documentation:Tutorial Section 2.1#Co-incident Surfaces]].
 ==Radiosity==
-*In scenes using radiosity, if the artifacts show up only when radiosity is turned on, then they are caused by radiosity sampling errors.  If you haven't already done so, check the [[Documentation:Tutorial_Section_3.7#Radiosity|Official Documentation on Radiosity]] or the [[HowTo:Use_radiosity|HowTo: tutorial on radiosity]].
+In scenes using radiosity, if the artifacts show up only when radiosity is turned on, then they are caused by radiosity sampling errors.  If you haven't already done so, check the [[Documentation:Tutorial_Section_3.7#Radiosity|Official Documentation on Radiosity]] or the [[HowTo:Use_radiosity|HowTo: tutorial on radiosity]].
 ==Transparent and Reflective Surfaces==
-*Scenes that many reflective/transparent surfaces may run afoul of the default [[Documentation:Reference_Section_3.1#Max_Trace_Level|max_trace_level]] setting.  Check the messages from the render, as POV-ray will tell you if the max_trace_level was reached during a render.  If it was reached, raise the max_trace_level to a higher value.
+Scenes that many reflective/transparent surfaces may run afoul of the default [[Documentation:Reference_Section_3.1#Max_Trace_Level|max_trace_level]] setting.  Check the messages from the render, as POV-ray will tell you if the max_trace_level was reached during a render.  If it was reached, raise the max_trace_level to a higher value.
 ==Other Causes==
-*You've rendered a scene using certain textures with [[Documentation:Reference_Section_1.3#Anti-Aliasing_Options|anti-aliasing]] turned off.  The difference caused by the use of anti-aliasing can be startling, especially with a texture which is supposed to have weird speckles! ;-)  Note that the appearance of speckles on a surface is not only controlled by the pigment statement, but can be the result of a small, bumpy normal, or the use of [[Documentation:Reference_Section_5.1#Crand_Graininess|crand]] in the finish statement.
+You've rendered a scene using certain textures with [[Documentation:Reference_Section_1.3#Anti-Aliasing_Options|anti-aliasing]] turned off.  The difference caused by the use of anti-aliasing can be startling, especially with a texture which is supposed to have weird speckles! ;-)  Note that the appearance of speckles on a surface is not only controlled by the pigment statement, but can be the result of a small, bumpy normal, or the use of [[Documentation:Reference_Section_5.1#Crand_Graininess|crand]] in the finish statement.
 ==Expressions==
-*You've created an expression where some fractional or decimal values are operated upon to create an integer, but the expressions don't evaluate to the correct amount. This problem is related to the one of [[Documentation:Tutorial Section 2.1#Co-incident Surfaces|co-incident surfaces]], in that floating-point values are cut-off at a level that is less precise than the one you are checking for.
+You've created an expression where some fractional or decimal values are operated upon to create an integer, but the expressions don't evaluate to the correct amount. This problem is related to the one of [[Documentation:Tutorial Section 2.1#Co-incident Surfaces|co-incident surfaces]], in that floating-point values are cut-off at a level that is less precise than the one you are checking for.
 The underlying problem is the same as if you'd try to compute 1/3 + 1/3 + 1/3 + ... using decimal numbers with a certain limit in precision; as you can't exactly represent 1/3 this way, you'd get e.g.:

← Older revision		Revision as of 16:10, 26 July 2010
Line 4:		Line 4:
	*Two or more surfaces occupy the same plane. The choice of which surface gets rendered varies from pixel to pixel according to the whim of POV-Ray. Translating one surface by 0.0001 out of the plane will usually fix this. This is probably the most common cause of 1px speckles on specific objects in a scene.		*Two or more surfaces occupy the same plane. The choice of which surface gets rendered varies from pixel to pixel according to the whim of POV-Ray. Translating one surface by 0.0001 out of the plane will usually fix this. This is probably the most common cause of 1px speckles on specific objects in a scene.

		+	See [[Documentation:Tutorial Section 2.1#Co-incident Surfaces]].

	==Radiosity==		==Radiosity==

@@ Line 1: / Line 1: @@
-Wierd speckles on a surface may be caused by:
+On occasion, some objects in your scene may have speckles or what looks like random noise on the surface.  Below are a few possible causes:
-*Two or more surfaces occupy the same plane. The choice of which surface gets rendered varies from pixel to pixel according to the whim of POV-Ray. Shifting one surface by 0.0001 or some such miniscule but significant amount will usually fix this.
+==Coincident Surfaces==
-*You've rendered a texture which is supposed to have wierd speckles! ;-)
+==Radiosity==

← Older revision	Revision as of 08:28, 29 April 2008
(No difference)