Tue, Nov 26, 8:50 AM CST

Renderosity Forums / DAZ|Studio



Welcome to the DAZ|Studio Forum

Forum Moderators: wheatpenny Forum Coordinators: Guardian_Angel_671, Daddyo3d

DAZ|Studio F.A.Q (Last Updated: 2024 Nov 26 6:59 am)



Subject: little help with an old product.


Noshoba ( ) posted Sun, 17 February 2013 at 11:45 AM · edited Tue, 26 November 2024 at 8:50 AM

file_491707.jpg

I downloaded Lynn's creation's  freebie  wolf/fox etc morph for old P4 wolf. Honestly because with her morph it looked like a real wolf vs the pitbull looking crap they call wolves available now.  But I degress.

 

What  I am getting is this.   It is a Poser map. I have checked all of the diectories and paths and they match.  Only thing is in character file it has both pngs and rsr files. 

I really want to use this.  And what is the way to convert to a standard mat file style if possible. 

 

thank you. 


FyraNyanser ( ) posted Sun, 17 February 2013 at 1:27 PM · edited Sun, 17 February 2013 at 1:29 PM

You obviously have no trouble loading the textures onto the wolf, but the problem is with the UV mapping.

From what I can tell, this package contains a remapping of the wolf object in UVMapper format (.UVS). You will need the UVMapper program and with this load a copy of the wolf object (.OBJ file) and the .UVS file and then resave the copy with the new map applied.

In DAZ you should then, in theory, be able to load the original wolf, and then add the UV map to it using the copy of the wolf object you saved with UVMapper. UV maps are loaded in DAZ by importing an OBJ file containing the mapping data using the "Load UV set" command which is available when you are in Surfaces.


Noshoba ( ) posted Sun, 17 February 2013 at 1:52 PM

Already done that with Lynn's uvs file. Still not sure what is acting up.  Hell I even saved a texture map in Uv Mapper to see if the jpgs used in the MapMorphs were flipped around or something.

 


FyraNyanser ( ) posted Sun, 17 February 2013 at 2:16 PM

Silly question, but did you select the alternative UV map in the shader panel after loading it? Have you had a look at the UV map in the UV View to see if it matches the layout of the new textures?


Noshoba ( ) posted Sun, 17 February 2013 at 2:36 PM

it doesn't   damn thing is 90 degrees off on the fur setting. First time I have  messed with one of these in Daz 4.5 pro.. So figured after unlocking the uvs that Lynn provides it load right. I have used 3d Menegeries wolf and Lynn's raven with no problem so not sure why this one isn't working right

 


Noshoba ( ) posted Sun, 17 February 2013 at 2:40 PM

for some reason the morphs are loading properly just can't get the uv map saved right


Noshoba ( ) posted Sun, 17 February 2013 at 2:47 PM · edited Sun, 17 February 2013 at 2:48 PM

This is what the texture map looks like when I save the model


Noshoba ( ) posted Sun, 17 February 2013 at 2:51 PM

file_491713.jpg

Here is the texture map that shows when I saved the model.. so not sure why the UV map doesn't match


FyraNyanser ( ) posted Sun, 17 February 2013 at 3:00 PM

Is that how it looks in UV View in DAZ, or is that in UVMapper? If that's from DAZ, it would seem bizarre that the textures don't fit if that is showing in DAZ, as that map matches the provided image textures.

Have you tried DAZ's own forum? There may be people there who have got it to work or have come across this kind of thing before.


Noshoba ( ) posted Sun, 17 February 2013 at 3:08 PM

that is how it looks in Uvmapper in  DAz it is showing the old DazWolf/P4 wolf. I just applied the DazWolf texture and it fit  but the maps should not have loaded. 

 

I haven't tried there  because they have pretty much archived everything and this was a old item from Lynn that she made into a freebie. And from her website would say she hates DAZ lol.  Was going to contact her here but her web page doesn't list her user name here nor a link just says  contact at Rendo. 

 

http://www.lynescreations.com/


vulcanis ( ) posted Sat, 23 February 2013 at 1:11 AM

There is a link in her readme that directs you to her gallery here.

Did you change the name of the newly mapped obj? If you didn't, then you now have 2 obj files in your wolf folder. One named blWolf.obj and one named blWolfLynes.obj.

          --This might have happened because when you use uvs files in UVMapper, UVMapper automatically updates the name of the object to the name of the UVS file as a default.--

If this is the case, you have two options.

  1. Rename your blWolf obj to something else to make it a backup. Then you can rename your blWolfLynes.obj to blWolf.obj (this is the file poser is looking for)

or

  1. You can update the reference in the cr2 to point to blWolfLynes.obj instead of blWolf.obj.

I would include an already modified cr2 for you. Unfortunately, the readme expressly forbids it.


Noshoba ( ) posted Sat, 23 February 2013 at 6:44 PM · edited Sat, 23 February 2013 at 6:46 PM

Quote - There is a link in her readme that directs you to her gallery here.

Did you change the name of the newly mapped obj? If you didn't, then you now have 2 obj files in your wolf folder. One named blWolf.obj and one named blWolfLynes.obj.

          --This might have happened because when you use uvs files in UVMapper, UVMapper automatically updates the name of the object to the name of the UVS file as a default.--

If this is the case, you have two options.

  1. Rename your blWolf obj to something else to make it a backup. Then you can rename your blWolfLynes.obj to blWolf.obj (this is the file poser is looking for)

or

  1. You can update the reference in the cr2 to point to blWolfLynes.obj instead of blWolf.obj.

I would include an already modified cr2 for you. Unfortunately, the readme expressly forbids it.

 

Ok where the problem seems to come and I am not sure why either. I followed her instructions. Afterwards the blwolf.obj when loaded in Uvmapper shows her uv file  in the Zygote directory file. But when I load it in to DAZ 4.5 Pro it reverts to the old uv map. And I have no idea why. I have used UV mapper in the past so know how to use it and to decode. If had way to contact Lynn I would.  Unfortunately I have no clue how to mod a cr2 file


RHaseltine ( ) posted Sun, 24 February 2013 at 9:47 AM

If you don't modify a copy of the CR2 to call the new OBJ instead of the old, or load the uvs from the new OBJ via the Surface pane's menu (right-click on the tab, or click the button in the top corner of the pane) then DS won't know about the new mapping and so won't apply it. Editing the CR2 should be covered in the readme.


Noshoba ( ) posted Sun, 24 February 2013 at 5:17 PM

Quote - If you don't modify a copy of the CR2 to call the new OBJ instead of the old, or load the uvs from the new OBJ via the Surface pane's menu (right-click on the tab, or click the button in the top corner of the pane) then DS won't know about the new mapping and so won't apply it. Editing the CR2 should be covered in the readme.

 

Why I am having trouble  I have used both but for modifying the CR2 which I have no way f doing. What I am trying to figure out is why is the obj file accepting the remapping until I load it into DAz then when I look at the obj file ai see a tiny padlock symbol. 


RHaseltine ( ) posted Mon, 25 February 2013 at 2:48 PM

You can use a text editor to edit CR2s - not Notepad, as that doesn't cope with the line end markers, but Notepad+ is free and works. All you do is sedit the two lines that refer to the old OBJ to refer to the new - assuming it's in the same folder that just means changing the name. I'm not sure what you mean about the padlock - where are you seeing that?


Noshoba ( ) posted Mon, 25 February 2013 at 7:13 PM

I am seeing the padlock emblem right on the Obj file icon.  I actually  directly loaded the modded obj  file to Daz and also Hexagon and the uv file showed the old uv


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.