HOME | DD
ken1171 β -Gen3F in Poser-
#female #genesis #pinup #poser #render #sexy #3
Published: 2015-07-10 06:07:28 +0000 UTC; Views: 5996; Favourites: 127; Downloads: 299
Redirect to original
Description
~Genesis 3 Female in Poser~After all the hype, my very 1st Gen3F render in Poser with Octane (8 mins). She doesn't like Poser at all, so I had to bring her by force. LOL
Technically speaking, Gen3F poses and morphs beautifully, though only in DS4.8 and nowhere else. Any attempts to export to FBX or COLLADA failed to load correctly in Poser. All parts and materials load up, but the clothing and hair are scattered across the scene.
The only option was to export to raw OBJ, and rebuild the materials in Octane. The material paths seem correct in the OBJ, but [I think] Poser can't read paths with spaces in them, so I have to manually copy all the scene maps to the OBJ folder. If not, Poser will ask me to locate each map, even if they are all in the same folder (duh!). Exporting to FBX creates a folder with all the maps, so that saves me the trouble of having to locate them manually. As a side note, exporting from DS for some reason does not include any transparency maps, so I had to reconnect them manually.
One could expect FBX and COLLADA to resolve all of the above, but in my experience these "universal" file formats have so many versions, which create a lot of incompatibility. Maybe there is a specific version of FBX or COLLADA that could make perfect transition between Poser and DS, but I haven't found which one - if any - this far.
I have played a bit with i-ray in DS, but I quickly grew impatient because it takes anything between 10s to half a minute to show any updates. Having to wait this long to see any material or light adjustments takes just too long. I also cannot edit anything while it's rendering. That's why I felt an urge to bring the entire scene to render in Poser with Octane, where I have instant updates for any changes I do, without having to stop the render. I-ray was also taking forever to clear the noise (even at small sizes), while Octane finished the final 1200p render in 8 minutes.
Very worth the try, and I now have a pipeline I can use when I want to render Gen3F in Poser. I am used to always rebuilding all materials in Octane, so at least this part is the usual for me. Hope you like it and thanks for coming by!
Related content
Comments: 77
Yeah, she can be imported, but does she bend as well as she does in DAZ? I think you still miss features like geografting so if I want to use some anatomically correct add-onsΒ you probably wouldn't be able to. Re-exporting every time you change a morph would be a pain. We'll just have to deal with the idea that the divorce is final and learn to live with Dawn,Β Pauline or Project E.
π: 0 β©: 1
If you check the description, all the posing/dressing/morphing work was done in DS. All I have in Poser is the static OBJ, and I still have to rework all the materials.
π: 0 β©: 0
Thanks! I would play more with Genesis if the process weren't so cumbersome.
π: 0 β©: 0
Thanks for letting us know how it can be done Too bad it has to be such a cumbersome process. I'm not buying V7 resources if they are that awkward to work with for a Poser user and require installing DS.
I've tried Collada a few times with other things in Poser, but with no real success.
She looks pretty and flexible, a shame she is so rigid about software.
π: 0 β©: 1
It is not cumbersome to use Gen3F contents in Poser - it is impossible. There is no DSON that can do it, so we have to either convert each and every item back to TriAx rigging (to use with DSON), or do everything in DS4.8 and only then export to raw OBJ. Even if you convert everything back to TriAx, the clothing fitting will not be perfect, and facial expressions and other morphs may not work at all. I think exporting to OBJ is the simplest way, that is, if you don't mind composing the scene in DS. I actually don't mind, but I know a lot of people who do, especially the ones who have never used it. Or in some cases the ones who tried DS and didn't like it.
I personally think Gen3F is [technically] a wonderful base to work with, but the Poser community was once again left out in the cold - this time more severely than it already was with Gen1 and 2. I am just showing there are still ways to get it done, though it's not ideal.
π: 0 β©: 1
Yeah, I'm one of those who minds. I haven't got DS installed on any of my machines ... and even if I had, I would have to get an additional Octane license for use with DS.
Well, it seems that as long as I'm not interested in using DS, I might as well continue with my choice to forget all about Genesis
To this date I haven't posted a single Genesis based render.
π: 0 β©: 1
You could still use Dawn, which has all of the Genesis features but also exists natively in Poser (no DSON). ^^
π: 0 β©: 1
Yeah, but Dawn gets so terribly sad and claims I don't love her when she sees what my V4 runtime looks like after 8 years ...
π: 0 β©: 1
My V4 runtime is that huge too, and often reuse her stuff on Dawn. Poser contents are more reusable than people realize. ^^
π: 0 β©: 0
Splendid work
I'm not sure that the problem comes from the spaces in the names: don't forget that Poser's default runtime is at least "Poser Pro xxxxΒ Content". Poser's functions are often written in Python, and even on a PC, paths may be expressed using, for example: "runtime:textures:author's name:author's folder:author's sub-folder:author's very specific name.jpg"
π: 0 β©: 1
Thank you! Oh, so you do think I could resolve the OBJ texture paths issue by replacing slashes with colons?
π: 0 β©: 1
Honestly: I don't know, but as a developer, I have the impression that the problems you have encountered may Β come from a (volontary?) incompatibility.
My small experience comes from LuxXeon 's great furniture: with each poser specific "obj" file comes an equivalent text file with the same name but with ".mtl" as extension. It describes the relative paths to the bitmaps and everything loads without a glitch.
π: 0 β©: 2
Thanks for the mention, Phil. Β In regard to OBJ, I've always found it to be best practice to use a mtl file for the materials and textures. Β Material definition files are a good way to identify maps and surface parameters with your model, between various software packages. Β Almost every software that supports .obj will know to look for the mtl file you specify, and search the paths contained therein. Β It's best also to keep all the file locations local, not relative, to avoid path conflicts and error messages. Β You can edit the mtl or obj files just like any text file, in notepad, to manually change these paths if necessary.
π: 0 β©: 1
You are right but Poser is not handling path correctly in fact... I mean: relative paths are ok, absolute path are ignored.
π: 0 β©: 0
That's what I was referring to - the MTL files that accompany the exported OBJs. DS creates absolute paths (complete with drive letters) for each of the textures, but Poser cannot find them. It stops at *each* texture and asks me where they are, even when they are in the same folder (very annoying). I then remembered Poser CR2 use double quotes when paths have spaces, and I tried adding those to the MTL paths, but that didn't help. The only thing that worked was to copy all textures to the same folder as the OBJ, and then remove all paths from the MTL.
π: 0 β©: 1
If the paths are absolute, you may have indeed a difficulty. But: you may use a text editor to search'n'replace.
Here is an example of a .mtl file, done by LuxXeon, and that contains spaces, without problems:
newmtl cushion
Β Β Ns ........
Β Β map_Ka ..\maps\Leather0041_2_S (diff).jpg
Β Β map_Kd ..\maps\Leather0041_2_S (diff).jpg
Β Β map_bump ..\maps\Leather0041_2_S (bump).jpg
Β Β bump ..\maps\Leather0041_2_S (bump).jpg
π: 0 β©: 1
What's wrong with absolute paths on an exported OBJ? I mean, that's not a Poser file.
π: 0 β©: 1
Unfortunately, you are absolutely right: Poser does not support absolute paths in the MTLs files, but only relative ones. Maybe they're ignoring this because it's multi-platforms...
π: 0 β©: 1
That's rather ironic when sometimes even Poser creates absolute paths in CR2, and other Poser files it creates - and they work.
π: 0 β©: 1
Lol.. Indeed... Looks like the wavefront importer needs some corrections... and unfortunately, it's not in the python code available
π: 0 β©: 1
That's what I was suspecting - the OBJ importer is buggy. I have used OBJ for years, and it should not matter if MTL paths are relative or absolute. But I so remember this OBJ importer always had this problem. I have first noticed in Poser 5.
π: 0 β©: 1
Maybe is the code still from the V5...Β Β
π: 0 β©: 1
Ah, this discussion of yours explains my ... "What do you mean you can't find the file! It's right THERE! In the same bloody folder as the previous one you stupid program!" moments with Poser 
π: 0 β©: 1
Honestly, I haven't seen a lot of programs which have a decent philosophy when it comes to folders and files management.
Double-clicking on a pz3 file, modifying the scene and then using the "Save as.." function should lead to the pz3's folder by default
Same wrong philosophy when using the "Recent files" list and when saving a picture after having rendered it.
Poser is not the only program with these conception errors.
π: 0 β©: 0
May be quicker to import directly in standalone octane from Daz ?
For Iray, a very important point is that's free and quite very good for "simple " scene as pinup like yours...I agree that it's slower than octane but... 
(I've tried all of them in poser or daz, + Vray in Max...so ... price is an important criteria for many non professional users at deviant or elsewhere..)
With a good Nvidia card, rendering under Iray same pic (dimension) would take around 20mn.(Nvidia 780 for example)
Nice pic Indeed.
π: 0 β©: 1
Thank you! I-ray is indeed a great way for the casual DS user to get access to unbiased rendering for free. But I have been spoiled with Octane since it was first released, and to me there is no way back. I have this old GTX580 video card and it's *so* much faster than i-ray that I can't even compare. I can only imagine how much faster this can get with a modern video card. Octane 3 is around the corner, and it will support all video cards, not just nVidia as it is now. Personally, I still think that V-Ray beats Octane in rendering and native materials quality, but the price and learning curve are equally much higher. V-Ray also takes forever to render, and V-Ray RT is taking too long to develop. When it comes to price vs performance, I haven't seen anything better than Octane when it comes to what is available to Poser/DS. ^^
As for your suggestion, I don't use Octane standalone. The Poser plugin offers an interface that is much better for handling Poser materials because of the way they are organized and handled. The plugin also offers many automations that are typical of Poser materials, so it makes the job much quicker and simpler. For instance, the standalone version does not understand how materials are organized in Poser figures, so setting them up would take much longer.
π: 0 β©: 1
I agree with you !
Working (for pleasure) since many years in poser, i just "discover" DS4.8 these last days....Posing in DS is great... Conforming is better than Poser, and Iray, as you say, is a good "beginning" to handle unbiased render. So may be a good choice to take Octane with DS plugin (cheaper)...
I've only worked with the demo on Max and Poser... Octane is very impressive , yes (speed, Converting materials)...
Have a nice day !
π: 0 β©: 1
Not only conforming, but also body scaling works much better in DS than in Poser, which didn't actually support body scaling until very recently, and yet, not so well. That's why I recommend people dress and pose the figures in DS, and only export to OBJ for rendering (if they need to like I do). Much better results this way! ^^
π: 0 β©: 0
Thank you! Finally rendered in Poser. ^^
π: 0 β©: 0
If you roll back her rigging to straight TriaX, and make the Poser Companion Files, she imports into Poser just fine. 
π: 0 β©: 1
Not only the expressions, but also conforming clothing will not always fit because of rigging-based JCM that won't carry to TriAx. If you loose expressions and clothing only fits in some situations, that's not much of a usable set. For Gen3, it's best to do everything in DS and only export to OBJ before rendering. That does the trick for me, and I didn't have to sacrifice anything. Besides, I am not a big fan of DSON because it slows Poser down. By composing the scene in DS and rendering in Poser I get the best of both worlds. ^^
π: 0 β©: 1
I haven't had much problem in terms of clothing that I also convert to TriaX but... I also only have like two outfits. :/Β The selection just isn't impressing me yet.Β Β I hear you about DSON -- I tend to rename the folder to "unhook" it when I don't need Genesis2/3 because it turns Poser to sludge even when I'm not using it.
If you don't mind a not-so-quick question:Β Is there anything that you miss in Genesis3, as far as the base figure goes, that you wish it had?Β Yes, I am fishing.
π: 0 β©: 1
That's a tricky question - I have tested Gen3F more from a content creator perspective. She poses well at the usual trouble zones, she morphs well thanks to the usually good DAZ topology, and most of all, her facial expressions are not creepy, which has been an issue many times before. The default shape is pleasant to the eyes, and I say this remembering how V3 had the proportions of a cave woman. Figure-wise, V4 was the "perfect girl", except for the many limitations imposed by legacy rigging. Her expressions were good, but I see Gen2 and 3 have visibly improved on that, which I guess comes from previous experiences.
The only thing "wrong" with Gen3 is that it is now completely isolated in DS. Other vendors like HiveWire3D and LadyLittleFox have been releasing their new figures natively to both Poser and DS, which [I think] is the proper way to address the market. All of my store products since 2013 have also been released in native formats for both platforms, so I am not just saying it. But DAZ is making it very hard to cope with that part now, so even though I do think Gen3F is an very well done figure, I have some reserves about her.
π: 0 β©: 0
Thanks for showing the way to export and render G3F in Poser.
Speaking of Poser, I have not touched it in years (because I have been using DAZ Studio lately) ... Maybe what you showed here may change that.
π: 0 β©: 1
You'd still have to do the posing and dressing in DS, but personally, when it comes to rendering, I do my best in Poser. ^^
π: 0 β©: 1
True, even though the dressing part is much less frustrating for me in DS (unless newer updates and/or versions of Poser (Pro) made the fitting process much better better). Lol, I see.
π: 0 β©: 1
Thanks to Gen3F, I now see a lot of questions about what Poser 11 will bring to the table. If I look back into how things have been with SMS, my bet is that they will innovate in their own ways, and will completely ignore whatever DAZ is doing with figures. Even if they come to add dual quaternion rigging and UDIM texturing, it will be utterly incompatible with Gen3F, in the same way that Poser weight maps are incompatible with TriAx. But who knows? They always manage to surprise me, with exception of the "Game Dev" fiasco, which is cute and going to the right direction, but is utterly useless in a practical way -Β I tried.
π: 0 β©: 1
I wouldn't be too surprised if SMS does what you said concerning innovation in their own ways.
Speaking about figures, do Poser users still mostly use DAZ figures (aside V4/A4/etc.) when using the program? If a very large proportion of users will not be able to take full advantage of SMS's innovations due to incompatiblity, then what real sense does it make to innovate that way.
I didn't tried and used "Game Dev" (mostly for practical reasons you already mentioned).
π: 0 β©: 1
I can't really tell what other people are using, but even amongst DS users, V4 is still strong in the market. I am telling this based on the fact that new V4 contents are still being made nowadays, and vendors only make contents where there is a market who buys it. We have to remember that V4 can work in Poser or DS without modifications, since she doesn't use any of the new innovations introduced in DS4. Nonetheless, DAZ3D keeps innovating all the time. ^^
One thing that gives me some hope is the fact that the new features added to Gen3F are open source, like dual quaternion rigging and UDIM UV mapping. Poser weight maps are incompatible with TriAx because that's closed proprietary format that belongs to DAZ3D, but these new ones aren't. But even if they introduce it in Poser 11, there is no telling their implementation will be compatible with Gen3. Time will tell. ^^
π: 0 β©: 0
| Next =>