| commentid | objectid | typeid | userid | subject | comment | timestamp | parentid |
|---|---|---|---|---|---|---|---|
| 13161 | Briquolo | games | -1 | Re: Briquolo | <p>Same here - on RH 9 it compiled, installed, and ran fine. Promising game - I played it for a few hours. This was last night. </p> Today, however, I can't get it to run. It gives this: <pre> BRIQUOLO v0.4 Fatal signal: Segmentation Fault (SDL Parachute Deployed) </pre> </p> <p> Did a debug build (./configure --enable-debug; make clean all) so that I could try to debug it with GDB. Here's the output from running it under GDB, with stacktrace: </p> <p> <pre> (gdb) run Starting program: /data3/Build/briquolo-0.4/src/briquolo [New Thread 1077978784 (LWP 7662)] BRIQUOLO v0.4 [New Thread 1098210608 (LWP 7665)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1077978784 (LWP 7662)] 0x42031c81 in __strtod_internal () from /lib/tls/libc.so.6 (gdb) bt #0 0x42031c81 in __strtod_internal () from /lib/tls/libc.so.6 #1 0x4212a417 in __libc_ptyname2 () from /lib/tls/libc.so.6 #2 0x40095108 in __gluTessErrorString () from /usr/lib/libGLU.so.1 #3 0x40097edc in gluBuild2DMipmaps () from /usr/lib/libGLU.so.1 #4 0x080a11a2 in MOGL_Texture::_Init() (this=0x80ea1c0) at MOGL_Texture.cpp:106 #5 0x080a1104 in MOGL_Texture::ChargerPNG(char const*) (this=0x80ea1c0, p_NomFichier=0x80de7a4 "/usr/local/share/briquolo/data/Environment.1.png") at MOGL_Texture.cpp:89 #6 0x0807e129 in Texture::ChargerTextures() () at Texture.cpp:42 #7 0x08058d13 in CasseBrique (this=0xbfffee40) at CasseBrique.cpp:88 #8 0x08064f54 in main (argc=1, argv=0xbffff1b4) at main.cpp:38 #9 0x420156a4 in __libc_start_main () from /lib/tls/libc.so.6 (gdb) </pre> </p> <p> This is a RedHat 9 system, AMD Athlon, ATI Radeon 32MB DDR. It worked fine yesterday, and other OpenGL apps (TuxRacer, at least) are still working fine. Any ideas as to what's gone wrong? </p><p> (The file mentioned in the stacktrace - "/usr/local/share/briquolo/data/Environment.1.png" - is still there, and accessible.) </p><p> Any help would be greatly appreciated, as I really like this game! </p> | 2003-08-12 10:17:50 | 13147 |
| 13162 | Slickworm | games | 8167 | doesn't compile | when I type make (after configure) I have this message :<p> Making all in src<br> make[1]: Entering directory `/usr/local/src/slickworm-0.2.0/src'<br> g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -Wall -W -Wno-unused -DDATADIR=\"/usr/local/share/slickworm/data\" -I/usr/include/SDL -D_REENTRANT -c application.cpp<br> Dans le fichier inclus à partir de application.cpp:50:<br> audiosystemopenal.h:88: erreur de syntaxes avantle jeton « * »<br> make[1]: *** [application.o] Erreur 1<br> make[1]: Leaving directory `/usr/local/src/slickworm-0.2.0/src'<br> make: *** [all-recursive] Erreur 1<p> My system:<br> Gentoo Linux uptodate<br> slickworm-0.2.0<br> openal-20020127<br> ODE 0.039<br> SDL 1.2.5<br> SDL_image 1.2.2<br> | 2003-08-12 10:21:16 | 0 |
| 13163 | Briquolo | games | -1 | Re: Briquolo | <p> Sorry, should have read the other comments. I had changed the screen resolution. Deleting my ~/.briquolo directory fixed it. </p> <p> Guess this is probably a fairly simple bug, likely to be fixed soon. Might try digging around in the code to find it mysellf, if I can find the time. In the meantime, I can play the game again! :) </p> Thanks! | 2003-08-12 10:25:19 | 13161 |
| 13164 | noeGNUd | games | 6732 | Why didn't i rated this one already? | Version 0.7.0 was excellent. i'm just downloading 0.8.0 full (55Mb) and i bet it's worth every byte, like the previous one was. | 2003-08-12 10:35:42 | 0 |
| 13165 | ScummVM | games | 4553 | Re: BASS stuck trying to get to Doctor B | You're supposed to know why you'd go to the doc before you try to get in. After all, you aren't particularly jazzed about cosmetic surgery. | 2003-08-12 10:46:58 | 12998 |
| 13166 | Neverball | games | -1 | problems with optical mouse? | hi there, a _very_ nice game. i've got some problems though, as some levels start to shake uncontrollably. is it a bug or a feature. (if it's the latter, i'd suggest to turn it off - in the first case, i can only hope so. ;) it may be related to me using an optical mouse (which, as optical mouses do, tends to flicker in the sub-pixel range). would it be possible to include a hysteresis option for this case? keep it on! | 2003-08-12 11:15:41 | 0 |
| 13167 | Briquolo | games | 7378 | Pretty | ...and compiled easily. The rushing transparent water should scroll much slower, that would make it less annoying, I'd guess. Controlling the ball is too hard; I like the way it's done in lbreakout, where you can set the whole paddle to be convex... | 2003-08-12 11:22:13 | 0 |
| 13168 | Atomic Tanks | games | -1 | very funny | try it! | 2003-08-12 12:06:52 | 0 |
| 13169 | Briquolo | games | -1 | Re: super bien fait | thx.<br> tips for tips, you need to put a br tag to have a nice layout to your posts around here :)<br> well, the simplest suggestion i can come up right now, is to be able to remove it alltogether in the options, so that people like me wont get annoyed.<br> I just looked carefully at it, and it is annoying only in the area of the paddle. when i'm looking at the bricks, it's not annoying and seems smaller. I believe the pattern is too big, too bright and attract the eye away from the paddle. <br> | 2003-08-12 12:18:02 | 13155 |
| 13170 | Neverball | games | 8316 | Re: problems with optical mouse? | A number of people have reported serious control issues. The first such post was tomble's, so he and I traded some email in an attempt to resolve the issue. It seems that this is how the game behaves when the hardware is not powerful enough to support it. Disappointing answer, I know.<p> Apparently if the value of RESPONSE in src/game.h is increased (to say 0.5) then the game becomes controllable. However, this is the time period over which input is smoothed, so control will become sluggish.<p> The sad truth is, I gotta put the performance minimum somewhere. If the floor is rotating uncontrollably, you're probably below this minimum. If you have a decent machine with a hardware 3D board, double check that your OpenGL isn't falling back on Mesa. | 2003-08-12 12:42:48 | 13166 |