12/16/2023 0 Comments Poser debut exportI have tried resaving as a scene, with no real luck. Maybe I am making the wrong type of target file. I mean if the runtimes are mapped to Poser, should it not be able to call them?Ģ. That seems to me what may be going on, but then again that seems to be very limiting. So I am wondering if Every asset called by the DUF/Companion files have to be in the same runtime as the Target DUF file. But when I try to load the scene subset, (or scene) at most I get a brown screen, and some random camera's but no figure, and no clothing. Now I have mapped all three runtimes to Poser, and poser sees the companion files. But when I create companion files for say v4_Claudia_FearMomma_Outfit. I keep my DAZ library divided into 3 "Runtimes" My IM Library, My Library (Rendo Assets), Studio 4/Content/ Runtime/ Tree, This library contains all the scenes, sets, props, et al, I have ever created but of course calls to assets in the other two libraries, and this works just fine for DAZ, if I want to load V4 wearing a given outfit I just merge her into scene and boom, NP. I have a couple quick Questions, I expect they have been anwsered before, but after a week of working on this issue, I have not found definative answers.ġ. Hi I am a long time DAZ user, who is trying to Migrate some of my content to Poser, mostly to use their comic rendering capacity. I'm hoping that some Poser 12 user here may have seen an error like this and found a resolution. Poser support has thrown up their hands they have no idea why I am experiencing this, they even offered to refund me my Poser 12 rather than pursue this further. I can, upon the install launch of Poser, run Python fine, Octane Render is fine, etc. I have to rerun the installer to fix that error, but it only lasts until the application is restarted. "An error occurred importing addon PythonShell :ERROR: DLL load failed: The specified module could not be found." BUT, the very next time I open Poser (without installing ANYTHING else) I get an error I originally thought that my Octane plug-in was breaking but after lengthy troubleshooting with Octane support it is pretty clear the issue was something wrong with my Poser 12, in that a fresh install of Poser fixes a problem of the Python Shell loading (there is no error on launch, etc.). I think Daz really outdid themselves in terms of shaping and rigging with this one! The shoulder and elbow seem to bend well in this image, at least to my eye! In any case, if any other enterprising Poser users are experimenting with G9, I welcome any tips or examples of your own! My first full render is hot off the presses! There are workarounds for this, of course, but I hope to find a more efficient workflow as I continue to tinker. For ther most part, I was right! Simply converting G9 to TriAx weight mapping, turning off any subdivision, and putting the base figure through the CR2 exporter works suprisingly well! Most of the conforming anatomy converts and attaches quite well too, though the mouth seems to be a bit wonky (going weirdly askew when conformed to a morphed figure).Īpplying hair and clothing is my main challenge at the moment, as clothing at least doesn't seem to follow morphs as well as could be hoped. Still, G8 still seemed to work well enough to be worth playing around with and updating my most-used characters, and I suspected that the same would be true of G9. There are fortunately workarounds for the base figures themselves, but the utility and power of the "Transfer Active Morphs" script, at least, remains difficult to fully emulate (unless there's been progress that I'm unaware of). When Poser 12 came out using Python 3 instead of Python 2, it essentially broke the DSON Importer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |