DAZ Studio 4.6 Models Break Apart (SOLVED)
Hi. Has anyone else experienced models (e.g., Genesis and Genesis 2 Female) breaking apart upon reposing in DAZ Studio? I've had this happen several times and haven't found a way to stop it. I even reinstalled DAZ Studio 4.6, but it didn't do any good. Renders are fine, but it's almost impossible to pose the models the way I want because of the visual chaos before rendering.
By breaking apart, I mean that arms and legs sometimes break off, leaving one part somewhere on the screen and the other part somewhere else on the screen. Sometimes eyeballs pop out and hang in space, as do teeth. Hair sometimes hangs free apart from the model. And very often I get stretched lines that totally obliterate most of the model (see attached screen capture). I've tried stripping everything but the model out of the picture (deleting the props as opposed to just hiding them), and the remaining model still breaks apart.
I didn't find this issue addressed anywhere else, thus this post.
Any help with this would be greatly appreciated. Thanks.
Comments
So it renders OK? What are your options for Skin Binding and SubDivision in the During Manipulation group in Tool Settings? Also what settings do you have in Edit>Preferences>Interface?
Richard,
I confess that I don't where those options are set (Skin Binding and SubDivision), nor exactly what they do (I'm fairly new to 3D graphics). As to the Interface settings, please see the attached screen capture.
Thanks.
Robert
The other settings are in Tool Settings, with a posing tool active - Window>Panes(Tabs)>Tool Settings.
Thanks.
See attached screen capture:
Try setting Skin Binding to Full.
Didn't seem to help.
But you say the Render turns out correct, that suggests to me the OpenGL viewport might be at fault here. Does your GPU support the minimum OpenGL needed to run DAZ Studio?
Jaderail,
I'm not much of a tekkie. How would I find that out?
But, reasoning indirectly apart from the tech side of it, Studio was working fine until a couple days ago. I haven't changed anything on my computer, other than adding some more content from daz3d.com.
Robert
Did you by any chance have a OS update in that Time? I have and it included GPU Drivers. Here are the spec's for DAZ Studio...
http://www.daz3d.com/products/daz-studio/daz-studio-tech-specs
Then you would Goolge or Other search your Graphix Card and check against the minimum required for DS. Often GPU updates can cause a Viewport error when it was fine before.
What operating system?
You can also see some info about your current graphics card (if you don't have a manual or bookmarked web page for it handy) as reported by DAZ Studio by selecting the following from the menu:
Help > Troubleshooting > "About Your Video Card..."
Jaderail - I didn't have an OS update at the time this started happening, though I had an update today.
I looked at the link you sent. It says I need AMD Opteron/Phenom processor(s). **shrugs** I assume that means "at least that," not necessarily "exactly that."...(?) Below is my system information.
mjc1016 - I think this will answer your question, too.
As you can see, I've got issues with a couple Mirage Drivers, but I'm not sure what that means. When I tell them to update, it comes back saying that I have the latest drivers.
Two or three weeks ago I lost all sound on my computer and any reference to having DVD/CD drives on my computer. It's something that I'll be taking care of soon, but, in the interim, I was not having any problems with DAZ Studio until just a couple/three days ago.
Thanks, Sean. I'll check that out.
This is what I see when I bring up Help-Troubleshooting-About Your Video Card:
This hasn't been going on since Sunday by any chance?
If it started Sunday...is your computer's time correct (ie did it update correctly to DST)?
I've seen incorrect time/date cause odder problems than this...
Mirage is the manufacturer's version of your video card drivers...and they basically ended back in 2010 (at least for that card). AMD probably has more recent drivers available.
http://support.amd.com/en-us/download
(last one for that card was in Oct of 2013)
Time is good. Updated automatically.
Sounds like I need a new graphics card(s) - and, of course, a new computer to go with it. I wish...
I just downloaded and installed the drivers that AMD's auto-detect told me I needed, but the problem is still there.
Even though nothing has worked yet, I do appreciate the help you guys are giving me. I just don't have a clue.
I posted this once already, rachris, but apparently it didn;t get through. What do you have the Mirage Driver installed for? I suspect that this could be your culprit. At the least, get rid of those two instances showing with the exclamation marks - you certainly don;t need three instances loading. Second, I would try uninstalling the Mirage driver from Add/Remove Programs in Control Panel. If you need it for something specific, you can re-install later, See if uninstalling it solves your issue. There may be a conflict between the Mirage Driver and the AMD driver for your actual video card,
Lastly, it is too bad that you can't render your previews, since you have the makings of some avant-garde Dali cum Picasso scenes there. :)
SixDs,
I did as you said and uninstalled my Mirage drivers, then rebooted. Problem remains. :(
-----Lastly, it is too bad that you can’t render your previews, since you have the makings of some avant-garde Dali cum Picasso scenes there. smile-----
Haha. You might have something there. I guess I could resign myself to unrendered screen shots. (Or not.) :cheese:
Playing around with DS settings under Edit / Preferences / Interface / Display Optimization, I found that "Best" is what is screwing up my models. When I put it on "None" or "Better," the models display fine.
So, the problem is solved, I guess...but does anyone have a suggestion as to why the "Best" option messes things up?
Thanks for your input.
Best uses more optimized OpenGL code, but if the videocard or the driver does not support that (or implements it wrong, very common) you will have display errors like that, or even crash or bluescreen.
Totte,
Thanks for the explanation. And thanks to everyone who gave me input in dealing with this issue.
I guess we can tag this problem SOLVED. :coolsmile:
~Robert
Hint, edit the subjectline in the first post and add [Solved].
Totte,
Thanks. Will do.
Well I missed the Fix but did hit the cause. OpenGL viewport. I'll remember from now on that it can cause errors in JUST the DS settings as well.