 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have been trying out Moray for a couple of days now and I can't seem to be
able to import existing textures into the material editor. Is there some
kind of conversion package that will allow me to take .inc texture files and
put them into Moray's binary format? I've been pulling my hair out trying
to enter them manually and found that some stuff couldn't be done.
Thanks in advance,
Bob Ratliff
FireWeb Consulting
elm### [at] mrtc com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi Bob, you recently wrote in moray.win:
> Is there some kind of conversion package that
> will allow me to take .inc texture files and
> put them into Moray's binary format?
Nope, that is not available.
> I've been pulling my hair out trying to enter
> them manually and found that some stuff couldn't be done.
It should be fairly straightforward for most textures, though.
The only place you may experience difficulties is with
out of range values.
Maybe you can give an example of one that's caused a lot of
hair loss<g>.
- Lutz
email : lut### [at] stmuccom
Web : http://www.stmuc.com/moray
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Lutz Kretzschmar wrote:
> > I've been pulling my hair out trying to enter
> > them manually and found that some stuff couldn't be done.
> It should be fairly straightforward for most textures, though.
> The only place you may experience difficulties is with
> out of range values.
>
> Maybe you can give an example of one that's caused a lot of
> hair loss<g>.
Lutz,
I have, on several occassions, needed to use out of range values for
textures. Will we be able to do this sometime in Moray's future?
Also, on a simi-related topic...
Out of range RGB values for lights (& textures) aren't currently
supported either. I'm not sure why I would ever need negative RGB
values for textures, but I do use lights with negative values quite
often. It would be nice to be able to do this in Moray.
Currently, I have to add lights that represent my negative-RGB-value
lights, export my scene, open the file in POV & make my changes there.
Is there a way to make parts of my POV export file not get changed each
time that I send it for test renders - sort of like we can do with
textures?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Lutz Kretzschmar <lut### [at] stmuccom> wrote in message
news:37ac80eb.12898837@194.174.214.110...
> Hi Bob, you recently wrote in moray.win:
>
> > Is there some kind of conversion package that
> > will allow me to take .inc texture files and
> > put them into Moray's binary format?
> Nope, that is not available.
>
> > I've been pulling my hair out trying to enter
> > them manually and found that some stuff couldn't be done.
> It should be fairly straightforward for most textures, though.
> The only place you may experience difficulties is with
> out of range values.
One feature that I find lacking in Moray, is the ability to layer pigmenst
and normals, for some reason you are only allowed one of each.
--
T'vakah
----------------------------------------------------------------------------
--------------------------------------------------
A small project I am working on know:
http://backdoor.to/edertav/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Tony Vigil wrote:
> I have, on several occassions, needed to use out of range values for
> textures. Will we be able to do this sometime in Moray's future?
> ...
> Out of range RGB values for lights (& textures) aren't currently
> supported either. I'm not sure why I would ever need negative RGB
> values for textures, but I do use lights with negative values quite
> often. It would be nice to be able to do this in Moray.
Generally speaking, in Povray, the ability to overdrive values
(many kind of values : colors, lights, finishes...) is *absolutely
essential* to obtain a good color amplitude in images.
Fabien.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Lutz Kretzschmar <lut### [at] stmuccom> wrote in message
news:37ac80eb.12898837@194.174.214.110...
> Hi Bob, you recently wrote in moray.win:
>
> > Is there some kind of conversion package that
> > will allow me to take .inc texture files and
> > put them into Moray's binary format?
> Nope, that is not available.
>
> > I've been pulling my hair out trying to enter
> > them manually and found that some stuff couldn't be done.
> It should be fairly straightforward for most textures, though.
> The only place you may experience difficulties is with
> out of range values.
>
> Maybe you can give an example of one that's caused a lot of
> hair loss<g>.
>
> - Lutz
> email : lut### [at] stmuccom
> Web : http://www.stmuc.com/moray
Lutz,
I know now that some of the textures I want have already been converted.
Here is one the one that was driveing me to going bald ;)
//
// CJFAlabaster is similar to PinkAlabaster, the colours and the scale
// have been changed
//
#declare CJFAlabaster =
texture {
pigment {
bozo
turbulence 0.25
color_map {
[0, 1 color red 0.9 green 0.75 blue 0.75
color red 0.6 green 0.6 blue 0.6 ]
}
scale 1
}
finish { ambient 0.25 }
}
texture
pigment
granite
color_map {
[0, 0.9 color DarkOrchid filter 1 color DarkOrchid
filter 0.5]
[0.9, 1 color DarkSlateBlue color DarkSlateBlue]
}
scale 5 // Twice as large as unit shape
}
finish
specular 1
roughness 0.0001
phong 0.25
phong_size 75
brilliance 4
}
}
I found it in a MTX that someone posted on the net.
Thanks,
Bob Ratliff
FireWeb Consulting
elm### [at] mrtccom
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi Tony Vigil, you recently wrote in moray.win:
> I have, on several occassions, needed to use out of range values for
> textures. Will we be able to do this sometime in Moray's future?
Maybe. It's quite difficult to make it intuitive and easy to configure
the sliders. It wouldn't be much of a problem if I simply offered an
editbox.....
> Out of range RGB values for lights (& textures) aren't currently
> supported either.
Yes, they are. The 'M' slider for lights lets you use values outside
the 0 to 1.0 range (up to 10 fold per default, but you can use your
own ranges by tweaking values in the Registry),
For colors you can use Range button to set the ranges for the colors.
> Is there a way to make parts of my POV export file not get changed each
> time that I send it for test renders - sort of like we can do with
> textures?
Nope, only textures support this. What you can do is put those things
in an include file and add this include file to the
Scene|Settings|Include list.
- Lutz
email : lut### [at] stmuccom
Web : http://www.stmuc.com/moray
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi T'vakah, you recently wrote in moray.win:
> One feature that I find lacking in Moray, is the ability to layer pigmenst
> and normals, for some reason you are only allowed one of each.
Since you can't do that in POV-Ray either, what would be the point?
Unless you are talking about layering textures, then you are mistaken,
since Moray has supported this since V2.5 for DOS. In the Material
Editor, use Create and selecte 'Layered Texture'. Then add as many
texture layrers as you need.
- Lutz
email : lut### [at] stmuccom
Web : http://www.stmuc.com/moray
Post a reply to this message
|
|
| |
| |
|
|
From: Lutz Kretzschmar
Subject: Re: An easy way to import textures - Alabaster.mtx (0/1)
Date: 10 Aug 1999 03:44:25
Message: <37aecf50.75576@news.stmuc.com>
|
|
|
| |
| |
|
|
Hi Elminster, you recently wrote in moray.win:
> Here is one the one that was driveing me to going bald ;)
OK, here is the MTX that contains it. It seemed pretty simple, but
then I wrote the program<g>. It would help me if you could describe
what presented you with the biggest problem.
Note that the second layer is a bit strange in that it defines both
phong and specular in the finish.
- Lutz
email : lut### [at] stmuccom
Web : http://www.stmuc.com/moray
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Post a reply to this message
Attachments:
Download 'Alabaster.mtx.dat' (2 KB)
|
|
| |
| |
|
|
|
|
| |
