WendyLuvsCatz said:

MAX Biped is the most commonly used bone hierarchy AFAIK

this doesn't seem any closer to any I have seen such as Unreal or Makehuman options and BVH import still broken

I can retarget and animate it easily enough elsewhere

https://www.daz3d.com/forums/discussion/591351/genesis-9-coming-soon-preorder-victoria-9-hd-today/p1

"Improved Posing & Animation 

With enhanced bone hierarchy and industry-standard naming."

I'm not understanding what this means in Gen9. I get industry-standard naming, but "enhanced bone hierarchy"...? 

What does that mean? What changed in the bone structure between 8 & 9?

MAX Biped is the most commonly used bone hierarchy AFAIK

this doesn't seem any closer to any I have seen such as Unreal or Makehuman options and BVH import still broken

I can retarget and animate it easily enough elsewhere

ahh, ok, manual install.

I use Daz Install Manager (DIM) for everything. It's easier for me to manage nearly 6,000 assets that way.

I'm not certain if the metadata is included in manual installs, but I assume it would be if downloaded from the Daz store.

Other than the "Filter by Context" box is unchecked at the bottom of the pane, The only thing I can think of right now for why you wouldn't be seeing your long list of shaders would be that the metadata for those products for some reason wasn't imported to the database.

Maybe someone with more experience working with manual installs can help with that part.

Your screenshot shows at least a few of them did get imported.

IceCrMn said:

If you can please, would you post a screenshot of what you are seeing.

I need to see the Surfaces pane open to the Presets tab and the Scene pane with your item selected just like in my screenshot.

Shaders installed from the Daz store will have the metadata needed to use the Presets tab, shaders from other stores most likely won't.

I can't show all the presets that are there, but I went through them and it's only the handful that have ever been there.

I never auto install anything.

If you can please, would you post a screenshot of what you are seeing.

I need to see the Surfaces pane open to the Presets tab and the Scene pane with your item selected just like in my screenshot.

Shaders installed from the Daz store will have the metadata needed to use the Presets tab, shaders from other stores most likely won't.

Panzer Emerald said:

nemesis10 said:

Ron Knights said:

criket, have you tried using Crossover?! Crossover allows you to create a "bottle" to run the installer in a simulation of Windows. I used Crossover many times when I had a Mac, and wanted to run old Windows installers.

I forget the price, but it is well worth it. It's certainly easier than what you've endured so far.

Unfortunately, I don't think it works.  The installers were designed to work in the era of OS 9 and early Windows.  OS X was introduced and the installers ran using Rosetta.  Eventually, Rosetta was deprecated.  In my experiments, the installers for Windows and OS X wrote to different system folders with appropriate permissions so simply placing the files where they should be isn't enough.  You could use Crossover to activate the Windows installer but you can't make it write to the proper OS X  system folders.

I should say that this isn't strictly Daz's fault.  In this case, they are the broker for a vendor who has passed away.  It isn't clear that they have access to the assets that the installers use.

Bolded for emphasis.
Also, it could be a lack of bodies to fill positions in the service (food and retail mainly) industry in general. You see it everywhere, all the people who used to work in that sector left after COVID for numerous reasons, not wanting to be dealing with Karen-esque customers anymore being one of them.  
 

could just be Daz lost a lot of their CS people to other remote or warehouse jobs.

I actually don't think this is this is what is going on.  Creators make their products, package them, and Daz3d creates the metadata, and posts them for sale and download.  Support can troubleshoot if there is an issue with Daz Studio, errors in a script, morph, or mat than can be seen in a text editor etc.  Otherwise, they contact the creator to fix the problem.  In this case, the creator has passed away and so can not do support. The company does not have the power or legal right to reverse engineer a creator's product. Exactly like Amazon, the company can accept a return, contact the vendor, and deal with a broken product that way.  They can't disassemble a product to update it.  This is an unusual situation where technology was rapidly changing and, in this case, the installers were never updated.

So here is a comparison between elbow bending in blender 3.2.2 and 3.3.1

It is the same blender file and the only difference is the blender version.

