|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> 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.
I'm used to getting a "thanks" only after finished work - I hope you don't
expect me to stop here and hand it over to anyone else 'cause I'd refuse to :)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
andrel <a_l### [at] hotmailcom> wrote:
> 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"
Now that you mention it - yes, sounds familiar :)
A former work colleague of mine used to equate the "P" in "ASAP" with "whenever
all the other work allows for it", i.e. "never" ;)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"clipka" <nomail@nomail> wrote:
> Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> > 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.
>
> I'm used to getting a "thanks" only after finished work - I hope you don't
> expect me to stop here and hand it over to anyone else 'cause I'd refuse to :)
What about "please"? Please, don't. :)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
stbenge wrote:
> Hmm, I got this to work for pvengine.exe , but not the sse2 version.
Not surprising; it must be at a completely different offset.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 03 Jan 2009 15:20:51 -0200, Nicolas Alvarez <nic### [at] gmailcom>
wrote:
>stbenge wrote:
>> Hmm, I got this to work for pvengine.exe , but not the sse2 version.
>
>Not surprising; it must be at a completely different offset.
The search string must have been the same as I got the sse2 version to work.
(after I saved the changes :) )
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 04-Jan-09 10:07, Stephen wrote:
> On Sat, 03 Jan 2009 15:20:51 -0200, Nicolas Alvarez <nic### [at] gmailcom>
> wrote:
>
>> stbenge wrote:
>>> Hmm, I got this to work for pvengine.exe , but not the sse2 version.
>> Not surprising; it must be at a completely different offset.
>
> The search string must have been the same as I got the sse2 version to work.
> (after I saved the changes :) )
>
I assume (but haven't checked) that it is a binary representation of the
date to compare with. Note that now we have beta binaries without
expiration floating on the internet and a recipe simple enough for a
script kiddie. I think Chris and the others would be grateful if you
destroy them after installing the new beta. If it happens again, perhaps
it would be advisable if you distribute the matching pattern by ordinary
email and not in one of the permanent newsgroups on the server?
This is exactly why I always tell sysops that you should never restrict
knowledgeable people when they want to do things that make their live
much more easy. Even if that might punch holes in the security if an
ordinary user does it. They'll do it anyway and if you don't have a good
relationship with them they might tell the other users how to do it too
and that is a much greater danger.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
stbenge wrote:
> but not the sse2 version. I'm not sure if I ever got a speed increase with that
anyway.
Having now downloaded POV.37.b.30 (the update which made the hex hack
obsolete), I can say with certainty that I get a speed boost of about
1.5x using the sse2 optimized version with my chipset(!). I take back my
previous statement, and I take it back with a smile :)
Sam
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"clipka" <nomail@nomail> wrote:
> .... I guess we *ALL* want a new beta *ASAP* now...!
I want it to come out of Beta... how long has it been now?
Or at least one that doesn't expire would be nice. What's the thinking behind
that, anyway?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
MGT Systems <nomail@nomail> wrote:
> What's the thinking behind that, anyway?
I wonder how many times this question has been asked, and always answered
the same way.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"MGT Systems" <nomail@nomail> wrote:
> I want it to come out of Beta... how long has it been now?
> Or at least one that doesn't expire would be nice. What's the thinking behind
> that, anyway?
As far as radiosity goes, it still needs some work to get back to release
quality:
- 100% reproducability of rendering output hasn't been achieved yet.
- Loading & saving of samples must be re-enabled.
- Radiosity internal parameters may still need some re-adjustment.
In addition, I want to get a good deal of improvement both regarding quality
(some of which has been achieved already, but there are still issues) and
performance (not much achieved here, despite promising approaches) before 3.7.0
gets released, because I fear it may be some time before we'd see a 3.7.1.
Other things still need some work, too. Caustics are still a problem, for
example. And there's a bump mapping issue that has been carried around probably
since the days of ancient Rome, which I hope someone will fix before the 3.7.0
release, because it requires some architectural change.
Regarding radiosity, I'd say two more months to go - if all runs smoothly. I've
made a lot of progress end of last year, but now RL is back on the scene again.
And even then, a lot of small details will still need cleaning up, and the
documentation has to be updated to include all the .ini parameter and SDL
language changes, possibly with a major edit of the radiosity-related portions.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |