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
This is not iray related at all; but I can tell that this issue, which is related with dforce, has been there for a while. I can't recall which beta this started happening though. The main driver for this one is that dforce engine somehow starts calculating *before* moving to the start frame. This is especially apparent if the previous calculation ended on a frame which has an active wind node. If you press simulate *without going to the supposed start frame* by yourself, it starts calculating the current frame, then it moves to the initial start frame. The workaround is to always go to the start frame manually, then press simulate. I know, irritiating, but a workaround at least.
i dont pay attention to developments, but are they going to make more filament render options. I like the purple Filament view that comes up before textures load in - wish there was a way to have that as a draw option.
+1 on that. It's so intruging but it only appears for a second or so on my system.
I would love the emitters or at least ambient glow the Google build has, better transmapping would be nice too
I know we had a little tussle in the past (eh, it happens :P), but I'm glad you suggested this solution! I sometimes run into this issue and I figure it must be two different morphs with the same name interfering with one another and cancelling the whole thing out, leading to figures looking slightly different after closing and re-opening Studio.
another beta and it wants to add libraries found again and has to locate the ruins HDRI (sigh) this is why I am having such issues
You could back up your program/install files located in \DAZ 3D\InstallManager\DOWNLOADS, IE: the zip and dsx files of DAZStudio412PublicBuildWin64bit and the accompanying GOZ/photoshop/alembic/decimator plugins and install the new build freely knowing that you can easily re-install the previous version without having to ask DAZ for an old version...
And even if they do give you an earlier version, you are not guaranteed with getting the previous version's plugins!
looks like I might need to start grabbing betas and saving them too
I'm pretty much a collecter as I have scores of betas and general releases, I even have my old DS 3 advanced installs!
they are not as easy to grab as production builds because I need to search for the zip so I generally don't but it's getting too unpredictable, I realise they are betas but because I use much older builds it's getting very messy for me juggling newer features with safe and reliable.
That said I definitely don't want to grab the previous one off of my other computer either as that started my issues on this one.
I also wish they would delay updates to the production builds until after the beta has been, you know, beta tested because I cannot grab that instead either.
is there anyway to download just the core app and not the additional content?
I'm on a metered connection, we have one ISP that offers service and the connection speed is deplorable when I can get it.
I need the Win64 bit, only my iMac is connected, I dont want to have to use whatever download manager that Daz has now, I just need the core app on a zip.
is there a way to get that? thanks.
Unfortunately the Beta version is only available through DIM ...
thank you for letting me know. :-)
Turn off the colections pop-up (there's a check box at lower-left) and you will be able to select individual parts.
Then there seems to be a bug in the latest beta; immediately after I had installed it when I first opened the beta (with -instanceName #) I was prompted to add
G:\DAZ 3D\Studio\CoreThat is the second directory in the "DAZ Studio Formats" entry of the default CMS directories list. It is immediately after the "My DAZ 3D Library" entry. I did not add it of course (since it was already there) and haven't seen the message again. I have seen it in previous betas, but it only gives one "new" directory - since I have added 40+ content directories via DIM it seems like DAZStudio and DIM aren't communicating in the way I think you are implying. I think I've only clicked OK on that dialog once; pretty much all the time I have updated the CMS directories manually, running without -instanceName. Maybe the -instanceName option changes the behavior? It certainly isn't possible to change the CMS directories permanently from an instance - the instance does not write ContextDirectoryManager.dsx, but even if it did it wouldn't be used with the default behavior (since the instance specific AppData directory is now cleaned before starting an identically named instance.)the directory it wants to add is not in DIM, it is a temporary one I created to save a freebie to and only contains that prop, I removed it from my library in the content directory after creating the freebie.
It seems to detect it but not other unused ones on the same drive (not the external I have my actual libraries on even)
the other one it adds is a duplicate of my existing one
as a result all my custom action scripts list two identical paths to choose from when I click them.
it does seem unique to the Windows 10 rig though, my Win7 with the same beta and quite a few different libraries is fine
There is just one CMS database in the configuration; there is only one entry for "Cluster Directory" under Preferences/CMS Settings. When DIM installs things and when we save stuff from DAZStudio it gets added to that, single, database. "Smart Content" shows the entire database and if the current CMS Directory List doesn't include everything in the database those entries will be shown as uninstalled. If the same thing gets installed to two separate paths presumably it will in the database twice and if something is deleted then, apparently, it is still in the database.
So one approach which I have not tried is to do "Stop CMS" (right click on the Content Directory tab), change the "Cluster Directory" to something new and restart the CMS. I think that will build a new database without destroying anything, though I haven't yet had the opportunity to try it.
Presumably the weird "you need to add this directory" message comes out when there are things in the database which aren't in the directory list, though I don't see why I only see it once.
Backing up software is sensible.
Even ones like Blender I keep a couple of versions as it's easier than re-downloading.
Only the main, unnamed instance reads the RunOnce folder. This is a long standing feature of DS, it used to be used for adding the metadata for content installed using the stand-alone installers before DIM. When DS finds a script in that folder it runs it on launching, then deletes the file. DIM adds a script that checks each of its destination folders after installing DS (first time or update) and when it is run by DS it puts a prompt up for any directories that are not set as both Poser and DS content directories - the script is an ASCII .dsa file so you can inspect it.
DIM keeps putting odd things in my Public Documents library which on my rig should only contain Install Manager.
Today it was an i13 secluded living update.
nothing else got written there out of things I newly bought or updates
I keep moving stuff out now when it happens but I want to stop it
these are my settings
so why does it do this?
OK edited this so hopefully fingers crossed fixes it
When I try the Beta download links from the DAZ store, both the IM and DC links fail to download the beta. When I type "DAZ Studio * Public Build" into the search on the Intall Manager, as suggested in the beta FAQ, it also fails to find it.
The DAZ store shows I've purchased it, and the links are there, but the apps don't do what they're supposed to.
Any other way to download the Beta or clues about why these methods wouldn't be working?
I don't really want to be using BETA software, I'd really like to go back to a version of DS that would allow me to continue my projects without having to navigate a dozen new glitches, but I guess there's no way to do that now. If I'd known this before, I'd never have "upgraded".
The inability to launch more than one instance of Studio is a real hit on my workflow. Studio is taking a lot longer to open and close and won't relaunch before it's done with whatever its doing in the background when it closes. Might as well be a beta.
And now I can't go back to the more functional version?
WTF?
Yup. Thanks for the suggestion.
The show hidden doesn't reveal it either.
The public build was present in the IM's "Installed" list before I tried to download the new version, but there is no other beta version presently installed. This is my best guess as to why it failed. There was no error message.
I just tried DAZ Studio 4.15.0.14 and (same like 4.15.0.13 before it) it crashes if you use Geometry Editor to select and delete polygons of a clothing item.
The crash is in DzCore.dll!DzFaceVertexDelta::operator=() method which gets called from copyDeltas().
The error is access violation (0xC0000005) accessing a memory address (the address is not a null pointer so I guess it is read after free type of error somewhere in there).
I wonder if DAZ even has a QA team anymore? I mean, if there is such a basic option such as selecting and deleting polygons in a 3D program which randomly crashes, how does that escape internal QA and ends up in public beta, much less in production version (which I assume has the same bug as well)?
I've used Geometry Editor yesterday to delete polygons from a t-shirt, no crash for me.
The thing you search for should be DAZ Studio * Public Build without the quotes. It's better in my experience to search for just Public Build - that will show you all the beta packages, I count six of them. Once you have "bought" it and refreshed DIM it should show up in the "Ready to Download" tab. I assume it doesn't but that other packages do show up.
I assume you mean the IM and DC links on the beta product page. The IM one should just fire up DIM IRC (I have to admit I never use them). It may be that recent browser updates or changes have stopped them working but if you just open DIM and go to the "Ready to Download" page you should see stuff. You can double check by "buying" one of the DAZ Productions weekly freebies and making sure that this shows up. If not it sounds like DIM has lost your account information somehow.
You can do that with recent versions of DAZStudio - just append -instanceName # to the command line. The fix for the load time is to reduce the number of morphs you have installed, the fix for the close time is to delete everything in the scene before closing DAZStudio.
You can also get that behavior by de-installing the product; DIM will then not have a "currently installed path" to install the update to. I suggest putting a / at the start of path names in DIM; i.e. I:/my DAZ 3D Library. It's probably safe not to but DOS had a horrible habit of remembering the current directory on each named drive, so I:foo would mean different files depending on where you (or DIM) had been before. Microsoft have never fixed this, it's a "feature".