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 Jim Holsenback - 2011-02-21
Last edited by Jim Holsenback - 2011-02-27
Opened by Jim Holsenback - 2011-02-21
Last edited by Jim Holsenback - 2011-02-27
FS#194 - command line parse error
povray +Imesh_camera.pov +Omesh_camera.png +FN +W800 +H600 produces a “Failed to parse command-line option” error. when I rename my pov source file to ess_mesh_camera.pov it runs fine. seems to be pointing to a clash with the +im option. i also had another file that renaming it got me going.
The problem is indeed with the addition of the IM option, which simply is not possible as it cannot be decided by the parser of command line options. We need a different option shortcut for IM functionaility.
since the next expected character after +im is a number, perhaps the trap can be refined instead.
no kludges please. "m20" is a valid filename, too.
Did anyone notice that a space can save a lot of thing.
povray +I mesh_camera.pov ... is ok
it still breaks backward compatibility with e.g. existing shell scripts.
Did anyone notice that a space can save a lot of thing.
povray +I mesh_camera.pov ... is ok
Yes, because it is an empty string +I option plus interpretation of the file name as input file (because it has a .pov extension).
What does IM stand for ?
Would +MI be ok ?
(from perforce, Max_Image_Buffer_Memory +IM... so +MI does still make sense)
In processrenderoptions.cpp, the M* section is empty enough (MBint, MB void, MVfloat), so an easy move could be +MI
(Max Image... instead of Image Memory !)
Or +MIM int ?
Corrected with #5414, +MI is the new name of the option.
Thanks ... works both on cmd-line and ini option now