Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 7.8K All Categories
- 11 Help with translations
- 4.2K General questions
- 107 Roadmap
- 358 Game & application design
- 315 Plugins
- 70 User experience
- 75 Marketplace
- 290 Code snippets
- 34 Building a team?
- 269 Suggestions & requests
- 352 Announce your apps made with Gideros.
- 90 Step by step tutorials
- 668 Bugs and issues
- 195 Introduce yourself
- 239 Announcements
- 106 Forum talk
- 404 Relax cafe
In this Discussion
RenderTarget memory allocation issue
FlimFlamboyant
Member
Version 2013.06.3
I believe I've found a rather nasty bug regarding texture memory allocation in connection with RenderTarget.new().
I have an app which is utilizing a retro-style graphics scheme (blocky pixels and whatnot). To accomplish this, I'm using logical dimensions of only 160x240 and letting the framework handle the up-scaling (using "pixelPerfect") for all of my assets at draw time. On my iPad 3, this results in a logical scale of 8.
When creating a render target while this logical scale is active, the actual dimensions of the texture remain exactly as I requested. For instance, if I do a RenderTarget.new(128, 128) and call getWidth(), it returns 128, exactly as expected. However, when I check my texture memory usage, I discover that it's actually allocating 64 times as much memory as it needs (8x8, as per the logical scale).
I have a workaround that's simple enough, I just set the scale mode to "noScale", create my render target, then set it back to "pixelPerfect" immediately afterward, but I figured I should call this out.
I believe I've found a rather nasty bug regarding texture memory allocation in connection with RenderTarget.new().
I have an app which is utilizing a retro-style graphics scheme (blocky pixels and whatnot). To accomplish this, I'm using logical dimensions of only 160x240 and letting the framework handle the up-scaling (using "pixelPerfect") for all of my assets at draw time. On my iPad 3, this results in a logical scale of 8.
When creating a render target while this logical scale is active, the actual dimensions of the texture remain exactly as I requested. For instance, if I do a RenderTarget.new(128, 128) and call getWidth(), it returns 128, exactly as expected. However, when I check my texture memory usage, I discover that it's actually allocating 64 times as much memory as it needs (8x8, as per the logical scale).
I have a workaround that's simple enough, I just set the scale mode to "noScale", create my render target, then set it back to "pixelPerfect" immediately afterward, but I figured I should call this out.
Comments
The no scale, scale fix works for this so it must be broken.
https://deluxepixel.com
Fragmenter - animated loop machine and IKONOMIKON - the memory game