RE: Texture mapping
2017-07-01, 6:56 (This post was last modified: 2017-07-01, 6:57 by Merlijn Wissink.)
2017-07-01, 6:56 (This post was last modified: 2017-07-01, 6:57 by Merlijn Wissink.)
(2017-07-01, 2:45)Travis Cobbs Wrote:(2017-06-30, 6:40)Merlijn Wissink Wrote: batman-crop.ldr uses more memory than batman.ldr in my LDview (~100MB vs ~85MB). How's that possible then? Or did you mean the vram?
I meant system memory. It's very odd for the cropped one to use more memory. Just to verify, each LDView run was separate, right? In other words, the only file you opened in LDView was the file in question (batman.ldr or batman-crop.ldr), and exited LDView between files? I would hope that LDView isn't be leaking that much memory, but memory does become fragmented, which causes it to use more and more as time goes by.
I can't think of any reason why the cropped version would use more memory than the non-cropped version. The GLU (OpenGL Utility Library) code I use to convert the image data into OpenGL MIP-Mapping format will resize images so their dimensions are powers of 2. (It resizes to the closest power of 2.) So while the cropped one might be scaled up by 50% in a given dimension, it still shouldn't use more memory than the uncropped one.
Yes, I had just 1 LDview open at a time. No 2 LDviews at the same time. The memory usage. Every single time it's ~85MB vs ~100MB (non-cropped vs cropped). I just tried it again on my freshly started machine. Same thing.
my batmanlogo.png is 2000x600 130kB
my batmanlogo-crop.png is 1768x879 54.2 kB
Maybe there's a difference. It looks like Jaco changed the size of batmanlogo.png between your message and me trying it out?