 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Carl lately stumbled upon this and was referenced to a thread in
povray.general on 24.11.2004, and I've now found that I'm having problems
with exactly the same bug. As I'm using thousands of objects which get
placed and modified via macros to create hair, single hairs will stick out
at random angles, so this bug is kinda annoying. It would also hinder the
workflow and design decisions on some important parts to make the system
customizable.
Thus, two questions, the first of an ordinary type which should be an easy
workaround as a solution for the time being, the second a little more the
kind of "handle-with-care", as it's actually a "Don't ask, just wait!"
question for which I'll probably get flamed or such. :-)
1. What were the changes from version 3.5 to 3.6? Which features got
changed/added/removed? I'm asking this as I would like to test the macros on
a "bug-free" system to assure that it's working properly. If the standard
SDL-programming author wouldn't recognize them (aside of the "when do the
radiosity values get clipped?"-Thingy), I could use them and hope that the
3.6.2 will be out soon. I'd just put a note in regard to this problem on my
website when making the system available for download.
2. Please don't kill me for asking, but is there any possibility of
releasing the patch for this (probably amonst other small things) ASAP
rather than waiting for other bugs to get fixed as well? Or maybe an
optional in-between fix to be downloaded for the desperate, with just this
bug fixed? The thread from 2004 suggests that Thorsten already has found a
fix for this... IMHO the issue of macros not working properly is actually a
major problem, at least on my end. I rely on many macros and if I can't be
sure that their values will be returned properly, I'd be sitting in some
sort of tiny Povers hell... ;-)
Kind regards,
Tim
--
"Tim Nikias v2.0"
Homepage: <http://www.nolights.de>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Eh, note to self: search the Povray.Org-Website more thoroughly next time. I
found the link to the changes between 3.5 to 3.6 somewhere in the
Downloads-Section...
Still, an answer question 2, anyone? ;-)
--
"Tim Nikias v2.0"
Homepage: <http://www.nolights.de>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Tim Nikias wrote:
> Still, an answer question 2, anyone? ;-)
Not sure, it _could_ be that the Windows 3.6.1a does contain the fix for this...
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> > Still, an answer question 2, anyone? ;-)
>
> Not sure, it _could_ be that the Windows 3.6.1a does contain the fix for
this...
Just tried, nope, doesn't. But thanks for the reply! I'll just go ahead and
install 3.5 for further development and patiently (yeah, right, as if us
Povers are patient when it comes to getting a new version...) wait for the
next release with the bugfix. :-)
Regards,
Tim
--
"Tim Nikias v2.0"
Homepage: <http://www.nolights.de>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
BTW, does this bug stop *all* variables to be returned, or just a random
one? I can check for the first, but not the second via SDL, so I might
script a simple workaround into the system and just remove it when 3.6.2 is
out...
--
"Tim Nikias v2.0"
Homepage: <http://www.nolights.de>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Tim Nikias wrote:
> BTW, does this bug stop *all* variables to be returned, or just a random
> one? I can check for the first, but not the second via SDL, so I might
> script a simple workaround into the system and just remove it when 3.6.2 is
> out...
See my original post explaining the problem. You cannot just "script a
simple workaround" as the problem does *not* depend on what you do but when.
And you cannot changee the "when" in an easy to predict manner.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> > BTW, does this bug stop *all* variables to be returned, or just a random
> > one? I can check for the first, but not the second via SDL, so I might
> > script a simple workaround into the system and just remove it when 3.6.2
is
> > out...
>
> See my original post explaining the problem. You cannot just "script a
> simple workaround" as the problem does *not* depend on what you do but
when.
> And you cannot changee the "when" in an easy to predict manner.
Hm, yeah, just re-read it. Looks like potential Users of my System might
want to use 3.5 or wait for 3.6.2 (or 3.6.1b ;-)... Thanks for the help, its
appreciated!
Regards,
Tim
--
"Tim Nikias v2.0"
Homepage: <http://www.nolights.de>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sun, 6 Feb 2005 17:08:08 +0100, "Tim Nikias"
<JUSTTHELOWERCASE:timISNOTnikias(at)gmx.netWARE> wrote:
>Hm, yeah, just re-read it. Looks like potential Users of my System might
>want to use 3.5 or wait for 3.6.2 (or 3.6.1b ;-)... Thanks for the help, its
>appreciated!
Not too much of a problem for Moray users as we are waiting for a
version of Moray that works fully with Pov 3.6.
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
