Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Any software using Rosetta2 to run *is* running "in Big Sur"; Rosetta allows Intel versions of a program to run on a system with an m1 chip, but it's not needed for Big Sur if it's an Intel-based machine.
Poser is running in Big Sur and if the system is m1-based, it's using Rosetta2 and if it's an Intel-baseds system, it doesn't need Rosetta2.
DAZ will most likely need Rosetta2 to run at first, but they've said that if that's the case, they'll continue to develop to run native under m1 systems.
-- Walt Sterdan
Thanks, Walt. Appreciate your knowledgable info. By the way, a friend just emailed me that there's an announcement "in the forums" about a "pre-release beta version of DS 5 that will run on Big Sur. It might not initially work on M1 Macs, but that will be coming soon. The full/final version should be available at the very end of this year." He did not provide a link. So, does anyone know where in the forums this announcement might be?
https://www.daz3d.com/forums/discussion/506346/daz-studio-5-development-update#latest
Thanks very much for the link, wsterdan. I just read the first part, and then came back to give thanks. I'm going to continue reading now. Yea!
My new computer cannot run Daz studio 4.15 without crashing. The problem seems to be with OpenSSL and two dlls included with the studio installer. The OpenSSL used triggers dim and studio to crash. ssleay32.dll and libeay32.dll appear to be at issue.
These dll's of speciifc versions seem to cause all programs to crash that use them. The solution to replace them with earlier ones from openssl-1.0.2u-x64_86-win64v works, but I am wondering if there will be a fix. My pc is brand new and well within the hardware requirements to run studio. These DLL's don't appear to work with the new hardware.
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: DAZ3DIM.exe
P2: 1.4.0.67
P3: 5f2a38e1
P4: LIBEAY32.dll
P5: 1.0.2.8
P6: 573e3641
P7: c0000005
P8: 00000000000e6643
P9:
P10:
When does it crash? Also, what are the specs of the new system, i.e. CPU, RAM, OS and GPU.
It crashes or 'quits' instantly upon login to DIM or DAZ, when those versions are present in my system. The fix was to download the OpenSLL drivers to: openssl-1.0.2u-x64_86-win64 when I replace the DLL's in dim and studio with those, it works.
It does this in other programs as well, using the DLL's in question. I get varying comments, that those DLL's aren't compatible with new machines, that a windows update is blocking them from connecting, but whatever reason, those two DLL's kill my connection to studio and cause it to crash.
Operating System: Windows 10 Home 64-bit (10.0, Build 19043) (19041.vb_release.191206-1406)
System Manufacturer: Alienware
System Model: Alienware Aurora R11
BIOS: 1.1.1 (type: UEFI)
Processor: 11th Gen Intel(R) Core(TM) i7-11700F @ 2.50GHz (16 CPUs), ~2.5GHz
Memory: 65536MB RAM
Available OS Memory: 65212MB RAM
Page File: 16481MB used, 58458MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
Card name: NVIDIA GeForce RTX 3090
Manufacturer: NVIDIA
Chip type: GeForce RTX 3090
Try disabling automatic login - work offline.
Yes, I can work without using services which use those OPENSll authentication, but I would rather use the product as intended.
Studio quits before you can make adjustments.
Yes, I can however use DIM Offline.
I would prefer though to have the software work. I had no issues with my last machine. There are also others with the same issues.
I've just did a search on my system, there are approx 40 instances each of those 2 dlls. All used by various applications, and they all work.
But remember, if you are using W10 and allowing it to update at will, your environment is constantly changing, changes that were not present in your last machine when you were using it.
There has to be some other factor at work too, I am (as far as I know) up to date on Windows 10 and don't have these issues.
Maybe updates for drivers that you don't have.
Sure, they worked on my old HP as well and I have different versions of this language installed with different apps. The new machine does not work with this version of the DLL, for unknown reasons. I am not alone in this either, as others report issues in the techncial support forum.
Possibly, although, DAZ studio did not run at all on this machine before changes were made. I am curious how well the program is tested on current hardware.
I rule nothing out, but since others with new hardware are also having this issue, there seems to be an incompatibility between openssl and some hardware.
How new is your computer? My computer just got here 2 weeks ago, and has never been able to use the current DAZ Studio build. I had no problems with my one year old HP either. This machine, it simply won't run those particular DLL's.
I am also up to date on Windows 10, and don't have these problems. But I do not have new hardware. SereneNight has a brand new top of the line computer with 11th Gen Intel(R) Core(TM). nonesuch00 pointed out an Intel OpenSSL SHA crash bug for newer processors and certain OpenSSL versions. Perhaps the version of OpenSSL in Daz products and the version of SereneNight's hardware are incompatible.
Ah, nice find - that sounds plausible (my system is about eighteen months old and has an AMD CPU).
I have learned more than I want to know aboutt Openssl.... In the last week. When I too scanned my hard drive, I have about 8 versions each installed by individual apps in their own application folders.
Most software programs are using ancient SSL which actually has security vulnerabilities. DAZ studio also is not using the latest SSL either which is 1.1 The reason for this, is not clear, but 1.1 does not have the libeay file at all. It has been renamed.
The version Studio uses is also used by Topaz Labs Photo software, and causes a crash there as well.
There is something about this version of SSL which is incompatible with my hardware, and this is all I know. I opened a ticket with TOPAZ And DAZ Store.
Other have reported that DAZ Store is giving them usable DLL's and I'm waiting to hear back. So far, no response.
Just like executable files, dynamic linked libraries on Windows (and UNIX and Linux and so on) have listings of dynamic linked library search pathes where the loader//linker searches for dynamic linked libraries a program needs to run. It seems like your computer has had a global dll search path set by another program install that uses those dlls and that is messing up DAZ Studio when it goes to load those dlls. Operating systems being what they are that is the most likely cause of your program but not the only possibility.
I saw in the writeups by Intel and others about this problem that UE4 is one of the problem executables. It may well be in some circumstances but I've had UE4 and DAZ Studio installed on brand new hardware since January 2020 and not had any problems with DAZ Studio and UE4.
Does AlienWare have AlienWare bloatware installed at the factory and written by the AlienWare workers that might use openSSL? I have a circa June 2019 HP Pavilion and it is loaded with HP bloatware that communicates over the net on secure channels with HP servers. (although it had no problem with DAZ Studio either even though I've since removed DAZ Studio from that laptop). HP also installed on that laptop some spyware / adware spammy game company store software called WildFire or WildTangent or something like that that I had to remove from that laptop.
I am not a programmer, but it appears Each program installs its own version and installs it in their own individual application folders it is not the same version so it appears to be program specific. for example Adobe products use one version, topaz uses a newer one, Microsoft office 365 has its own. Daz studio installs this version which works just fine on my hp machine. If you search for the dll that is installed on your pc, your will find different versions. Even with new programs. So I think it's coming with the installs otherwise there would be a specific single version getting installed again and again.
I have not installed anything on the computer beyond windows updates, Adobe products and photoshop plugins and antivirus
I even wiped it and performed a new install of windows from the web, ignoring the one on my partition and same issue.
Interestingly all these apps use out of date versions of ssl, the current version is 1.1 and studio use 1.028 on my machine.
Like the Intel Bulletin says, effects only 10th generation (or newer) Intel Processors
I have discovered a fix for the 11th generation processor incompatibility issue here:
11th Gen Intel CPU users - Launching/Crashing Issue – Survios (zendesk.com)
So far, I have not experienced a crash while implementing this solution and I am now able to use the default installation of studio and dim without it quitting, I am not sure it will work for others, but it seems to work for me, to do this, then reboot.
you can try this:
Dependency Walker (depends.exe) Home Page
Or just study the code of how it works and then do the dll dependency walk yourself manually.
I fixed it already. See the post above yours.
Great, but those sorts of problems have been going on for decades. It's nice to have a dependable & easy tool to use.
Thank you you so much for this link. I have been pulling my hair out, installing/uninstalling, reaching out to Dell and Daz support (still haven’t heard back from them). The link you posted has the fix I needed to get DIM and Daz Central working as well as Studio. Currently downloading remainder of my library/store purchases. RTX 3060 rendered a scene in 2 min 7 seconds that took 27 minutes on old machine. Thank you again for the link to the solution.
You are welcome! I have the same card, and the same manufacturer, so it makes sense. It also had the happy result of fixing problems I was having with crashing in other apps dude to the same issue. Glad it worked.