I think the problem is that the default DaztoBlender rig fails to load some jcms or shapekeys in blender 3.3

Another issue with this is that when you just import a character into blender, it does work as intended.

However after some saving and loading, material tweaking, some rendering and then all of sudden it just does not want to work anymore

I tried reimporting the model and it worked at that moment and 1 day later the elbow problem came out.

And then I used blender 3.2 to open that file, the elbow worked as usual again and I think this happens to knee bending as well.

Currently I am back with blender 3.2.2 but I really wish this could be solved since blender 3.3 gives a render speed boost of my scenes with latest driver

Oh btw, I tried blender 3.3.0 and it didn't give any difference.

Hi

I agree with update hexagon 

So it becomes unnecessary to switch to other 3d modeller when it lacks that function 

Import. Stl? 

Compiled to 64bit possible? 

Here is a project I have been working on and it will be released shortly is now available. 

This is a port of Fverbaas MDBridge to Daz Studio. The script will allow Daz Studio to send poses and receive clothing from Marvelous Designer.

Here is a quick YouTube video of MDBridge for Daz Studio.

A typical session will always start with “Start MDBridge”, usually followed by “Setup Figure”. You can then change attention to MD to load the avatar in an A-pose and morph to T-Pose and Posed Avatar for testing prior to creating or fitting a garment to your avatar. Once the garment is fitted to the A-pose you can use the “Morph to” option to test the garment on your Daz posed figure. If you would like to change the avatar’s pose in Marvelous Designer, you can simply select the “Start/Stop AutoUpdate” option in MD and send a new pose from Daz Studio with the “Export Shape” option. When done you can export the garment from MD, back to Daz Studio using the “Export Thin Garment” option and the “Import Garment Prop” option in Daz Studio to get the result in your Daz scene. For more complete info consult the main manual

• Start MDBridge: Starts your session. It launches Marvelous Designer with the bridge functions running. The first time you use the bridge Daz Studio will ask you to select the location of the Marvelous Designer executable file. The information will be stored so you not need to do this again. You will likely find the executable in the default install path: C:/Program Files/Marvelous Designer 9 personal/MarvelousDesigner9_Personal_x64.exe ◦ If you want to change this later you can use the preference page options to select the folder location.

• Setup Figure: This is an automated option that will send your figure’s current pose as well as a compatible A-pose and T-pose to Marvelous designer as the essential avatars. The data is stored on your hard disk in a temporary folder that can be chosen on the preference tab. The data will normally remain available between sessions unless you or the operating system do a clean-up.

• Export Shape lets you export the current posed shape of the selected figure in your scene.

• Import Garment Prop lets you import the geometry that MD made of the garment fitted to the posed figure. The name of the garment prop is forDaz3D. ◦ If there is already a prop with the name 'forDaz3D’ in the scene, another prop will be added with the new import. If you want to keep the current 'forDaz3D' prop rename it in your scene. 

DOWNLOAD HERE if not working below

For chest breathing, the morph is very easy to do with Blender, regardless of the 3D character.
Just import the character's OBJ file and use the Lattice modifier to deform very slightly the rib cage.
There are many tutorials for the Lattice modifier. In a few minutes you will be able to do this job.

That's a shame. I'll rely on the Smart Collection tab in the meantime, but I did quite enjoy the aesthetic quality of DC (large tiles, links out to purchase page, etc.).  My ideal situation would be to pull the product metadata into a CSV sheet so that users (me) could organize them by whatever values they contain in the DB (purchase date, size, title, any tags, etc.).

Thank you for your response.

To create custom shapes for specific poses you could use the morph system of Blender :

Export Genesis as obj, no SubD, default pose.

Import in Blender. Create a Shape Key.

Export Genesis in your final pose. Export as obj.

Import in Blender. Add that second obj as a second Shape Key on the first imported Genesis.

Now do the same with the Geograft. Export it as base, default pose and shape. Import in Blender and create a Shape Key.

Export the same geograft in the final pose. Import in Blender, add that as a 2nd Shape Key on the base geograft.

