Some Windows/Widgets just not being displayed at high load?

[Varity]

I am using the CEGUI 0.41 source package, Ogre 1.0.5 with the standard 1.0.5 OgreGUIRenderer.

I am currently trying to render a window with 2 ScrollablePanes in it.
Each of these panes contains a number of dynamically created Drag&Drop slots (100-150 total) and each of the slots contains a DragContainer, which itself contains a DragItem (FrameWindow with 5-8 Widgets). (Like this)
Everything is working fine if the total number of Slots on the panes doesn't get above some threshold number. Above that, additonal slots and their content don't get displayed anymore, although the log lists their creation. Even the scrollbars on the ScrollablePanes become invisible, but still function normally.

If I reduce the number of widgets on the DragItems, I can create more Slots with DragItems before things start to disappear,
the total number of CEGUI::Windows in the system at that point is about 5800.

Neither Ogre.log nor CEGUI.log report any errors.

What is going on here?

[lindquist]

It sounds like a problem with the Ogre renderer module.
One reason could be the internal vertex buffer simply is'nt big enough. eg. it does not handle "buffer overflow" correctly.

Unfortunately I don't have the Ogre renderer around, so I'm not able to check.
I'm fairly confident that this is not an issue with the CEGUI core as we don't limit anything at all in there...

I hope this helps you in locating this issue.

[Varity]

Thanks for the reply, lindquist!

It seems indeed to be a problem with the renderer(s).

I have taken the relevant portions of my code and merged it into the framework of SampleDemo7. I find that the problem doesn't occur with the DirectX renderer, but using the OpenGL renderer, I get EXACTLY the same symptoms as with the Ogre renderer!

I have now upgraded to the current CVS version of Ogre (Dagon), but the renderer seems essentially unchanged and there is no change in the results. I don't think that an overflow of the vertex buffer is the problem, as it can change its size dynamically and it seems to do so correctly (as far as I can tell from my limited understanding of its workings).

If anyone is willing to look into this, I can mail or post my code to demonstrate the problem.