- This topic has 13 replies, 5 voices, and was last updated 7 years ago by
.
-
Posts
-
Yeah so, ever since I DL'd 4.12 Beta, dForce decided its going to raise the middle finger. I start the simulate and... =|== , every time. So all my dForce items are useless. I uninstalled 4.12 and it didn't fix the issue with 4.11 beta.
Also, you can point dForce to use your CPU instead of GPU, forcing it to rewrite the code used to render the simulation.
That was what I did after I installed the 4.12 beta a couple weeks ago and found that dForce would just freeze Studio until I forced it closed then had to re-work everything I did before dForce crashedDoesn't matter what I use. user created? I don't know much about dForce so I'm not creating anything myself.
Everything was fine before I DL'd 4.12. Had no issues with dForce except getting stuck on hands when the hands passed through cloth while simulating.
The only error I've ever gotten, was your computer doesn't have the kernel would you like to set that up. I press yes.
Then it crashes when done. Then I try again. I hit simulate. It immediately pops up with the box, PLEASE WAIT.. (ie; I'm going to make you look at me because I'm crashing DAZ right now and pissing you off).
Quite simple.
ALSO, since I DL'd 4.12, I am unable to render UNLESS I have CPU checked. Even though I uninstalled 4.12, it is the same. I've already updated my drivers.Simulating hair, like Oso Furo. Daz cat hair. Sometimes it would just lock up up my PC and I'd have to do a hard reboot. I finally rendered cat hair without simulating.
With Oso Furo, it doesn't say anything about it being dForce, which pissed me off. I found out going to the forums on DAZ because when I rendered it looked liked a sick animal with a puffy thin hair disease and nothing like the promos.I haven't tried clothes, TBH.
since you also can't use your GPU for rendering, there seems to be an issue with your GPU driver maybe, as also dforce uses the GPU for calculation. try to reinstall drivers etc.
Daz Studio 4.12 works perfect for me.
OK,, STOP... I never said I couldn't use Iray. I never said I couldnt use my GPU.
What I said was, in the advanced render options, I can't have JUST my card running to render. Before 4.12, I could. In fact I unticked the CPU on purpose. NOW, I have to have it ticked ALOMG WITH my card. Now here's the kicker.. Before I uninsalled 4.12, I could use 4.11 Beta without the CPU box being ticked. Now I can't. I also downlaoded 4.11 full and same thing.
Again, my drivers are up to date. I WAS running latest but its uninstalled now.HOWEVER, with all that being said, I thank everyone for their response. But of course, when I go to test again after opening my giant maw, BA BLAM!!! I can dForce a dress. Really Preda? You're going make a liar out of me?
I'm also still testing the DAZ dForce hair. I found a png text file for Oso Furo that was freezing my computer. I removed it and I can render him now after the missing file error. I can't find where its being used so... I'm not sure if I'm supposed to be simulating or just rendering. The whiskers don't look like a frizzed ball of fur on his head right out of the dryer anymore though, so thats something..
What I was getting before, not simulating.
What I get NOW without simulating..
I swear. I didn't do anything. It seems to have just fixed itself on its own after all the multiple freezes and fails. Except having to have the CPU ticked in in the Photoreal Devices tab in advanced render settings.Operating System: Windows 8.1, 64-bit
DirectX version: 11.0
GPU processor: GeForce GTX 1070
Driver version: 391.35
Direct3D API version: 11.2
Direct3D feature level: 11_1
CUDA Cores: 1920
Core clock: 1594 MHz
Memory data rate: 8008 MHz
Memory interface: 256-bit
Memory bandwidth: 256.26 GB/s
Total available graphics memory: 14304 MB
Dedicated video memory: 8192 MB GDDR5
System video memory: 0 MB
Shared system memory: 6112 MB
Video BIOS version: 86.04.50.00.72
IRQ: Not used
Bus: PCI Express x16 Gen3Just found out I'm not the only person to have the blank render CPU must be ticked, issue.. I'm going to go directly to Nvidia and check the driver..
OK, final update.. That was the UN-tick-it. Manual DL and install of of the driver. Stupid Nvidia Experience not giving me latest driver and lieing to me.
I've got goosebumps saying I have my speed back. YAY!!!!
Thanks everyone for your help and input.Uh... Okay. Update your shit.
Windows 10, and minimum Nvidia driver 419.x
It's listed as a requirement for the Beta (was for 4.11 as well)...
@errilhl LOL I did.. I did.. But honestly it wasn't my fault. Nvidia Experience updated it on 8/20, but not to the latest one but told me I was current, so I thought I was. I found out I wasn't, by going to to Nvidia itself. I'll be doing a manual install from now on.
But screw Win 10.. Not happening. Had it before. Hated it before. hated it. I'm good with 8.1 Pro.Yup. That was it Tony.
- You must be logged in to reply to this topic.
