Optimize + PolyReduction



  • On 08/04/2016 at 09:32, xxxxxxxx wrote:

    Hi there,_
    Our team have created a bunch of script to automate importing CAD files into C4D. As it is well known, CA_<_o:_<_o:p_>_ can be painful to work with, often heavy with unnamed objects._<_o:_<_o:p_>_p>At some point our script apply some heavy Optimization (2 cm) + a strong PolyReduction Deformer (90%).
    So far we have experience 2 strange bug while doing those functions:
    _<_!----_>_yle="margin-left:36.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo1">1-    The PolyReduction hang on_<_!---_<_o:_<_o:p_>_cts IF the Mesh Quality Factor is higher than 0. It seams like some bad polygon are throwing the deformer in an endless loop. As anybody had similar experience?

    _<_!----_>_o:p>
    2-    The second problem is more problematic and more urgent, we sometimes have point th_<_o:_<_o:p_>_ wild._<_o:p_>_eems to be the results of the Optimization function, but I cannot reproduce the result manually. If I take the same_<_o:p_>_t, a_<_o:p_>_manually the optimization and than apply a PolyReduction NO points goes wild…
     
    I suspect that C4D interface command are_<_o:p_>_ mor_<_o:_<_o:p_>_ex than a simple python function (probably multiple function bundled together) since we get different result with the interface and by pure script (Using MCOMMAND_OPTIMIZE ), as if C4D had some cleaning internal process…
    Lastly we've just discovered that page:
    https://developers.maxon.net/docs/Cinema4DPythonSDK/html/modules/c4d/C4DAtom/index.html?highlight=message#C4DAtom.Message
    So none of our script contains " MSG_CHANGE". Could this be the root of our problem? Can you give us a rule of a thumb when to use them? At each function that change the ge_ <_o:_<_o:p_>_ at the end only of the script?
     And is there any other command that we have to use when changing the geometry by script?
    _.0pt;font-family:Verdana;mso-bidi-font-family:Verdana; mso-bidi-font-weight:bold">Thank you for any help you can provide 🙂
    Edit: I've changed the link in the post from NodeData to Atom.Message



  • On 09/04/2016 at 10:33, xxxxxxxx wrote:

    Hi,
    I've made further test and it appears that it's mainly the PolyReduction that mainly causes the problem. With a reduction Below 60% the problem goes away using the scripts, Higher the problem appears.

    However no problem appears when doing the same step manually, even at 90% Reduction.



  • On 11/04/2016 at 02:15, xxxxxxxx wrote:

    Hello and welcome,

    could you share your code with us? Without knowing what exactly you are doing and how you are doing it, it is hard to make any statement.

    Best wishes,
    Sebastian


Log in to reply