 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
When running the following code with:
povray +a0.03 +kff240
#include "colors.inc"
#include "metals.inc"
#include "stones.inc"
#include "math.inc"
light_source { <10, 50, -30> rgb 1 }
camera {
location <0.0, 6.0, -15.0>
up y
right x*(image_width/image_height)
look_at 0.0
}
#default {
pigment { White }
finish { ambient 0.1 diffuse 0.6 }
}
difference {
plane { y, 0 }
sphere { 0.0, 5.0 }
pigment { White*0.625 }
finish { ambient 0 diffuse 0.4 }
}
difference {
intersection {
torus { 5.0, 0.75 }
cylinder { -0.5*y, 0.5*y, 6.0 }
}
sphere { 0.0, 4.9375 }
}
#declare Frame_Rate = 24;
#declare Duration = 10;
#declare Frame_Count = Frame_Rate * Duration;
#macro index(seconds)
#local tick = (1 / Frame_Count) * Frame_Rate;
seconds*tick
#end
union {
union {
difference {
cylinder { -0.375*y, 0.375*y, 4.875 }
cylinder { -0.4375*y, 0.4375*y, 4.625 }
}
difference {
cylinder { -0.375*y, 0.375*y, 4.5 }
cylinder { -0.4375*y, 0.4375*y, 4.25 }
}
}
difference {
cylinder { -0.375*y, 0.375*y, 4.125 }
cylinder { -0.4375*y, 0.4375*y, 3.875 }
#if(clock <= index(5))
rotate (3600*pow((clock-index(0)),2)/index(5))*x
#else
rotate (3600*(clock-index(5))/index(10))*x
#end
}
}
A.D.B.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 11/09/2010 02:58, Anthony D. Baye nous fit lire :
> When running the following code with:
>
> povray +a0.03 +kff240
Rendered, cannot reproduce the segfault.
Povray 3.7beta38+, on Ubuntu amd64
(additional personal data: +WT18, -H1025 -W1025 )
There is a discontinuity between image 120 & 121.
Images 1 & 121 looks alike.
Images 120 & 240 too.
Have you more details for your segfault ?
(povray version, operating system, ...)
Rendering frame 240 of 240
Parser Options
Input file: seg.pov
Remove bounds........On
Split unions.........Off
Library paths:
/usr/local/share/povray-3.7
/usr/local/share/povray-3.7/ini
/usr/local/share/povray-3.7/include
==== [Parsing...] ==========================================================
----------------------------------------------------------------------------
Parser Statistics
----------------------------------------------------------------------------
Finite Objects: 4
Infinite Objects: 1
Light Sources: 1
Total: 6
----------------------------------------------------------------------------
Parser Time
Parse Time: 0 hours 0 minutes 0 seconds (0.014 seconds)
using 1 thread(s) with 0.013 CPU-seconds total
Bounding Time: 0 hours 0 minutes 0 seconds (0.000 seconds)
using 1 thread(s) with 0.000 CPU-seconds total
----------------------------------------------------------------------------
Render Options
Quality: 9
Bounding boxes.......On Bounding threshold: 3
Antialiasing.........On (Method 1, Threshold 0.030, Depth 3, Jitter 1.00,
Gamma 2.50)
==== [Rendering...] ========================================================
----------------------------------------------------------------------------
Render Statistics
Image Resolution 1025 x 1025
----------------------------------------------------------------------------
Pixels: 1118275 Samples: 298926 Smpls/Pxl: 0.27
Rays: 1417201 Saved: 0 Max Level: 1/5
----------------------------------------------------------------------------
Ray->Shape Intersection Tests Succeeded Percentage
----------------------------------------------------------------------------
Cone/Cylinder 3788985 2330974 61.52
CSG Intersection 5836665 2300467 39.41
Plane 2681769 1359732 50.70
Sphere 3522038 1446511 41.07
Torus 840269 534844 63.65
Torus Bound 840269 596794 71.02
Bounding Box 10727076 2667349 24.87
----------------------------------------------------------------------------
Roots tested: 596794 eliminated: 69323
Shadow Ray Tests: 1291314 Succeeded: 26908
Shadow Cache Hits: 26746
----------------------------------------------------------------------------
----------------------------------------------------------------------------
Render Time:
Photon Time: No photons
Radiosity Time: No radiosity
Trace Time: 0 hours 0 minutes 0 seconds (0.473 seconds)
using 18 thread(s) with 5.196 CPU-seconds total
POV-Ray finished
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Same version. Ubuntu Karmic, povray 3.7 beta 38, fujitsu lifebook w/ intel core2
duo 32-bit
segfaults after rendering the first frame, even with your extra arguments
gdb returns the following:
[New Thread 0xb495ab70 (LWP 3483)]
[New Thread 0xb2cb0b70 (LWP 3484)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb705eb70 (LWP 3456)]
0x08053f14 in ?? ()
hope this is helpful
A.D.B.
Le_Forgeron <jgr### [at] free fr> wrote:
> Le 11/09/2010 02:58, Anthony D. Baye nous fit lire :
> > When running the following code with:
> >
> > povray +a0.03 +kff240
>
> Rendered, cannot reproduce the segfault.
> Povray 3.7beta38+, on Ubuntu amd64
> (additional personal data: +WT18, -H1025 -W1025 )
>
> There is a discontinuity between image 120 & 121.
> Images 1 & 121 looks alike.
> Images 120 & 240 too.
>
> Have you more details for your segfault ?
> (povray version, operating system, ...)
>
> Rendering frame 240 of 240
>
> Parser Options
> Input file: seg.pov
> Remove bounds........On
> Split unions.........Off
> Library paths:
> /usr/local/share/povray-3.7
> /usr/local/share/povray-3.7/ini
> /usr/local/share/povray-3.7/include
> ==== [Parsing...] ==========================================================
> ----------------------------------------------------------------------------
> Parser Statistics
> ----------------------------------------------------------------------------
> Finite Objects: 4
> Infinite Objects: 1
> Light Sources: 1
> Total: 6
> ----------------------------------------------------------------------------
> Parser Time
> Parse Time: 0 hours 0 minutes 0 seconds (0.014 seconds)
> using 1 thread(s) with 0.013 CPU-seconds total
> Bounding Time: 0 hours 0 minutes 0 seconds (0.000 seconds)
> using 1 thread(s) with 0.000 CPU-seconds total
> ----------------------------------------------------------------------------
> Render Options
> Quality: 9
> Bounding boxes.......On Bounding threshold: 3
> Antialiasing.........On (Method 1, Threshold 0.030, Depth 3, Jitter 1.00,
> Gamma 2.50)
> ==== [Rendering...] ========================================================
> ----------------------------------------------------------------------------
> Render Statistics
> Image Resolution 1025 x 1025
> ----------------------------------------------------------------------------
> Pixels: 1118275 Samples: 298926 Smpls/Pxl: 0.27
> Rays: 1417201 Saved: 0 Max Level: 1/5
> ----------------------------------------------------------------------------
> Ray->Shape Intersection Tests Succeeded Percentage
> ----------------------------------------------------------------------------
> Cone/Cylinder 3788985 2330974 61.52
> CSG Intersection 5836665 2300467 39.41
> Plane 2681769 1359732 50.70
> Sphere 3522038 1446511 41.07
> Torus 840269 534844 63.65
> Torus Bound 840269 596794 71.02
> Bounding Box 10727076 2667349 24.87
> ----------------------------------------------------------------------------
> Roots tested: 596794 eliminated: 69323
> Shadow Ray Tests: 1291314 Succeeded: 26908
> Shadow Cache Hits: 26746
> ----------------------------------------------------------------------------
> ----------------------------------------------------------------------------
> Render Time:
> Photon Time: No photons
> Radiosity Time: No radiosity
> Trace Time: 0 hours 0 minutes 0 seconds (0.473 seconds)
> using 18 thread(s) with 5.196 CPU-seconds total
> POV-Ray finished
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 12/09/2010 03:03, Anthony D. Baye nous fit lire :
> Same version. Ubuntu Karmic, povray 3.7 beta 38, fujitsu lifebook w/ intel core2
> duo 32-bit
>
> segfaults after rendering the first frame, even with your extra arguments
>
> gdb returns the following:
>
> [New Thread 0xb495ab70 (LWP 3483)]
> [New Thread 0xb2cb0b70 (LWP 3484)]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb705eb70 (LWP 3456)]
> 0x08053f14 in ?? ()
>
> hope this is helpful
>
It might... it might be a 32 bit issue.
I recompiled for gdb, and ran from the debugger: no SIGSEGV on my 64
bits. (Lucid)
Maybe someone with a 32 bits system could help ?
Maybe a precision issue or a compiler issue ?
Notice that index(seconds) should be expanded as
"seconds*(1 / Duration)"
as tick= (1/FC)*FR
and FC = FR*Duration
ergo tick = (1/(FR*Duration)*FR = 1/Duration (as long as FR !=0)
pow(clock-index(0),2) might be clearer as pow(clock,2)
and it might also be interesting to use frame_number, initial_frame,
final_frame to automatically adjust the frame_rate
( http://www.povray.org/documentation/view/3.6.1/228/ )
from the command line
( http://www.povray.org/documentation/view/3.6.1/216/ )
+kff240 +kf10.0 +ki0.0 +kfi1
(clock going from 0 to 10, frames from 1 to 240, 20 frames per clock unit)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 09/12/2010 06:10 AM, Le_Forgeron wrote:
> Maybe someone with a 32 bits system could help ?
Ran to completion on my opensuse-11.2 32bit system. Code exactly as
original poster. I'm running the current state of the perforce depot.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 2010-09-12 13:02, Jim Holsenback a écrit :
> On 09/12/2010 06:10 AM, Le_Forgeron wrote:
>> Maybe someone with a 32 bits system could help ?
>
> Ran to completion on my opensuse-11.2 32bit system. Code exactly as
> original poster. I'm running the current state of the perforce depot.
>
Ran without any problem under Windows XP 32 bits.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le_Forgeron <jgr### [at] freefr> wrote:
> Le 12/09/2010 03:03, Anthony D. Baye nous fit lire :
> > Same version. Ubuntu Karmic, povray 3.7 beta 38, fujitsu lifebook w/ intel core2
> > duo 32-bit
> >
> > segfaults after rendering the first frame, even with your extra arguments
> >
> > gdb returns the following:
> >
> > [New Thread 0xb495ab70 (LWP 3483)]
> > [New Thread 0xb2cb0b70 (LWP 3484)]
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 0xb705eb70 (LWP 3456)]
> > 0x08053f14 in ?? ()
> >
> > hope this is helpful
> >
>
> It might... it might be a 32 bit issue.
> I recompiled for gdb, and ran from the debugger: no SIGSEGV on my 64
> bits. (Lucid)
> Maybe someone with a 32 bits system could help ?
> Maybe a precision issue or a compiler issue ?
>
>
> Notice that index(seconds) should be expanded as
> "seconds*(1 / Duration)"
> as tick= (1/FC)*FR
> and FC = FR*Duration
> ergo tick = (1/(FR*Duration)*FR = 1/Duration (as long as FR !=0)
>
> pow(clock-index(0),2) might be clearer as pow(clock,2)
>
> and it might also be interesting to use frame_number, initial_frame,
> final_frame to automatically adjust the frame_rate
> ( http://www.povray.org/documentation/view/3.6.1/228/ )
> from the command line
> ( http://www.povray.org/documentation/view/3.6.1/216/ )
> +kff240 +kf10.0 +ki0.0 +kfi1
> (clock going from 0 to 10, frames from 1 to 240, 20 frames per clock unit)
I normally do use the built-ins for computation, but I couldn't find my
animation notes on what was what, so I made my own terms.
I haven't been using all the animation options...
A.D.B.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Anthony D. Baye" <Sha### [at] spamnomorehotmailcom> wrote:
> Le_Forgeron <jgr### [at] freefr> wrote:
> > Le 12/09/2010 03:03, Anthony D. Baye nous fit lire :
> > > Same version. Ubuntu Karmic, povray 3.7 beta 38, fujitsu lifebook w/ intel core2
> > > duo 32-bit
> > >
> > > segfaults after rendering the first frame, even with your extra arguments
> > >
> > > gdb returns the following:
> > >
> > > [New Thread 0xb495ab70 (LWP 3483)]
> > > [New Thread 0xb2cb0b70 (LWP 3484)]
> > >
> > > Program received signal SIGSEGV, Segmentation fault.
> > > [Switching to Thread 0xb705eb70 (LWP 3456)]
> > > 0x08053f14 in ?? ()
> > >
> > > hope this is helpful
> > >
> >
> > It might... it might be a 32 bit issue.
> > I recompiled for gdb, and ran from the debugger: no SIGSEGV on my 64
> > bits. (Lucid)
> > Maybe someone with a 32 bits system could help ?
> > Maybe a precision issue or a compiler issue ?
> >
> >
> > Notice that index(seconds) should be expanded as
> > "seconds*(1 / Duration)"
> > as tick= (1/FC)*FR
> > and FC = FR*Duration
> > ergo tick = (1/(FR*Duration)*FR = 1/Duration (as long as FR !=0)
> >
> > pow(clock-index(0),2) might be clearer as pow(clock,2)
> >
> > and it might also be interesting to use frame_number, initial_frame,
> > final_frame to automatically adjust the frame_rate
> > ( http://www.povray.org/documentation/view/3.6.1/228/ )
> > from the command line
> > ( http://www.povray.org/documentation/view/3.6.1/216/ )
> > +kff240 +kf10.0 +ki0.0 +kfi1
> > (clock going from 0 to 10, frames from 1 to 240, 20 frames per clock unit)
>
> I normally do use the built-ins for computation, but I couldn't find my
> animation notes on what was what, so I made my own terms.
>
> I haven't been using all the animation options...
>
> A.D.B.
Ran a simple test with full command line options, replacing the animation code
with rotate 360*clock*x and reducing the number of frames to 24.
Render still seg-faults after first frame.
Is there any way to do a full un-install of povray in linux?
I could try re-compiling from sources.
A.D.B.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
the problem disappeared when I turned of the display (-D). There must be
something buggy in the display code or it's interaction with X.
A.D.B.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 13/09/2010 21:41, Anthony D. Baye nous fit lire :
> "Anthony D. Baye" <Sha### [at] spamnomorehotmailcom> wrote:
>> Le_Forgeron <jgr### [at] freefr> wrote:
>>> and it might also be interesting to use frame_number, initial_frame,
>>> final_frame to automatically adjust the frame_rate
>>> ( http://www.povray.org/documentation/view/3.6.1/228/ )
>>> from the command line
>>> ( http://www.povray.org/documentation/view/3.6.1/216/ )
>>> +kff240 +kf10.0 +ki0.0 +kfi1
>>> (clock going from 0 to 10, frames from 1 to 240, 20 frames per clock unit)
>>
>> I normally do use the built-ins for computation, but I couldn't find my
>> animation notes on what was what, so I made my own terms.
>>
>> I haven't been using all the animation options...
it was just a reminder, I just know they exists... have always trouble
to find them all. Do not take that too seriously.
>>
>> A.D.B.
>
> Ran a simple test with full command line options, replacing the animation code
> with rotate 360*clock*x and reducing the number of frames to 24.
>
> Render still seg-faults after first frame.
>
> Is there any way to do a full un-install of povray in linux?
>
> I could try re-compiling from sources.
Installation from sources does not need uninstall (it might just
overwrite the old files... and change the damned ownership of your
default in $HOME/.povray/3.7/... if you install with "sudo make install"
(and it will install them in ~root/.povray/3.7 if you install as true root)
Last idea, what is your image format for output, and what is the library
version ?
(hint: libpng ??? might have a binary issue between the 1.2 & 1.4, IIRC)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
