I have a problem with send big data now, problem is model too big to can send to speckle. At the moment, we have any to way to split model, or scale or split JSON file to manager with big model ?
With my case is model include 500 file Revit linked or more than 500 file nwc for one project
This is how the known issue that manifests in the Developer Console. For reference, the send was completed the third time trying. Each pass was committing serialized chunks of data; on the 3rd try, it was successful as all the objects were already present on the server.
This is not ideal as the conversion also needed to be completed 3 times
This is detail I read from dump file of navisworks : The thread tried to read from or write to a virtual address for which it does not have the appropriate access. dumpinfo.zip (4.5 MB)
Next time it happens, try debugging the .dmp file before closing the app. You will see more detail and context. - and from that screenshots are fine.
Separate from the issue I linked to, this does seem more like the errors I was getting when trying to async parts of the conversion, however. (an abandoned initiative)
System.NullReferenceException: Object reference not set to an instance of an object.
at Autodesk.Navisworks.Gui.Roamer.AutoRecover.AutoRecoverControlImpl.IsModifiedSinceLastAutoSave()
at Autodesk.Navisworks.Gui.Roamer.AutoRecover.AutoRecoverControlImplBase.OnIdle()
at Autodesk.Navisworks.Gui.Roamer.MainWindow.OnIdle(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at NetRoamer.RoamerStartup.Run()
at Autodesk.Navisworks.Api.Interop.AbortOnException.CallAction(Action0 del)
Thanks for reporting, this is the first we have seen where a failure to send has triggered an exception that escapes the error handling in DUI. Most others result in the UI display as you showed in your screen shot