 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
First, I was fairly sure that *someplace* there was a utility for
creating POVRay textures around, which wasn't a) shareware and b) didn't
rely in POVRay to render the texture. Am I wrong? Its just that having
to render every time to see what the changes you make are going to look
like is a serious pain, especially if you have to use some clunky
interface, like the shareware TXMag to do it. I have something I want to
do and need a simple, clear, and easily tweakable method to match
existing textures, without having to use something that generates a
tillable image, instead of a native texture. Nothing "recent" seems to
do this.
Second, I need to make something that looks a bit like an 8 sided D&D
dice. The plan is to texture it using one of the matched textures, add
some metal bits too it that match others, carve into it some symbols,
some of them also matched to textures from a game, then have the whole
thing floating and slowly rotating on the Guild webpage. I really am not
in the mood to try to code the textures, or the object, manually using a
mess of CSG chopping, but I have only fiddled now and them with the
program, so maybe I need to post on like "intermediate" instead (if we
had such a place). lol
Seriously, this is *one* thing that having the license change will help
with. Right now you can't yank out the code that handles some of this
stuff and really make utilities that *use* that code to produce simple
editors, which also support the full capability of the engine. And some
of those, for textures, or even media, would be very nice to have, so
you can tweak settings and see what will happen *before* having to
render some complex scene to see the result.
Oh, and one thought on someone's mentioning DKBTrace. The only advantage
I could see with it is that it has enough similar syntax that you
*could* maybe run it on low power, low memory, systems, like Palm
Pilots, where I don't imagine managing to get POVRay onto one of them,
or at least have it run at all, even if you could. Its unfortunate that
the same issue exists for its code as did for POVRay. :(
--
void main () {
If Schrödingers_cat is alive or version > 98 {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Patrick Elliott nous apporta ses lumieres en ce 2008/02/19 22:57:
> First, I was fairly sure that *someplace* there was a utility for
> creating POVRay textures around, which wasn't a) shareware and b) didn't
> rely in POVRay to render the texture. Am I wrong? Its just that having
> to render every time to see what the changes you make are going to look
> like is a serious pain, especially if you have to use some clunky
> interface, like the shareware TXMag to do it. I have something I want to
> do and need a simple, clear, and easily tweakable method to match
> existing textures, without having to use something that generates a
> tillable image, instead of a native texture. Nothing "recent" seems to
> do this.
Whenever you render any texture with any other application, the end result will
be different. Simply put, the other application don't have the same algorythm to
generate it's textures.
>
> Second, I need to make something that looks a bit like an 8 sided D&D
> dice. The plan is to texture it using one of the matched textures, add
> some metal bits too it that match others, carve into it some symbols,
> some of them also matched to textures from a game, then have the whole
> thing floating and slowly rotating on the Guild webpage. I really am not
> in the mood to try to code the textures, or the object, manually using a
> mess of CSG chopping, but I have only fiddled now and them with the
> program, so maybe I need to post on like "intermediate" instead (if we
> had such a place). lol
>
> Seriously, this is *one* thing that having the license change will help
> with. Right now you can't yank out the code that handles some of this
> stuff and really make utilities that *use* that code to produce simple
> editors, which also support the full capability of the engine. And some
> of those, for textures, or even media, would be very nice to have, so
> you can tweak settings and see what will happen *before* having to
> render some complex scene to see the result.
>
> Oh, and one thought on someone's mentioning DKBTrace. The only advantage
> I could see with it is that it has enough similar syntax that you
> *could* maybe run it on low power, low memory, systems, like Palm
> Pilots, where I don't imagine managing to get POVRay onto one of them,
> or at least have it run at all, even if you could. Its unfortunate that
> the same issue exists for its code as did for POVRay. :(
>
You can create a very simple test scene with 2, 3 or 4 box and apply your
textures to those boxes. Such a test scene renders prety quickly and allow you
to compare several textures side by side. That's usualy the technic I use.
There are other applications that enable you to do texture tweaking, but the end
result can't be guaranteed in all cases. You can only be confident about the
result if you use plain pigments. Anytime you have any reflection or
transparency, the end result will depend on the environment.
--
Alain
-------------------------------------------------
You know you've been raytracing too long when you've gained twenty pounds
sitting at the computer, but can't tell because your beard covers your stomach.
Taps a.k.a. Tapio Vocadlo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Patrick Elliott wrote:
> Oh, and one thought on someone's mentioning DKBTrace. The only advantage
> I could see with it is that it has enough similar syntax that you
> *could* maybe run it on low power, low memory, systems, like Palm
> Pilots, where I don't imagine managing to get POVRay onto one of them,
> or at least have it run at all, even if you could. Its unfortunate that
> the same issue exists for its code as did for POVRay. :(
why would someone in their right mind want to render stuff in
underpowered hardware?! We should all be wanting more, not less!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alain wrote:
> Whenever you render any texture with any other application, the end
> result will be different. Simply put, the other application don't have
> the same algorythm to generate it's textures.
It would render the same if it was compiled using POV source. Seems like
a waste of time, though, considering the fact that an orthographic POV
scene works just fine for this kind of thing.
Sam
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <47bc9b41@news.povray.org>, stb### [at] hotmail com says...
> Alain wrote:
> > Whenever you render any texture with any other application, the end
> > result will be different. Simply put, the other application don't have
> > the same algorythm to generate it's textures.
>
> It would render the same if it was compiled using POV source. Seems like
> a waste of time, though, considering the fact that an orthographic POV
> scene works just fine for this kind of thing.
>
> Sam
>
Well, I think you are missing the point. Most programs now have a way to
create textures to be applied to objects, such that the algorithms are
the same and you don't need to render. The purpose being to allow you to
play with them, until you get what you want, not set X, render, set Y,
render, decide X isn't right, change it and add Z, render, etc. You get
to determine the texture in real time. The problem being not just that
other programs don't use the same algorithms, they don't even use the
same methods, and nearly all of them generate an image, not a texture
definition.
Sure, if you are used to doing it the hard way, and you have a clear
idea what effects you will get, it works OK to throw 3-4 things
together, render, then tweak. Its useless if you only have the vaguest
clue what you are trying for, no idea if that *is* what you really want
to do, and you don't want to have to run another program every time to
see what you end up with (especially given how broken that is at the
moment for say the recent versions and Moray).
--
void main () {
If Schrödingers_cat is alive or version > 98 {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <47bc5412@news.povray.org>, nam### [at] nospamgmailcom
says...
> Patrick Elliott wrote:
> > Oh, and one thought on someone's mentioning DKBTrace. The only advantag
e
> > I could see with it is that it has enough similar syntax that you
> > *could* maybe run it on low power, low memory, systems, like Palm
> > Pilots, where I don't imagine managing to get POVRay onto one of them,
> > or at least have it run at all, even if you could. Its unfortunate that
> > the same issue exists for its code as did for POVRay. :(
>
> why would someone in their right mind want to render stuff in
> underpowered hardware?! We should all be wanting more, not less!
>
Well, if that is all you have to work with... I mean, what else am I
supposed to do during my lunch breaks, read? lol
--
void main () {
If Schrödingers_cat is alive or version > 98 {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <47bc4d81$1@news.povray.org>, ele### [at] netscapenet
says...
> > Second, I need to make something that looks a bit like an 8 sided D&D
> > dice. The plan is to texture it using one of the matched textures, add
> > some metal bits too it that match others, carve into it some symbols,
> > some of them also matched to textures from a game, then have the whole
> > thing floating and slowly rotating on the Guild webpage. I really am no
t
> > in the mood to try to code the textures, or the object, manually using
a
> > mess of CSG chopping, but I have only fiddled now and them with the
> > program, so maybe I need to post on like "intermediate" instead (if we
> > had such a place). lol
> >
Oh, and BTW, thanks for the total lack of advice on the one thing that
is *more* critical to what I am attempting than the textures, which I
could tweak from the standard set, if necessary. :p
--
void main () {
If Schrödingers_cat is alive or version > 98 {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Patrick Elliott" <sel### [at] rraznet> wrote in message
> Oh, and BTW, thanks for the total lack of advice on the one thing that
> is *more* critical to what I am attempting than the textures, which I
> could tweak from the standard set, if necessary. :p
Have you looked at the Material Editor in Moray which claims that it
"supports (almost) all POV-Ray 3.5 texturing features, even including
advanced features like media, interior, density, warps, slopemaps and
texturemaps. The colormap allows you to build complex colormaps in realtime.
And you can preview your textures (or subtextures) at any time. POV-Ray will
render a thumbnail into the Material Editor. While POV-Ray renders you can
continue editing the material in Moray."
See http://www.stmuc.com/moray/ for a screenshot.
Regards,
Chris B.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Patrick Elliott nous apporta ses lumieres en ce 2008/02/20 22:19:
> In article <47bc5412@news.povray.org>, nam### [at] nospamgmailcom
> says...
>> Patrick Elliott wrote:
>>> Oh, and one thought on someone's mentioning DKBTrace. The only advantage
>>> I could see with it is that it has enough similar syntax that you
>>> *could* maybe run it on low power, low memory, systems, like Palm
>>> Pilots, where I don't imagine managing to get POVRay onto one of them,
>>> or at least have it run at all, even if you could. Its unfortunate that
>>> the same issue exists for its code as did for POVRay. :(
>> why would someone in their right mind want to render stuff in
>> underpowered hardware?! We should all be wanting more, not less!
>>
> Well, if that is all you have to work with... I mean, what else am I
> supposed to do during my lunch breaks, read? lol
>
On a palm... maybe withess the completion of 1 line... possibly 2 or 3 for a
prety simple scene.
Read? Why not? You could read the POV-Ray's documentations ;-) or this news group.
--
Alain
-------------------------------------------------
You know you've been raytracing too long when you've gained twenty pounds
sitting at the computer, but can't tell because your beard covers your stomach.
Taps a.k.a. Tapio Vocadlo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> to render every time to see what the changes you make are going to look
> like is a serious pain
> I have something I want to
> do and need a simple, clear, and easily tweakable method to match
> existing textures, without having to use something that generates a
> tillable image, instead of a native texture. Nothing "recent" seems to
> do this.
> you can tweak settings and see what will happen *before* having to
> render some complex scene to see the result.
> Sure, if you are used to doing it the hard way, and you have a clear
> idea what effects you will get, it works OK to throw 3-4 things
> together, render, then tweak. Its useless if you only have the vaguest
> clue what you are trying for
To avoid rendering a complex scene just to test a texture, what about making a
simple texture test scene in POV-Ray SDL? The incdemo files bundled with
POV-Ray illustrates this in a much better way, even with animation.
But perhaps this small example is something you could use? It allows for testing
of to different variables at the same time. Render the scene, pick the values
you like and insert them in the code. Then continue with two other variables.
This should help you to narrow down the effect you like in a rather short time.
As your experience increases you will need fewer and fewer tries to get what you
want ;)
Good luck!
-Peter
// +h1000 +w1000 +a0.3
camera{
orthographic
location z*-10 look_at 0 angle 60
right x up y
}
light_source{<5,5,-20>,1}
#local Space = 0.1;
#local X = 0;
#while (X <= 1)
#local Y = 0;
#while (Y <= 1)
#local Location = <-5+X*10,-5+Y*10,0>;
sphere{0,Space*4
texture{
pigment {rgb 1}
finish {phong X}
normal{granite Y}
}
translate Location
}
text{ttf "arial.ttf"
concat("X: ",str(X,3,1), " Y: ",str(Y,3,1)) 1,0
pigment {rgb y*1}
scale Space translate Location-Space*<3,5,0>
}
#local Y = Y+Space;
#end
#local X = X+Space;
#end
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <47bd4fd7$1@news.povray.org>, nom### [at] nomailcom says...
>
> "Patrick Elliott" <sel### [at] rraznet> wrote in message
> > Oh, and BTW, thanks for the total lack of advice on the one thing that
> > is *more* critical to what I am attempting than the textures, which I
> > could tweak from the standard set, if necessary. :p
>
Real time as in "real time preview", which it doesn't do. Also, I found
the octahedron I needed, which I guess will work, since I plan to line
the edges, maybe. If I don't, then I am back where I started, needing an
octahedron that has rounded edges (a blob might work, if I can figure it
out, since that also would allow me to make it slightly more real, by
being not 100% symetrical). *That* is the "critical" thing I was trying
to find a simple solution for. The textures, as I said, I can adapt from
existing ones, though not being able to "immediately" see the change,
the way one could with most other programs, makes it a bit harder.
BTW, how do people get 3.5 and 3.6 on the same system? I have the later,
and obviously support for Moray in the later is rather seriously
broken...
--
void main () {
If Schrödingers_cat is alive or version > 98 {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.47bdcc0fef771f4c5116a38d0@news.povray.org>,
peter@**nospam**hertel.no says...
> > to render every time to see what the changes you make are going to look
> > like is a serious pain
> > I have something I want to
> > do and need a simple, clear, and easily tweakable method to match
> > existing textures, without having to use something that generates a
> > tillable image, instead of a native texture. Nothing "recent" seems to
> > do this.
>
> > you can tweak settings and see what will happen *before* having to
> > render some complex scene to see the result.
>
> > Sure, if you are used to doing it the hard way, and you have a clear
> > idea what effects you will get, it works OK to throw 3-4 things
> > together, render, then tweak. Its useless if you only have the vaguest
> > clue what you are trying for
>
> To avoid rendering a complex scene just to test a texture, what about mak
ing a
> simple texture test scene in POV-Ray SDL? The incdemo files bundled with
> POV-Ray illustrates this in a much better way, even with animation.
>
> But perhaps this small example is something you could use? It allows for
testing
> of to different variables at the same time. Render the scene, pick the va
lues
> you like and insert them in the code. Then continue with two other variab
les.
> This should help you to narrow down the effect you like in a rather short
time.
> As your experience increases you will need fewer and fewer tries to get w
hat you
> want ;)
>
> Good luck!
>
> -Peter
>
> // +h1000 +w1000 +a0.3
>
> camera{
> orthographic
> location z*-10 look_at 0 angle 60
> right x up y
> }
>
> light_source{<5,5,-20>,1}
>
> #local Space = 0.1;
>
> #local X = 0;
> #while (X <= 1)
> #local Y = 0;
> #while (Y <= 1)
> #local Location = <-5+X*10,-5+Y*10,0>;
>
> sphere{0,Space*4
> texture{
> pigment {rgb 1}
> finish {phong X}
> normal{granite Y}
> }
> translate Location
> }
>
> text{ttf "arial.ttf"
> concat("X: ",str(X,3,1), " Y: ",str(Y,3,1)) 1,0
> pigment {rgb y*1}
> scale Space translate Location-Space*<3,5,0>
> }
> #local Y = Y+Space;
> #end
> #local X = X+Space;
> #end
>
Umm, because that still means I have to hit render? lol
Mind, its not a bad idea and certainly one I hadn't considered. Now,
there are 1-2 on the utility page for POVRay that *do* this, but they do
so in a way that isn't transferable to POVRay code. In other words, they
do so by generating an image, not a texture SDL.
Lets put it this way. Open PSP X or Photoshop, go to something like (in
PSP) Effects->Distortion->Warp, then **see** it actually doing it in the
preview. This is quite different than manually changing lines of code,
or even tweaking a setting as in Moray, TXMag, or others, then having to
hit "run" (or preview, which is fundamentally the same thing). Its also
nicer than your solution even, since once you think you have one thing
right, you can just move on to tweak the other variables. Yours.. You
have to plug in the ones you had right, then run it again, with
different variances. Kind of annoying, even if it is feasible.
Ok, being a bit nit picky maybe, but seriously, this is one of those
things that most frontends for other engines "will" do. That you can't
even find a stand alone utility to do it for POVRay is imho, not a good
thing when you want people to consider using it, instead of one of those
fancy smancy ones that *do*. And, sometimes it just nice to be able to
do that, especially when you don't want to spend a lot of time fiddling,
even if you know how to do it the hard way. ;)
--
void main () {
If Schrödingers_cat is alive or version > 98 {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Patrick Elliott wrote:
> BTW, how do people get 3.5 and 3.6 on the same system? I have the later,
> and obviously support for Moray in the later is rather seriously
> broken...
Why do you conclude that it is POV-Ray 3.6 that breaks Moray and not the
other way around?
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Patrick Elliott <sel### [at] rraznet> wrote:
<snip>
> This is quite different than manually changing lines of code,
<snip>
> have to plug in the ones you had right, then run it again, with
> different variances. Kind of annoying, even if it is feasible.
<snip>
> especially when you don't want to spend a lot of time fiddling,
<snip>
Well.. It's hard to explain, but I belive those points are one of the main
reasons why I like POV-Ray so much. A little tweaking here, and a little there,
full control over what happens in your scene (hopefully ;) and you get what you
want in the end.
> having to hit "run"
If you don't like clicking "Run" you can press Alt+G, I find it saves a lot of
time while tweaking ;)
Try out Jpatch - http://www.jpatch.com/ - It has a very nice material editor
with a lot of sliders for pigment and finish which puts out pure, clean POV-Ray
code.
KPovModeler might also be an alternative if you run Linux, -
http://www.kpovmodeler.org/
Or you could use the provided code to do a real time preview in POV-Ray. Sorry,
I couldn't resist. :P
Jokes aside, I trie to quickly put togehter that dice you wanted, but it turned
out to be a bit harder to make it with rounded corners than I thought. It was
easy making it in Wings 3D and uv mapping it though ;)
-Peter
// POV-Ray does REAL TIME TEXTURE PREVIEW!!
// (Requires POV-Ray 3.7 beta)
// Command line options:
// +kla +rtr +w160 +h120 -a
#local SPC = 0.01; // [0.001-1] lower makes more spheres
#local Fancy_Stuff = off; // Turn impractical eye candy on or off
#local Use_Hdr = off; // Requires hdr_env.hdr from megapov present
#local Translate = 4/SPC;
#local Cam = 0;
#while (Cam <=1)
camera{
location z*-10 look_at 0 angle 25 translate x*Cam*Translate
}
#local Cam = Cam+SPC;
#end
light_source{<Translate/3,Translate*0.1,-Translate*1.5>,1}
#local X = 0;
#while (X <= 1)
sphere{0,1
no_shadow
pigment {rgb <1,0.6,0.5>}
normal {granite 0.6 scale 5 turbulence X}
finish {phong 0.2 specular 0.4 reflection 0.2*Fancy_Stuff}
rotate X*360*Fancy_Stuff
translate x*X*Translate
}
text{ttf "arial.ttf"
concat("Value: ",str(X,3,3)),0.1,0
pigment {rgb y*1+<0.3,0,1>*Fancy_Stuff}
finish {reflection Fancy_Stuff*0.2}
rotate <sin(X*pi)*50,sin(X*pi)*30,0>*Fancy_Stuff
scale 0.5 translate <-1.33,-1.5+Fancy_Stuff*0.1,0>
translate x*X*Translate
}
#local X = X+SPC;
#end
#if(Fancy_Stuff & Use_Hdr)
sphere {
0,1
pigment { image_map { hdr "hdr_env.hdr" once interpolate 2 map_type 1 } }
finish { ambient 0.8 diffuse 0 }
scale <-1,1,1>*Translate*2
hollow
}
#end
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Patrick Elliott <sel### [at] rraznet> wrote:
> Second, I need to make something that looks a bit like an 8 sided D&D
> dice. The plan is to texture it using one of the matched textures, add
> some metal bits too it that match others, carve into it some symbols,
> some of them also matched to textures from a game, then have the whole
> thing floating and slowly rotating on the Guild webpage. I really am not
> in the mood to try to code the textures, or the object, manually using a
> mess of CSG chopping
The six vertices are x,y,z,-x,-y,-z, possibly scaled by something.
If you want rounded edges, say with radius R,
then put spheres with radius R at each vertex, a cylinder with radius
R at each edge (or, to save code, a spheresweep
x y (-x) (-y) x z y (-z) (-y) z (-x) (-z) x )
displace the triangle with vertices a,b,c by (a+b+c)*R/sqrt(3) (for
all applicable values of a b and c).
This assumes, that you do not need a solid die, i.e. your textures are
not transparent.
> but I have only fiddled now and them with the
> program, so maybe I need to post on like "intermediate" instead (if we
> had such a place). lol
I believe there is povray.general
Mark Weyer
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <47be631e@news.povray.org>, tho### [at] trfde says...
> Patrick Elliott wrote:
> > BTW, how do people get 3.5 and 3.6 on the same system? I have the later
,
> > and obviously support for Moray in the later is rather seriously
> > broken...
>
> Why do you conclude that it is POV-Ray 3.6 that breaks Moray and not the
> other way around?
>
Just a matter of convention. Its fairly irrelevant which one breaks
which, since it just doesn't work.
--
void main () {
If Schrödingers_cat is alive or version > 98 {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.47be68d3ef771f4c5116a38d0@news.povray.org>,
peter@**nospam**hertel.no says...
> Try out Jpatch - http://www.jpatch.com/ - It has a very nice material edi
tor
> with a lot of sliders for pigment and finish which puts out pure, clean P
OV-Ray
> code.
>
Thanks, will take a look. That may have even been what I was thinking
of, though it might have been the **much** earlier cmapper and crender,
which I 'thought' had at one point been combined into something more
useful. By themselves, they are not too useful, since you can preview
modifiers in one of them, but not what it does to complex textures,
while the other lets you create the banding for one, but not *see* what
the actual result will be. Not too helpful. lol
> Or you could use the provided code to do a real time preview in POV-Ray.
Sorry,
> I couldn't resist. :P
> Jokes aside, I trie to quickly put togehter that dice you wanted, but it
turned
> out to be a bit harder to make it with rounded corners than I thought. It
was
> easy making it in Wings 3D and uv mapping it though ;)
>
> -Peter
Yeah, figured it would be complicated. Nearest idea I could come up with
was using cylinders and the blob primitive, but I am not even sure how
well that would work. It would allow adding minor components in, to make
the surface less perfect, but it might just be easier to build a
cylinder+sphere cage, then glue stuff in between the fill in. :p Or, I
could just place metal plates along the edges, instead of only having
caps on the top and bottom. Not sure yet. The one has the advantage of
looking more like its carved from "real" polished ore, while the other
would be more manufactured looking. Its a hard call.
--
void main () {
If Schrödingers_cat is alive or version > 98 {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.47be7ffcef771f4cfddaa4670@news.povray.org>,
nomail@nomail says...
> Patrick Elliott <sel### [at] rraznet> wrote:
>
> > Second, I need to make something that looks a bit like an 8 sided D&D
> > dice. The plan is to texture it using one of the matched textures, add
> > some metal bits too it that match others, carve into it some symbols,
> > some of them also matched to textures from a game, then have the whole
> > thing floating and slowly rotating on the Guild webpage. I really am no
t
> > in the mood to try to code the textures, or the object, manually using
a
> > mess of CSG chopping
>
> The six vertices are x,y,z,-x,-y,-z, possibly scaled by something.
> If you want rounded edges, say with radius R,
> then put spheres with radius R at each vertex, a cylinder with radius
> R at each edge (or, to save code, a spheresweep
> x y (-x) (-y) x z y (-z) (-y) z (-x) (-z) x )
> displace the triangle with vertices a,b,c by (a+b+c)*R/sqrt(3) (for
> all applicable values of a b and c).
> This assumes, that you do not need a solid die, i.e. your textures are
> not transparent.
>
Got to be solid, or at least mostly. I need to cave in a set of symbols,
and lettering. Basically... A broken moon on two top faces, with red
between the fragments, three shooting star like objects on the other two
tops, also red. These would us a molten texture with a displacement of
the wave pattern that matches the rotation of the object, so it pulses
as it rotates (though whether faster or slower... I haven't decided).
Guild cloak is green with red symbols (the falling stars), so I need
forest green on it too. That would be lettering, possible along the
edges, and on the bottom, in some EQ2 sort of language (Kerra, assuming
there is such a character set they use. Hard to tell, since I started at
one myself). Those also will have the molten glow effect. The main
surface is a pinkish color, almost flesh tone, while other parts are
various metallics, of the refined versions, or the grey speckle of the
"etched Acrylia" you could pick up in the old EQ1. The whole thing will
be floating over a stand on the floor, and slowly spinning.
Basically, the guild name is Shards of Luclin. Luclin being the moon
that the city of the Vah Shir (Luclin's Kerra) stood on, before the moon
exploded in between EQ1 and EQ2. The textures are all from the material
"Acrylia" that 90% of the armor that you crafted there was based on.
No idea what I will do with the rest of the room yet, but I wish there
was some way to get a better look at ingame textures on items like the
Shade Silk cloaks and stuff, so I could see if they where unique enough
to try to duplicate them for tapestries or something. This 8 sided thing
is just step one. lol
Am I crazy wanting to do this for a web page, or just overly bored?
--
void main () {
If Schrödingers_cat is alive or version > 98 {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <MPG.2229049a9aceccf798a105@news.povray.org>,
sel### [at] rraznet says...
> In article <web.47be68d3ef771f4c5116a38d0@news.povray.org>,
> peter@**nospam**hertel.no says...
> > Try out Jpatch - http://www.jpatch.com/ - It has a very nice material e
ditor
> > with a lot of sliders for pigment and finish which puts out pure, clean
POV-Ray
> > code.
> >
> Thanks, will take a look. That may have even been what I was thinking
> of, though it might have been the **much** earlier cmapper and crender,
> which I 'thought' had at one point been combined into something more
> useful. By themselves, they are not too useful, since you can preview
> modifiers in one of them, but not what it does to complex textures,
> while the other lets you create the banding for one, but not *see* what
> the actual result will be. Not too helpful. lol
>
Latest version, I think, doesn't seem to allow color maps, effects on
those maps, and some of the basic controls, in the modeler part,
themselves didn't work for me.. Basically, its texture system is what
crender did. Settings for basics, like transparencies, metallic
finishes, phong, etc, but no way to do what I need, which is play with
banding and the like. Guess I am going to have to go with the hard way
at this point. Almost as much of a pain in the ass as finding out that I
need the "raw" unpatched EQ1 Titanium to log into the emulation server
(s), so I can look around for textures and stuff to use in other parts.
I ain't paying Sony more money to log into that again, just to get
screenshots for design ideas... :(
--
void main () {
If Schrödingers_cat is alive or version > 98 {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> > The six vertices are x,y,z,-x,-y,-z, possibly scaled by something.
> > If you want rounded edges, say with radius R,
> > then put spheres with radius R at each vertex, a cylinder with radius
> > R at each edge (or, to save code, a spheresweep
> > x y (-x) (-y) x z y (-z) (-y) z (-x) (-z) x )
> > displace the triangle with vertices a,b,c by (a+b+c)*R/sqrt(3) (for
> > all applicable values of a b and c).
> > This assumes, that you do not need a solid die, i.e. your textures are
> > not transparent.
>
> Got to be solid, or at least mostly. I need to cave in a set of symbols,
> and lettering.
In that case replace the triangles with something solid.
The easiest would be an eight of an octahedron: For the triangle with
vertices a, b, and c this would be
intersection {
plane { -a 0 } plane { -b 0 } plane { -c 0 }
plane { a+b+c 1/sqrt(3) }
translate (a+b+c)*R/sqrt(3)
}
Keep in mind, though, that carved dice are not considered fair.
Best,
Mark Weyer
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.47c2d45def771f4cfddaa4670@news.povray.org>,
nomail@nomail says...
>
> > > The six vertices are x,y,z,-x,-y,-z, possibly scaled by something.
> > > If you want rounded edges, say with radius R,
> > > then put spheres with radius R at each vertex, a cylinder with radius
> > > R at each edge (or, to save code, a spheresweep
> > > x y (-x) (-y) x z y (-z) (-y) z (-x) (-z) x )
> > > displace the triangle with vertices a,b,c by (a+b+c)*R/sqrt(3) (for
> > > all applicable values of a b and c).
> > > This assumes, that you do not need a solid die, i.e. your textures ar
e
> > > not transparent.
> >
> > Got to be solid, or at least mostly. I need to cave in a set of symbols
,
> > and lettering.
>
> In that case replace the triangles with something solid.
> The easiest would be an eight of an octahedron: For the triangle with
> vertices a, b, and c this would be
>
> intersection {
> plane { -a 0 } plane { -b 0 } plane { -c 0 }
> plane { a+b+c 1/sqrt(3) }
> translate (a+b+c)*R/sqrt(3)
> }
>
> Keep in mind, though, that carved dice are not considered fair.
>
> Best,
>
> Mark Weyer
>
Decided to use the one in shapes2.inc and just scale it, thought that
means, at some point, lopping edges off and replacing them with
cylinders, etc, to round it. Got a different problem though. The
texture... So far I have this, which I am not real satisfied with:
texture {
pigment {marble
turbulence 0.85
color_map {
[0.00 0.40 color rgb <0.66275,0.57647,0.58824>
color rgb <0.65882,0.56078,0.57255>]
[0.40 0.72 color rgb <0.64275,0.55647,0.56824>
color rgb <0.63882,0.54078,0.55255>]
[0.72 0.95 color rgb <0.62275,0.53647,0.54824>
color rgb <0.61882,0.52078,0.53255>]
[0.95 1.00 color rgb <0.57775,0.49147,0.50324>
color rgb <0.57382,0.47578,0.48755>]
}
}
What I am trying to do is duplicate the colors in this:
http://everquest.allakhazam.com/pgfx/item_1138.png
but looking more like:
http://everquest.allakhazam.com/pgfx/item_1095.png
Though, in fact, I plan to use "both" color sets for different parts of
the item I am building. And, since this is going to be a *large* object,
I want to make at least one band in it so that, instead of having the
reflective qualities of polished stone, it has granular crystal like
veins, which have a metallic finish. So, what I am looking for is
something like:
texture {
pigment {marble
turbulence 0.85
color_map {
[0.00 0.40 color rgb <0.66275,0.57647,0.58824>
color rgb <0.65882,0.56078,0.57255>]
[0.40 0.72 color rgb <0.64275,0.55647,0.56824>
color rgb <0.63882,0.54078,0.55255>]
[0.72 0.95 color rgb <0.62275,0.53647,0.54824>
color rgb <0.61882,0.52078,0.53255>]
[0.95 1.00 color rgbt <1,1,1>
color rgbt <1,1,1>]
}
finish { stuff to make it polished stone }
}
texture {
pigment {marble
turbulence 0.85
crinkle
color_map {
[0.00 0.95 color rgb <1,1,1>
color rgb <1,1,1>]
//Darkened to enhance the vein like appearance.
[0.95 1.00 color rgb <0.47775,0.39147,0.40324>
color rgb <0.47382,0.37578,0.38755>]
}
finish { stuff to make it metallic }
}
Right? Can just try it, but wouldn't mind some input on how to get the
texture itself a bit closer to what I want as well.
--
void main () {
If Schrödingers_cat is alive or version > 98 {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
