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
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Yep. Frustrating because dialing in just the body should not increase height. But it does. Granted Leo 7 is a tall thin guy but they designed him different than the others. It makes using his genetics with other characters really difficult. You need to think about scaling the head shape and it is not very easy to get good proportions. IT basically makes him useless as a gene donor. If they were going ot do that.... They should've just not made him a base. As a base it is expected his genetics will behave like the others.
Blaming the trainee is a poor excuse, and the sort of actions would turn me off a company's products: accountability. You (whoever you are) assign a task to a trainee makes you responsible, not them.
Never liked the character so didn't bother even considering; but something like that, if I notice, I tend to return.
If there is an issue; I need to be either to work around it, or return it. I'll consider keeping whilst the issue is fixed, but expect to be able to return if it's considered not worth fixing.
I buy all of the products with all of the functionality; my choice if I use them or not.
SixDs: I've had nothing but good experiences with Customer Service when it comes to things like sale prices or returned items, for which I'm very grateful. I've had about a 5-10% success rate with bug reports.
This is a big problem on every tablet I own or have tried. Even with a full sized IPad, or my Samsung tablet (10.4) it's really hard to hit that little zone for the arrow!!! I keep thinking that they will fix it some day, but obviously they have no intention to fix it. I really get tired of repeated attempts to go to the next image just cycling between zooming to full resolution and back. Too bad they don't get it is a problem for many (most?) people. It would be really nice if they would make it "swipe" friendly..
Personally, I don't bother trying to look at the promo images on my tablet or smartphone anymore, since I'd end up having to scroll around the image to get a decent view of it on them. If I do want to take a close look at them, I do it on the laptop when I'm at home.
If I ever had to file a bug report, I would check regularly on my reports progress through the system, as it's my fault if they end up closing it if I don't respond if they need verification it was fixed.
Um. It's their business, and their system. Isn't the onus on them to ensure their stuff works?
When I submit bug reports, I generally regard it as doing them a favor, because I'm taking my time to help them with their product. In every case, I am resigned to the bugs never being fixed, but I figure I may as well help.
Mind you, whenever I've had bugs closed, it's generally because there's been no response because the last thing they said was 'we're checking with the devs.'
Bug reports are of course useful and helpful. However, not every issue reported is a bug - for example, some of the things mentioned with respect to Leo 7 are feature requests (a desire for things to be done a different way) not bugs (something not working correctly). Even those that are bugs may not be immediately fixable, or may require several elements to come together to effect a fix. I fully understand how frustrating an unfixed bug can be - I have a number of pending bugs of my own, and I've had some closed due to inactivity too - but there is always going to be an element of that (I can remember long-running unresolved issues in the Adobe forums, which I haven't visited for a while, and still see them in the modo and other application support forums). That doesn't mean you should shrug and walk away, but nor should you assume that every unresolved ticket is down to intransigence or neglect.
Yeah, honestly I was surprised at the amount of work I was asked to do when I did file the real bug in DAZ Studio but in a GUI system like DAZ very detailed instructions on how to replicate the bug are needed. I am surprised though that since the bug was actually fixed that no one notified my to test again with the latest DAZ Studio or even bothered to close the ticket because clearly someone fixed that particular bug.
And about the website bug that has been complained about repeatedly in these forums where one is overcharged when they checkout and see something like are $25 debit to their bank account ballon into an over $200 charge because of that bug. Needless to say I was not pleased although DAZ took care of it before it did any damage to my bank account with NSF charges. If I was Bill Gates I might never of even checked and really that's not the right attitude for a business to take. It has the potential to get any businesses into big trouble because it has the potential to throw customers out on the street or leave them without enough to go grocery shopping or pay utilities or their other bills. People make budgets for a reason. Really, that is going to get DAZ in trouble someday, I have to say it and DAZ had better get to fixing it. Not trying to cause trouble, trying to avoid it.
I'm sure the developers are already looking at similar schemes but they ought to check out regression test automating of the sort like Unity 3D uses or Microsoft uses. True I still file bugs with Unity 3D and Microsoft but then I am using their latest betas and the progress they have made in improving their SW in the past year and a half is amazing, of course with much bigger staffs and budgets than DAZ 3D but automated comprehensive regression testing will let SW engineers spend more time on modular design and improvements to DAZ Studio.
Those developers also have a larger number of users of their products that are willing to participate in beta testing programs, which also helps immensely in dealing with bugs and feature testing.
I would agree though; customer service have always been efficient, polite and helpful.
Generally speaking, bug reports should never be closed on product you've paid for. If the bug is open -- no resolution and it's not "working as designed" -- means you're not getting the value you paid for. I can see closing bugs on D|S, which is free, as well as usability and functionality reports on the Web site. There's no real duty with either to fix the flaw. But it's fairly non-standard to close a bug on something that has involved a customer charge. I've never submitted a bug on a product that hasn't been dealt with to closure, so I've not seen this myself, if it happens.
I suspect if reports are getting closed it's a feature of their bug reporting system, of which there are many available, where the length of time to keep a report open is a configuration value. Given Daz's willingness otherwise to offer free customer service, I'm thinking it's more likely it's a configuration setting, perhaps with the inability to exempt the automatic expiration on paid product. Some of these reporting systems aren't all that flexible.
The popup images for products are produced by a free and open source lightbox script, which is fairly easy to modify. Having implemented a few of these myself, including this one, I know it can be a hassle to adapt them to mobile devices, but it can be done. I've seen a few mobile-aware lightboxes that don't display the < and > arrows on mobile devices, and instead rely on right and left swipes.
One of the reasons I use Paypal; it clearly states how much I'm being charged, which I can compare with Daz's balance and what I thought it should be; all three match, then it's a click to confirm.
Unfortunately, I wasn't aware of this issue immeadiatly. So it was beyond the 30 day return period. While I don't like Leo's face, his body sculpt is really useful to dial in to other men's bodies.
Oh?
It doesn't work correctly. The body slider should not alter height. If there is a difference with a specific character this should be stated in product description. Alterations like this make the character unusuable for its genetics without tweaking. To me that is a bug. It doesn't work correctly.
Why not? (Asking as a PA candidate, mind you) To me, dialing in body scaling in the combined dial (or in a preset for the character) is only going to give a body shape that may not be what the PA was envisioning for the character they are creating.
Not in my experience. I've had excellent and rapid responses from CS for pretty much everything except bug reports, but those exceptions... oy.
It doesn't help that the method of re-opening closed reports — and sometimes just seeing old reports — is the most awkward and unobvious undocumented mess I've seen since the last major store website change. At one point I actually had to open a report to ask how I reopened a report...
Generation 7 characters typically do not have height scaling baked in the body (only) morph. So if you dial Michael 7's body without his head, it should not increase the character's height. If it does, you will mess up the user's character who may not want the character taller. Can you image the hullabaloo if Victoria 7 body increased her height? Leo 7 is intended to be a lanky character, but his shape is not so unique it should warrant breaking the established character process. It is understandable if a full character preset of full character dial increased height. This is intended to be the full shape of the character including height dimensions. Body only however should not alter character size.
Discussion is here: http://download.daz3d.com/forums/discussion/140881/question-about-leo-7-morph
FWIW, I agree with this. I use a lot of my base characters in mixed amounts. Having one that effects scaling is a no-no...means I won't be using that particular character to mix. What that boils down to is basically all I have now is the texture since I can't use the morph too. Might be enough for some people, but not what I bought it for.
Laurie
IF this was minotaur I could kind of understand his genes and height being more of an issue since the shape is extreme.. But Leo is like an inch or so taller than Gianni. It's not that unique of a shape.
So glad this was posted and Jack responded. Let me tell you what I've discovered, from doing product showcasing for four years:
Post it in a thread, ask for other people to test it for you if you're not sure (and just to verify the mistake) and then put the @ with vendor name, and ask if they will take a look at it. I've had SO many nice vendors pop in to the thread and then do tweaks within a day to a week. I give the vendors first crack at it, and also it's so others know what problem I am having. Just like Jack said, "Oh?" If he'd been @ (his name) he would have gotten notified by you and most certainly (knowing Jack) addressed it. Many vendors would have done the same with all these bug reports.
I have had nice vendors (Kindred Arts comes to mind) go out of their way to "fix" things that aren't even bugs. Now I buy from that store when new products come out, as a token of appreciation, and in the knowledge that products will be supported.
Unfortunately there are a lot of vendors that don't visit the forums. I don't think they would get your message. Anyway, we have been told that submitting a help request is how these issues are supposed to be handled. It is disappointing to see that so many help request go into the "bug tracker" and never emerge with fixes, or even a status update, or even a response saying they've been reviewed and will not be fixed. We just hear nothing.
Well actually until only recently having a larger number of users only got those organizations an overwhelming amount of filed bugs that shouldn't have been filed as bugs, bug reports that not enough data was reported to investigate with reasonable efficiency, or duplicate bug reports. They keep refining their automated regression tests and their algorithms comb through the bug reports in their database(s) and now they are making improvements much faster.
However, it is true too that although I have filed multiple bug reports with them that have been accepted as bugs by one of their 'replication bug report screeners' I have yet to be notified by Unity when the bugs I reported have gotten fixed. In a few cases I have observed independently that the bugs were later fixed but in other obscure cases I would have to do a bit of work to replicatte the situation that caused the bug and then test for it again. It's also not as easy to look up on their public web page to see the status of the bugs I reported as with DAZ.
Also, finally, I (and many others) were promised nerdyphernalia in the form of Unity t-shirts if we reported a bug that was actually accepted as a bug by their QA staff via them being able to replicate the bug and accepting it as needing to be fixed and I and many others have have done this and yet received no t-shirts (the offer is already long gone now though).
So it's not like Unity and MS bug QA procedures are perfect but DAZ Studio could have automated regression tests added...(maybe they do)