LÖVE

BlackBulletIV wrote:I think BarnD has completed the test without FB support.

Yeah, with the new one when it asks me to push space, it just wont do anything, just stays there doing nothing.
I feel so left out, eveyone else supports framebuffers..

Argh, I had someone else have trouble with the 'space' bit. Thankfully it's the last part, so you don't have to to run it.

I ran the updated version -- now it says I support everything. (Framebuffers up to the size of 16384x16384, PO3 framebuffers up to 19683x19683, maybe the maximum is 20000x20000?)

Jasoco wrote:What's your computer specs?

Ehm, it's an Asus laptop?
Ubuntu 10.10
3.7 GiB RAM
Quadcore Intel i3 (2.27 GHz)
Dunno about anything else --- I'm hopeless when it comes to hardware.

BlackBulletIV wrote:

nevon wrote: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.

I don't know what's going on here. I tried downloading the latest version, and I get the same thing. The only output I get is "killed". Could you have it output some messages along the way, so maybe we can figure out what's going on?

EDIT: Lol. I'm thinking driver issue, because it crashed my Flash player, somehow.

Just as a note, once you get to the number 16K and 19K the test stops. Anyone who gets those numbers might and probably does support larger FBs.

nevon wrote:

BlackBulletIV wrote:

nevon wrote: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.

I don't know what's going on here. I tried downloading the latest version, and I get the same thing. The only output I get is "killed". Could you have it output some messages along the way, so maybe we can figure out what's going on?

EDIT: Lol. I'm thinking driver issue, because it crashed my Flash player, somehow.

Wow that's weird. I guess I could do that, but I've spent too much time on this already today.

EDIT: I'm liking these results. 8 for everything so far. Sometime soon we might have to put a test like this out to the public to get an even bigger context.

I support everything. And that's on my laptop bought 4 years ago, with linux drivers (16384x16384 max fb size, 19683x19683 max po3 fb size).

I haven't tested this on my recently bought desktop machine, but it's bound to be more than that.

Awesome! As I said in my previous post, you can't get more than 16384x16384 and 19683x19683 on these tests, it cuts out then.

Same problem as BarnD.
"You support : Non-PO2 Images"
Then when I press "space", nothing happens.
I'll try on my others PCs.
[EDIT]

Results for another PC :

Ghuntar wrote:Same problem as BarnD.

I'm not alone.

Thanks for the results! Ah well, the framebuffer sizes isn't too important.

EDIT: Oh wait! Of course nothing happens! You guys don't support framebuffers, and the code is set to do nothing. However it should give a "thanks" message... I'll have to fix that sometime soon.