void-linux / void-linux/void-packages

POV-Ray parse error with demo scene, 0 intersections

Open
#55,478 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs-testing
Dominant language
Shell
Stars
3.4k
Forks
2.8k
Avg merge
2d 5h
Merged PRs (30d)
299

Description

Is this a new report?

Yes

System Info

Void 6.12.28_1 x86_64 GenuineIntel uptodate rrrmFFF

Package(s) Affected

povray-3.7.0.8_11

Does a report exist for this bug with the project's home (upstream) and/or another distro?

Potential: https://github.com/POV-Ray/povray/issues/460

Expected behaviour

Povray renders the demo scene.

Actual behaviour

Povray output:

File 'demo.pov' line 7: Parse Error: Viewing angle has to be smaller than 180
 degrees.
Fatal error in parser: Cannot parse input.
Render failed
Steps to reproduce
  1. Save as demo.pov (from the official tutorial):
#include "colors.inc"
#include "stones.inc"
 
camera {
  location <0, 2, -3>
  look_at <0, 1, 2>
}
 
sphere {
  <0, 1, 2>, 2
  texture {
    pigment {colour Yellow}
  }
}
 
light_source {<2, 4, -3> colour White}
  1. $ povray demo.pov

Note: adding an angle to the camera specification produces only a blank image, logs indicate 0 ray->shape intersections.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the supplied demo.pov from the official tutorial and reproduce the failure using the povray-3.7.0.8_11 package and povray demo.pov. Review the related upstream issue 460 and compare the parser and rendering behavior; done means the demo scene renders successfully without the parse error or zero intersections.

Written by the indexing model from the issue text.

Assessment

Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.