Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pushing Civil 3D Corridor shows an error #3516

Open
jhdempsey86 opened this issue Jun 17, 2024 · 0 comments
Open

Pushing Civil 3D Corridor shows an error #3516

jhdempsey86 opened this issue Jun 17, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@jhdempsey86
Copy link

Prerequisites

What package are you referring to?

Civil 3D Connector

Describe the bug

A simple Civil 3D Corridor is failing to push to Speckle.
It shows an error when just the corridor object is selected to be pushed (first screenshot)

If you select everything to be pushed, it shows a success message, but everything except the Corridor has been pushed
The corridor is on layer "C-ROAD-CORR" (see second screenshot)
But this layer is not visible when you view the latest commit online (third screenshot)

To Reproduce

In the Speckle connector, choose your
For the objects to send, choose the "Selection" setting
Select the corridor in the model, then click "

See this video recording of the process

2024-06-17.12-12-57.mp4

Expected behavior

The corridor should upload to Speckle

Screenshots

image

image

image

System Info

If applicable, please fill in the below details - they help a lot!

Desktop (please complete the following information):

Speckle Civil 3D Connector v 2.20.0-wip2
Civil 3D 2024.3
Windows 11 Enterprise

Failure Logs

From %appdata%\Speckle\Logs\civil3dCivil 3D 2024\SpeckleCoreLog20240617.txt

2024-06-17 12:13:15.727 +01:00 [ERR] SendCommand failed - Zero objects converted successfully. Send stopped.
Speckle.Core.Logging.SpeckleException: Zero objects converted successfully. Send stopped.
   at Speckle.ConnectorAutocadCivil.UI.ConnectorBindingsAutocad.<SendStream>d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at DesktopUI2.ViewModels.StreamViewModel.<SendCommand>d__215.MoveNext()

-->

Additional context

Drawign which produces the error is attached here.

The drwaing is a simple corridor using one of Civil 3D's built in subassemblies

Drawing1.zip

Proposed Solution (if any)

None

Optional: Affected Projects

None

@jhdempsey86 jhdempsey86 added the bug Something isn't working label Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant