Now with basic support for motion blur.

Source & Windows binary packages are available at:

https://github.com/UberPOV/UberPOV/releases/tag/v1.37.0.0-beta.2

Post a reply to this message

> Now with basic support for motion blur.

    I just started to try to apply reflection blur to my christmas
baubles... but found a problem even before starting:

    As a first test, I just changed the version directive and rendered it
with UberPOV, and the garland was missing. Checking my ugly code, I
found that trace() seems to not be working at all. The attached simple
scene shows the problem: on 3.7 you get some scattered spheres, as the
trace() call finds an intersection point with the plane, but on UberPOV
all the spheres get placed at <0,0,0>, as the intersection test seems to
fail (normal is also 0).

--
Jaime

Post a reply to this message

Attachments:
Download 'us-ascii' (1 KB)

Am 24.11.2013 13:05, schrieb Jaime Vives Piqueres:

>> Now with basic support for motion blur.
>
>     I just started to try to apply reflection blur to my christmas
> baubles... but found a problem even before starting:
>
>     As a first test, I just changed the version directive and rendered it
> with UberPOV, and the garland was missing. Checking my ugly code, I
> found that trace() seems to not be working at all. The attached simple
> scene shows the problem: on 3.7 you get some scattered spheres, as the
> trace() call finds an intersection point with the plane, but on UberPOV
> all the spheres get placed at <0,0,0>, as the intersection test seems to
> fail (normal is also 0).

I've already stumbled across - and fixed - this very bug myself 
yesterday :-)

In case you are using Linux, or have access to Visual Studio 2010, you 
may want to get the latest code from the "master" branch at 
https://github.com/UberPOV/UberPOV.

I would have rushed out a new beta already, but haven't found the time 
yet; it'll probably happen no sooner than tomorrow. Windows users might 
want to use the older beta.2 until then.

There is another bug in beta.2 that breaks SSLT; again, both beta.2 and 
the current master branch are fine.

Post a reply to this message

On 11/24/2013 08:02 AM, clipka wrote:
> There is another bug in beta.2 that breaks SSLT; again, both beta.2 and
> the current master branch are fine.

Hmmm ... just pulled and I'm getting:

In file included from /usr/include/boost/thread.hpp:24:0,
                  from ./backend/povray.h:53,
                  from ./backend/control/renderbackend.h:40,
                  from ./backend/control/messagefactory.h:39,
                  from backend/frame.h:65,
                  from lightgrp.cpp:35:
/usr/include/boost/thread/future.hpp:286:12: error: stray ‘\267’ in program
/usr/include/boost/thread/future.hpp:286:12: error: stray ‘\23’ in program
/usr/include/boost/thread/future.hpp: In static member function ‘static 
void 
boost::detail::future_traits<void>::cleanup(boost::detail::future_traits<void>::storage_type&)’:
/usr/include/boost/thread/future.hpp:286:19: error: ‘orage’ was not 
declared in this scope

I last built yesterday (23rd) early in the morning ... was fine then. I 
was not getting the results I was expecting from +am3, so after seeing 
Jamies post I decided to re-build.

Jim

Post a reply to this message

> I've already stumbled across - and fixed - this very bug myself
> yesterday :-)

   Surely, just moments after I downloaded it... :) ...will try again 
with the latest code, thanks.


--
Jaime

Post a reply to this message

Am 24.11.2013 15:36, schrieb James Holsenback:
> On 11/24/2013 08:02 AM, clipka wrote:
>> There is another bug in beta.2 that breaks SSLT; again, both beta.2 and
>> the current master branch are fine.
>
> Hmmm ... just pulled and I'm getting:
>
> In file included from /usr/include/boost/thread.hpp:24:0,
>                   from ./backend/povray.h:53,
>                   from ./backend/control/renderbackend.h:40,
>                   from ./backend/control/messagefactory.h:39,
>                   from backend/frame.h:65,
>                   from lightgrp.cpp:35:
> /usr/include/boost/thread/future.hpp:286:12: error: stray ‘\267’ in program
> /usr/include/boost/thread/future.hpp:286:12: error: stray ‘\23’ in program
> /usr/include/boost/thread/future.hpp: In static member function ‘static
> void
>
boost::detail::future_traits<void>::cleanup(boost::detail::future_traits<void>::storage_type&)’:
>
> /usr/include/boost/thread/future.hpp:286:19: error: ‘orage’ was not
> declared in this scope

