3D Objects tab error: "Image cannot be added to image list"

[AJB]

Hello, I'm getting a strange error when clicking on the 3d object tab and on the textures tab; "Image cannot be added to the ImageList".

It only appears on the 3d objects tab not the 3d string objects tab (that works) and when selecting textures from the tab - selecting 'get texture' still works.

The top google results suggest it's some kind of out of memory problem, it is quite a big track and smaller tracks are still working on the same copy of BTB. And it's an intermittent problem sometimes the 3d object tab works with no problem. It's just irritating to have to reload the program ten times to get the occasion when it doesn't crash.

Anyone else find this one happening them them? Any solutions? I've tried shutting off background programs to free up a bit of memory.

************** Exception Text **************
System.InvalidOperationException: Image cannot be added to the ImageList.
at System.Windows.Forms.ImageList.AddToHandle(Original original, Bitmap bitmap)
at System.Windows.Forms.ImageList.CreateHandle()
at System.Windows.Forms.ImageList.get_Handle()
at System.Windows.Forms.ListView.RealizeProperties()
at System.Windows.Forms.ListView.OnHandleCreated(EventArgs e)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ListView.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.3603 (GDR.050727-3600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
MC
Assembly Version: 3.0.0.0
Win32 Version: 2.0.50727.3603 (GDR.050727-3600)
CodeBase: file:///C:/Windows/assembly/GAC_32/mscorlib/2.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
†ˆŒ˜™•‰Ž†•Œ““™š
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3603 (GDR.050727-3600)
CodeBase: file:///C:/Windows/assembly/GAC_32/mscorlib/2.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
License
Assembly Version: 1.0.0.0
Win32 Version: 2.0.50727.3603 (GDR.050727-3600)
CodeBase: file:///C:/Windows/assembly/GAC_32/mscorlib/2.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
BobsTrackBuilder
Assembly Version: 0.8.0.3
Win32 Version: 2.0.50727.3603 (GDR.050727-3600)
CodeBase: file:///C:/Windows/assembly/GAC_32/mscorlib/2.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
BobsBits
Assembly Version: 1.1.1.5
Win32 Version: 2.0.50727.3603 (GDR.050727-3600)
CodeBase: file:///C:/Windows/assembly/GAC_32/mscorlib/2.0.0.0__b77a5c561934e089/mscorlib.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
----------------------------------------
Microsoft.VisualC
Assembly Version: 8.0.0.0
Win32 Version: 8.00.50727.3053
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualC/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualC.dll
----------------------------------------
ICSharpCode.SharpZipLib
Assembly Version: 0.85.5.452
Win32 Version: 0.85.5.452
CodeBase: file:///C:/Program%20Files/BobsTrackBuilder/ICSharpCode.SharpZipLib.DLL
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3074 (QFE.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.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.

 

[jcrr]

Hello
Sorry no help .... But i've the same issue with a long track with a lot of textures and objects.
Is it a Framework problem? (images catalog is full?) I have more than 1000 walls...
Is it a memory problem? If I add 4Go of memory (From 4 to 8 go) It will be better?
Thanks for your answers

 

[Erwin Greven]

I also got that issue on bigger tracks. click on "cancel" and save the track. Reopen the track and it should work again.

 

[jcrr]

Thanks a lot!

When I saw this error message, there was two button : continue and quit.
With my first track (Peyregrosse) I' had click on continue, and after, I never had possibility to see the textures thumbails... so i was careful...
But here I've click continue... and ... surprise... The images appeared... but I must click on time on any button (ex : Wall only) to change image folder of the xpacks....

thanks and excuse my dirty english...

 

[SmashingPants67]

Out of Memory (for me) Unhandled exception: Error in application
|
\/
Bob's Track Builder has stopped working
A problem has caused the program to stop working
correctly. Windows will close the program and notify
you if a solution is available.

 

[bioLarzen]

Out of Memory (for me) Unhandled exception: Error in application
|
\/
Bob's Track Builder has stopped working
A problem has caused the program to stop working
correctly. Windows will close the program and notify
you if a solution is available.

Oh, I get that a lot - together with the other "usual" crash types... When a track project gets "big enough", BTB always seems to start acting up. It seems to use an insanely huge amount of system resources. I mean, I got it crash multiple times with "not enough memory" errors on a computer that was able to run Crysis well, for heaven's sake... and we all know if a PC can handle Crysis (the first game), it can handle anything

Something else I noticed is how suspiciously long time a simple operation like undoing the last action sometimes takes even when it was a simple action like moving a couple of vertices of the terrain. With most software - even 3D graphics editing software - undoing the last action is usually instantenious - with BTB I had cases where I had to wait like half a minute for the undo to complete - and once again, that happened on a computer that had quite lot of juice and had no problem handling resource-intensive programs and games.

What makes it all even more puzzling - at least to someone who doesn't know a lot about coding - is that those problems don't seem to be consistent: sometimes projects that are far more elaborate and contain much more XPacks, objects etc... work smoothly, but smaller projects keep crashing the application - and then those very same projects work fine?

BTB is a very very handy tool which could even be exceptional, if these annoying things didn't happen. It's no fun at all to work on a project for months, putting A LOT of time and effort in it - only to reach a point beyond which the software seems to stop collaborating smoothly and starts acting like a diva. And don't think of grand projects. I've seen finished BTB-tracks on the web that were way bigger, more elaborate and contained way more objects, textures etc. than the ones I do.

I wish there was a patch or something...

bio