Survey: Do You Support Framebuffers and/or Non-Po2 [RERUN]

[Jasoco]

What's your computer specs? You can support pretty much anything. (I don't know what the maximum size is out there, but I put in the 8192 size just in case. Real world usage would probably rarely need more than 1024x1024 and maybe 1 or 2 of them.

[BlackBulletIV]

Sorry guys about the .love issue, and the bug that anjo kindly pointed out. I've updated this test to fix that bug, and run size tests. My computer comes out with everything! And sizes of 4096 x 4096 and 2187 x 2187! Not bad for 64 MB of shared memory.

If everyone could re-run the tests, that would be great.

[Lafolie]

Woohoo, looks like I support everything.


Edit: Nice typo there! "framesbuffers"

[BlackBulletIV]

Awesome!

EDIT: Fixed the typo .

[Lafolie]

You might wanna add a little message saying that the post-spacebar operations will take a few seconds too. I was bashing space because I had no idea what was going on.

Edit: Interesting. While I was having a paranoid moment and making sure there was no message already, I noticed that it worked it out much faster than the first run. Is this a systemy/processy cache thing? Or am I just overtired...

[nevon]

Your test died once it started trying to create framebuffers, so I don't know if my computer supports non-Po2 framebuffers or not. Couldn't you put the tests in pcalls so that the test won't die if it fails?

[bartbes]

Code: Select all

You support:
  Framebuffers
  Non-Po2 Framebuffers
  Non-Po2 Images
  Framebuffers up to the size 16384 x 16384
  Power of 3 Framebuffers up to the size 19683 x 19683

Power of 3?

[BlackBulletIV]

You might wanna add a little message saying that the post-spacebar operations will take a few seconds too. I was bashing space because I had no idea what was going on.

I guess it takes a few seconds for you because your Po3 FB support is so good. It takes a few milliseconds for me. I'm putting up one now.

Your test died once it started trying to create framebuffers, so I don't know if my computer supports non-Po2 framebuffers or not. Couldn't you put the tests in pcalls so that the test won't die if it fails?

I put them in pcalls. I don't what the problem is there. I think BarnD has completed the test without FB support.

Code: Select all

You support:
  Framebuffers
  Non-Po2 Framebuffers
  Non-Po2 Images
  Framebuffers up to the size 16384 x 16384
  Power of 3 Framebuffers up to the size 19683 x 19683

Power of 3?

Next up from power of 2. I can't create tonnes of framebuffers by doing it in increments of 5 or something. Powers help to condition how many sizes we create.

[bartbes]

I guess it takes a few seconds for you because your Po3 FB support is so good. It takes a few milliseconds for me. I'm putting up one now.

Yeah, same here, took pretty long. On the other hand, I gave up on jasoco's test after 30 seconds of completely freezing my computer, I had to do a hard reset.

[BlackBulletIV]

It would take long considering your supported resolutions! I'll put one up that gives a message saying what it's doing.