CEGUI (Crazy Eddie's GUI) Forums

Hi you guys!
I'm having some serious framerate-troubles, and my profiler says that rendering the gui takes something like 700-890 milliseconds per seconds.
Not even the 3d-rendering takes that much time.
I have a lot of GUI-objects, but most of them is set to invisible (and disabled) , and made visible (and enabled) only when the gamestate decides to make them so.
Anyone have a clue what could be causing all of this?

btw. I have my DirectX-drivers set to retail. I am not _that_ goofy.

1) CEGUI log would be useful (if only for version info)
2) What version are you running (see #1). If you have hidden widgets I believe there was recently some work in improving rendering performance when there are hidden things.
3) Are you running in debug? It is notorious for completely destroying performance.

2) I'm currently running 0.6.2. I have a lot of hidden windows all the time.
3) I've notices extra problems in debug, yes, but I'm still having a tremendous fps-drop even in release.

1) Log:

Due to the scenario you describe - that of lots of hidden windows and such - I'm going to have to label this as "known issue" and "fixed in the latest release". I know that's not particularly helpful for yourself having this issue with the older release, although it does, almost certainly, accurately describe the situation. Also be aware that the older rendering back end suffers with many issues, so you'll be paying a penalty there too (though the 0.7.x code does not support Direct3D 8.1, so I guess that's why you're stuck in 0.6.x land? A 8.1 compatible renderer should not be hard to write, though it's not something I want to have to support).

The topic covering the issue with hidden windows is here: viewtopic.php?f=3&t=4500 You may be able to find some useful info there if you decide you'd like to hack on the older code. I could post the patch for the fix I put in the v0-7 branch, although it would not apply cleanly to the v0-6 code (mainly due to the changed directory structure).

CE.

I decided to convert to the latest version (0.7.1), but now when I try to run the program it crashes, and throws a Cegui-exception.
The log looks like this:


I searched the forums, but the only similar problems seemed to be related to CELayoutEditor. What to do?

Looks like its looking for the SILLY image codec dll. Did you build from source? If so, you probably have silly as the default image codec, do you also have it enabled to build? Did it build successfully - if so you need to have that dll available to your application - presumably in the same place as CEGUI_d.dll

If you didn't build from source, just look for the SILLY image codec dll in the package you downloaded and put that in the same place as your CEGUI_d.dll.

If you don't wan to use SILLY, and instead use one of the others you'll have to setup your CEGUI::System with the image codec of your choice (calling setImageCodec).

There's probably another few hundred things I could be missing, but those are the most common issues I can think of.

Thanks, that was it.

And, is your framerate better now?

It is! Thanks alot

Although, I have one question about subscribing events. Back when I were using the 0.6.2 version, I had a system for queing the building of callbacks, something like this:



And then, once per frame I resolve the que of event-bindings. Why this hassle, you ask.
Well, I experienced some weird bugs, which turned out to be related to me deleting subscriptions, while still in the scope of a callback.
The Gui is under much transformation during the entire game, and more often than not, the Gui changes depending on which gui-button you press and so on.

Now, after I've upgraded this does not work anymore. I've torn my hair trying to figure out why and It comes down to this:





My guess is that cegui has a similar queing-system internally this time around, and that the event that I subscribe gets removed at once, since I told it to remove the event with that same string.
I bet you're wondering why I'm removing the events at all, and it's because certain Gui-objects has to be initialized several times, and it's a precaution to prevent one window having to send several hundreds of callbacks
each time it's clicked after an hour of play-time.

There have been no changes to the event system from 0.6.2 to 0.7.x I'm not sure why what you are doing worked before.

Before I can offer insight, I think we need to know what the function "removeSubscibedEvent" is, when it's called and what it's doing

CE.

Nevermind me. I hadn't got my morning-dose of caffein in me, it was an idiotic error were I subscribed to the wrong window. Sorry.