Make the icon renderer use sub viewports instead of copying textures

Bug #195832 reported by Erik Ogenvik on 2008-02-26
Affects Status Importance Assigned to Milestone
Erik Ogenvik

Bug Description

Currently icons is implemented through first rendering to a texture, and then copying the content of the texture to an area on another, larger, atlas texture. The problem with this is that since GPU operations are async we must wait some frames before we issue the copy op. All in all it's a cumbersome setup, since there exists a much better way through the use of sub viewports. Instead of rendering to a dedicated texture we can instead render directly to the atlas texture (i.e. to a subarea of that texture). That will do away with the need for a separate texture and the copy operation completely.

Changed in ember:
importance: Undecided → Wishlist
Erik Ogenvik (erik-ogenvik) wrote :

I've added this, but there seems to be some issues. Or more precise, it works splendidly if not for the fact that if there's a normal frame rendering sandwiched between two icon render ops, the area outside the current viewport will contain strange data. It seems as if there's either a bug which causes this behaviour, or it's intended behaviour and I've misunderstood how the Viewports work when applied to a render texture. It needs more investigation. All code is committed, but currently deactivated.

Changed in ember:
assignee: nobody → erik-hjortsberg
status: New → In Progress
Erik Ogenvik (erik-ogenvik) wrote :

Given some fixes in Ogre I think this should be revisited.

Changed in ember:
importance: Wishlist → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers