Specs: Lenovo Thinkpad X61 Tablet, Intel Core 2 Duo L7500, Intel GMA X3100, 4GB RAM, Windows 7 32-bit
You support:
Framebuffers
Non-Po2 Framebuffers
Non-Po2 Images
Framebuffers up to the size 4096 x 4096
Power of 3 Framebuffers up to the size 2187 x 2187
Survey: Do You Support Framebuffers and/or Non-Po2 [RERUN]
Re: Survey: Do You Support Framebuffers and/or Non-Po2 [RERU
Last edited by pk on Sat Mar 10, 2012 3:09 am, edited 2 times in total.
ALL CREATURE WILL DIE AND ALL THE THINGS WILL BE BROKEN. THAT'S THE LAW OF SAMURAI.
- ston
- Prole
- Posts: 21
- Joined: Fri Jan 27, 2012 9:53 am
- Location: Holt, a small village in Wiltshire. We have cider!
Re: Survey: Do You Support Framebuffers and/or Non-Po2 [RERU
On my work PC: HP Compaq 6000 Pro, Duo E8500 CPU, 4GB RAM, Intel Express Q45/Q43 gfx (AKA 'steaming pile of junk'):
You support:
Framebuffers
Non-Po2 Framebuffers
Non-Po2 Images
Framebuffers up to the size 4096 x 4096
Power of 3 Framebuffers up to the size 2187 x 2187
You support:
Framebuffers
Non-Po2 Framebuffers
Non-Po2 Images
Framebuffers up to the size 4096 x 4096
Power of 3 Framebuffers up to the size 2187 x 2187
- slime
- Solid Snayke
- Posts: 3162
- Joined: Mon Aug 23, 2010 6:45 am
- Location: Nova Scotia, Canada
- Contact:
Re: Survey: Do You Support Framebuffers and/or Non-Po2 [RERU
There's a decent list of video cards which support framebuffers/canvases here: http://www.kludx.com/capability.php?capability=512 and a bigger one here: http://feedback.wildfiregames.com/repor ... fer_object , and a list of cards which support non power of 2 images http://feedback.wildfiregames.com/repor ... wer_of_two (there will never be a case where a video card supports npo2 images and regular framebuffers but doesn't support npo2 framebuffers, because images and framebuffers both use opengl 2d textures).
The wildfire games reports also list max texture sizes for all video cards, among many other things.
The wildfire games reports also list max texture sizes for all video cards, among many other things.
Re: Survey: Do You Support Framebuffers and/or Non-Po2 [RERU
ATI Radeon HD 6850, AMD Phenom X4 965 (iirc)
Framebuffers, Non-Po2
Framebuffers up to the size 32768^2
Po3 Framebuffers up to the size 19683^2
Framebuffers, Non-Po2
Framebuffers up to the size 32768^2
Po3 Framebuffers up to the size 19683^2
Re: Survey: Do You Support Framebuffers and/or Non-Po2 [RERU
NVIDIA GeForce GTX 570M on Windows 7 x64
Framebuffers, npot framebuffers, npot images
Framebuffers up to size 16384x16384
Po3 framebuffers up to size 19683x19683
Framebuffers, npot framebuffers, npot images
Framebuffers up to size 16384x16384
Po3 framebuffers up to size 19683x19683
Re: Survey: Do You Support Framebuffers and/or Non-Po2 [RERU
GT120 256, Duo Core, OSX Snow Leo
With 0.7.2
Framebuffers, Non-Po2 Framebuffers, Non-Po2 Images
Hangs and crashes in max size test.
With 0.8
Non-Po2 Images only
Max Size Test? Don't hang, don't crash, don't do nothing even after some minutes.
Crash Log
With 0.7.2
Framebuffers, Non-Po2 Framebuffers, Non-Po2 Images
Hangs and crashes in max size test.
With 0.8
Non-Po2 Images only
Max Size Test? Don't hang, don't crash, don't do nothing even after some minutes.
Crash Log
Code: Select all
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.apple.GeForceGLDriver 0x8f0d975f gldAttachDrawable + 2655
1 com.apple.GeForceGLDriver 0x8f1a42f8 gldUpdateDispatch + 15176
2 com.apple.GeForceGLDriver 0x8f1a4bfe gldFinish + 702
3 com.apple.opengl 0x955a703c CGLFlushDrawable + 67
4 SDL 0x0055138b SDL_SoftStretch + 14171
5 SDL 0x005453d7 SDL_GL_SwapBuffers + 39
6 org.love2d.love 0x00060c15 love::graphics::opengl::w_present(lua_State*) + 19
7 com.yourcompany.Lua 0x0059f623 luaD_precall + 890
8 com.yourcompany.Lua 0x005b65f7 luaV_execute + 7461
9 com.yourcompany.Lua 0x0059f895 luaD_call + 165
10 com.yourcompany.Lua 0x00595145 f_call + 48
11 com.yourcompany.Lua 0x0059eaba luaD_rawrunprotected + 73
12 com.yourcompany.Lua 0x0059fc04 luaD_pcall + 99
13 com.yourcompany.Lua 0x005951ea lua_pcall + 163
14 com.yourcompany.Lua 0x0059acfd luaB_xpcall + 104
15 com.yourcompany.Lua 0x0059f623 luaD_precall + 890
16 com.yourcompany.Lua 0x005b65f7 luaV_execute + 7461
17 com.yourcompany.Lua 0x0059f895 luaD_call + 165
18 com.yourcompany.Lua 0x005950eb lua_call + 67
19 org.love2d.love 0x0002fd94 SDL_main + 452
20 org.love2d.love 0x00089447 -[SDLMain applicationDidFinishLaunching:] + 95
21 com.apple.Foundation 0x90f9adb3 _nsnote_callback + 176
22 com.apple.CoreFoundation 0x927c2763 __CFXNotificationPost + 947
23 com.apple.CoreFoundation 0x927c216a _CFXNotificationPostNotification + 186
24 com.apple.Foundation 0x90f8fc50 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128
25 com.apple.Foundation 0x90f9d05d -[NSNotificationCenter postNotificationName:object:] + 56
26 com.apple.AppKit 0x9a305216 -[NSApplication _postDidFinishNotification] + 125
27 com.apple.AppKit 0x9a305126 -[NSApplication _sendFinishLaunchingNotification] + 74
28 com.apple.AppKit 0x9a51e9c5 -[NSApplication(NSAppleEventHandling) _handleAEOpenDocumentsForURLs:] + 975
29 com.apple.AppKit 0x9a45bfe0 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 236
30 com.apple.Foundation 0x90fd01f8 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 511
31 com.apple.Foundation 0x90fcffbc _NSAppleEventManagerGenericHandler + 228
32 com.apple.AE 0x935eef5c aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 166
33 com.apple.AE 0x935eee5b dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 43
34 com.apple.AE 0x935eed65 aeProcessAppleEvent + 197
35 com.apple.HIToolbox 0x97e9a197 AEProcessAppleEvent + 50
36 com.apple.AppKit 0x9a2d57d2 _DPSNextEvent + 1420
37 com.apple.AppKit 0x9a2d4dd6 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
38 com.apple.AppKit 0x9a2971f3 -[NSApplication run] + 821
39 org.love2d.love 0x00089cbc main + 1882
40 org.love2d.love 0x0002fa66 start + 54
Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x9a040382 kevent + 10
1 libSystem.B.dylib 0x9a040a9c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib 0x9a03ff59 _dispatch_queue_invoke + 163
3 libSystem.B.dylib 0x9a03fcfe _dispatch_worker_thread2 + 240
4 libSystem.B.dylib 0x9a03f781 _pthread_wqthread + 390
5 libSystem.B.dylib 0x9a03f5c6 start_wqthread + 30
Thread 2:
0 libSystem.B.dylib 0x9a019b5a semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x9a0476e1 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x9a0765a8 pthread_cond_timedwait_relative_np + 47
3 com.apple.audio.CoreAudio 0x955d33ab CAGuard::WaitFor(unsigned long long) + 219
4 com.apple.audio.CoreAudio 0x955d63dd CAGuard::WaitUntil(unsigned long long) + 289
5 com.apple.audio.CoreAudio 0x955d3cda HP_IOThread::WorkLoop() + 1892
6 com.apple.audio.CoreAudio 0x955d3571 HP_IOThread::ThreadEntry(HP_IOThread*) + 17
7 com.apple.audio.CoreAudio 0x955d3488 CAPThread::Entry(CAPThread*) + 140
8 libSystem.B.dylib 0x9a047259 _pthread_start + 345
9 libSystem.B.dylib 0x9a0470de thread_start + 34
Thread 3:
0 libSystem.B.dylib 0x9a019c0e mach_wait_until + 10
1 libSystem.B.dylib 0x9a0a1429 nanosleep + 345
2 SDL 0x0055a453 SDL_Delay + 99
3 org.love2d.love 0x0003c65d love::audio::openal::Audio::run(void*) + 35
4 SDL 0x0054becd SDL_Linked_Version + 397
5 SDL 0x0055a1f1 SDL_SemWait + 49
6 libSystem.B.dylib 0x9a047259 _pthread_start + 345
7 libSystem.B.dylib 0x9a0470de thread_start + 34
Thread 4:
0 libSystem.B.dylib 0x9a019c0e mach_wait_until + 10
1 libSystem.B.dylib 0x9a0a1429 nanosleep + 345
2 SDL 0x0055a5c3 SDL_Delay + 467
3 SDL 0x0054becd SDL_Linked_Version + 397
4 SDL 0x0055a1f1 SDL_SemWait + 49
5 libSystem.B.dylib 0x9a047259 _pthread_start + 345
6 libSystem.B.dylib 0x9a0470de thread_start + 34
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0xe00002c2 ebx: 0x8f1a4001 ecx: 0xbfffe39c edx: 0xe00002c2
edi: 0xbfffe350 esi: 0x17294000 ebp: 0xbfffe2d8 esp: 0xbfffe2d8
ss: 0x0000001f efl: 0x00010296 eip: 0x8f0d975f cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000000
Re: Survey: Do You Support Framebuffers and/or Non-Po2 [RERU
Framebuffers, Non-Po2 Framebuffers, Non-Po2 Images
Specs:
OS:
MS Windows 7 Home Premium EDIT: 64-bit
CPU:
Intel Celeron T3100 @ 1.90GHz
Penryn 45nm Technology
RAM:
3.00 GB Dual-Channel DDR2 @ 332MHz
MOTHERBOARD:
Hewlett-Packard 3069 (CPU)
GRAPHICS:
Generic PnP Monitor (1366x768@60Hz)
Mobile Intel(R) 4 Series Express Chipset Family
HARD DRIVES:
313GB SAMSUNG SAMSUNG HM320II ATA Device (SATA)
AUDIO:
IDT High Definition Audio CODEC
I'm not an expert so I don't really know is this is crap or not, can somebody tell me?
Specs:
OS:
MS Windows 7 Home Premium EDIT: 64-bit
CPU:
Intel Celeron T3100 @ 1.90GHz
Penryn 45nm Technology
RAM:
3.00 GB Dual-Channel DDR2 @ 332MHz
MOTHERBOARD:
Hewlett-Packard 3069 (CPU)
GRAPHICS:
Generic PnP Monitor (1366x768@60Hz)
Mobile Intel(R) 4 Series Express Chipset Family
HARD DRIVES:
313GB SAMSUNG SAMSUNG HM320II ATA Device (SATA)
AUDIO:
IDT High Definition Audio CODEC
I'm not an expert so I don't really know is this is crap or not, can somebody tell me?
u wot m8
Re: Survey: Do You Support Framebuffers and/or Non-Po2 [RERU
0.8.0 breaks several things. Framebuffer is now Canvas, and the OpenGL version requirements are higher.coffee wrote: With 0.8
Non-Po2 Images only
Max Size Test? Don't hang, don't crash, don't do nothing even after some minutes.
ALL CREATURE WILL DIE AND ALL THE THINGS WILL BE BROKEN. THAT'S THE LAW OF SAMURAI.
- slime
- Solid Snayke
- Posts: 3162
- Joined: Mon Aug 23, 2010 6:45 am
- Location: Nova Scotia, Canada
- Contact:
Re: Survey: Do You Support Framebuffers and/or Non-Po2 [RERU
As was shown in the wilfiregames link I posted above, ~91% of video card/driver combinations support framebuffers/canvases, and ~86% support non power of two images (although in love 0.8.0 images are auto-padded if there is no npo2 video card support - but canvases are not).
Additionally in love 0.8.0 you can test for support with love.graphics.isSupported("canvas") and love.graphics.isSupported("npot") (although the last one is usually unnecessary because of the padding).
Additionally in love 0.8.0 you can test for support with love.graphics.isSupported("canvas") and love.graphics.isSupported("npot") (although the last one is usually unnecessary because of the padding).
Re: Survey: Do You Support Framebuffers and/or Non-Po2 [RERU
Here's a real simple test using the new love.graphics.isSupported function:
My new results are:
Pass: NPOT
Fail: Canvas
Fail: PixelEffects
I have to say this is quite disheartening. My graphics card went from being awesome to being pitiful.
I can live without shaders. However, taking away my FrameBuffers for full OpenGL 3.0 coverage seems... overzealous.
My new results are:
Pass: NPOT
Fail: Canvas
Fail: PixelEffects
I have to say this is quite disheartening. My graphics card went from being awesome to being pitiful.
I can live without shaders. However, taking away my FrameBuffers for full OpenGL 3.0 coverage seems... overzealous.
Last edited by pk on Sat Mar 10, 2012 9:11 am, edited 1 time in total.
ALL CREATURE WILL DIE AND ALL THE THINGS WILL BE BROKEN. THAT'S THE LAW OF SAMURAI.
Who is online
Users browsing this forum: No registered users and 2 guests