Before dirty rectangle system (analysis \/ release):\r\nShip scene: 13.50 \/ 57 fps\r\nLucre Island: 9 \/ 47 fps\r\nAct 1 Beginning: 25 \/ 135 fps\r\nGrim scene 1: 50 \/ 160 fps\r\nGrim scene 2: 62 \/ 220 fps\r\nGrim scene 3: 57 \/ 243 fps\r\nGrim scene 4: 60 \/ 205 fps<\/pre>\nAfter dirty rectangle system (analysis \/ release):\r\nShip scene: 12 \/ 55 fps\r\nLucre Island: 9 \/ 45 fps\r\nAct 1 Beginning: 24 \/ 133 fps\r\nGrim scene 1: 23 \/ 136 fps\r\nGrim scene 2: 62 \/ 500 fps\r\nGrim scene 3: 27 \/ 180 fps\r\nGrim scene 4: 42 \/ 250 fps<\/pre>\nAs we can see dirty rects introduces an heavy overhead, especially with analysis build; but release build is somewhat balanced: the fps is pretty much the same for crowded scenes whereas it goes up by quite a bit if the scene has only a few animated objects (like grim scene 2 or scene 4, where animated objects are small and dirty rects yield some performance advantage).<\/p>\n
In my personal opinion dirty rects should only be employed on some specific scenarios, as its overhead generally slows down the code and it only shines in some cases.
\nDirty rects is a system that is probably better off being used in 2D games where screen changes are more controllable and there is no need to perform more calculation to know which region of the screen is going to be affected.<\/p>\n
Developing this system was quite challenging and it took a lot of time but I think that the overall task was beneficial because it gave us an insight on how this could have affected performance: I think that implementing this system on an higher level of abstraction might result in being more effective but more research would be required for doing so (such system would not be applicable for this project though as the engine has to support a vast variety of games).<\/p>\n","protected":false},"excerpt":{"rendered":"
As I’ve spent the last week fixing some minor bugs and documenting code, I wanted to analyse better the effects of this system on the current games. I’ve done some profiling by measuring fps in two modes: analysis and release; Analysis build is a build with less optimizations enabled and debug symbols whilst release mode […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-62","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.scummvm.org\/subr3v\/wp-json\/wp\/v2\/posts\/62","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.scummvm.org\/subr3v\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.scummvm.org\/subr3v\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.scummvm.org\/subr3v\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.scummvm.org\/subr3v\/wp-json\/wp\/v2\/comments?post=62"}],"version-history":[{"count":3,"href":"https:\/\/blogs.scummvm.org\/subr3v\/wp-json\/wp\/v2\/posts\/62\/revisions"}],"predecessor-version":[{"id":72,"href":"https:\/\/blogs.scummvm.org\/subr3v\/wp-json\/wp\/v2\/posts\/62\/revisions\/72"}],"wp:attachment":[{"href":"https:\/\/blogs.scummvm.org\/subr3v\/wp-json\/wp\/v2\/media?parent=62"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.scummvm.org\/subr3v\/wp-json\/wp\/v2\/categories?post=62"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.scummvm.org\/subr3v\/wp-json\/wp\/v2\/tags?post=62"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/a>\n\t\t\t<\/div><\/figure>