At first I was upset about the problems with this software - now I am fairly angry - after yet another system crash with this "update." IF YOU LIKE DAZ - DON'T UPDATE IT! YOU'LL BE SORRY! My quotes for this situation (I know because I'm definitely in one of the categories below - hey, at least I admit it). Half the world is composed of idiots, the other half of people clever enough to take indecent advantage of them.

I sympathize totally with you. Judging by this forum and the one over at Daz an awful lot of people are experiencing problems with the new version. I've had a couple of crashes and can't save to file - never had any problems with version 1.1. I can't understand why Daz bothered with this new version. They should have waited,tested it PROPERLY or added some new features that were worthwhile. Yeah, I suppose we musn't forget that it is free, but it's still gonna annoy alot of people who were very impressed and happy with the first version.

I've had problems with it too. It now refuses to find half the objects I had in my scenes and although it seems to let me import objects, via the Import menu, they don't actually appear in the scene. That's the last time I install a new version as soon as it comes out. I'm going back to my old philosophy of being one step behind the cutting edge. Now, where's my wire brush? I need to scrub this version from my hard drive.

I hope that you are all putting in bug reports so that DAZ know exactly what they have to sort out.

RubiconDigital - did you delete the ContentData folder when you uninstalled the old version? That holds the actual mesh for your saved scenes, which might account for the missing objects if they are (not) in .DAZ files.

Wow. I haven't done a whole lot in D|S, but I haven't had any problems at all. No crashing, broken models.Definitely report your situation.

Oops. Spoke to soon.I can't save, but no crashes. I usually export to obj for another program and had no problems with that.Checking logs to report. It says it can't rename the temp file.Also, see lots of can't initialize in opengl, but didn't see any visual problems. It's a long list so I don't know if these may be unsupported by my card...need to check some of them.

The name shows for the file in the top. If I go rename the file removing .tmp it works fine.

Well - I'm surprised that my original post in this matter was not removed for troll like behaviour. Why on earth wouldn't DAZ allow a number of their users to pre-test this version - then iron out the bugs - then release it to the seething hordes? Me, I am just beyond being a newbie with this software, and the issues that accompany this release are out of my grasp. How many crashes will you all tolerate before DAZ Studio - into the recycle bin it goes? For what it's worth - the folks at DAZ are good people, as well as most of the Renderositers who I have crossed paths with. I will terminate this post with an ancient Chinese proverb. The great question is not whether you have failed, but whether you are content with failure

No, I didn't delete any folders. I have since uninstalled 1.2, cleaned out my registry of any reference to Daz, and re-installed 1.0.1 and everything works perfectly again.

I've not had any crashes with the new version, but I have had to deal with the "doubling morphs" bug. I've seen enough to know that they're moving in the right direction, especially with the object export (oh yeah, and then there's the bug I reported on that because it doesn't maintain node groups when you import an object then export it).

I suppose it's worth exactly what you've paid for it. :) I'm sure that someone did test it, but technically we're all testing it in return for getting it FREE.

Edited to add: Oh, BTW, most long-time D|S users will warn you to ALWAYS keep the previous install file until you're sure that you don't need it (this would now include all the matching plugin installs as well). Saves a lot of headbanging, fist slamming and other comparable troll like behavior.

Message edited on: 01/18/2006 18:47

Yeah, I reported. They are swamped. I also noticed I can't use the button for where you change your render file name or change the file name.Does seem a bit rushed.Glad I don't count on it for primary renders. I am sure they will get it sorted out tho.

The problem with objects seems to be a scale issue. I made my own simple cyclonearama that in Studio scale should 2 meters tall and 5 meters in diameter. Importing at 100% it was only a tenth of the size. Hopefully this is just math mistake that can be quickly found and fixed. I've only noticed the morph issue with morphs that use PBM channels.

I have been working on an important scene for the past two hours.I have had to start over 4 different times because 1.2 keeps crashing.I reverted back to using 1.0 again until they cure 1.2.Don't get me wrong I love DAZ|Studio but the newer version had given me more headache than happiness. I saw that some poeple are wondering how to get DAZ 1.0 back.Just go to DAZ3D.com, click on the support tab,scroll down to downloads. scroll down and choose DAZ|Studio when it asks what product to download (I know it says 1.2 but trust me it's 1.0) During the installation process it will tell you that it is the old version and will prompt you to uninstall the new one.Just click okay and it will uninstall 1.2 and install 1.0 Have a good night everybody :o)

Did you create what you imported in D|S or another program? Import and export scaling is actually fairly common from what I have seen. Anytime you go from one program to another it can be a whole new process. Really annoying.I had burned a disc so I have the prior version anyway.night.

Im sorry to hear you are having problems with D/S. I guess I have been one of the lucky ones that hasnt had a single problem with it yet. I dont do anything special other then making sure my drivers are up to date. :D

Only 1.2 has apparently been this problematic.Dallas40m did you try to save a a file?

http://forum.daz3d.com/viewtopic.php?t=30892 Blame Microsoft... An out of date DLL file has been the cause of a number of crashes.

This scale problem with objects is not the old issue of different programs using different scales. The object was made in Blender using an exported cylinder prop from Studio as a size reference, it imported fine in the previous Studio. I was getting an error message about that .dll file whenever I closed PaintShop Pro but it never crashed PSP when using it so I just ignored it. I've downloaded it but am reluctant to try it.

Those are runtime dll's eventually you will have to update it anyway because they are bound to be included or installed by the developer. There has been a debate going on for sometime regarding dll handling in MS.You can just update windows for .net or wait for the D|S update.

I have had no problems opening previously saved files or saving new ones. There is a thread over at daz discussing a possible fix for some peoples crashing problems. It is the first topic in the Daz Studio forum as a Sticky. Hope it fixes your problems. :D

Any other replicatable crashes, such as geom switching and Scaling (As long a a bug report is filed) will be fixed in update 1.3. Geom Switching is confirmed to be fixed.

It would have been nice to have been told that DS required .NET dll's, most .NET dependant apps state this dependancy. And it's not a great fix, I already had .NET on my system. So the warning re 1.2 is still valid. Wait till 1.3 eventually comes out, then wait some more untill the braver ones amongst us, have destruction tested and sounded the all-clear.

I've been pretty impressed with DS 1.2 on Mac OS 10.4.4 That said, it has crashed a couple of times--more or less at random, but overall I see the improvements and like them. I particularly like being able to point eyes at the camera and have it persist when a camera is moved! Finally! Pobble

I haven't had any probs besides not being able to save to file.

I originally had the 1.0 version, but being new to D|S, I was messy (and apparently still am with the new install) I uninstalled but lost the original zip so dl'd the latest, NOT realizing it was newer. Once I installed everything it all seemed to run find, but I get occasional crashes. I can open and save just fine, its the crashes. I have to say and I don't mean this badly, I'm glad it's not just me. I thought i was having PC issues. Glad I peeked in here.

Well there are other issue pending besides the dll issue.They haven't fully stated those yet that I can see. Also, had D|S included the appropriate file to go in the D|S directory like most programs do it should have avoided this.Unless, there is a good reason to count on a shared windows file or update it, always including your runtimes in your directory is a better way to go.I think their description of the problem is confusing people.