Christoph Lipka

Having just had a look at invocations of `Inside`, I see no evidence of insideness-tests when initializing secondary rays. Initialization of primary rays (both camera and photons) does require insideness-tests...

For the records: I'll file this as "exceptionally rare scenario, with involvement of the parser", so nothing we want to tackle in a hurry while we prepare for v3.8.0 release.

I'd like to leave the POVMS interface unchanged for v3.8, and only tackle the regression vs. v3.6 there. For v4.0, I think we should indeed fully support double precision for...

@wfpokorny Can you give a short TL;DR of the current state of the issue?

@chris20 Did you ever find the time to address the hard-to-hit pause button issue? If not, would you consider it worthwhile trying to address this in v3.8?

For the records: This is long-standing behavior, and I suspect it might be non-trivial to fix, so I'm quite confident that we don't want to mess with this as we're...

@wfpokorny @LeForgeron Can you provide a TL;DR on the findings discussed in pull request #358?

At a first glance, it looks like you're simply missing an input image file (i.e. an image used as a texture or some such). Maybe a typo in the file...

According to https://github.com/termux/termux-packages/issues/202, the problem is getting the boost libraries to compile on Android. Since POV-Ray 3.7 relies heavily on boost throughout the code, that's a deal breaker. Thanks to...

Anti-aliasing makes use of pseudo-random sequences which are seeded based on the render thread block coordinates to make sure the results are repeatable regardless of the order of render thread...