After you have loaded the .udo in Moray, try using the texture editor to
create a new texture. Create a pigment inside the texture, then select
"image_map" for the type of pigment. There should be a little button that
will let you browse to find your .png map image. After you've done that,
then use the "Assign" button to give your object that texture. Let me know
how you make out in any case!

> I'll try it all again tonight. I'm looking forward to getting back to
actual
> modelling and rendering and not just fiddling with file formats and
converters
> which I seem to have been doing for way too long!

I know exactly what you mean! I went through the same thing the first time I
tried the new uv mapped texture.

> If this works out then the "only" outstanding problem (other than the
> clumsiness of the whole process (Poser, Moray, POV, Poser2POV, UVmapper,
> Paintshop pro) thats 6 programs!) is that the UDO is a single mesh. Means
that

Now you know one reason why so many people use only the scripting language
and no modeler. I do really like using modelers (esp. NURBS) but I spend
alot more time dinking around with the pov script than anything else.

HH

Post a reply to this message

Halbert,

Many thanks for your advice. I know how to make an image map as a texture... I'm
just flummoxed when it doesn't come out as expected - part of not knowing enough
about POV scripts.

Anyway, in this image of mine the rug on the floor is an image map:

http://www.renderosity.com/viewed.ez?galleryid=13908&Start=1&Sectionid=0&Form.Search=Rhialto

And the reason I want Poser figures is to populate this scene:

http://www.renderosity.com/viewed.ez?galleryid=15109&Start=1&Sectionid=0&Form.Search=Rhialto

Yes, these figures are cheats from the ray-tracing point of view in that the sky
in the latter picture and the image in the mirror in the former is a Terragen
creation. I've just discovered the sky and clouds in POV tutorials though, so
some day....

Simon (Rhialto)


Halbert wrote:

> After you have loaded the .udo in Moray, try using the texture editor to
> create a new texture. Create a pigment inside the texture, then select
> "image_map" for the type of pigment. There should be a little button that
> will let you browse to find your .png map image. After you've done that,
> then use the "Assign" button to give your object that texture. Let me know
> how you make out in any case!
>
> > I'll try it all again tonight. I'm looking forward to getting back to
> actual
> > modelling and rendering and not just fiddling with file formats and
> converters
> > which I seem to have been doing for way too long!
>
> I know exactly what you mean! I went through the same thing the first time I
> tried the new uv mapped texture.
>
> > If this works out then the "only" outstanding problem (other than the
> > clumsiness of the whole process (Poser, Moray, POV, Poser2POV, UVmapper,
> > Paintshop pro) thats 6 programs!) is that the UDO is a single mesh. Means
> that
>
> Now you know one reason why so many people use only the scripting language
> and no modeler. I do really like using modelers (esp. NURBS) but I spend
> alot more time dinking around with the pov script than anything else.
>
> HH

Post a reply to this message

Sorry for going into too much detail; I wasn't sure how much you've worked
with Moray and POV.
Yes, I think that scene would look good with some people. I think it would
be cool to put the people in the reflection, is that what you are planning?
You should post it in p.b.i. when you get it where you want it.
Actually, it already looks pretty good. :-)
HH

Post a reply to this message

Peter Popov wrote in message ...
>Try restoring the maximized render window, your render is too small
>conpared to the window size and Windows can't manage the zoom factor.
>At least that's what my experience tells me about this error.


My experience with rendering on Windows NT is that this error is
semi-random.  It will usually not occur the first time you render an image
at a given resolution, and usually reducing the render resolution will
temporarily solve the problem.

Mark

Post a reply to this message

> Halbert,

I finally resolved my problem! I found an excellent tutorial titled "Using
UV-mapping with POV-Ray meshes" at

http://www.mediaport.net/Artichaud/Tran/sources/tutuve.htm

Its a very pragmatic tutorial written in June 2000 and states in part:
"Presently there is no 100% reliable way to convert an ObJ or 3DS file with UV
mapping to POV"
But he goes on to describe several different ways of going about it.

The thing that helped me was that he describes how to edit the texture file
(file nameT.inc) that Pose2POV produces. I went in and using the POV editor
replaced all the default texture statements with statements declaring a texture
based on the image map and that did the trick. The render quality of POV is
beautiful compared to Poser's render or even the Vue D'esprit render.

So in summary the current problems seem to be:

