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
Ahh k then I missed it as there is nothing in my messages about it, ah well maybe next time with version 3.. lol
I'm afraid it's working as designed then, and the design is not optimal. :-) I'll try to come up with a fix but it's not going to be out in a week or so, unfortunately.
Thank you for the report!
OK. At least there is a workaround. Always switch away from dForce Companion and back in order to refresh the settings.
Has anyone else had trouble installing through DIM? I bought it the day it came out and every day I go back into DIM and find that it's there to download and install again as if I hadn't pressed the button the day before to download and install.
Yes. That happened to me. I've had to do it a few times. Seems to install. Works in Studio. Then pops up in DIM again.
Do you have DS open when your installing it? I know this was an issue with some other things.
I actually usually do. I'll try with Studio turned off later this evening, thanks for the tip, fingers crossed!
I'm having trouble installiing this on Daz 4.15. I have Dforce Companion 1 installed and working, but no matter how I install Dforce Companion 2 it does'nt show up in the Panes. Tried to install through DIM and manual and tried removing Dforce Companion 1 before installing with no succes. The install is going without any problems, but it does not show. Any help would be appreciated.
go to your daz studio folder (not the content Lib) and check the folder Plugins, if the .dll is there.
also look here:
if the dll is correct there:
↑there see you also the path, where it should be, its important, that you have only ONE dforce.dll dont have 2! also not one named (backup), you need to move the old one out of that folder.
Thank you, Loony - only the old dll was in the plugin-directory - deleted that and reinstalled DC 2 - and it works like a charm :)
Very good ;) If you want to dforce a towel etc. that isnt a figure, make sure to disable the rigged thing in the new panel at the top right, that is one of the greatest changes! I hated that all need to be a figure :)
Is there a way to uncheck everything that is marked as "vis" all at once? When I have a really large scene, it takes a long time to go through the list and uncheck everything that is visible to dForce. It would be faster to uncheck everything at once and select the items I do want visible instead. I love this plugin BTW.
The answer is very simple, you just select anything and everything other will be unselected.
Explaining Clip:
https://s1.webmshare.com/0y0Aw.webm
The link sends me to a 404 page, but I get what you mean. Select everything in the scene tab and turn off visibility for everything all at once. That makes sense. Thanks for the tip.
Click on this checkbox 2x then all other get unselected. If you wanna simulate multiple, hold CTRL and click the checkboxes, then it will use multiple.
Thanks for taking the time to show me Loony. That works great for the left side. I wish I could do the same thing on the right side under "Vis" but since that correlates to a settings option in the parameters tab, it might not be possible. The idea of selecting everything in the scene tab and turning off "Visible In Simulation" still works a lot better than unchecking each item one at a time though, especially when there are a ton of props in your seen that don't need to collide with your dForce items.
I have a scene that seems to kill Daz Studio with the attached error. Hitting "Ignore" two time seems to make everything continue otherwise Daz Studio crashes out with a bug report.
Any tips on how to avoid this in some scenes?
Oh, I'm sorry, that does look like a bug in my code. I've never seen that though so I'm not sure what's in your scene that triggers this.
In what situation exactly does the error appear? After you load the scene file or when you click on something?
My suspicion is that there is something in your scene that the Companion considers worth hearing about for updates, but it's not willing to provide them -- but I don't know what exactly that is. Can you try deleting scene nodes until the error stops appearing to try find out what item causes it?
The cause my not be the same but it's a reproducable issue that happens 100% of the time for me. If I apply Bone Minion then go to the dforce Compnion tab I get that exact same error, but if I hit Ignore twice the message goes away and Studio won't crash. Once I delete Bone Minion the error message stops though.
I bought this updated version in the PA sale. I previously had the original version which didn't work for me so I disabled it. Now this version is proving just as difficult to work with. Once I have made something not-visible in simulation (outside of dFroce Companion) there seems to be no way to make it visible again. I am attemting this with a couple of dForce bed covers and they just refuse to be visible in dForce Companion or, indeed, able dForce at all. If I disable the companion, they work again. Doesn't matter whether they are enabled/visible in the companion, they are just static items which give an error when attempting to dForce them.
As with the previous version, I don't have the time to figure out why things don't work with this plugin so it is now disabled. Very frustrating but I am back to painstakingly making objects visible or invisible in the viewport which is how I have worked since dForce was released.
dForce Companion 2 has a 6 page PDF document explaining how to use it. Have you looked there for instructions? For example, it shows you how to use it with non-rigged items by selecting an option in the node list filters. (see attached screenshot snippet from the documentation.) If your bed covers are not rigged figures, you need to disable the filter that says "Show only figures (nodes with rigging)". If the covers have dForce applied to them, they will then be visible in dForce Companion 2 and will simulate.
Here's a snippet from the product readme, in case you don't know where to look for the PDF documentation:
Or, even easier, if you installed it with DIM, you can right click on the product name in your DIM Installed Files tab and select Show Installed Files, then click the URL for the manual.
Or, inside Daz Studio, hit F1 to open the Help browser and navigate to Plugins section, Expand dForce Companion 2, and select Documentation.
I tried with the rigged switch on and off - still the same. I displayed everything in the scene - rigged and non rigged in the companion and went through selecting and deselecting. When I say "visible" - I don't mean visible to the companion (although that can also be a problem, it seems). I mean visible to the simulation.I just can't get them to simulate whether I use the companion or not. It seems something gets switched off and does not switch on again.
It occurs to me that when I disabled the companion and I could then simulate again, I think I restarted DAZ Studio just to make sure it was disabled. Perhaps restarting DAZ Studio was the trick to clearing the "stuck" switch.
I've never experienced the problem you describe. I use dForce Companion 2 exclusively for simulation. There are multiple ways to make something not visible to dForce, though. You can turn simulation visibility off in the Display section of the Parameters pane, and you can turn if off for a surface in the Surfaces pane, and you can turn it off in dForce Companion 2. Maybe one of those that you are not thinking about has caused your problem. Also, maybe you have set the item to be frozen in simulation, preventing it from simulating. Without seeing all of your settings, it is hard to guess. I don't want to be insulting, but since it sounds like you don't have a lot of experience with using dForce Companion 2, are you sure you are clear about the meanings and effect of each of the checkmark columns (Sim and Vis)? Both of those need to be checked to simulate the item. The Sim column is essentially the freeze column. If it is unchecked, the item is frozen will not simulate, even if the Vis box is checked. If Sim is unchecked and Vis is checked, it means that other dForce items will see it and be able to collide with it.
I am not experienced with dForce companion but I am familiar with dForce itself so the settings in the Companion seem fairly self-explanatory. As for much of the remainder of your post, yes, I know about making things visible for simulation, about freezing, etc. I may have misunderstood the Sim column by assuming that it was related to "Visible in Simulation" rather than the Freeze option, however.
This maybe related to something you, yourself, discussed in another dForce thread here:
https://www.daz3d.com/forums/discussion/275451/solved-dforce-no-objects-to-simulate ;
Do you mean the mCasual script? Do you use that? I haven't. Do you mean static vs. dynamic simulation property? Only dynamic objects with move with gravity and wind when simulating. Static lets you set a friction value that will affect other dForce objects interacting with it. I have had some dForce hair products that are dForce only because the use strand-based hairs and they are not meant to be simulated. However, you are not talking about hair products. There is also the case that if you get an "error during simulation" message, you often have to restart Daz Studio before simulation will work again.
No, I don't use any script. Nor am I switching between static and dynamic. I appreciate your help but it has little to do with the problem I am seeing. I don't use dForce hair either.I'm not getting the "error during simulation" either.
Simply put: if I make something invisible to the dForce simulation (I mean in the Display parameter settings), the Companion no longer recognises that object in the scene even when I make it visible again. If I disable the Companion, I still can't simulate that object unless I restart DAZ Studio. If I don't restart, I get an error complaining that there are "no objects to simulate".
What is the "something"? Is that the bedding you were talking about, or does this problem happen for EVERYTHING you try to simulate? I'll try to replicate your scenario as closely as possible and see what happens.