DG Kernel Forum

We will look at it shortly as well.
Thanks for reporting

We have started to look into this.

This should not matter for the problem, just in case:
In your code MyDictionary is not used. You must have meant
iModelStandalone.LoadEx(txtFilePath.Text, MyDictionary);

And a typo in the MyDictionary.SetBool("SeperateObjects", true);

It is v5.3. We do not do anything special in DGK 7.2 with it. We have updated this functionality last year and just call the relevant OCCT 7.7.0 API. Specifically IGESControl_Writer class. OCCT does not concern themselves with iges versions. I do not see anything specific in their code and they do n...

Sorry for the lack of response. We have put this in for the v7.3. It is unsafe to fix the memory leaks in v7.2. Sometimes the fix causes a crash. It is a fine line between a leak or a crash. Leaks are safer. So, the decision was to put it into 7.3. This way it will go through lots more testing. Rele...

This is an OCCT bug. This case of geometric configuration is not handled inside the algorithm, and it is a pretty old bug, The case may have never been handled. We have submitted a clear proof in the OCCT bug reporting system. See the issue 0033877 at tracker.dev.opencascade.org . We have to wait fo...

I have added public void RenderSolid_ForumT116() { base.Load("IGES\\Lens.iges"); int n = m_iModel.GetEntityCount(); Debug.Assert(n > 0); IEntity_DG entity = m_iModel.GetEntityAt(0); IEntity_DG entityNew = entity.Clone(); IDictionary_DG iDict = m_gen.Create<IDictionary_DG>(); iDict.SetDoubl...

The fix is up in today's 5558 update.

Thanks for the good suggestion.

Regards

BTW, we do not keep updates on the web to keep the costs down. I recommend storing few good downloads you use with the update number. Sometimes bad releases happen, so you could use it to revert.

Sorry, 5555 should be considered a bad build. We have removed four methods from IGeometricObject_DG which are duplication of IObject_DG and have issues. It was not a good idea. We will revert the change tomorrow the latest.

Thank you for reporting this.

Thank you for the great analysis, Oliver.
We have entered the problem into the system. It is in the queue.
Regards