1. Pose2POV needs to work on a single mesh rather than a collection of meshes
otherwise you don't get a usable UDO in Moray..
2. The output file filename.inc seems still to lack the #version unofficial
MegaPOV 0.5; statement and I had to add this by hand.
3. The filenameT.inc has a default texture rather than image map and Moray
doesn't seem to be able to overwrite this when producing the files for POV, or
at least I haven't found out how to do it other than to manually alter the file
in POV's editor.

All of these can at least be worked round now.
Thanks a lot, HH!

Post a reply to this message

OK. But the version number shouldn't be a problem (at least until POV 3.5 is
released, Or if you need to use Megapov > 0.3 features in the same scope as
the .inc file.) I was thinking it should be reletively easy to create a
windows version that could allow you to adjust things like whether to use a
default texture, or maybe the location of the image map you want to use.
Maybe even the version of POV being used. What are your thoughts?
HH

Post a reply to this message

On Mon, 24 Jul 2000 07:59:05 -0700, Simon Lacey <sfl### [at] yahoocom>
wrote:

Hi,

now there is guide available how to convert poser objects ot povray.
Just follow the link. 

http://www.stmuc.com/thbaier/3dwin_faq.txt

-tb


>Agreed. Its a Windows error. I'm running W98 though. I discovered the actual
>existence of the render despite the error myself.
>However, the render is still an untextured white though.
>Ah well.. I'm very close to giving up on P2Pov since 3DWin 4.2 is supposed to
>do it all if you pay for the registered version. Has anyone experience with
>the registered version and a review?

Post a reply to this message

"Simon Lacey" <sfl### [at] yahoocom> wrote in message
news:397DB0FA.44A7CE80@yahoo.com...
> > Halbert,
>
> I finally resolved my problem! I found an excellent tutorial titled "Using
> UV-mapping with POV-Ray meshes" at
>
> http://www.mediaport.net/Artichaud/Tran/sources/tutuve.htm
>
> Its a very pragmatic tutorial written in June 2000 and states in part:
> "Presently there is no 100% reliable way to convert an ObJ or 3DS file
with UV
> mapping to POV"
> But he goes on to describe several different ways of going about it.
>
> The thing that helped me was that he describes how to edit the texture
file
> (file nameT.inc) that Pose2POV produces. I went in and using the POV
editor
> replaced all the default texture statements with statements declaring a
texture
> based on the image map and that did the trick. The render quality of POV
is
> beautiful compared to Poser's render or even the Vue D'esprit render.
>
> So in summary the current problems seem to be:
>
> 1. Pose2POV needs to work on a single mesh rather than a collection of
meshes
> otherwise you don't get a usable UDO in Moray..
> 2. The output file filename.inc seems still to lack the #version
unofficial
> MegaPOV 0.5; statement and I had to add this by hand.
> 3. The filenameT.inc has a default texture rather than image map and Moray
> doesn't seem to be able to overwrite this when producing the files for
POV, or
> at least I haven't found out how to do it other than to manually alter the
file
> in POV's editor.
>
> All of these can at least be worked round now.
> Thanks a lot, HH!

I don't know how late I am but...

I've recently(ish) updated my OBJuvPOV program to add the #version
unofficial MegaPOV 0.5 line to it's output. It copes with multiple meshes as
far as I've used it and produces 2 files - a .inc file which holds the mesh
and a .pov file which defines the textures (you'd have to specify the
bitmap/s you want to use) and calls the .inc file.

I haven't uploaded the update due to assuming there was a lack of interest,
but if people want my little Visual Basic 5 effort then it's free. Limited,
but free. This was a quick hack (adding the #version) because long term I
hope to include .OBJ to .POV functionality within a little normal editor
(because far too many .OBJ files have normal problems for my liking and,
well, it's something to do).

--
Cheers,
Cliff Bowman

http://www.geocities.com/who3d/

Post a reply to this message

Yes. I'd be willing to give it a try. I'm just too damn lazy to continue
working on that code that someone else wrote. Mood has to be juuuuust right
before I will even fire up Visual C++. I assume that your program is located
at the web address indicated by your signature. Yes?

Post a reply to this message

Cliff Bowman wrote:
> 
> 
> I haven't uploaded the update due to assuming there was a lack of interest,
> but if people want my little Visual Basic 5 effort then it's free. Limited,
> but free.

Yes, I want... ;)

I often use OBJuvPOV in conjonction with UVMapper, and it works
perfectly for me
(except that the camera and light location are generated with ','
instead of '.'
in the numbers (am I clear ??)...)

Thanks in advance.

Bouf.

Post a reply to this message