dForce hair doesn't want to render
Enerla
Posts: 16
Hi,
On an ASUS ROG STRIX with i7, Geforce 1050Ti, etc. I have installed DAZ studio to my HDD (D) as the content librabry and everything wouldn't fit to the smaller SSD (C).
When dForce hair came out, I have tried to render some images with dForce hair, but it didn't work at all. Hair was invisible.
Had some motherboard issue so the laptop was fixed... When it got back I tried to render dForce hair again (no luck)
Uninstalled everything with DAZ Install manager, reinstalled it... Opened the scene. Still no luck. Some of the "hair cap" might be visible, but the hair isn't.
Created a scene, with only longdrape hair in it... Hair didn't really render.
Tried to reset styles, one file was missing. runtime/textures/philw/longdrapeb/hair density/bust.png
Deleted this... Tried with Kay hair... No luck, but hair cap was more visible, hair still wasn't.
Tried my luck with femme fatale hair... No luck yet again.
Trying to turn off GeForce GTX as a device: No luck.
Tried my luck with a
mklink /D "My Library" "D:\My DAZ 3D Library"
command. When I tried to set renderer to OpenGL guide hairs rendered. But in iRay it still didn't work.
Deleted the log file, and tried to add longdrape hair to a new scene and hit render.
Still no luck.
Current driver: GeForce Game Ready Driver 430.86
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
For some reason it didn't attach the log file, here are its contents:
2019-07-11 17:32:57.553 *** Scene Cleared ***2019-07-11 17:33:33.078 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Could not adjust thumbnail path from support path: /Runtime/Support/DAZ_3D_17109_Carrara_Hair_Caps_for_Genesis_and_Genesis_2.dsx2019-07-11 17:33:43.113 *** Scene Cleared ***2019-07-11 17:33:43.236 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(4679): Could not find node parent.2019-07-11 17:33:43.239 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(4679): Could not find node parent.2019-07-11 17:33:43.434 Iray INFO - module:category(SCENE:IO): 1.0 SCENE io info : Loading module "::daz_3d::dual_lobe_hair" from "D:\Program Files\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\dual_lobe_hair.mdl".2019-07-11 17:33:43.607 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(1770): Failed to follow node.2019-07-11 17:33:43.607 File loaded in 0 min 0.5 sec.2019-07-11 17:33:43.608 Loaded file: longdrape hair for g8f.duf2019-07-11 17:33:43.856 Loaded Morph Deltas in 0 min 0.0 sec.2019-07-11 17:33:43.857 Loaded file: Behind Right Shoulder.dsf2019-07-11 17:33:44.002 Loaded image Haircap Trans.png2019-07-11 17:35:00.240 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=02019-07-11 17:35:19.849 Rendering image2019-07-11 17:35:19.931 Iray INFO - module:category(IMAGE:IO): 1.0 IMAGE io info : Loading image "D:\My DAZ 3D Library\Runtime\Textures\PhilW\Strand Based Hair Shaders\Haircap Trans.png", pixel type "Rgb", 2048x2048x1 pixels, 1 miplevel.2019-07-11 17:35:19.964 Iray INFO - module:category(IMAGE:IO): 1.0 IMAGE io info : Loading image "D:\Program Files\DAZ 3D\DAZStudio4\shaders\iray\resources\DTHDR-RuinsB-500.hdr", pixel type "Rgb_fp", 512x256x1 pixels, 1 miplevel.2019-07-11 17:35:20.094 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating geometry.2019-07-11 17:35:20.115 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Using OptiX Prime ray tracing (5.0.1).2019-07-11 17:35:20.116 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Importing scene graph.2019-07-11 17:35:20.118 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Auto instancing compression ratio 1.00 (Full instancing compression ratio 1.00)2019-07-11 17:35:20.132 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Importing geometry for motion time 02019-07-11 17:35:20.134 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Geometry import (1 object with 4704 triangles, 1 instance yielding 4704 triangles) took 0.0024822019-07-11 17:35:20.134 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating materials.2019-07-11 17:35:20.137 Iray INFO - module:category(MATCNV:RENDER): 1.0 MATCNV rend info : found 3 textures, 0 lambdas (0 unique)2019-07-11 17:35:20.150 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating environment.2019-07-11 17:35:20.168 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating backplate.2019-07-11 17:35:20.171 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating lens.2019-07-11 17:35:20.171 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating lights.2019-07-11 17:35:20.171 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating object flags.2019-07-11 17:35:20.186 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating caustic portals.2019-07-11 17:35:20.186 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating decals.2019-07-11 17:35:20.209 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Allocating 1-layer frame buffer2019-07-11 17:35:20.211 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Using batch scheduling, caustic sampler disabled2019-07-11 17:35:20.211 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Initializing local rendering.2019-07-11 17:35:20.257 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : CPU: using 11 cores for rendering2019-07-11 17:35:20.262 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Rendering with 2 device(s):2019-07-11 17:35:20.262 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : CUDA device 0 (GeForce GTX 1050 Ti)2019-07-11 17:35:20.262 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : CPU2019-07-11 17:35:20.262 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Rendering...2019-07-11 17:35:20.272 Iray VERBOSE - module:category(IRAY:RENDER): 1.2 IRAY rend progr: CUDA device 0 (GeForce GTX 1050 Ti): Processing scene...2019-07-11 17:35:20.273 Iray INFO - module:category(IRAY:RENDER): 1.9 IRAY rend info : Using device 0 to build data for host2019-07-11 17:35:20.275 Iray VERBOSE - module:category(IRAY:RENDER): 1.6 IRAY rend progr: CPU: Processing scene...2019-07-11 17:35:20.282 Iray VERBOSE - module:category(IRAY:RENDER): 1.5 IRAY rend stat : Geometry memory consumption: 133.438 KiB (device 0), 0 B (host)2019-07-11 17:35:20.727 Iray INFO - module:category(IRAY:RENDER): 1.9 IRAY rend info : Importing lights for motion time 02019-07-11 17:35:20.727 Iray INFO - module:category(IRAY:RENDER): 1.9 IRAY rend info : Initializing light hierarchy.2019-07-11 17:35:20.727 Iray INFO - module:category(IRAY:RENDER): 1.9 IRAY rend info : Light hierarchy initialization took 0.00s2019-07-11 17:35:20.731 Iray VERBOSE - module:category(IRAY:RENDER): 1.5 IRAY rend stat : Texture memory consumption: 5.25 MiB for 2 bitmaps (device 0)2019-07-11 17:35:20.744 Iray VERBOSE - module:category(IRAY:RENDER): 1.5 IRAY rend stat : Material measurement memory consumption: 0 B (GPU)2019-07-11 17:35:20.744 Iray VERBOSE - module:category(IRAY:RENDER): 1.9 IRAY rend stat : Native CPU code generated in 1.4e-06s2019-07-11 17:35:20.744 Iray VERBOSE - module:category(IRAY:RENDER): 1.5 IRAY rend stat : Materials memory consumption: 20.6172 KiB (GPU)2019-07-11 17:35:20.747 Iray VERBOSE - module:category(IRAY:RENDER): 1.5 IRAY rend stat : Lights memory consumption: 196 B (device 0)2019-07-11 17:35:20.820 Iray INFO - module:category(IRAY:RENDER): 1.6 IRAY rend info : CPU: Scene processed in 0.550s2019-07-11 17:35:20.822 Iray INFO - module:category(IRAY:RENDER): 1.6 IRAY rend info : CPU: Allocated 2.96654 MiB for frame buffer2019-07-11 17:35:20.851 Iray INFO - module:category(IRAY:RENDER): 1.6 IRAY rend info : Allocating 1-layer frame buffer2019-07-11 17:35:20.854 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00001 iterations after 0.584s.2019-07-11 17:35:20.892 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00002 iterations after 0.621s.2019-07-11 17:35:20.964 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00004 iterations after 0.693s.2019-07-11 17:35:21.099 Iray INFO - module:category(IRAY:RENDER): 1.2 IRAY rend info : CUDA device 0 (GeForce GTX 1050 Ti): Scene processed in 0.829s2019-07-11 17:35:21.102 Iray INFO - module:category(IRAY:RENDER): 1.2 IRAY rend info : CUDA device 0 (GeForce GTX 1050 Ti): Allocated 2.96654 MiB for frame buffer2019-07-11 17:35:21.132 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00008 iterations after 0.839s.2019-07-11 17:35:21.146 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00009 iterations after 0.876s.2019-07-11 17:35:21.163 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00010 iterations after 0.893s.2019-07-11 17:35:21.301 Iray INFO - module:category(IRAY:RENDER): 1.2 IRAY rend info : CUDA device 0 (GeForce GTX 1050 Ti): Allocated 1.6875 GiB of work space (2048k active samples in 0.140s)2019-07-11 17:35:21.370 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00012 iterations after 1.099s.2019-07-11 17:35:21.397 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00016 iterations after 1.127s.2019-07-11 17:35:21.421 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00024 iterations after 1.151s.2019-07-11 17:35:21.487 Iray VERBOSE - module:category(IRAY:RENDER): 1.0 IRAY rend progr: 62.70% of image converged2019-07-11 17:35:21.532 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00032 iterations after 1.262s.2019-07-11 17:35:21.534 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00048 iterations after 1.264s.2019-07-11 17:35:21.644 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00053 iterations after 1.374s.2019-07-11 17:35:21.774 Iray VERBOSE - module:category(IRAY:RENDER): 1.0 IRAY rend progr: 81.39% of image converged2019-07-11 17:35:21.791 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00085 iterations after 1.521s.2019-07-11 17:35:21.799 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00089 iterations after 1.529s.2019-07-11 17:35:21.974 Iray VERBOSE - module:category(IRAY:RENDER): 1.0 IRAY rend progr: 86.74% of image converged2019-07-11 17:35:21.974 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00123 iterations after 1.703s.2019-07-11 17:35:22.017 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00128 iterations after 1.747s.2019-07-11 17:35:22.154 Iray VERBOSE - module:category(IRAY:RENDER): 1.0 IRAY rend progr: 90.09% of image converged2019-07-11 17:35:22.154 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00164 iterations after 1.884s.2019-07-11 17:35:22.185 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00168 iterations after 1.914s.2019-07-11 17:35:22.340 Iray VERBOSE - module:category(IRAY:RENDER): 1.0 IRAY rend progr: 92.20% of image converged2019-07-11 17:35:22.340 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00206 iterations after 2.070s.2019-07-11 17:35:22.349 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00211 iterations after 2.079s.2019-07-11 17:35:22.523 Iray VERBOSE - module:category(IRAY:RENDER): 1.0 IRAY rend progr: 94.02% of image converged2019-07-11 17:35:22.537 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00250 iterations after 2.266s.2019-07-11 17:35:22.546 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00255 iterations after 2.275s.2019-07-11 17:35:22.723 Iray VERBOSE - module:category(IRAY:RENDER): 1.0 IRAY rend progr: 95.26% of image converged2019-07-11 17:35:22.723 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00298 iterations after 2.452s.2019-07-11 17:35:22.763 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Convergence threshold reached.2019-07-11 17:35:22.903 Saved image: C:\Users\theel\AppData\Roaming\DAZ 3D\Studio4\temp\render\r.png2019-07-11 17:35:22.906 Finished Rendering2019-07-11 17:35:22.968 Total Rendering Time: 3.26 seconds2019-07-11 17:35:22.969 Loaded image r.png2019-07-11 17:35:22.985 Saved image: C:\Users\theel\AppData\Roaming\DAZ 3D\Studio4\temp\RenderAlbumTmp\Render 11.jpg2019-07-11 17:35:24.892 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Device statistics:2019-07-11 17:35:24.906 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : CUDA device 0 (GeForce GTX 1050 Ti): 298 iterations, 1.138s init, 1.480s render2019-07-11 17:35:24.906 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : CPU: 49 iterations, 0.553s init, 1.890s render2019-07-11 17:38:59.032 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=02019-07-11 17:39:01.084 WARNING: Object::disconnect: Unexpected null parameter2019-07-11 17:39:01.093 WARNING: QCoreApplication::postEvent: Unexpected null receiver2019-07-11 17:39:01.297 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Tcp shutdown called on a Tcp connection without a shutdown2019-07-11 17:39:02.727 Iray INFO - module:category(IRT:RENDER): 1.1 IRT rend info : Shutting down irt render plugin.2019-07-11 17:39:03.781 *** Scene Cleared ***2019-07-11 17:39:04.545 DEBUG: End DAZ Studio to Hexagon Bridge log...2019-07-11 17:39:05.452 --------------- DAZ Studio 4.11.0.383 exited ------------------2019-07-11 17:39:05.467 ~When you say they don't render do you mean in Iray preview or in an actual render?
If you mean in iray preview, you need to go to the parameters tab with the hair selected, then enable "Preview PR Hairs" in the Line Tesselation group.
If you mean an actual render, one thing you could try is to reinstall the dForce starter essentials which contains the shaders used by dForce hair.
Actual render, as the uploaded picture shows.
It is after reinstalling everything with DAZ Install manager. So it didn't help. And I am not sure if there is any place where things can be cached, etc. even after reinstall.
I don't see any picture in your post, just a blank attachment
Check that attachment, some "hint" of the haircap is visible on that render, but it is rather small. :) This is why I see something went very wrong here.
Hi there :) a few things to check
1. you have ds 4.11 installed (yes, as per your log)
2. you have dforce essentials up to date?
3. make sure you haven't currently got a geometry editing tool selected, select the pointer tool instead and then try to render again.
UPDATE: please read here for my updated dForce Strands hair render checklist https://www.facebook.com/notes/aprilysh3d/aprilysh-dforce-hair-tips/3548983945134478
1. Yes, it is installed
2. Fresh reinstall with DAZ Install Manager, so yes it is up to date.
3. Changing selected tool helped :)
Never tought it could be an issue :)
we need to submit feature request to Daz to turn the preview hairs grey(or some warning color) if a geom editing tool is currently selected.
any other ideas for an indicator?
It is kind of crazy that the hair won't render if you have the wrong tool selected.. but the tip helped me as well. Thanks.
Jesus christ i was trying for hours to figure out why the hair wasnt rendering, it was because geometry editor was on.
A better feature request would be to render no matter what tool is selected lol.
+1
Wow!!!
I got trapped in this "wrong tool selected" too!
Thanks a lot, you released me from anguish!
Thanks to everyone who posted to this. I had the same problem but thanks to you a quick web search of "Daz DForce Hair Won't Render" brought this thread up. Y'all are great!
just want to also say thank you, because I was infuriated with WHY it wouldn't work. they need to fix this, it is a bug.
What is a bug? Something not working as you want or expect may be confusing but it is not a bug.
OK, So I feel like a complete moron. THANK YOU SO MUCH! I cannot express how much agony you've just saved me. I've had constant issues with renders where after I move or pose a character, the hair stops rendering. I delete it, re-add it, and still nothing. I have an add-on called Mesh Grabber Tool. I had that tool selected. I know it always gave me issues with not rendering geoshells properly in preview if I had it selected so why I never thought of that earlier... anyway, Thank you so much for pointing this out. My renders are working normally now that I don't have that tool selected. I truly appreciate the wisdom.
So what's wrong if the hair looks like this - Atlas hair, Atlas Hair for Genesis 8 Male | 3D Models and 3D Software by Daz 3D
I've got other D-force hairs which loads and renders just perfectly, but Atlas hair keeps giving me trouble.Supposed to look like this:
I don't have that hair but someone else seemed to have figured out it needs an included preset applied before any render: https://www.daz3d.com/forums/discussion/417626/ ;
Thanks!
Finally. I got that stupid hair to work. Why not simply keep the 'preview' state ON to avoiid all the hazzle.
I'd returned that hair if I'd remembered to test it earlier, and I beleive I'm not the only one. :(
If I look here immediately I could save 5 hours. On other side, now I know better all dforce settings I tried to change :)
Bringing this thread back from the dead to note that I just fell in this trap yesterday and spent hours trying to figure this out. I knew it wasn't an inherent problem with the hair, which had been working all day long. I was testing new products and one of them includes a part where you use geometry editor, which is a feature I had barely used before. I had no idea one needed to specifically select some other tool or else hair - which was not obviously related to the product I was testing - would not render. Luckily, I had tested the hair first, because had it been the other way around, I would have reasonably assumed that the hair was broken. I have middling experience with Daz, having been using it for somewhat over a year now, and I don't recall any other circumstance I've run into as a typical user where this sort of behavior happened. I do software support IRL, and have spent my share of time at the corporate level doing QA, documentation and training, and this is arguably bug-worthy. I do agree with other posters on this thread that this at least merits some kind of warning - perhaps when you click the geometry editor, it pops a warning message that some objects may not render until the tool is deselected.