civil 3d 2014 working plane tool - attention Jeff_M

[neilyj666]

Jeff

I tried the working plane tool in 2014 and the tool crashed - I don't have the screengrab of the error handy.

Are you able to take a look to see if there are any issues with 2014?

thanks

[Alfred.NESWADBA]

Hi,

what path is now shown as not trusted, the one from the ACAD.LSP or the one with the DLL?

And jsut to make sure: when you set SECURELOAD to 0, then restart C3D ... you are also asked?

- alfred -

[neilyj666]

It works as expected with SECURELOAD=0 but the following whe SECURELOAD=1 - could the double slashes have an effect??

[Jeff_M]

---

@neilyj666 wrote:
Yes I think it probably was, although I was meaning about the surface rebuilds rather than the code rebuilds. 

---

Oh, 2 different Rebuilds mentioned and I chose the wrong one to think about. Yes, you are right, it was not an issue while using the old version. It appears to be something wrong with the Rebuild() method of the .NET API which I have inquired about in the other thread I started.

[Alfred.NESWADBA]

Hi,

>> could the double slashes have an effect?

I would not think that, but who knows. At least it's not absolutely wrong, but also not absolutely correct to set double slashes.

Either you use single slashes or double backslashes (for the LISP syntax), so try to change them single slashes and lets know if that works then:

(command "_NETLOAD" "C:/AutoLISP/C3D Surface .....

If that also brings up the dialog for trusting the load then try to input the path in the same way with slashes within the trusted paths in the options. (btw. to be sure what and how you have set that now, can you upload a screenshot that shows your trusted paths settings within the options?)

- alfred -

[neilyj666 · Accepted solution]

Well what a turn up.... single slashes seem to have solved the problem  I don't get the Trusted Location dialog box now and I can run the WorkingPlane command

[stacy.dunn]

Jeff,

Were you able to remove the COM dependencies?  Are you planning to post the source code?

Thank you,

Stacy

[Jeff_M]

Yes, Stacy, the current iteration is COM-free. Attached is the current source code which references the 2013 .NET libraries and works in both 2013 & 2014.

[stacy.dunn]

Thanks again Jeff.