In Blender, slide the 2nd Shape Key for both Genesis and the geograft.

You now have your final pose for both, but as morphs. Create a 3rd Shape Key for the geograft and make modifications to the geometry to shape it the way you want. NONE of the vertices connected to the Genesis can be moved, even so slightly. Or morph won't be usable on the Daz geograft.

Once your geograft is shaped as you want, slide the 2nd Shape Key down to 0. Geograft is now in its default base pose but with your modifications added to it. Export that geograft from Blender as obj. Import in Daz using morph loader pro.

You can now, in Daz, go to the keyframe of your final pose. And load your custom geograft morph.

As for your issue, I guess it's related to the fact that you may have moved one or more vertices from the open edges (the ones connected to Genesis). That's very probably why the morph can't be used, as I can confirmed that all that still works as usual in the most recent version of Daz.

You can import a vertex cache animation with obj and morph loader. Don't know if there's a plugin to automate this.

edit. Found this.

https://github.com/versluis/animmorph

Hi all! I export a model from Daz3D, and when I load it into cinema 4d, it shows this information - "Nothing to import. You have to export from DAZ Studio first."

Please, help.

@Padone do you think it is so diffrent to import it into unreal5? I wanted to know your opinion can you import shapekeys and other stuffs to unreal 5? Does unreal 5 even has bone control or you need to make everything in blender even bone moves than import to unreal?

Hi,since yesterday evening I have a problem with daz,after about 2 seconds after clicking the render button the application pauses rendering with a blank window.From the logs it looks like not enough vram but earlier I rendered images on this scene and nothing like this happened One g

2022-11-17 13:56:39.214 [INFO] :: Rendering image

2022-11-17 13:56:41.332 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating geometry.

2022-11-17 13:56:41.332 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating motion transforms.

2022-11-17 13:56:41.333 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing scene graph.

2022-11-17 13:56:41.536 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Auto instancing compression ratio 1.00 (Full instancing compression ratio 1.00)

2022-11-17 13:56:41.536 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing geometry for motion time 0

2022-11-17 13:56:41.730 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Geometry import (1 triangle object with 3 M triangles, 0 fiber objects with 0 fibers (0 segments), 1 triangle instance yielding 3 M triangles, 0 fiber instances yielding 0 segments) took 0.194 s

2022-11-17 13:56:41.731 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating section objects.

2022-11-17 13:56:41.731 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating materials.

2022-11-17 13:56:41.838 Iray [INFO] - MATCNV:RENDER ::   1.0   MATCNV rend info : found 232 textures, 0 lambdas (0 unique)

2022-11-17 13:56:41.848 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Emitter geometry import (13 light sources with 15122 triangles, 1 instance) took 0.001 s

2022-11-17 13:56:41.848 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating volumes.

2022-11-17 13:56:41.849 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating environment.

2022-11-17 13:56:41.849 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lens.

2022-11-17 13:56:41.849 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.

2022-11-17 13:56:41.849 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.

2022-11-17 13:56:41.850 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating backplate.

2022-11-17 13:56:41.853 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating caustic portals.

2022-11-17 13:56:41.854 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.

2022-11-17 13:56:41.861 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using iray core convergence estimate.

2022-11-17 13:56:41.861 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer

2022-11-17 13:56:41.869 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using batch scheduling, caustic sampler disabled

2022-11-17 13:56:41.869 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing local rendering.

2022-11-17 13:56:41.872 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing OptiX Prime for CUDA device 0

2022-11-17 13:56:41.877 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 1 device(s):

2022-11-17 13:56:41.877 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (NVIDIA GeForce GTX 1080)

2022-11-17 13:56:41.877 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...

2022-11-17 13:56:41.877 Iray [INFO] - IRAY:RENDER ::   1.9   IRAY   rend progr: CUDA device 0 (NVIDIA GeForce GTX 1080): Processing scene...

2022-11-17 13:56:42.332 Iray [INFO] - IRAY:RENDER ::   1.3   IRAY   rend info : Importing lights for motion time 0

