|
|
This thread is locked; no one can reply to it.
|
1
2
|
| Allegro 4.2.1 & AllegroGL 0.4.0RC7 bugs |
|
Niunio
Member #1,975
March 2002
|
I've updated my Allegro and AllegroGL (Win32 only, tomorrow I'll update my Kubuntu). They works nice, specially AllegroGL because the prior version (CVS) didn't work with my Intel GFX, the new version works without big problems, but I find two bugs: Allegro: The square root doesn't works well. In the math test I tried "49 [sqrt]" and it doesn't return exactly 7 (7 * 7 = 49, so sqrt (49) = 7). I don't remember what it returned before the update. My System is Pentium 4, Windows XP SP2, MinGW32 5.0, MSys 1.0, Graphics Intel i810, Allegro 4.2.1, AllegroGL 0.4.0 RC7 ----------------- |
|
tobing
Member #5,213
November 2004
|
I'll put my previous post into this thread instead: AllegroGL: I have just recompiled the released version of allegrogl on my PC here, and dumbtest crashes again. The PC has an Intel Graphics chipset, and we had this problem discussed some time ago, a few weeks I think. There was a fix, and I thought it should have been in the SVN, but now I see that seemingly that fix got lost somewhere? Please check! I have double checked that my local files are identical to those from the released version. Ah, btw, dumbtest crashes in line 52, because in line 51 the allocation of a video bitmap of dimension 50x50 failed, but the resulting pointer isn't checked to be non 0. About fonttest: This is due to a broken a32.tga file. I'm not sure if the reason os known, but it was something about SVN and Windows or so... |
|
Elias
Member #358
May 2000
|
Do the other AllegroGL examples work? If you have the time, you could compile in debug mode (make DEBUGMODE=2 LOGLEVEL=2; make install DEBUGMODE=2 LOGLEVEL=2), and AllegroGL will write down everything it does in the file allegro.log. But maybe it's related to tobing's problem in the other thread, since you both have an Intel card. -- |
|
tobing
Member #5,213
November 2004
|
The other examples work for me. The point is, there has been a fix for this around... Found the thread: http://www.allegro.cc/forums/thread/588077 |
|
Milan Mimica
Member #3,877
September 2003
|
tobing said: AllegroGL: I have just recompiled the released version of allegrogl on my PC here, and dumbtest crashes again. The PC has an Intel Graphics chipset, and we had this problem discussed some time ago, a few weeks I think. There was a fix, and I thought it should have been in the SVN, but now I see that seemingly that fix got lost somewhere? Please check!
It has to crash because your GFX cars doesn't support either ARB_npot or ARB_texture_rectangle OGL extensions. The fix you are probably referring to was for your other card, X850Pro. I proposed the patch on the ML, Bob was against it, so it was left unapplied. http://sourceforge.net/mailarchive/message.php?msg_id=37179899 Niunio said: fonttest.c doesn't work. No error message, no window, no output, no nothing, just do nothing... I remember it crashing when my desktop color depth was 16-bit depth. set_gfx_mode failed or something... Can you try it in 32-bit?
-- |
|
tobing
Member #5,213
November 2004
|
I see, thanks. I have tried fonttest with 32bit resolution, but the point was that the file a32.tga is somehow damaged. Never got a proper version of that file, even not when I accessed the SVN depot using the web interface. Strange. Here's the posting I'm refering to: |
|
Elias
Member #358
May 2000
|
What would be a fix for dumbtest? Recreate the bitmap as 64x64 if NULL is returned? -- |
|
tobing
Member #5,213
November 2004
|
or just create it as 64x64 instead. |
|
Milan Mimica
Member #3,877
September 2003
|
There is no point creating a 64x64 bitmap. dumbtest is used to test the capabilities of gfx card and the AGL ability to use this capabilities. The returned bitmap pointer should be tested all over the code and display "unsupported" where the image should be. edit:
-- |
|
tobing
Member #5,213
November 2004
|
OK, I'll wait for the corrected dumbtest.c in SVN then. Just checked: The a32.tga file in the distribution is identical to the one I have retrieved from SVN. Size is 9984 bytes, if that helps... |
|
Milan Mimica
Member #3,877
September 2003
|
Can't you open it in a image viewer/editor and see if it's corrupted or not?
-- |
|
tobing
Member #5,213
November 2004
|
I can do that when I'm back home. I don't have a viewer at work that can display tga-files, but I remember that I have once opened the file with IrfanView, and only saw the letter a in that file... |
|
Elias
Member #358
May 2000
|
It's supposed to contain only the letter A -- |
|
tobing
Member #5,213
November 2004
|
Aha, so why does it not load then? Now I'm a little confused... |
|
Milan Mimica
Member #3,877
September 2003
|
set_color_depth(32); in fonttest.c is wrong. set_gfx_mode will fail if desktop color depth is other than 32, because can't change that in windowed mode. And fonttest doesn't display correctly in 16-bit mode. 32-bit ALPHA, LUMINANCE and INTENSITY are not displayed.
-- |
|
tobing
Member #5,213
November 2004
|
It doesn't help: I've replaced set_color_depth(32); by the two lines you suggested, but the crash remains the same. Happens in allegro, file fontbmp.c, line 263, when it tries Desktop resolution is 32 bit, and everything was built from scratch and as debug version, too. |
|
Elias
Member #358
May 2000
|
Just to make sure, are you using Allegro 4.2.1? -- |
|
tobing
Member #5,213
November 2004
|
No, I'm using 4.2.0, didn't have much time to upgrade to 4.2.1 yet. Is there a fix which could affect that behavior in 4.2.1? |
|
Elias
Member #358
May 2000
|
Yes. The anti aliased fonts require Allegro 4.2.1. In general, I see AllegroGL 0.4.0 depending on Allegro 4.2.1 - that's also why I wanted to wait with the release after 4.2.1 comes out. -- |
|
tobing
Member #5,213
November 2004
|
Just unpacked the all421.zip file and started to compile. First, fix msvc7 --msvcpaths Then, make. What's going wrong here? I'm using MSVC 7.1 and MinGW is also installed... Edit: Seems that the compiler installation is different from what would be needed to build allegro. No idea what's wrong though, I'll try again at home. Edit again: At home now, allegro 4.2.1 compiled, dumbtest OK, fonttest OK. Great! |
|
Bob
Free Market Evangelist
September 2000
|
Quote: There is no point creating a 64x64 bitmap. dumbtest is used to test the capabilities of gfx card and the AGL ability to use this capabilities. The returned bitmap pointer should be tested all over the code and display "unsupported" where the image should be. I disagree: AGL should support all video bitmap sizes that we can. I think this is a bug I accidentally added with revision 1016. Before that, AGL did support NPOT video bitmaps on GPUs that don't support NPOTs. -- |
|
Milan Mimica
Member #3,877
September 2003
|
Quote: I disagree: AGL should support all video bitmap sizes that we can. But it can't. His card doesn't support either ARB_npot or ARB_texture_rectangle.
-- |
|
Elias
Member #358
May 2000
|
I think, this was solved by scaling the image to the next power of two, and using a PO T texture. Of course, I doubt that usually can be a good idea.. what might work though is, combine multiple POT textures into a single video bitmap, I think AllegroGL already can do that. Not that I know the code well enough to implement/fix it. -- |
|
Bob
Free Market Evangelist
September 2000
|
Quote: what might work though is, combine multiple POT textures into a single video bitmap, I think AllegroGL already can do that. This is what used to work (and probabaly still does). -- |
|
Milan Mimica
Member #3,877
September 2003
|
Quote: I think, this was solved by scaling the image to the next power of two, and using a POT texture. We do this for textures, not for bitmaps.
-- |
|
|
1
2
|