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
Drag and Drop in the Figure Setup window isn't working.
Anyone see this problem before? Know a way to fix it?
EDIT: Oh right..just remembered..you toggle it to parametric weighs, then back to triax and the thing then works. Someone should fix that.
Because life has to be annoying, I've had to reformat my iMac and reinstall everything fresh.
CAN Daz Studio be just copied from the old backup over, or does it need to go for a full reinstall?
I've been doing OK with the 4.9 public release beta, and am considering upgrading 4.8 to release version 4.9. My configuration is kind of a mess (notably, the application lives in my home directory, not /Applications), so this might be a disaster in the making.
So my question is: what is the complete list of things I need to back up in case I want to go back to 4.8? Not just the content folders, those are probably the least of the problems, but stuff in $HOME/Library, the root /Library, and … ?
Wow, so nice of you. Thank your for the guide.
hey,
i got a question, i have daz on a pc and on the mac. on the pc evertything works fine.
but on the mac not, when i open keiko or aiko, the charaters doesn´t come as they have too look like. and pretty much with every genesis 2.
the 2 genesis i reinstalled still the same. so last time i had made a charater on the pc with keiko and saved and opened it on the mac, too my suprise it opened as keiko has too look. but as soon i hit save file it turned back too the old thing that doesn´t look anything as keiko.
has anyone i idea or so. i´m tottaly noob too mac´s with this can´t of things.
oyeah i installed bathany 7 last time and that one work fine.
Hi. Im considering buying a new power book mac 13" to run Daz. Does it run ok on the latest offerings? Are there any configurations to avoid? Any other considerations I should be aware of? Thanks for any info.
You'll have trouble getting enough of the Daz on screen . . . if you use an external monitor, it might be OK. I find my 15" fairly cramped, personally I can't see it being comfortable on a 13" . . . so many palettes and things you want open.
Hello!
This is a quite long discussion already. I dont know if this topic was raised before. I am new on Daz3D Version 4.9.2.70 on a MacBook Pro Mid 2015. Unfortunatly is keeps crashing constantly. I am not even able to do the Tutorials.
Regards
Hello,
A couple of questions to establish the reason.
(1) Which version of OS X are you running?
(2) How did you install, via DIM or via the BitRock installer?
(3) Did you allow DAZ Studio to open network ports when the firewall asked for it or didn't you get any questions abut that?
(4) Where is you content installed? Look under Preferences, Content... -> Click the Content Directory Manager button (open up the tree and take a schreenshot (CMD+SHFT+4) hit space and select the window and open the screeshot and resave as jpg and post here
(5) Did you install additional content using DIM or manually?
(6) What do yo do when it crashes? Render? Work in Viewport? If render, is that nVidia Iray or 3Delight render engine?
Hello,
A couple of questions to establish the reason.
(1) Which version of OS X are you running?
El Capitan 10.11.16
(2) How did you install, via DIM or via the BitRock installer?
DIM
(3) Did you allow DAZ Studio to open network ports when the firewall asked for it or didn't you get any questions abut that?
There was never any question
(4) Where is you content installed? Look under Preferences, Content... -> Click the Content Directory Manager button (open up the tree and take a schreenshot (CMD+SHFT+4) hit space and select the window and open the screeshot and resave as jpg and post here
https://www.dropbox.com/s/2b8ua009uolq13s/Screenshot 2016-09-20 10.34.32.png?dl=0
(5) Did you install additional content using DIM or manually?
No. I am still trying to do the tutorials
(6) What do yo do when it crashes? Render? Work in Viewport? If render, is that nVidia Iray or 3Delight render engine?
Viewport.
As Example: When I do the tutorial: "Day at the Beach" at the step "Modifying the Bikini Bottom Strings" the application crashes at the moment when I do any change and release the slider. This happens when I do that in the tutorial and also when I try the same without the tutorial.
Here is a screenshot: https://www.dropbox.com/s/n33gk99wkd7iqtd/Screenshot 2016-09-20 10.45.31.png?dl=0
(Tried to fix the quote.)
Sorry for the late reply, been busy.
Are you using OpenGL preview or nVidia Iray Preview?
I just loaded that SET up and played with the adjustment sliders and no crash, but did it in OpenGL (your screenshot do look like OpenGL though)
Hello,
I'm using 4.9 on a Mac so configured:
Os X 10.11.5 El Capitan
Mac Pro (half 2010)
CPU 2,8 GHz Quad-Core Intel Xeon
RAM: 32 GB DDR3 a 1066 MHz
Graphics ATI Radeon HD 5870 1024 MB
and the renders, except when using "Basic Open GL" do make Daz crash (even with the optimizations for Iray turned off)
Here's the latest crash report:
Process: DAZStudio [22795]
Path: /Applications/Grafica : visualizzatori/*/DAZStudio.app/Contents/MacOS/DAZStudio
Identifier: com.DAZ.DAZStudio
Version: 4.9.1.30 (4.9.1.30)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: DAZStudio [22795]
User ID: 501
Date/Time: 2016-09-26 17:46:57.173 +0200
OS Version: Mac OS X 10.11.5 (15F34)
Report Version: 11
Anonymous UUID: 897CDCC7-9738-D0EE-445A-9381AF3E0A1D
Time Awake Since Boot: 450000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
VM Regions Near 0:
-->
__TEXT 0000000100000000-0000000100002000 [ 8K] r-x/rwx SM=COW /Applications/Grafica : visualizzatori/*/DAZStudio.app/Contents/MacOS/DAZStudio
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libdzirayrenderer.dylib 0x0000000119f7e718 mi::ISint32* mi::neuraylib::IAttribute_set::edit_attribute<mi::ISint32>(char const*) + 16
1 libdzirayrenderer.dylib 0x0000000119fa0222 DzUberIrayMaterial::setMaterial(mi::neuraylib::INeuray*, mi::neuraylib::ITransaction*, mi::neuraylib::IFactory*, IDzIrayMaterial::SetMaterialInfo const&, IDzIrayMaterial::SetMaterialOut&) + 472
2 libdzirayrenderer.dylib 0x0000000119f5fd2b DzIrayRenderGroup::Data::createMaterial(DzNode*, DzTSharedPointer<DzMaterial>, IDzIrayMaterial::DisplaceData&, mi::neuraylib::INeuray*, mi::neuraylib::ITransaction*, DzFacetShape*, QList<QByteArray>&, QColor&, DzMaterial*, DzMaterial*) + 1467
3 libdzirayrenderer.dylib 0x0000000119f62d58 DzIrayRenderGroup::Data::renderNode(mi::neuraylib::INeuray*, mi::neuraylib::ITransaction*, DzNode*, QList<QByteArray>&, QList<QByteArray>&, DzRenderSettings const&, mi::neuraylib::IGroup*, QByteArray) + 4072
4 libdzirayrenderer.dylib 0x0000000119f6819d DzIrayRenderGroup::Data::renderNodes(mi::neuraylib::INeuray*, mi::neuraylib::ITransaction*, QListIterator<DzNode*>&, QList<QByteArray>&, QList<QByteArray>&, DzRenderSettings const&) + 673
5 libdzirayrenderer.dylib 0x0000000119f683bb DzIrayRenderGroup::Data::setupSceneRoot(QByteArray&, mi::neuraylib::INeuray*, mi::neuraylib::ITransaction*, DzIrayPropertyHolder*, QListIterator<DzLight*>&, QListIterator<DzNode*>&, QList<QByteArray>&, DzRenderSettings const&) + 247
6 libdzirayrenderer.dylib 0x0000000119f68a58 DzIrayRenderGroup::buildGroup(mi::neuraylib::INeuray*, mi::neuraylib::ITransaction*, DzIrayPropertyHolder*, QListIterator<DzLight*>&, QListIterator<DzNode*>&, DzRenderSettings const&) + 62
7 libdzirayrenderer.dylib 0x0000000119f68bb8 DzNeurayMgr::getGroup(mi::base::Handle<mi::neuraylib::IScope>&, QListIterator<DzLight*>&, QListIterator<DzNode*>&, DzRenderSettings const&, bool) + 328
8 libdzirayrenderer.dylib 0x0000000119f0cd5b DzIrayRenderer::renderFrame(DzRenderContext&, DzRenderHandler*, DzCamera*, QListIterator<DzLight*>&, QListIterator<DzNode*>&, int, bool, DzRenderOptions const&, QStringList&, DzIPRContext*, DzIraySnapShot*) + 495
9 libdzirayrenderer.dylib 0x0000000119f1062b DzIrayRenderer::doRender(DzRenderHandler*, DzCamera*, QListIterator<DzLight*>&, QListIterator<DzNode*>&, DzRenderOptions const&) + 2719
10 libdzirayrenderer.dylib 0x0000000119f10bd2 DzIrayRenderer::render(DzRenderHandler*, DzCamera*, DzRenderOptions const&) + 136
11 libdzcore.dylib 0x0000000100b58096 DzRenderDataEvent::~DzRenderDataEvent() + 29180
12 libdzcore.dylib 0x000000010021cd65 DzScriptAction::Data::Data(QString const&) + 1521
13 QtCore 0x0000000102cf3131 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 2001
14 QtGui 0x0000000102f838a2 QAction::activate(QAction::ActionEvent) + 194
15 QtGui 0x00000001032f3151 QAbstractButtonPrivate::click() + 141
16 QtGui 0x00000001032f336c QAbstractButton::mouseReleaseEvent(QMouseEvent*) + 106
17 QtGui 0x00000001033b23a6 QToolButton::mouseReleaseEvent(QMouseEvent*) + 18
18 QtGui 0x0000000102fd83f0 QWidget::event(QEvent*) + 334
19 QtGui 0x00000001032f2456 QAbstractButton::event(QEvent*) + 220
20 QtGui 0x00000001033b1f92 QToolButton::event(QEvent*) + 54
21 QtGui 0x0000000102f878b8 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 304
22 QtGui 0x0000000102f88348 QApplication::notify(QObject*, QEvent*) + 2666
23 libdzcore.dylib 0x000000010025a323 DzAiffImporter::~DzAiffImporter() + 36101
24 QtCore 0x0000000102cdd7e2 QCoreApplication::notifyInternal(QObject*, QEvent*) + 104
25 QtGui 0x0000000102f8fffe QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) + 432
26 QtGui 0x0000000102f3edb3 qt_mac_handleMouseEvent(NSEvent*, QEvent::Type, Qt::MouseButton, QWidget*, bool) + 995
27 com.apple.AppKit 0x00007fff920f0713 -[NSWindow _handleMouseUpEvent:isDelayedEvent:] + 119
28 com.apple.AppKit 0x00007fff920f13ad -[NSWindow _reallySendEvent:isDelayedEvent:] + 212
29 com.apple.AppKit 0x00007fff91b30539 -[NSWindow sendEvent:] + 517
30 QtGui 0x0000000102f365a2 -[QCocoaWindow sendEvent:] + 114
31 com.apple.AppKit 0x00007fff91ab0a38 -[NSApplication sendEvent:] + 2540
32 QtGui 0x0000000102f3a07e -[QNSApplication sendEvent:] + 94
33 com.apple.AppKit 0x00007fff91917df2 -[NSApplication run] + 796
34 QtGui 0x0000000102f42b77 QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 879
35 QtCore 0x0000000102cdab68 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 394
36 QtCore 0x0000000102cddf33 QCoreApplication::exec() + 175
37 libdzcore.dylib 0x000000010025b1ec DzAiffImporter::~DzAiffImporter() + 39886
38 libdzcore.dylib 0x0000000100274339 DzAiffImporter::~DzAiffImporter() + 142619
39 com.DAZ.DAZStudio 0x000000010000147a main + 506
40 com.DAZ.DAZStudio 0x000000010000117c start + 52
Under 4.8 everything with the renders worked fine; I woul downgrade, if possible, but I don't have the former version file executable anymore (stupidly, didn't back it up before upgrading).
Suggestions?
Thanks,
Flaminia
Crash inside Iray, if you render using 3Delight, do you crash then?
Doesn't crash, but all I get is a completely black picture :'-(
3Delight Requires lights, like for example UberEnvironment2, or it will be dark.
Verified with a scene I formerly had working renders of: still working only with Basic Open Gl.
Do you say that it crashes with 3Delight or still dark with 3Delight after adding an UberEnvironment2 light?
Still Dark with 3Delight in the old scene; to the new scene I'm using I added a "new distant light" and a "new spotlight" with default settings.
May it be some problems with installations paths? Didn't change anything manually from the former version, but I have have software files on a hard-drives and Users file on another for matter of backups, could this intefere someway?
The Iray crash, what are the elements in the scene? Is it by any chance TerraDome 3?
paths usually won't create crashes, they yiou create "missing object greay meshes"
The elements in the new scene are these:
MRLN Birch tree
ATC_ground
AC_TIsky
Genesis 2 male
AI Shirt
Genesis 2 male (2)
TnC_pants
WildMane hair
Olympia
F40s Pumps
Jewel hair
Distant Light 1
SpotLight 1
I attach the OpenGl render
Hi people there. I running Studio (not now because of many problems i trying to solve with my mac-not with Studio) only at Mac's from start since some years now.
As i see till now with my little experience and some knowledge with mac hardware the problem is with version of OSX not with hardware of macs.
I have 2 imac's one with Snow Leopard and one newer. With old one i never had problem since Daz decided to add Iray feature. So i decided to buy a newer model with nvidia card thinking that will be running Daz iray...But no...Anyway to not fill whole pages the problem is with video card of macs and temperatures. Must be very careful when running iray renders.Can easily destroy internal parts because of high temps and because of unsufficient air flow. This can be easily corrected but with video card is a mess.To go back to versions of osx it looks to me that Yosemite is better. I tried a lot with El capitan but no luck especially when scrolling the viewport with heavy scenes.When i say heavy i mean some trees a terrain with grass and a house..Cannot even move the viewport... tried also same scene under 3d delight and almost same results.
i didnt had such problems with Snow Leopard and older imac.
Also as i have seen till now the originals hard drives of my imacs were both so slow and they needed replace and cannot this happening to both models..and they both bought new.
New models looks that they have problems with open gl....Sometimes when Studio running looks that they are the worst machines on the planet even if their specs are high and sometimes running well. i really dont know how to explain this.
Both models have almost same hardware except video card and the new one with problems have more vram memory! i cant install Snow Leopard in newer one to see what will happen but even if i could then i will not have thunderbolt ports because SL does not support them.
So my only option is to put an external video card via thunderbolt and see the results...
Sorry for long post just wanted to share my experience and maybe someone give an idea :) Thank you
I Wanted to add that it looks the 4.8 version of studio running better than 4.9 at mac. At least to me
At least a couple of Mac users have bought basic PCs, with decent power supplies and a good nVidia GPU card, to use purely as a render machine while doing all the posing and development on their Macs - it has the advantage that the mac iss till fully usable while the render is going on, even if it drops back to CPU due to size. It does require double installation of content, or using a networked location.
Not any Apple hardware with built in Graphics comes even close to what Iray needs. I use an old Mac Pro (2012) with nVidia card in as my render machine
Has anyone tried Studio with Sierra (the new OS update)? Most of the programs I work with are fine with it from what I've noticed (Adobe CC, Clip Studio Paint), but I'm hesitant to update unless I know Studio works reasonably well with it. Only reason why I ask is b/c Mac users tend to get short thrift compared to PC users from what I can tell/experience (especially with plug-ins, oi vey), so I want to make sure 4.9 is fully compatible /w Sierra before updating my iMac.
I will try that on a machine but I haven't upgraded yet.
Thanks for the reply Dear Totte :) I Dont know why but its the first time that i didnt get a notification for the reply. Yes it looks like that but my old imac with amd card and less vram ( 512mb) was much better than my new one with nvidia and 4 gb vram..!! Strange yes? So i think that the problem is the OSX version...
At my old imac i was able to do animations with studio too...but with old version (4.7) Now im stuck with new one.Anyway i trying to see what is going wrong.
Of course big difference is when the cuda and web drivers are installed.The default nvidia drivers are very old and as i saw Apple still using same drivers since Yosemite...Maybe thats why Yosemite running better with studio..i dont know ! Ok the main problem is not the render..its the way that viewport working.
I dont want to go to windows after XP because of the bad inteface and the bad firewall they have.Also they have so many security holes due to so many applications for internet..and these are tottaly useless for working with studio...
i guess you have the alu tower yes? This is good but for how long? As i was searching for this i found that the pci connector to these cannot accept new video cards like titan x because new cards need pci 3.0 version....and old mac pro they have till 1.0?
Thanks for the suggestion dear Richard but i dont want to buy a new computer running windows .Was good with Win XP but i dont like new versions of windows at all..And they cahnging operating systems every year now.
I want to do all in one suitable computer and i think that macs are far better than current windows.. The only problem they have is the video card...and the open GL sometimes open CL too.
i dont have render problems even with iray. My problem is with studio viewport and i dont understand why is so slow to render the scene! Whts the difference between rendering the scene as a file and rendering scene at viewport?
Sierra is new one and is better to leave it for a while since most of the times they new releases have problems..Also does not have good disk utility like Yosemite and some features from El Capitan removed. Now the permissions and checking disk are automatically when updating... and who knows what else...Anyway..
AMD cards cannot be used at all with Iray as HW, so it relies only on CPU (where CPU cores and RAM is the factor)
4GB VRAM is the mimimum for using Iray, but should work.
The main issue is that Viewport (OpenGL), Windowserver Window backingstore and Iray is fighting in the same crowded 4GB space, but have you configured your new machine (Video settings) and enabled performance optimizations? This do a real difference.
If you put a 3.0 card in a PCI 2.0 or 1.0 slot it will step down. My son runs a GTX-960 (which says PCI 3.0) in his PCI 2.0 Mac Pro 2012 with no problems (the only issue is when playing games where the BUS speed limits the theoretical performance uploading stuff to the card, but that's about. I don't really think Titans are the best cards. The new 1080 does give a lot of bang for the buck with 8GB VRAM, but it's still unclear when they will be supported in Iray though, but according to the forums at nVidia it's happening, but no timeframe really yet.
I hope this cleared something out.
Yes..very helpful :) I like so much when conversation are inside the subject and the person knows what it says!!
i have done that setting you refer Totte , but not so much difference...anyway So if i understood well this you saying is that Studio viewport using CPU and render using the GPU?
Also i wanted to ask you as i saw before you said something for the terra... i bought it..i will have problems?