Problems with Multiple Meshes using XAML notation.

Nov 21, 2009 at 10:11 PM

I am using the XAML notation and the latest 0.8.7 build and I having issues when I have the following scenario:

<Controls:RenderingContainer x:Name="_renderingContainer" Width="800" Height="600" BackgroundColor="Black">
            <Controls:RenderingContainer.Nodes>
                <Controls:RenderedNodeCollection>
                    <Controls:Mesh x:Name="_audi" AssetName="audi.ASE" />
                    <Controls:Mesh x:Name="_audi2" AssetName="audi.ASE"/>
                </Controls:RenderedNodeCollection>
            </Controls:RenderingContainer.Nodes>
        </Controls:RenderingContainer>

That works if i only have 1 mesh. As soon as I get 2 meshes like in that example it falls over complaining of a collection has been modified. I took all code out of my update action handler and that still occured. All I want to do is display a couple of models in the same rendering container.

 

Coordinator
Nov 22, 2009 at 6:00 AM

The Xaml support has been totally rewritten for the new release and this problem is not present there. We're really close to a new release.

The development branch on GitHub holds the latest code now. Syntax has changed a bit:

<balder:Game x:Name="_game" Width="800" Height="600" Background="White">

<balder:Game.GameClass>

<local:MyGame/>

</balder:Game.GameClass>

<balder:Mesh x:Name="_teapot" AssetName="/Balder.Silverlight.TestApp;component/Assets/teapot.ASE"/>

</balder:Game>