topic When test Clash using TestsAddCopy crashes Navisworks 2016? in Navisworks API Forum

When test Clash using TestsAddCopy crashes Navisworks 2016?

Anonymous — Tue, 13 Dec 2016 02:10:42 GMT

Hi,

I try to test clash of 2 selection set. First, I wrote function addClashTest()

Using the following code, have have a very strange behavior.

When run to ｢docClash.TestsData.TestsAddCopy(oNewTest);｣ occurred exception and crashes Navisworks
It is surrounded by a try catch block but the exception is not caught.
Why is the exception not caught? ｢TestsAddCopy｣API has problems?

Any tips on these will be great help. Thanks in advance.

Here is the code I use:

DocumentClash docClash = Autodesk.Navisworks.Api.Application.ActiveDocument.GetClash();

// Create a ClashTest
ClashTest oNewTest = new ClashTest();
oNewTest.CustomTestName = "Test_Clash";
oNewTest.DisplayName = "Test_Clash";
oNewTest.TestType = ClashTestType.Clearance;
oNewTest.Tolerance = 1500;

//Set SelectionA and SelectionB of the ClashTest
ModelItemCollection oSelA = new ModelItemCollection();
ModelItemCollection oSelB = new ModelItemCollection();

// Create 1st Selection Set: SelectionSet1

// Create 2nd Selection Set: SelectionSet2

// Loop list selection set
foreach (SavedItem set in listSelectionSets)
{
    if ("SelectionSet1".Equals(set.DisplayName))
    {
        oSelA.AddRange(SelectionSet1);
    }
    else if ("SelectionSet2".Equals(set.DisplayName))
    {
        oSelB.AddRange(SelectionSet2);
    }
}
            
if ((0 < oSelA.Count) && (0 < oSelB.Count))
{
    oNewTest.SelectionA.Selection.CopyFrom(oSelA);
    oNewTest.SelectionB.Selection.CopyFrom(oSelB);

    try
    {
        docClash.TestsData.TestsAddCopy(oNewTest);
    }
    catch (Exception ex)
    {
        // Information of the exception
        //throw new ApplicationException("Error :", ex);
        System.Windows.Forms.MessageBox.Show(ex.Message);
    }
}

Regards,
MinhHN

Re: When test Clash using TestsAddCopy crashes Navisworks 2016?

Anonymous — Tue, 13 Dec 2016 15:28:43 GMT

I am also having the issue where Try/Catch is being ignored. The program simply errors and quits. I am using VS2015 against Simulate 2016. This is the error it throws that it can not recover from:

Exception thrown at 0x00007FFA90BEA837 (ASMKERN221A.dll) in RequestedModelBuild_2016.exe: 0xC0000005: Access violation writing location 0x0000000000000010.

This is thrown when using TryAppend with a .DWG file. I can load the file manually without errors.

I do not have this issue with VS2013 or earlier with Simulate 2015 or earlier. I have not attempted VS2015 with an earlier version of Simulate with the same code.

Re: When test Clash using TestsAddCopy crashes Navisworks 2016?

Anonymous — Wed, 14 Dec 2016 00:32:42 GMT

Thank you for the reply!

I'm using VS2012 with .Net 4.5
Because no exception has been thrown, I do not know the exact cause

According to what you talked, the cause may be "Visual Studio" and ".Net" version is old ?

Re: When test Clash using TestsAddCopy crashes Navisworks 2016?

Anonymous — Fri, 16 Dec 2016 13:50:58 GMT

The version of .NET does not matter. I am using .NET 6.1 in Windows 7 and Windows 10 with the same behavior. My issue seems to be localized in the Document object, specifically when using TryAppend when reading in .DWG files. My app is a console app, rather than a plug-in.

Re: When test Clash using TestsAddCopy crashes Navisworks 2016?

Anonymous — Mon, 19 Dec 2016 14:27:37 GMT

Not because it is old. Because Simulate 2016 has api issues. I tried with all .NET versions from 4.5 through 6.1. with same result.

Re: When test Clash using TestsAddCopy crashes Navisworks 2016?

Anonymous — Tue, 20 Dec 2016 00:31:06 GMT

Hi, thank you!
Because no exception has been thrown, I do not know the exact cause.
I'm investigating the cause 🙂

Re: When test Clash using TestsAddCopy crashes Navisworks 2016?

Anonymous — Tue, 27 Dec 2016 19:09:22 GMT

an exception is thrown. The complaint is that it is not handed back to the customization through the api, rather, roamer handles the exception and quits. I have found that If I am in Windows 10 and turn on Close On Load performance option the error does not occur. It is still a problem that if an error occurs, the program quits instead of allowing the api calling program to handle the error.