Difference between revisions of "HowTo:Known Issues"
Jump to navigation
Jump to search
(Adding some items to the know issues entry.) |
m (Adding known issue for assumed_gamma 1 and .gray operation.) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
===Known Issues=== | ===Known Issues=== | ||
| − | <p>Quick list of general <em>known issues</em> with the <em>version 3.7</em> | + | <p>Quick list of general <em>known issues</em> with the <em>version 3.7</em>, the <em>3.7.1</em> pre-release and the current master branch(3.7.2):</p> |
<ol> | <ol> | ||
| − | <li>Due to problems with <em>X11</em> libraries, some special command line parameters are not available | + | <li>Unix users. Due to problems with <em>X11</em> window libraries, some special command line parameters, such as -geometry, are not available. These were previously enabled via X11 itself. However, a preview display can still be enabled if building from source and the optional [http://www.libsdl.org SDL Simple Directmedia Layer (V1.2)] development library is available to link against.</li> |
<li>While utf-8 support is available in scene files, there are still issues with file names using non-ASCII characters. Meaning a user running in utf-8 or equivalent must take care to use only ASCII characters for all scene related file and directory names. See: [https://github.com/POV-Ray/povray/issues/152 github issue 152]</li> | <li>While utf-8 support is available in scene files, there are still issues with file names using non-ASCII characters. Meaning a user running in utf-8 or equivalent must take care to use only ASCII characters for all scene related file and directory names. See: [https://github.com/POV-Ray/povray/issues/152 github issue 152]</li> | ||
| + | <li>Agressive Anti-Aliasing (AA) usually addresses bright and dark speckles sometimes seen with media where rays glance - tangentially - to a mathematical surface in a way which confuses interval determination for sampling. Further, while using 'sturm on' is usually a help, it tends to make such media speckling worse. Search the newsgroups for more detail.</li> | ||
| + | <li>The internal .gray | .grey, color to gray conversion is not adjusted for assumed_gamma as the current conversion was set up for other than the recommended assumed_gamma 1 setting. See the newsgroup discussion at: [http://news.povray.org/povray.general/thread/%3C58800d3c%241%40news.povray.org%3E/ "Assumed_gamma and .gray"]. The following macro, as suggested in the news thread, can be used by assumed_gamma 1 users: | ||
| + | <p> | ||
| + | <pre> | ||
| + | #macro DotGray (Color) | ||
| + | #local C = color Color; | ||
| + | (0.2126 * C.red + 0.7152 * C.green + 0.0722 * C.blue) // ITU-R BT.709 | ||
| + | #end | ||
| + | </pre> | ||
| + | </p> | ||
| + | </li> | ||
</ol> | </ol> | ||
| − | <p>The developer's issue tracking can be at [https://github.com/POV-Ray/povray/issues Github Issue Tracking System]</p> | + | <p>The developer's issue tracking can be found at [https://github.com/POV-Ray/povray/issues Github Issue Tracking System]</p> |
Latest revision as of 11:39, 23 January 2017
Known Issues
Quick list of general known issues with the version 3.7, the 3.7.1 pre-release and the current master branch(3.7.2):
- Unix users. Due to problems with X11 window libraries, some special command line parameters, such as -geometry, are not available. These were previously enabled via X11 itself. However, a preview display can still be enabled if building from source and the optional SDL Simple Directmedia Layer (V1.2) development library is available to link against.
- While utf-8 support is available in scene files, there are still issues with file names using non-ASCII characters. Meaning a user running in utf-8 or equivalent must take care to use only ASCII characters for all scene related file and directory names. See: github issue 152
- Agressive Anti-Aliasing (AA) usually addresses bright and dark speckles sometimes seen with media where rays glance - tangentially - to a mathematical surface in a way which confuses interval determination for sampling. Further, while using 'sturm on' is usually a help, it tends to make such media speckling worse. Search the newsgroups for more detail.
- The internal .gray | .grey, color to gray conversion is not adjusted for assumed_gamma as the current conversion was set up for other than the recommended assumed_gamma 1 setting. See the newsgroup discussion at: "Assumed_gamma and .gray". The following macro, as suggested in the news thread, can be used by assumed_gamma 1 users:
#macro DotGray (Color) #local C = color Color; (0.2126 * C.red + 0.7152 * C.green + 0.0722 * C.blue) // ITU-R BT.709 #end
The developer's issue tracking can be found at Github Issue Tracking System