 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 8/10/20 3:35 PM, Thorsten wrote:
> On 10.08.2020 14:05, William F Pokorny wrote:
...
>
The additional information is appreciated Thorsten. Thank you.
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> On 11.08.2020 18:13, Alain Martel wrote:
>> condition where two or more processes or threads are asking for the
>> same resource at the same time and each is waiting for the other to
>> finish using that resource.
>
> No, this is not how POVMS is written. I am its author ;-)
>
> Thorsten
One of the process may not be POV-Ray related.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 12.08.2020 19:08, Alain Martel wrote:
>> On 11.08.2020 18:13, Alain Martel wrote:
>>> condition where two or more processes or threads are asking for the
>>> same resource at the same time and each is waiting for the other to
>>> finish using that resource.
>>
>> No, this is not how POVMS is written. I am its author ;-)
>>
>> Thorsten
>
> One of the process may not be POV-Ray related.
The error message "Operation timed out" comes from inside POV-Ray.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi(gh)!
On 10.08.20 14:05, William F Pokorny wrote:
> Use -cc so the state file work does not get done.
Where - in the command line? This results in an error: "Failed to parse
command line option"
See you in Khyberspace!
Yadgar
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Hi(gh)!
>
> On 10.08.20 14:05, William F Pokorny wrote:
>
>> Use -cc so the state file work does not get done.
>
> Where - in the command line? This results in an error: "Failed to parse
> command line option"
>
> See you in Khyberspace!
>
> Yadgar
OK. Expect this means you are running v3.7?
This option was added to v3.8 by Christoph to re-enable continuation
capability available in earlier the v3.7 versions of POV-Ray.
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi(gh)!
On 14.08.20 13:06, William F Pokorny wrote:
> OK. Expect this means you are running v3.7?
Yes, I do... this probably means I have to do POVEarth animation loops
manually! Ars longa, vita brevis...
See you in Khyberspace!
Yadgar
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 12/08/2020 à 19:23, Thorsten a écrit :
> On 12.08.2020 19:08, Alain Martel wrote:
>> Le 2020-08-11 à 13:29, Thorsten a écrit :
>>> On 11.08.2020 18:13, Alain Martel wrote:
>>>> Another case that can cause an «operation timed out» is a race
>>>> condition where two or more processes or threads are asking for the
>>>> same resource at the same time and each is waiting for the other to
>>>> finish using that resource.
>>>
>>> No, this is not how POVMS is written. I am its author ;-)
>>>
>>> Thorsten
>>
>> One of the process may not be POV-Ray related.
>
> The error message "Operation timed out" comes from inside POV-Ray.
And the only spot in source for it is when a stream was not provided
answer for long enough time (unclear if it is 100 or 10 seconds).
Which remind me of a windows specific bug for povray: rendering a large
but empty (or easy) scene would overflow the collecting thread with
amount of blocks to process (while the system actually starts swapping
everyone, or at least that process), leading to a problem that the
collecting thread get no cpu to process the queue, and then detecting
that too much time has past since the query.
(well behaved operating systems try to slow the producer thread(s) when
a stream get filled too fast, in order to give a chance to the consumer,
but not MS, IIRC)
A workaround might have been to reduce the number of rendering threads
(+WT1 ?) in such situation.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> But when I try to render a sequence of consecutive images, such as
>
> +ipovearth.pov +ogeorgia_panorama-.png +w1024 +h768 +a0.3 +ki0 +kf719
> +kfi0 +kff719 (a simple camera rotation pull)
>
> after completing the first frame, I get:
>
> Operation timed out
> Operation timed out
> Render failed
Did you find a solution to this problem? I get this error all the time when
rendering animation frames. It's maddening. It seems to happen when a new frame
is about to begin and the status area displays the message "Running pre-frame
shellout" for a long time.
Kind regards,
Dave Blandston
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi(gh)!
On 26.12.20 12:15, Dave Blandston wrote:
> Did you find a solution to this problem? I get this error all the time when
> rendering animation frames. It's maddening. It seems to happen when a new frame
> is about to begin and the status area displays the message "Running pre-frame
> shellout" for a long time.
I programmed a workaround via bash shell scripting!
See you in Khyberspace!
Yadgar
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I programmed a workaround via bash shell scripting!
>
> See you in Khyberspace!
>
> Yadgar
Awesome! I will see if there's a similar solution for Windows.
Kind regards,
Dave Blandston
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
