|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"SafePit" <ste### [at] reids4funcom> wrote:
> "clipka" <nomail@nomail> wrote:
> > .... I guess we *ALL* want a new beta *ASAP* now...!
>
> Ditto! Mine stopped completely and won't extend any more. I "really" don't
> want to go back to 3.6 on Vista -- pain in the butt. So far, I've been able to
> work around the minor differences in 3.7.
If you don't have the source code around to compile a newer version, then use a
hex editor to search for and change 60EB5B49 to something bigger, like FFFFFF7F
in pvengine.exe.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"nemesis" <nam### [at] gmailcom> wrote:
> clipka has the source and is working on improvements for radiosity. I don't
> think he meant he couldn't get around with the time limit, instead I'll take it
> he finally got to a turning point and is wanting us to test it! :D
Actually... both :)
Radiosity is getting better and better (I'm currently working on splotchy
stripes typically seen on cylinders, with promising results so far), so yes - I
think it's getting time to get it beta-tested :)
But although I personally don't have *any* significant problems getting around
that 2008-12-31 24:00 "self destruct", others probably do.
So it's a good time for a new beta, either way.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Random Coder" <nomail@nomail> wrote in message
news:web.495d23e2ea83a9b946e008d40@news.povray.org...
> "SafePit" <ste### [at] reids4funcom> wrote:
>> "clipka" <nomail@nomail> wrote:
>> > .... I guess we *ALL* want a new beta *ASAP* now...!
>>
>> Ditto! Mine stopped completely and won't extend any more. I "really"
>> don't
>> want to go back to 3.6 on Vista -- pain in the butt. So far, I've been
>> able to
>> work around the minor differences in 3.7.
>
> If you don't have the source code around to compile a newer version, then
> use a
> hex editor to search for and change 60EB5B49 to something bigger, like
> FFFFFF7F
> in pvengine.exe.
>
Thanks, That works for me (on pvengine-sse2.exe in my case).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka wrote:
> .... I guess we *ALL* want a new beta *ASAP* now...!
yup, apologies for the expiry. I'm on it now (on vacation and finally have
time to spend on POV exclusively). expect new beta ASAP, mainly to extend,
then further updates to fix bugs etc.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 02-Jan-09 21:08, Chris Cason wrote:
> clipka wrote:
>> .... I guess we *ALL* want a new beta *ASAP* now...!
>
> yup, apologies for the expiry. I'm on it now (on vacation and finally have
> time to spend on POV exclusively). expect new beta ASAP, mainly to extend,
> then further updates to fix bugs etc.
>
Hi Chris,
we have been missing your input in some of the discussions on radiosity.
Clipka has made some changes to the beta and he wants the group to test
them. You are the main one to decide if these changes can be
incorporated in a regular beta or if there is another way to do it that
is legally safe. From your reply I gather that they won't be in the next
beta, is that correct?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> yup, apologies for the expiry. I'm on it now (on vacation and finally have
> time to spend on POV exclusively). expect new beta ASAP, mainly to extend,
> then further updates to fix bugs etc.
That's good news - so the POV team is expecting so to speak, while we're in
expectation :)
You know that in companies I have worked for, "ASAP" invariably meant "yesterday
if possible, an hour ago otherwise"? ;)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Random Coder wrote:
> "SafePit" <ste### [at] reids4funcom> wrote:
>> "clipka" <nomail@nomail> wrote:
>>> .... I guess we *ALL* want a new beta *ASAP* now...!
>> Ditto! Mine stopped completely and won't extend any more. I "really" don't
>> want to go back to 3.6 on Vista -- pain in the butt. So far, I've been able to
>> work around the minor differences in 3.7.
>
> If you don't have the source code around to compile a newer version, then use a
> hex editor to search for and change 60EB5B49 to something bigger, like FFFFFF7F
> in pvengine.exe.
Hmm, I got this to work for pvengine.exe , but not the sse2 version. I'm
not sure if I ever got a speed increase with that anyway. thanks for this!
Sam
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
andrel wrote:
> Clipka has made some changes to the beta and he wants the group to test
> them. You are the main one to decide if these changes can be
> incorporated in a regular beta or if there is another way to do it that
> is legally safe. From your reply I gather that they won't be in the next
> beta, is that correct?
They won't be in what I release tonight, but you may expect several
releases over the next week (maybe formal betas, maybe just EXE's). either
way I will definitely be looking at his code.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
where I work, it means "last week" :} and is one of the primary reasons
I've been basically absent for the last few months. we had a big crunch on.
to complicate matters, since I last released any code, I have switched to a
new machine (skulltrail) which is running Vista, and getting everything re-
installed and working has taken waaaay too long. I have at this point yet
to do a full build/release on this hardware (worst case though I can fire
up the old machine).
NB thanks for your work on radiosity. I haven't caught up on it yet since
I've got a lot of newsgroup posts to read, but will try to do this as soon
as I've got the build done.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 03-Jan-09 4:59, clipka wrote:
> Chris Cason <del### [at] deletethistoopovrayorg> wrote:
>> yup, apologies for the expiry. I'm on it now (on vacation and finally have
>> time to spend on POV exclusively). expect new beta ASAP, mainly to extend,
>> then further updates to fix bugs etc.
>
> That's good news - so the POV team is expecting so to speak, while we're in
> expectation :)
>
> You know that in companies I have worked for, "ASAP" invariably meant "yesterday
> if possible, an hour ago otherwise"? ;)
>
There is a difference in "you'll do it ASAP" which means the above and
"I'll do it ASAP" where the interpretation depending on the cultural
context could mean from within an hour, to "whenever I feel like it" to
"if you want it done, do it yourself because I won't"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |