The Persistence of Vision Raytracer (POV-Ray).
This is the legacy Bug Tracking System for the POV-Ray project. Bugs listed here are being migrated to our github issue tracker. Please refer to that for new reports or updates to existing ones on this system.
Attached to Project: POV-Ray
Opened by Mike H - 2010-06-22
Last edited by Thorsten Fröhlich - 2011-08-23
Opened by Mike H - 2010-06-22
Last edited by Thorsten Fröhlich - 2011-08-23
FS#147 - Statistic_File not working?
In POV 3.6 you could set the Statistic_File option to a custom file and folder path. In the beta I get an “Cannot open file” error. Has the feature been intentionally removed or did it become broken?
To quote the introductory section at the top of all our bugtracker pages:
"Before opening a new task, please read http://wiki.povray.org/content/HowTo:Make_A_Bug_Report"
If you are in doubt whether it is a bug or not, please ask the question in povray.beta-test. If you are sure that it is a bug, please re-word it accordingly: What did you do? What did you expect? What happened? (Please, by all means, be as precise as you can; extra information doesn't hurt. Also, don't expect the developers to follow each and every newsgroup thread, so do include information already posted in newsgroups.) As it is now, this bugtracker entry is a mere question.
(As a hint to answer the question: You can safely presume that all 3.6 features are intended to work in 3.7 as well, unless stated otherwise in the beta version history (http://www.povray.org/beta/).)
[edit: getting the reports confused... I meant this thread:]
http://news.povray.org/povray.general/thread/%3C4c1f9812%241%40news.povray.org%3E/
Not a "bug" I guess. Rather, 3.7 simply does not allow full paths to be passed to the parameter any more. Instead, the parameter expects a relative path, to the path specified using Output_File_Name if set, or wherever images go to by default if not set.
@thorsten: In which change has this issue been fixed?
You added an error message, see FS#206.
Ah, okay - so this issue should actually have been closed as a dupe to FS#206.
Well, it isn't strictly a duplicate. It would be nice if the bug tracker could merge issues instead. But I could not find a solution to do that other than that duplicate message.