2022-11-17 13:56:42.332 Iray [INFO] - IRAY:RENDER ::   1.3   IRAY   rend info : Initializing light hierarchy.

2022-11-17 13:56:42.519 Iray [INFO] - IRAY:RENDER ::   1.3   IRAY   rend info : Light hierarchy initialization took 0.187 s

2022-11-17 13:56:42.550 Iray [INFO] - IRAY:RENDER ::   1.9   IRAY   rend info : CUDA device 0 (NVIDIA GeForce GTX 1080): Scene processed in 0.673s

2022-11-17 13:56:42.550 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(367): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (NVIDIA GeForce GTX 1080): Not enough memory for kernel launches (222.797 MiB (354.047 MiB) required, 0.000 B available). Cannot allocate framebuffer.

2022-11-17 13:56:42.550 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(367): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (NVIDIA GeForce GTX 1080): Failed to setup device frame buffer

2022-11-17 13:56:42.550 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(367): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (NVIDIA GeForce GTX 1080): Device failed while rendering

2022-11-17 13:56:42.550 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(367): Iray [WARNING] - IRAY:RENDER ::   1.9   IRAY   rend warn : CUDA device 0 (NVIDIA GeForce GTX 1080) ran out of memory and is temporarily unavailable for rendering.

2022-11-17 13:56:42.555 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(367): Iray [WARNING] - IRAY:RENDER ::   1.9   IRAY   rend warn : All available GPUs failed.

2022-11-17 13:56:42.555 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(367): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: Fallback to CPU not allowed.

2022-11-17 13:56:42.555 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(367): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: All workers failed: aborting render

2022-11-17 13:56:42.555 [ERROR] Iray :: Internal rendering error.

2022-11-17 13:56:42.717 [INFO] :: Saved image: C:\Users\\AppData\Roaming\DAZ 3D\Studio4\temp\render\r.png

2022-11-17 13:56:42.724 [INFO] :: Finished Rendering

2022-11-17 13:56:42.776 [INFO] :: Total Rendering Time: 3.65 seconds

2022-11-17 13:56:46.144 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Device statistics:

2022-11-17 13:56:46.144 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (NVIDIA GeForce GTX 1080): 0 iterations, 0.679s init, 0.005s render

 one character and a small room The card is gtx1080 and the scene takes only 300mbvram

SpaceCoyote said:

I'm having the same problem. I've tried to install/uninstall Daz Studio and Daz to Maya using Daz Central in every possible order I can think of, without and with Studio being open, and I never get the "Script" menu in the top menu bar.

Oh my, after quite a day of trying to get all this to work, I've finally had success. Turns out the documentation on the Daz to Maya help page is outdated and there is no longer a "Scripts" menu in the menu bar after installing the Daz to Maya bridge. Instead, sending your Daz model is done by going to File > Send To > Daz to Maya. This will open a window that has updated instructions on how to install the bridge in Maya, including this very useful YouTube video:

I also had to do one extra step in order to launch the Daz Import window in Maya, which was to install PyMEL, otherwise Maya would give me an error. I think PyMEL was an optional install that I chose not to install when I updated to the latest version of Maya so others may not encounter this problem.

golem841 said:

I use DazStudio 4.20 017, Blender 3.3, Dzblender bridge2022.2.18.42

When I try to import a posed figure, the pose is not or not completely imported.

I keep skeletal mesh, export morphs is unticked.

I suppose there's something I'm doing wrong somewhere.

When I try to apply a pose from the Daz Library to the figure, I receive an error message in Python.

I'm totally new to Blender.

I Also tried to install Diffeo before the official bridge, there are maybe some interferences with "residues" I forgot to delete.

Could somebody give me a hint ?

Thanks a lot

 

the same question +1

Tried using earlier versions of DTU and it wouldn't import into UE5 at all. Like I had to completely uninstall UE5 reinstall it reinstall the latest DTU to get it to work again at all. I'd ask how to downgrade to Daz 4.20 but that's probably gonna cause me a different set of hell. Is there a good third option? Is DTU gonna get fixed at all ever? At least these issues?