Daz 3D is part of 
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.Daz 3D is part of
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Thanks! So although there is a DIM link for the beta in my product library, that is defunk because it doesn't do anything. Is that right. In other words, the BETA can't be had anymore. Is that correct?
figured it out ..... just needed to follow the instructions on the download page .... little circulocutuos, but figured it out.
Did you ever "buy" the beta in the Daz Store? It is free, but you have to "buy" it to add it to your product library. To get it to show in DIM, you also need to enable the download filter for the Public Build.
after the update also stopped working iray . The second day I can't work. The second day I can't work. Can I install version 4.10 again?
I got the idea that it would be something that involved the aux viewport when reading the post.
So I let the aux viewport stay open when I shut down - and voila the shutdown was complete !
Tested on Beta also with the same result.
Emptied scene and same renderer on both viewports - but I dont know if this is necessary.
See http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_14_1_11 - you can leave the Aux Viewport closed as long as it isn't set to show the IPR toolbar (so open it if you've been having the shut down hang, open the option menu - the lined button in the top corner or right-click the tab - and uncheck the toolbar, then you can close the pane and leave it closed)
You need to update your GPU driver, assuming you aren't using a device that is no longer supported. 4.14.0.8 requires a driver version of 451.06 or later. If your GPU is no longer supported you can open a support ticket to request an older version of Daz Studio.
thanks, i already installed the old version. i had old installation files, luckily! I will try to follow your advice, update drivers
I checked my logs today and I am getting some weird things happening. This is excerpt is right after the file starts to render. I am on the latest everything
Running 2080ti FTW3 Ultra overclocked to 7500 on Memory and 2085 on the gpu clock. Everything seems ok but these server errors are concerning. Let me know if I need to do some changing.
2020-11-17 03:54:12.172 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : Initializing light hierarchy.
2020-11-17 03:54:12.173 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : Light hierarchy initialization took 0.001s
2020-11-17 03:54:12.174 Iray [VERBOSE] - IRAY:RENDER :: 1.11 IRAY rend stat : Lights memory consumption: 772.000 B (device 0)
2020-11-17 03:54:12.177 Iray [VERBOSE] - IRAY:RENDER :: 1.11 IRAY rend stat : Material measurement memory consumption: 0.000 B (GPU)
2020-11-17 03:54:12.184 Iray [VERBOSE] - IRAY:RENDER :: 1.11 IRAY rend stat : Materials memory consumption: 157.902 KiB (GPU)
2020-11-17 03:54:12.353 Iray [INFO] - IRAY:RENDER :: 1.10 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Scene processed in 3.061s
2020-11-17 03:54:12.370 Iray [INFO] - IRAY:RENDER :: 1.10 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Allocated 600.030 MiB for frame buffer
2020-11-17 03:54:12.370 Iray [INFO] - IRAY:RENDER :: 1.10 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Allocated 1.688 GiB of work space (2048k active samples in 0.000s)
2020-11-17 03:54:12.377 Iray [INFO] - IRAY:RENDER :: 1.10 IRAY rend info : CUDA device 0 (GeForce RTX 2080 Ti): Used for display, optimizing for interactive usage (performance could be sacrificed)
2020-11-17 03:54:13.131 Iray [INFO] - IRAY:RENDER :: 1.10 IRAY rend info : Allocating 1-layer frame buffer
2020-11-17 03:54:13.435 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00001 iterations after 4.144s.
2020-11-17 03:54:14.244 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00002 iterations after 4.953s.
2020-11-17 03:54:15.035 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00003 iterations after 5.744s.
2020-11-17 03:54:15.822 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00004 iterations after 6.531s.
2020-11-17 03:54:16.613 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00005 iterations after 7.322s.
2020-11-17 03:54:17.393 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00006 iterations after 8.101s.
2020-11-17 03:54:18.196 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00007 iterations after 8.905s.
2020-11-17 03:54:19.095 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00008 iterations after 9.804s.
2020-11-17 03:54:19.843 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00009 iterations after 10.552s.
2020-11-17 03:54:20.635 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00010 iterations after 11.344s.
2020-11-17 03:54:21.417 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00011 iterations after 12.126s.
2020-11-17 03:54:22.914 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00013 iterations after 13.623s.
2020-11-17 03:54:24.470 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00015 iterations after 15.179s.
2020-11-17 03:54:25.895 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00017 iterations after 16.604s.
2020-11-17 03:54:28.064 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00020 iterations after 18.773s.
2020-11-17 03:54:28.822 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: HTTP/1.1 400 Bad Request
2020-11-17 03:54:28.822 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: Date: Tue, 17 Nov 2020 09:54:29 GMT
2020-11-17 03:54:28.822 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: Server: Apache
2020-11-17 03:54:28.829 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: Vary: Accept-Encoding
2020-11-17 03:54:28.830 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: Content-Length: 226
2020-11-17 03:54:28.830 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: Connection: close
2020-11-17 03:54:28.837 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: Content-Type: text/html; charset=iso-8859-1
2020-11-17 03:54:28.837 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection:
2020-11-17 03:54:28.837 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
2020-11-17 03:54:28.843 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: <html><head>
2020-11-17 03:54:28.844 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: <title>400 Bad Request</title>
2020-11-17 03:54:28.844 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: </head><body>
2020-11-17 03:54:28.851 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: <h1>Bad Request</h1>
2020-11-17 03:54:28.858 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: <p>Your browser sent a request that this server could not understand.<br />
2020-11-17 03:54:28.858 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: </p>
2020-11-17 03:54:28.867 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: </body></html>
2020-11-17 03:54:28.867 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0
2020-11-17 03:54:30.388 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00023 iterations after 21.098s.
2020-11-17 03:54:33.242 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00027 iterations after 23.951s.
Yes, I saw that last night - I have sent in a query. My guess would be that it is related to the store software change in some way.
I'm getting those "unknown command" errors also, followed by "Metadata update failed".
I guess Octane does not work in Beta. It shows up in the standard release but not beta
I guess you didn't *install* it in the beta. Check under C:/program files/..../plugins
It might work if you simply copy the octane plugin folder from release to beta (not sure).
What I find particularly annoying is that it turns out that during a dForce simulation DAZStudio queries the DAZ cloud once every minute:
I guess I could pull my RJ45 and see what happens, but I don't want to have to do things like that.
If Daz Studio is connected (which is always your choice) it will poll to get updated data; how often is, I think, controlled by an event timer - but of course the main loop has to be processing events for that to be acted on.
Good point. I have always avoided "work offline" because I figured it might cause something not to work... However I use the log file a lot to determine stuff like correct collision offsets and the DazConnect pollution is now very annoying so I'll just work offline from now; I use DIM for content download.
This does show a problem with -instanceName; it would appear that with -instanceName DAZStudio ignores the "startup" settings in preferences, so I can set the prefs to prevent login just fine if I don't run with -instanceName but as soon as I do every instance insists on logging in, and not loading my startup file... Some validation is required before I report a bug because I have two instances running at present with multi-hour Iray renders.
There are other command line options which control which settings, if any, an instance reads Daz Studio Pro 4.12 - instances
It was my error; I used the beta version to save the settings but the instances were of the general release...
I woould bet those go away if you work offline. At least for me, getting metadata updates isn't a real concern. I don't use Connect and i don't use Smart Content. I recognize that this might be a bigger issue for some.
I cannot even install previous versions of Daz on Big Sur.
Anyone with any tips be nice....i really dont want to move on from Daz
Big Sur is not supported at the moment.
not even older versions of Daz? I really really dont want to wait till Mid 2021? I am sure others have expressed frustration but I mean this was not exactly a surprise that it was coming
Big Sur support requires a newer version of SDK for DS, one using QT5 - This means that some plugins will no longer work, and they cannot be made to work not on MAC and not on PC.
It is a major change and that kind of change is never fast.
One of the reasons it is better to wait before jumping to any upgrades and/or new technology
But fixing it is going to force changes to the plug-in interface which means that existing plug-ins will stop working, on both Mac and Windows. Some will be updated but others will not, for various reasons. I don't know if that mid-2021 was for a final release, perhaps at the end of a cycle of Public betas, or was the earliest even a beta was expected.
They do go away and, indeed, Daz starts significantly faster for me. It doesn't update the metadata, but so what, I use DIM - doesn't it do that?
Older versions have the exact same problem as this one, they rely on libraries which don't work anymore with Big Sur.
Same here. Mid 2021 is way to far - especially if you are planning to buy a new M1 based Mac, that can only run BigSur.
It would be very interesting to hear any DAZ comment on running on the M1.
Of course the M1 is an excellent reason to release a version now which supports BigSur, i.e. a native version, but I'm not sure Qt is available native on M1 yet; it shouldn't be a problem, I've run KDE on a raspberry pi, gee, I've built KDE on an RPi :-|
Anyway, move to Qt5 at the same time; I'm continuously impressed by Qt's major releases, they aren't like other guys major releases, they do actually do something useful rather than look pretty and fall over. I'm not being in the slightest bit sarcastic or even ironic here; the M1 is a really good reason to step away from legacy. Anyway, remember what the CPU is[are] in all those NVidia GPUs.
Apropos of nothing, it would be good if Daz updated the user facing information about beta builds before, or even, subject to the Whim of the Web, at the same time as, new releases.