According to the message, the file "future.hpp" - part of the boost 
library's dev package that apparently comes with your Linux distro - 
contains two non-ASCII characters among the program code. \267 (aka 
0xB7, or decimal 183) and \23 (aka 0x13, or decimal 19), are a centered 
dot ("MIDDLE DOT") and a non-printable character ("DEVICE CONTROL THREE" 
aka DC3), respectively.

The code you just pulled probably doesn't have anything to do with it; 
something must have garbled your libboost-dev package.

Post a reply to this message

On 11/24/2013 04:32 PM, clipka wrote:
> Am 24.11.2013 15:36, schrieb James Holsenback:
>> On 11/24/2013 08:02 AM, clipka wrote:
>>> There is another bug in beta.2 that breaks SSLT; again, both beta.2 and
>>> the current master branch are fine.
>>
>> Hmmm ... just pulled and I'm getting:
>>
>> In file included from /usr/include/boost/thread.hpp:24:0,
>>                   from ./backend/povray.h:53,
>>                   from ./backend/control/renderbackend.h:40,
>>                   from ./backend/control/messagefactory.h:39,
>>                   from backend/frame.h:65,
>>                   from lightgrp.cpp:35:
>> /usr/include/boost/thread/future.hpp:286:12: error: stray ‘\267’ in
>> program
>> /usr/include/boost/thread/future.hpp:286:12: error: stray ‘\23’ in
>> program
>> /usr/include/boost/thread/future.hpp: In static member function ‘static
>> void
>>
boost::detail::future_traits<void>::cleanup(boost::detail::future_traits<void>::storage_type&)’:
>>
>>
>> /usr/include/boost/thread/future.hpp:286:19: error: ‘orage’ was not
>> declared in this scope
>
> According to the message, the file "future.hpp" - part of the boost
> library's dev package that apparently comes with your Linux distro -
> contains two non-ASCII characters among the program code. \267 (aka
> 0xB7, or decimal 183) and \23 (aka 0x13, or decimal 19), are a centered
> dot ("MIDDLE DOT") and a non-printable character ("DEVICE CONTROL THREE"
> aka DC3), respectively.
>
> The code you just pulled probably doesn't have anything to do with it;
> something must have garbled your libboost-dev package.
>

Since I hadn't touched my end I didn't think it was the problem, but I 
refreshed my boost package and that was indeed the problem ... however a 
render I left running while at work (yesterday build) had an error when 
I got home to check:

Rendered 379904 of 705600 pixels (53%)
Cannot access data in file.
Rendered 380928 of 705600 pixels (53%)
Fatal error in renderer: Frontend halted render.

Dunno if it was related to the above problem ... just thought I'd 
mention it anyways

Post a reply to this message

On 11/24/2013 11:11 PM, James Holsenback wrote:
> Dunno if it was related to the above problem ... just thought I'd
> mention it anyways

sheesh ... should have realized my pull script was snagging the master 
/not/ beta branch ... that will teach me to try to throw something 
together quickly before i've checked things a bit more

Post a reply to this message

On 11/24/2013 11:11 PM, James Holsenback wrote:
> Rendered 379904 of 705600 pixels (53%)
> Cannot access data in file.
> Rendered 380928 of 705600 pixels (53%)
> Fatal error in renderer: Frontend halted render.
>
> Dunno if it was related to the above problem ... just thought I'd
> mention it anyways

decreased +am3 aa depth from +r6 to +r4 and abort went away ...

Post a reply to this message

Am 25.11.2013 21:14, schrieb James Holsenback:
> On 11/24/2013 11:11 PM, James Holsenback wrote:
>> Rendered 379904 of 705600 pixels (53%)
>> Cannot access data in file.
>> Rendered 380928 of 705600 pixels (53%)
>> Fatal error in renderer: Frontend halted render.
>>
>> Dunno if it was related to the above problem ... just thought I'd
>> mention it anyways
>
> decreased +am3 aa depth from +r6 to +r4 and abort went away ...

Strange one - can't make any sense of this yet.

Post a reply to this message