28 Replies Latest reply on Sep 5, 2017 5:44 PM by Jacky Su

    How complicated SolidWorks assembly can Visualize 2017 to open?

    Jacky Su

      My goal is to transfer PV360 to Visualize for some environmental rendering. I have been trying to open/import Solidworks floor plan assembly by Visualize, but no matter it's a complicated one or simple one it never successfully opened/imported and eventhough black out my screen and jam my computer.

       

      below are some rendering examples done by PV360 and failed opened by Visualize.

      simple one:

      S18 - SM BROCHURE - ( MENS BACKWALL +FITSIGN + BOTTOMS ) - RENDERING.JPG

       

      Medium:

      F17 - EMEA - ( SR INDISTRIES ) - RENDERING.JPG

      Complex:

      F17 SHOP - ( BOOT BARN ) - RENDERING.JPG

      none one of them could be opened/Imported by Visualize. I'm wondering that is there any bug limited Visualize from opening a large SolidWorks assembly?

       

      Thx,

       

      Jacky

        • Re: How complicated SolidWorks assembly can Visualize 2017 to open?
          Helge Feddersen

          Hi Jacky,

           

          could you provide some specs of you PC and GPU that you are using? Are you using Visualize Pro?

          The GPU RAM pretty much dictates the number of polygons your model can have.

           

          It could also help to check the Image Quality settings in your SolidWorks Document Properties of the assembly.

          Should the slider be in the red - shift this as far as possible to the left.

           

          br

          Helge

          • Re: How complicated SolidWorks assembly can Visualize 2017 to open?
            Ron Bates

            Also, how are you importing it into Visualize?

             

            Are you using the SW Visualize Plug-In?

            Or are you opening the file directly in Visualize?  And if so, what "Part Grouping Mode" are you using?

             

             

            You should stay away from "Retain Structure" and judging from your PV renders, use either Automatic or Appearance modes to import.

             

            Ron

            • Re: How complicated SolidWorks assembly can Visualize 2017 to open?
              Alen Topic

              Hello Jacky,

               

              I find that over 5-10 million polygons the opening sometimes fails...

               

              polygon count.jpg

               

              Alen

              • Re: How complicated SolidWorks assembly can Visualize 2017 to open?
                Jacky Su

                By the way, below are two renderings comparison:

                 

                Photoview360 rendering

                ( 3TT + T-SHIRTS ) - RENDERING.JPG

                 

                Visualize rendering...........really nice!

                ( 3TT + T-SHIRTS ) - VISUALIZE MODEL.jpg

                • Re: How complicated SolidWorks assembly can Visualize 2017 to open?
                  Robert Pancoast

                  Greetings Jacky,

                   

                  I recently battled this issue.

                  REF: 1-14553478018 Bunkspeed.Common.Import.Manage.DataModelImporter.Failed(Exception exception) System.OutOfMemoryException = "Array dimensions exceeded supported range."

                   

                  To overcome the limitations, you must actually export the ASM from SolidWorks into Visualize, do NOT import files using Visualize.

                  There is a SolidWorks Add-in for Visualize that enables you to export an assembly from SolidWorks straight into Visualize with one button click.  This SolidWorks Add-in solution worked for me.

                   

                  Thanks,

                  Coast

                  • Re: How complicated SolidWorks assembly can Visualize 2017 to open?
                    Ron Bates

                    Jacky,

                     

                    You can import the model or open it directly.

                     

                    But your screenshot shows you are using the dreaded "Retain Structure" option for part grouping. Do NOT use this option in your case.  It will create way too much data.  We are working on revising the import dialog to remove these often confusing options.  In the meantime, I recommend using Appearance or Automatic.

                     

                    The SW Visualize plug-in only helps skip the import options.  Export Standard will import the model using Apperance grouping.  Export Advanced will import using Automatic grouping.  So it's the same really as importing manually and choosing the correct options.  The only thing extra the plug-in will do is allow you to include animations...but it doesn't sound like you're using SW motion studies at this point.

                     

                    It wouldn't hurt to adjust tessellation down but you ought to do it for ALL COMPONENTS in SW to be on the safe side.  To do this, make sure the assembly is opened fully resolved, then go to Tools, Options, Document Properties, Image Quality, and slide the slider to around halfway.  Be sure to make sure you have "Apply to all referenced part documents" checked.

                     

                    Lastly, you may be running out of GPU memory with an M2000 and model of this size.  In which case I recommend starting Visualize, changing option to use CPU only, then restart and try re-importing.

                     

                    • Re: How complicated SolidWorks assembly can Visualize 2017 to open?
                      Jacky Su

                      I finally successfully open it in Visualize, but when I set up everything and started rendering it, it pop up something went wrong.

                      and I copied to clipboard, the detail says as below:

                       

                      An error has occurred.

                      Error occurred at 13:51:45 on Tuesday, 05 September
                      2017.  Build version is 25.1.0.49.

                       

                      1. System.IO.IOException = "There is not enough space on
                        the disk.

                      "

                       

                      Stack Trace:

                         at
                      System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

                         at
                      System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean
                      overwrite, Boolean checkHost)

                         at
                      Bunkspeed.Common.DataModel.Manage.ProjectPackageDataStore.CopyDirectoryRecursively(String
                      sourceDirectoryPath, String targetDirectoryPath)

                         at
                      Bunkspeed.Common.DataModel.Manage.ProjectPackageDataStore.CopyDirectoryRecursively(String
                      sourceDirectoryPath, String targetDirectoryPath)

                         at
                      Bunkspeed.Common.DataModel.Manage.ProjectPackageDataStore.CopyAllExceptAssetWrappers(String
                      copyRootDirectory)

                         at
                      Bunkspeed.Common.DataModel.Manage.ProjectDocument.SaveUnpackagedProjectData(IProjectCurrents
                      simpleCurrents, String rootProjectDataDirectory, Boolean includeOnlyDataReferencedByProjectCurrents,
                      Boolean includeAllCamerasInCurrentWorld, Boolean includeAllConfigurations,
                      Boolean includeThumbnail)

                         at
                      Bunkspeed.Rendering.ApplicationLayer.Controllers.OfflineRenderOutputController.Initialize(IProjectCurrents
                      projectCurrents, RenderingOptionsViewModel renderingOptionsViewModel,
                      IComposerProductSettings settings)

                         at
                      Bunkspeed.Rendering.ApplicationLayer.Controllers.DocumentManager.DoRenderInNewViewportOffline(RenderingOptionsViewModel
                      renderingOptionsViewModel, IProjectCurrents projectCurrents)

                         at
                      System.Windows.Input.CommandBinding.OnExecuted(Object sender,
                      ExecutedRoutedEventArgs e)

                         at
                      System.Windows.Input.CommandManager.ExecuteCommandBinding(Object sender,
                      ExecutedRoutedEventArgs e, CommandBinding commandBinding)

                         at
                      System.Windows.Input.CommandManager.FindCommandBinding(CommandBindingCollection
                      commandBindings, Object sender, RoutedEventArgs e, ICommand command, Boolean
                      execute)

                         at
                      System.Windows.Input.CommandManager.FindCommandBinding(Object sender, RoutedEventArgs
                      e, ICommand command, Boolean execute)

                         at
                      System.Windows.Input.CommandManager.OnExecuted(Object sender,
                      ExecutedRoutedEventArgs e)

                         at
                      System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)

                         at
                      System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target,
                      RoutedEventArgs routedEventArgs)

                         at
                      System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs
                      args, Boolean reRaised)

                         at
                      System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs
                      args)

                         at
                      System.Windows.Input.RoutedCommand.ExecuteImpl(Object parameter, IInputElement
                      target, Boolean userInitiated)

                         at
                      MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource
                      commandSource, Boolean userInitiated)

                         at
                      System.Windows.Controls.Primitives.ButtonBase.OnClick()

                         at
                      System.Windows.Controls.Button.OnClick()

                         at
                      System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs
                      e)

                         at
                      System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)

                         at
                      System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target,
                      RoutedEventArgs routedEventArgs)

                         at
                      System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs
                      args, Boolean reRaised)

                         at
                      System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender,
                      RoutedEventArgs args, RoutedEvent newEvent)

                         at
                      System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)

                         at System.Windows.RoutedEventArgs.InvokeHandler(Delegate
                      handler, Object target)

                         at
                      System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target,
                      RoutedEventArgs routedEventArgs)

                         at
                      System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args,
                      Boolean reRaised)

                         at
                      System.Windows.UIElement.RaiseEventImpl(DependencyObject sender,
                      RoutedEventArgs args)

                         at
                      System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)

                         at
                      System.Windows.Input.InputManager.ProcessStagingArea()

                         at System.Windows.Input.InputManager.ProcessInput(InputEventArgs
                      input)

                         at
                      System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)

                         at
                      System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd,
                      InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y,
                      Int32 wheel)

                         at
                      System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd,
                      WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

                         at
                      System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg,
                      IntPtr wParam, IntPtr lParam, Boolean& handled)

                         at
                      MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr
                      lParam, Boolean& handled)

                         at
                      MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)

                         at
                      System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback,
                      Object args, Int32 numArgs)

                         at
                      System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate
                      callback, Object args, Int32 numArgs, Delegate catchHandler)

                       

                      Direct3D Device Feature Level: Level_11_0

                      Microsoft Windows 10 Enterprise Service Pack -1 - Pass

                      6 x Intel(R) Xeon(R) CPU E5-2603 v4 @ 1.70GHz - Pass

                      32690 MB RAM available - Pass

                      4095 MB NVIDIA Quadro M2000 - Pass

                      03/17/2017 00:00:00 GraphicsCard drivers - Attention

                      1 CUDA devices

                      9318 MB disk space free - Pass

                      5765 MB ram used by application

                       

                      NeurayDeviceMode is CPUOnly

                       

                      could anyone tell what went wrong?

                       

                      Thx,

                       

                      Jacky

                      • Re: How complicated SolidWorks assembly can Visualize 2017 to open?
                        Ron Bates

                        Lots of very large, failed Visualize sessions can leave behind loads of temporary data.  If cleaning up your disk via normal means doesn't quite do the trick to give you enough space, use WinDirstat to see what's taking up so much space.  It works great and is free.

                         

                        WinDirStat - Windows Directory Statistics