 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I love the Galaxy include file by Chris Colefax, but since 3.5 came out,
things don't render quite the same. With background nebulas, I
sometimes get a weird wiggly cut-off across the horizontal center of the
picture.
I've included an attachment to show what I mean. Has anyone else
noticed this, and possibly figured out a fix?
Post a reply to this message
Attachments:
Download 'galaxy_bug.jpg' (7 KB)
Preview of image 'galaxy_bug.jpg'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
It would appear that some pattern it used has not had a waveform
explicitly defined. As such it's using a sawtooth wave - which is what
you're seeing. That discontinuity is where the wave begins again.
I don't know these include files very well but I'd guess that somewhere
in one layer of the texture theres a marble pattenr used which needs to
be given the sine_wave modifier.
-Qfyd
Joe Moon wrote:
> I love the Galaxy include file by Chris Colefax, but since 3.5 came out,
> things don't render quite the same. With background nebulas, I
> sometimes get a weird wiggly cut-off across the horizontal center of the
> picture.
>
> I've included an attachment to show what I mean. Has anyone else
> noticed this, and possibly figured out a fix?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Joe Moon wrote:
> I love the Galaxy include file by Chris Colefax, but since 3.5 came out,
> things don't render quite the same. With background nebulas, I
> sometimes get a weird wiggly cut-off across the horizontal center of the
> picture.
>
> I've included an attachment to show what I mean. Has anyone else
> noticed this, and possibly figured out a fix?
It's due to the change in how the "gradient" function operates (from v3.1 to 3.5
I think, or was it 3.0 to 3.1?). Somewhere in the include/macro files, the
gradient function is used one or more times (I don't remember the specifics).
Find it(them) and change "gradient y" (or x or z) to "function { abs(y) }" (or x
or z).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> It's due to the change in how the "gradient" function operates (from v3.1
to 3.5
> I think, or was it 3.0 to 3.1?). Somewhere in the include/macro files, the
> gradient function is used one or more times (I don't remember the
specifics).
> Find it(them) and change "gradient y" (or x or z) to "function { abs(y) }"
(or x
> or z).
Crazy... I made almost the exact same post in povray.general. =)
Speaking of which, Joe, please don't multipost...
- Slime
[ http://www.slimeland.com/ ]
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Slime wrote:
>> It's due to the change in how the "gradient" function operates
>> (from v3.1
>
> to 3.5
>
>> I think, or was it 3.0 to 3.1?). Somewhere in the include/macro
>> files, the gradient function is used one or more times (I don't
>> remember the
>
> specifics).
>
>> Find it(them) and change "gradient y" (or x or z) to "function {
>> abs(y) }"
>
> (or x
>
>> or z).
>
> Crazy... I made almost the exact same post in povray.general. =)
>
> Speaking of which, Joe, please don't multipost...
>
> - Slime [ http://www.slimeland.com/ ]
That seems to have done the trick, though I think there are still subtle
differences in the results of the Galaxy include since 3.1.
Sorry for the cross-post - first time in these newsgroups, and there's
just so darn many, I wasn't sure where to go. So I'll just thank
everyone on this thread :)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
