A new issue involves the Anvel::Rendering::RendererManager DestroyLineRenderable() function.
The above line crashes Anvel when the simulation is run with an "unknown, unhandled exception," even when we ensure that the lineId[index] refers to a valid, present renderable ID.
We tried working around this by creating an instance of the RendererManager class and calling the DestroyLineRenderable directly on it, but it logged a message in Anvel "Registering message that has previously been initialized", and we could not pan around in the environment window any more.
Generally speaking, you should not create a new RendererManager since it's a singleton. What are you trying to do exactly? This is just a guess, but if you're trying to destroy a debug renderable with that call it might cause issues. If you send us over your code, we may be able to help debug further.