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
Did you enter the serial for V2? It deactivates V1.
That did it! Thank you Mr, Professor, Doctor Jellybean
Hi, Marshian.
You should enter the Gescon II Serial Number to register the plugin. Be sure not to register again the v1 after Gescon II, because the last registered will prevail. The content, by the way, is the same as in v1, you don't see any change there. The Pane, however, is the different one.
Thank you, Doctor Jellybean. My answer is crossed with yours.
Do I need Gescon 1 and Gescon 2 upgrade both installed. I have 1 and now the upgrade for 2, but I want to make sure there is no conflicts if they are both installed. Do they both need to be activated with their individual serial numbers?
Hi Alvin; Long time no see :)
I've been always waiting for your gescon upgrade (for two years? )
Nevertheless, I'm happy to see it released and I immediately jumped to it. I installed it, started using it. Liked it.
(Keeping mind that I almost always Surface Adaptivity 1.0);
I did several difference operations and they performed very well despite high precision (i.e: 9.0).
- I tend to use very big objects with very very small spheres or cylinders, Gescon II is definitely doing its job better than first iteration.
- Animation was awesome! Some time to get used to mesher thingy, but hey, it is nice. I found a workaround to accumulation, so I can "simulate" accumulation on the same object :)
However; with the latest daz beta update, my 2-day enjoyment streak got a huge hit.
- Whatever I do, if I set precision 5-6 or more, I always have a crash. The crash for different operations (union, difference) are different, however they're always same within each operation.
- If I start an animation with more than a few frames, (30 in my case), even if I set precision to 5 (which doesn't do enough in my case), it also crashes the studio after a random frame.
Since these crashes are on difference operation, the crash is always the same. Please see the attachment.
It is coming somewhere from tbb.dll, then goes into openvdb. I don't know any more details. Do you need anything? O.o
They don't interfere between them. Although Gescon 1 must be installed, only one of the two can be activated at the same time. Only register Gescon II (without uninstalling Gescon 1), and it's ready!
Is your Gescon II copy updated?
Could you upload the zip report that Daz Studio generates?
Maybe it's a problem with the beta update.
Ops, you responded! :)
Looking into it immediately and I'll come back with the log ASAP.
GesconII is at latest (as everything else)
I've generated 2 errors. The cloudinfo is not important (empty).
Errorlog.xml's are attached.
Crashdumps have too many personal information which I can't send. However, I do have windbg, so if you need anything I can look at it and send you the results instead.
almost always Surface Adaptivity 1.0
It's very high for most cases! Values of 0.01 - 0.1 are fine, generally.
Do you have a simple example of the crashes, with primitives, you can share?
0.1 also didn't matter. Same exception in difference operation (called openvdb - NonLinearFrustumMap or something like that).
I think that my case doesn't seem to be fitting under category of "most cases", since I do difference operation on relatively very small primitives against big objects.
In the diff test,
- first load "difference settings" for gescon, which is already in the project, correct the temp path for yourself,
- then select the table -> difference -> select all the children of the table -> difference -> fireworks.
- the timeline is already configured.
(in this example, you also see how I have the workaround for simulated difference on the same object :) )
---
In the union test,
- first load union settings for gescon, which is already in the project,
- then expand the table group -> select table up -> union -> select the rest in the group -> union -> fireworks
---
I hope these help.
Let me check them.
I did several tests with the beta 4.23.0.4, and cannot replicate the crash. Maybe the scene is requiring to much memory?
Since I suddenly come up with an accusation of instability, I owe you an apology and explanation.
Yes, you're right. It is not about memory. It is about this processor of mine which caused me to grow gray hair ever since (13900ks). The day I updated daz studio, I also updated the bios, which, in intel's words: "solves the stability and reliability issues with the latest microcode". They changed the values of some of the options internally in bios, causing my stable settings (in the previous bios) to cause instability.
I have been adjusting them, after you said you couldn't reproduce the issue. Now, I finally found a stable setting after so much trial-error, I can say that there is nothing wrong with your product and I'm sorry I caused trouble.
(For the interested parties: with Microcode 12B on 13900KS, stability issues with default intel suggested settings are caused because of missing AVX2 bindown on heavy loads.Go to avx2 settings, set *manually* avx bindown to 4. By default, it was set to auto and bindown was set to 0, causing avx2 stress to be too much for full frequency at 6ghz).