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
Well that didn't work. It said it was installing, then came up as installed failed but stayed in Ready to Install. I tried to install it from there, it said it was installing but finished very quickly. Now it says 4.15 is installed but when I try to view the installed files in DIM it doesn't show any, and I still have 4.14 release installed.
That indicates that DIM did not install DAZ Studio; DIM creates the ManifestFiles .dsx when it installs the product. In a DIM setup the first step is to download DIM which then downloads and installs everything else. IRC DAZ Central does the same and creates ManifestFiles/*.dsx too, but I don't use it - I only use DIM, no DAZ Central, no DAZ Connect.
You should go to DIM setup and choose "Default Install Sets..." from the menu. All the entries apart from PostgreSQL should either be in green or marked as optional. PostgreSQL might be green or yellow depending on whether you have the Release or Beta installed - at present it doesn't matter which you use but only one can be installed at once. Check for anything else that is missing and not optional; DIM won't see updates to whatever version of these you do not have installed, it will just see them as "new".
When I checked in DIM, Daz Studio 4.15, Inreractive Lessons, Secret Garden Shaded Havens and Daz Studio Iray HDR Environments were red, everything else was green and nothing marked as optional.
I then had aanother thought. I've been using Studio earlier so I checked in task manager and Daz Studio was still running as a backgrounf task. I've seen this before when I can't start Studio again after quiting. So I stopped the process and tried the install again and this time it worked. The only thing it didn't do was update the desktop icon, this still says 4.14 but when I run it I get 4.15.0.30
Is it just me or is this new version more laggy? Moving and posing the characters is noticeably more laggy than it was before the update.
Is anyone else having issues with Daz crashing? If I try to use Iray Viewport or render in Iray, it crashes instantly without any error message. Using an NVIDIA GTX 1060 that is fully updated.
Is it just one product that's causing it, or is it everything?
Have you tried running the iray preview with an empty scene?
The new iray verison has issues with certain tif file formats causing a problem like yours.
If iray preview will run with an empty scene or a different product, then it maybe the tif files in the materials causing it.
I have 1080 , i have no problem . Driver v.462.59 .
After testing a lot of stuff, I found it was only a single normal map from Leo 7 that was crashing it.
DAZ Studio crashes so often since the update. Many characters i was able to render in IRAY just before, now causing Studio to crash, from old G2 characters up to G8 characters (but not all). I already got updates from vendors that fixed some textures that cause the newest Studio to crash so it seems the problem is in the Iray render engine.
...what version of Iray is currently being used with 4/15/0/30, is it Iray 2020.1.6, build 334300.9558?
Yea, I just checked the change log. Not sure when the CTD with tif files started, I first noticed it when I was trying to render one SWTriums swim suits from another store.
I've not been seeing any problems, though I've pretty much been working with one scene trying to better understand animation stuff. My Iray version seems to be the same:
It sounds like the TIFF files in question are broken if vendors are replacing them (although I have been in a situation where I had to avoid a valid bitmap file format feature because the maker of a widely used app refused to fix it); does anyone know what the problem is? For example does tiffinfo, or tiffinfo -D, report a problem?
I don't have tiffinfo on Windows, but I do have irfanview.
Here's what I could find out comparing the files that work with the ones that cause the CTD.
Column on the left is the file that works.
The one on the left uses deflate compression, a stream format based on LZ77 compression which is used in the PNG file format. The one on the right uses LZW, a version of which is used in the GIF file format and which, unlike LZ77, was patented. The bug I referred too was, curiously, caused by an LZW encoder I wrote and I doubt the bug was ever fixed, anywhere! I doubt this is the cause because; it was caused by usage of an LZW encoding feature that commonly doesn't give a compression benefit, so most LZW knowledgable people wouldn't consider putting it in an encoder.
The two files are both valid from the information in those screenshots, although the one on the left has had some color reduction done; possibly this is because of the convertion to sRGB, the LZW version does not contain colorspace information and any pixel based convertion using 8-bit components will lose colors (correct convertions, which diffuse the errors, massively increase the number of colors.)
EDIT: I can't get the original (April 2020) because it was updated on Renderosity this month; my download just has the updated (deflate compressed) file. Because the file is a normal map it would actually make sense to use the optimisation I used 20 years ago; I was simply not issuing the LZW table-reset code which, I believe, the other implementation automtically issues when the string (compression code) table is filled. This causes the table to be fixed, which may sound foolish but for a normal map it makes some sense. In this case the deflate file size is 3.6% smaller but then SWTrium also reduced the number of colors in the new normal map by 8.4%.
That's the same thing for me in DAZ Studio 4.15. Purchased a new GPU this summer in August. Could only afford a GeForce RTX 3060 with 12 GB. Now the program is as slow as it was before my purchase. Also have had lots of crashes since the update.. and the story goes on and on and on and on...
...hmm, think I'll sit this latest version out. Maybe 4.16 will be better (although there needs to be a way around having OptiX always on by default for older GPUs).
I'm stuck with 4.12.0.86 for a reason. Try guess why.
Thinking back - If I had to choose and weren't to quick to click on Install Managers "Update" message right away as I've done, I would've stayed with 4.11. To me that was one of the more stable versions. But I guess that's a question of personal taste and experiences, not a rule of thumb.
Yes! The new DS version crashes EVERY time I put on iRay preview with just a naked G8 character! I went back to a DS 4.14 beta version but now can’t render G8.1 characters. I updated the NVIDIA studio drivers, did not help. I have a 1080ti. The original 4.15 was crashing all the time too, I sent in a ticket 4 months ago, got two automated responses saying sorry they are slow due to Covid and then the ticket was closed marked solved.
It takes 15-20 minutes just to open DS, then another half hour just to load a G8 character, I’m still getting the duplicate formula pop up and I have spent many many thousands of dollars here over the years and the only software I can use with the products is unusable!
I just sent in another ticket but if they don’t respond, I want all of my G8.1 products reimbursed. This is getting ridiculous!
I, like you, have a 1080Ti card, and don't experience crashes using Iray Preview. Loading DS times of 15-20 minutes indicate issues somewhere along the line. Have you tried resetting the CMS database? What are your system specs?
Processor Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz, 4201 Mhz, 4 Core(s), 8 Logical Processor(s)
OS Name Microsoft Windows 10 Home
Version 10.0.19041 Build 19041
16 GB RAM
Thank you.
Have you tried resetting the CMS database? In DS - Content Library Pane, click the hamburger menu - Content DB Maintenance - Reset Database. Once that is done, restart DS and see how long it takes. Once DS is running, repeat the steps but instead of Resetting the database, select Re-Import Metadata.
Thanks, I’ll try that soon but I’m in the middle of working on something in 4.14 which is working great. Wouldn’t those issues, if they exist, affect 4.14 too? Actually that took a long time to load too and the character, a G3 still took a long time, but at least it’s not crashing and I can actually work in iRay mode.
Wait, it says resetting the data base will remove any user data. What user data will It remove
Use Export User data first, then afterwards you can use reimport Metadaat to reload the data for products and the userdata.
Resetting the database will wipe out any metadata changes you made (categories you assigned to files, etc.). Before you ever reset the database, you need to export your user data if you hope to have any chance of restoring it. Exporting you user data stores it in a file or files in runtime/support, so it can be read back in later to repopulate the database.
Unless things have changed recently, resetting the database will make Daz Connect (installation from within Daz Studio) completely forget what products you had previously installed. The files will still be on your computer, but Daz Studio will think NOTHING is installed. You have to resinstall everything that you want installed. If you had installed only some of your owned products, you have to identify and select each of those again, skipping over things you don't want to install. This is only one of the reasons I completely gave up on Daz Connect. I reported this issue in a help request years ago, but as far as I can tell, nothing has been done about it. So, user beware!!
You have too little RAM, you could try increasing the size of your virtual memory, but in general DS doesn't like using virtual memory.
@barbult: But this is for DAZ Connect, not for the DIM. Correct?
As far as I know: Resetting the database clears all metadata, regardless of how that metadata was entered into the database. The first paragraph above applies to all installation methods. It is good practice to periodically export your user data for safe keeping and restoration possibilities. The second paragraph above is specific to Daz Connect, and based on (bad) personal experience, after being directed by Customer Support to reset the database.
@barbult: Thank you. Yes, that's what I was questioning: the second paragraph. I wasn't specific enough.