 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <40fc182d$1@news.povray.org> , "Jeremy M. Praay"
<jer### [at] questsoftware com> wrote:
> I don't want to get into the "this is a bug or not" argument, but I find it
> annoying, and this "feature" was not in 3.5. In fact, I've returned to
> 3.5, as this seems to happen to me every few minutes when using 3.6. I
> guess it just has to do with the way some of us stop renders/parses.
Well, that attitude is hardly helpful. You refuse to provide any even
remotely useful description how to reproduce a problem you are seeing. Do
you really think this makes it more likely the problem will go away in the
future? Whining does really get nobody anywhere!
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:40fc1a56@news.povray.org...
> In article <40fc182d$1@news.povray.org> , "Jeremy M. Praay"
> <jer### [at] questsoftwarecom> wrote:
>
> > I don't want to get into the "this is a bug or not" argument, but I find
it
> > annoying, and this "feature" was not in 3.5. In fact, I've returned to
> > 3.5, as this seems to happen to me every few minutes when using 3.6. I
> > guess it just has to do with the way some of us stop renders/parses.
>
> Well, that attitude is hardly helpful. You refuse to provide any even
> remotely useful description how to reproduce a problem you are seeing. Do
> you really think this makes it more likely the problem will go away in the
> future? Whining does really get nobody anywhere!
>
I've seen this mentioned at least a couple of other times in these
newsgroups. I don't feel the need to mention it again and again (or at all
if someone has already mentioned it), but I don't mind saying that I'm
experiencing the same annoying problem, hoping that the more people who
mention it will lead to it getting fixed sooner. I didn't think I was being
whiney. I thought I was just letting someone know that this is not an
isolated case.
--
Jeremy
www.beantoad.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <40fc7542$1@news.povray.org> , "Jeremy M. Praay"
<sla### [at] hotmailcom> wrote:
> I've seen this mentioned at least a couple of other times in these
> newsgroups. I don't feel the need to mention it again and again (or at all
> if someone has already mentioned it), but I don't mind saying that I'm
> experiencing the same annoying problem, hoping that the more people who
> mention it will lead to it getting fixed sooner. I didn't think I was being
> whiney. I thought I was just letting someone know that this is not an
> isolated case.
Well, it should be fairly obvious that only a few of the thousands of people
using POV-Ray for Windows see the problem, so obviously a tiny bit more is
needed than saying "me too". The bug reporting guidelines in the faq group
exist for a reason ... if you do not follow them, we just won't be able to
help you. It is that simple, sorry!
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:40fcc820@news.povray.org...
> Well, it should be fairly obvious that only a few of the thousands of
people
> using POV-Ray for Windows see the problem, so obviously a tiny bit more is
> needed than saying "me too". The bug reporting guidelines in the faq
group
> exist for a reason ... if you do not follow them, we just won't be able to
> help you. It is that simple, sorry!
>
I'm apologize that I can't provide you with much more information than has
already been posted by others on this matter. I believe that it is a bug,
and I that was my point to Apache. It appears in 3.6 and it is not in 3.5
(in other words, it is not related to a separate change in my operating
system). This seems to be a random occurrence that may be in relation to
the way I (we) stop parses/renders.
I'm sorry that doesn't help you. Like the others, I'm running XP Home with
I/O permissions turned off. As far as I can tell from previous posts, this
is the common theme.
--
Jeremy
www.beantoad.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
A way to reproduce this thing:
1.
Take any scene that needs a long parse time so that you have the time to
abort it before the rendere kicks in.
2.
While pov-ray is parsing, abort it and change something in the source so
that you can save changes.
POV-Ray won't be liking that because the file is apparently still in use
and/or locked because it's apparently still parsing. Press Abort when
POV-Ray asks you what you want to do now so that you can edit the code again
if you like
3.
When parsing has really stopped and the RUN (alt-g) button is available
again, try to save once again. POV-Ray will refuse to save even now. I
simply copy-paste the code I want to save, close POV-Ray without storing
data. And I'll paste the code into a new instance of POV-Ray
Although I'm pretty sure you guys already know of this kind of behaviour, I
still hope I'm at least helping a bit with this!
Regards,
Eli Jehoel
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <40fd4ec1$1@news.povray.org> , "Apache"
<apa### [at] hotmailcom> wrote:
> 1.
> Take any scene that needs a long parse time so that you have the time to
> abort it before the rendere kicks in.
>
> 2.
> While pov-ray is parsing, abort it and change something in the source so
> that you can save changes.
> POV-Ray won't be liking that because the file is apparently still in use
> and/or locked because it's apparently still parsing. Press Abort when
> POV-Ray asks you what you want to do now so that you can edit the code again
> if you like
>
> 3.
> When parsing has really stopped and the RUN (alt-g) button is available
> again, try to save once again. POV-Ray will refuse to save even now. I
> simply copy-paste the code I want to save, close POV-Ray without storing
> data. And I'll paste the code into a new instance of POV-Ray
I tried the "Tierra (LOTW)" scene posted in p.b.s-f a few weeks ago and used
it with 30000 trees and let it parse to 50 million tokens, then used the
keybord to stop the render and instantly after that save the modified scene
file (in which I had inserted a space). The files was saved as expected.
The system was a P4 3GHz with 1 GB of memory running Win XP Pro (used over
remote desktop) with all available Win patches installed.
Thus, I am afraid more information is needed. A scene for example. And the
system software, processor and physical memory of everone seeing this
problem will surely not hurt either.
> Although I'm pretty sure you guys already know of this kind of behaviour, I
> still hope I'm at least helping a bit with this!
Well, I think you have been told numerous times that this is not the case.
And given that there is no flood of reports in these groups despite
thousands of download, it should be fairly clear that this only happens on
some systems...
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi,
This thread probably belongs in povray.windows.
That being said, I can't replicate the problem either. If I can you can be
sure it will be fixed but at this point I'm not seeing it.
Thorsten, I wonder if this is another example of non-volatile variables causing
problems ? e.g. I could never replicate that 'thread failed to init' problem
either but I know it affected certain machines but not others, just like this
one does.
If so a VC++ compile will probably flush it out.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <40fddf29@news.povray.org> , "Chris Cason"
<new### [at] deletethispovrayorg> wrote:
> Thorsten, I wonder if this is another example of non-volatile variables
causing
> problems ? e.g. I could never replicate that 'thread failed to init' problem
> either but I know it affected certain machines but not others, just like this
> one does.
I rather suspect it is a race condition somewhere.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I'm sorry that doesn't help you. Like the others, I'm running XP Home
with
> I/O permissions turned off. As far as I can tell from previous posts,
this
> is the common theme.
I have had the problem using Windows ME, but so far any attempt to replicate
the problem has failed.
Peter
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:40fd5fcf$1@news.povray.org...
>
> I tried the "Tierra (LOTW)" scene posted in p.b.s-f a few weeks ago and
used
> it with 30000 trees and let it parse to 50 million tokens, then used the
> keybord to stop the render and instantly after that save the modified
scene
> file (in which I had inserted a space). The files was saved as expected.
> The system was a P4 3GHz with 1 GB of memory running Win XP Pro (used over
> remote desktop) with all available Win patches installed.
I generally use the "Stop Sign" button, if that's at all relevant.
When you say you stopped "the render", do you actually mean "the parse"?
Again, as others have mentioned this does not appear to happen every time.
You could try your test at various intervals during the parse, and after
perhaps 10 or 20 times, see if it eventually causes the problem.
>
> Thus, I am afraid more information is needed. A scene for example. And
the
> system software, processor and physical memory of everone seeing this
> problem will surely not hurt either.
XP Home with all critical updates, AMD XP 3200+, 1GB RAM. I can retest
after making sure that I have ALL XP updates.
>
> > Although I'm pretty sure you guys already know of this kind of
behaviour, I
> > still hope I'm at least helping a bit with this!
>
> Well, I think you have been told numerous times that this is not the case.
This problem was first mentioned on June 16th.
> And given that there is no flood of reports in these groups despite
> thousands of download, it should be fairly clear that this only happens on
> some systems...
>
This may be an underestimate. The fact that a few regular posters to this
newsgroup have reported this problem likely means that a great deal more
people are having this problem and are simply not reporting it.
I'm willing to try anything that you can suggest to narrow this down, but
right now it appears to be completely random.
--
Jeremy
www.beantoad.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
