Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Yes, but the first developer and public beta was available since june 2018 and DAZ is aware of the crash(ticket submitted) since this date...
I think the main issue is the difference between "being aware of it" and actually get a machine up for testing, test it, and debug it, and also at the same time not break the functionallity of of the current os version. I know it sounds stupid, but sometimes things are like that, time and resources.
Since which date? They are aware of the issue with the release version of Mojave (obviously) but only the testers, if they had a Mojave beta (and I'm sure Daz at least did) could know if it was crashing previously, or when the issue was first uncovered and reported.
....now I keep getting a "not responding" error. It's been showing this for the last 15 minutes.
Just before this when I tried to change directory targets, it went into an extended search process that wouldn't end.
Tried it again after a full shutdown and start and still the same, it just freezes.
Now going on almost 30 min.
Ended up having to shut it down through Windows Task Manager.
This is totally stupid,. I've never seen it take this long to open up.or change tabs.
__________
After nearly an hour of no response, ended up uninstalling it and installing a new copy., Still the same situation.
Looking at the Ready to Download tab it still shows items I already downloaded and installed, but not any of the updated files.
I just needed to go to the Daz3 folder to install some updates to older content when this rubbish all began.
This is just total garbage.
Did you change or did you not change? Do you mean for installation, or the Downloads dirctory, or editing the .ini file to chnage the Manifests folder? Have you tried starting with the Work Offlien option?
Totte, like you I'm a developer (for 32 years on mainframes IBM and later on PC and Macs) and deployed hundreds of applications for thousands of users for worldwide companies.
I think it doesn't give me more credit than other people as a user (Bought only 6532 products on DAZ Store) and don't want (and hate) controversy but I have my opinion:
-Even if Mac users are 1% of the market, as soon there are people making products for them, they must be aware of new major OS versions of it, and have time and resources to install Mojave beta
and their main products on a Mac to give them a try.
-Doing this, one has not to wait for a ticket to see that the products simply doesn't launch at all and will not work 4 months later so it must become HIGH priority and all other dev have to be halted until this one is resolved !
-Not doing this, some companies I was talking about precedently would have been in great difficulties...(what happen when you can no more buy or sell products, work with your bank and so on ?)
=> Since 2018/09/24 i.e 2 weeks from now, 50%(Mojave rate adoption) of mac users can no more use DAZDIM and/or are forced to use DAZ Studio 4.10.0.123.
This is what I have done as a user 2 months ago (DAZDIM Ticket on 2018/8/1) and what some other users have done(see forums) please have some confidence.
While I appreciate DAZ help and transparency : http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_11_0_235 ,
it seem to me that the problem is because of various cost(as Tottle said) regarding of numbers of impacted users, some have minimized the risk (analyzing comments in this forum).
After all, the victims are from a small and not so important community: Mac users, and DAZ is not the only one... :-(
I promize to stop this useless controversy and apologize for this, maybe I'm wrong, it is just frustration so I will no more post in this forum.
Sorry for my bad English,
Regards from France.
...never edited the .ini.
The situation occurred when I was switching targets to install Poser and some older content that used the "Content/Runtime" structure that was recently updated.
Downloads are set to go to a folder named "Install Backup" on my D drive. Everything had been working fine prior to last night.
After did a clean install of the DIM and restarted it the programme itself seemed to have trouble loading that folder in the "Ready to Install" tab. Instead of all the downloaded files (I keep them as backups so I don't have to re-download them again if something breaks), I only got a handful of items showing and the progress meter in the upper right corner stalled for a long time then started for a moment and stalled again as it slowly loaded more items in. Never saw this behaviour before. I let the process run overnight only to find this morning it crashed. After shutting down and restarting my system to clear buffers, checking the events log, and running a cleaner utility, I first started it in offline mode to check settings and filters. This time it appeared to be loading the saved downloads correctly (but still slowly) however when it finished all I saw in the tab were 10 items.
I checked the download path again and it was correct after which I went to the folder on the D drive to look at it. When I clicked on it the folder wouldn't open and an error message popped up that mentioned it was either "corrupted or unreadable".
Not sure how that would have occurred or how it can be fixed.
I also noticed all the items I downloaded and installed last night as well as other items I installed in the past (that were also listed in the "Installed" tab) were all showing in the Ready to Download tab.
How did you know DIM would crash 2 months ago? Or did you report the need for a 64 bit version, which Daz was aware of and working on? Daz has usually been able to develop Mac and Windows versions in step (there was a delay on the Mac 64 bit DIM as I recall).
...again is there any way to fix that folder or do I just delete it and create a new one?
One thing I did notice while sifting through the event logs was a defrag operation was initialised sometime in the middle of the night. Not sure though that probably would be the reason because it wasn't a long drawn out process by the start-stop time stamps (defragging a large drive usually takes hours) and like I mentioned the Ready To Download tab was having trouble showing all the files that are in the folder last night as well as this morning. So not sure when or how the corruption could have occurred.
How far does it get - do you get the account choice box?
...when I first open the DIM? Yes.
I get the complete listings in the Ready to Download and Installed tabs, but only seven items show in the Ready To Install Tab: four of them Bryce content (not sure where to direct that) A couple Legacy files, and a Poser (Ps) file for Sylphiad Hair Which when i clicked Install it kicks back an "Install Failed" error even though I have all Poser as well as Daz 3.0 filters selected..
-I said previously I don't want controversy (in fact I started it) and that I will leave this forum, but I can see it was not clear and you ask for justifications so:
-DAZ have announced the disponiblity of DIM 1.1.0.100 32/64bits for Mac on June 25, 2018 and DIM 1.1.0.98 32/64bits on June 4,2018 (page 1 of this forum).
I have downloaded and installed both of them on my production Mac with High Sierra and also later (manual install) on my Dev Mac with Mojave beta 3 (build : 18A326h) released on 2018/07/11 where it crashed at launch...
-So I knew that DIM was crashing since July 11,2018 i.e more than 2 months ago !!! >>> I opened a ticket (2018/08/01) and the answer was something like "we don't support OS betas" and I resign.
-I didn't report the need for a 64bits version because THIS is not the problem: I use it and it was working well for me(the 32 bits version too) with High Sierra and because it is NOT related to the crash:
>> The version of DIM 1.1.100 (32bits or 64bits) IS related to the crash: DIM 1.1.0.72(32 bits) is still working fine with High Sierra, Mojave betas(all of them) and Mojave public release 10.14 (build : 18A391).
I saw in several DAZ forums people saying 32bits applications are no more supported in Mojave and it's FALSE there is only an alert:
Mojave is the last Apple MacOS to OFFICIALY support 32bits applications: https://support.apple.com/en-us/HT208436
When something is not working as expected I prefer to open a ticket rather than asking help in forums because this way the developer is directly informed.
When the developer doesn't/can't give help, or ask me to debug for them(doing the job for them), I ask in forums.
When in forums it turns in endless discussions before DAZ is informed, I prefer to leave.
Hope it's clear this time, Sorry.
...OK new development.
I received a warning of a possible drive failure on drive D: earlier this evening which made me wonder if that wasn't the culprit in why the DIM was loading so slowly and why the folder teh DIM sends downloaded content filed towas corrupted.
I attempted a back up but after it finished something apparently didn't work right as it should have taken up more space on the backup drive than indicated.
As a test, I opened teh Daz Daz programme (had to rebuild my menu panes as for some reason, only the viewport with the Render settings and Scene tabs appeared on the right display with nothing on the left). After setting that up I was able to open a scene and even select content (all which are on D: as that is the larger drive) with no trouble at all. I then created a new folder for downloads, pointed the DIM to it (bypassing the corrupted one), then downloaded and installed the remaining Poser content files that didn't install Saturday evening when the DIM began experiencing issues. .Everything worked fine and the content files populated the new folder correctly.
Now the dilemma is what to do with the old corrupted folder. Because there are files in it I cannot delete the folder however I also cannot open it to batch delete the files it contains, so it is just wasting about 60 GB of drive space.
I am told that there was no crashing with the Mojave beta for the Daz developers. A bug, even a crash bug, that cannot be reproduced cannot be fixed. It may be that for some reason your system(s) was more vulnerable than were theirs - perhaps an add-on, perhaps a configuration settings, perhaps simply the order in which things were done, but it certainly wasn't a case that Daz was ignoring a known and reproducible issue. CS saying they cannot support betas means just that - CS cannot support betas as they are not final and pinned down current versions; it doesn't mean that the developers are not aware of, and testing on, beta versions of the OSes.
Latest macOS Mojave user here. Installation went fine until first launch via the installer. Here an error dialoge says: "LSOpenURLsWithRole() failed with error -10810 for the file /Applications/DAZ 3D/DAZ3DIM1 64-bit/DAZ3DIM.app.".
When trying to run the program via Terminal, same exception occurs. When trying to launch it via Spotlight/Icon, just nothing happens (i.e. no startup error displayed).
I've had Mojave since Friday and the DIM crashes. I have to download my files within DAZ Studio or put them away manually.
Updated DIM: https://www.daz3d.com/forums/discussion/282546
Sounds good. I guess I'm in the minority here, but DIM has always worked fine for me; I've never had a problem. Adding more download slots sounds like a nice idea, though. Thanks for the info.
The bug was with DIM 1.1.0.100 on Mac with Mojave, not with "My system: i5 6600 quad-core 3.3Ghz, 16 Gb ram, Gtx 1080ti, Gtx 770, Windows 7 Ultimate"
Regards.
That's cool. I know not every update is for everyone. I just see so much anger towards DIM in the forums, I wanted to show it some love.
I'm new as anewly created embryo & as dim with 3d... thus patience req'dwith this -
How can I delete ALL of my ancient d'loads in DIM, start with a clean plate/comp?
Please