SR 3D Builder - mysterious error

[Michael Horvath]

I got an error in SR 3D Builder that is a bit mysterious to me. It says:

Found 1 parts duplicated in the model file. These parts need to be removed to load selected model. Proceed?

My problem with it is that it provides little feedback. Which part is being removed? Which is the other part? Why can't it continue?

This is very vague.

[edit]

Also, the model I am working on (Datsville) has 170,000 parts. I do not want to click through every one of these errors.

[Roland Melkert]

I think it want's to remove duplicate references to submodels.

As far I know SR3D doesn't (fully) support MPD's it want's a single flat model.

Or..

Some part is at the exact same place a another, something that messes with he part snapping I'm guessing.

[Michael Horvath]

OK, I got this message too:

Code:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at af.a2.d(az& A_0, q[]& A_1, Int32 A_2)
   at an.a(String A_0, Boolean A_1)
   at an.a(String A_0, Boolean A_1)
   at g.bw(Object A_0, EventArgs A_1)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5472 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
SR3DBuilder
    Assembly Version: 0.8.11.5
    Win32 Version: 0.8.11.5
    CodeBase: file:///C:/Program%20Files%20(x86)/SR%203D%20Builder/SR3DBuilder.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
Microsoft.DirectX
    Assembly Version: 1.0.2902.0
    Win32 Version: 5.04.00.2904
    CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.DirectX/1.0.2902.0__31bf3856ad364e35/Microsoft.DirectX.dll
----------------------------------------
Microsoft.DirectX.Direct3D
    Assembly Version: 1.0.2902.0
    Win32 Version: 9.05.132.0000
    CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.DirectX.Direct3D/1.0.2902.0__31bf3856ad364e35/Microsoft.DirectX.Direct3D.dll
----------------------------------------
Microsoft.DirectX.Direct3DX
    Assembly Version: 1.0.2911.0
    Win32 Version: 9.12.589.0000
    CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.DirectX.Direct3DX/1.0.2911.0__31bf3856ad364e35/Microsoft.DirectX.Direct3DX.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
ImageCombo
    Assembly Version: 1.1.2991.21158
    Win32 Version: 1.1.2991.21158
    CodeBase: file:///C:/Program%20Files%20(x86)/SR%203D%20Builder/ImageCombo.DLL
----------------------------------------
Microsoft.VisualBasic.PowerPacks.Vs
    Assembly Version: 10.0.0.0
    Win32 Version: 11.0.50727.1
    CodeBase: file:///C:/Program%20Files%20(x86)/SR%203D%20Builder/Microsoft.VisualBasic.PowerPacks.Vs.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

I guess that SR 3D Builder is out of the question. Will try LDCad a second time.

[Roland Melkert]

It ran out of memory, don't know your specs but you probably need at least 1GB of ram for datsville in any editor.

[Michael Horvath]

I have 3GB.

LDCad loads the file, but it is pretty much unusable. I don't understand how camera movement works either.

edit

Code:

        Operating System
            Microsoft Windows 7 Home Premium 64-bit SP1
        CPU
            Intel Core 2 Duo E6600 @ 2.40GHz    36 °C
            Conroe 65nm Technology
        RAM
            3.00GB Single-Channel DDR2 @ 333MHz (5-4-4-14)
        Motherboard
            eMachines EMCP73VT-PM (CPU 1)    26 °C
        Graphics
            ASUS VS247 (1920x1080@60Hz)
            767MB GeForce GTX 460 (nVidia)    43 °C
        Hard Drives
            466GB Seagate ST350041 8AS SCSI Disk Device (SATA)    35 °C
        Optical Drives
            HL-DT-ST DVDRAM GH41N SCSI CdRom Device
        Audio
            High Definition Audio Device

[Roland Melkert]

Unless you have a very fast graphics card you want to switch to submodels for detail editing. You can do that but double clicking any of the submodels or using the part bin 'overview' (bulldozer pic)/'all models'(houses pic) group.

Camera move is done by holding down shift and a mouse move on the background or inside the compass. shift+ctrl does the same but uses the current grid as a guide.

edit: if you got any more questions feel free to ask them in my release tread.

[Michael Horvath]

The program also can't seem to find the "LDraw\parts\b" folder for Tore's boxed parts.

[Sergio Reano]

Hi Michael,

about the problems notified this is what I can say:
- The duplicate part messages refers exactly to the fact that programs find a duplicate part in exactly the same position and due to connection management this is not allowed. The program autofix the model by removing one of the duped parts, but need to save the correct model before loading it
- The out of memory messages is trown exactly when system memory is exausted. Check with task manager the available system resources when this happens. Please notice that a 170.000 parts model is quite unusual. The big Millenium Falcon is a model with about 5000 parts and takes about 300MB ram to load. A 170.000 could require about 9GB ram to load properly, but due to the high triangle count of such a model, I cannot imagine a graphic card that could correclty manage it with my application. Probably a 40-50000 parts is a reasonable limit with latest available cards and a 8GB ram system

Byes

Sergio

[Michael Horvath]

Thanks for clearing that up.


Mike