During IntroGame, click the mouse on the Particle Actor screen causes a crash.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Download and unpack the source code.
2. Open the solution in Visual Studio.
3. Build the solution.
4. Run without debugging.

What is the expected output? What do you see instead?
When the mouse button is clicked, a particle should be placed at the mouse
location.  Instead, the application crashes.

What version of the product are you using? On what operating system? Is it
a downloaded distribution or from SVN?
I am using the stable Angel-2.0 from the zip file.  I am attempting to
build and run it on Windows Server 2003 using Visual Studio 2008 on a dual
CPU Intel Xeon x86 2.0GHz with 2 gigs of RAM.  I have the latest DirectX
SDK installed (November 2008).

Please provide any additional information below.
N/A

Original issue reported on code.google.com by johnatho...@gmail.com on 2 Mar 2009 at 2:07

[GoogleCodeExporter]

Can't reproduce on my end -- could you run in Debug and let us know where the 
crash
is occurring? 

Original comment by lieseg...@gmail.com on 2 Mar 2009 at 7:20

• Changed state: Accepted

[GoogleCodeExporter]

Unfortunately, this is the code that I can't get to run the Debug version, 
however
the Visual Studio debugger still seems to work fine on the Release version.  
Here is
the call stack, starting from the line where it seems to die:

Actor::SetColor() line 356 of Actor.cpp
DemoScreenParticleActors::MouseDownEvent() line 137 of 
DemoScreenParticleActors.cpp
MouseButton() line 101 of MouseInput.cpp

The remainder of the call stack goes through a lot of disassembled code and 
ducks
through several DLLs before ending up World::StartGame(), so I imagine that is 
not
helpful for you.  It specifically looks like it is crashing while trying to 
load or
set color from the triangle texture, but I'm not sure why.  If you need more
information, let me know (its easily re-creatable on my end).

Original comment by johnatho...@gmail.com on 2 Mar 2009 at 7:50

[GoogleCodeExporter]

This might have something to with the Python lib weirdness you were seeing. 
Since you
indicated you weren't seeing it in the changeset I'm about to merge, I'm going 
to
close this. 

Original comment by lieseg...@gmail.com on 2 Mar 2009 at 4:31

• Changed state: WontFix