Recent changes to bugs

No respotted Black after a draw

Mst — Sun, 04 Nov 2012 08:29:00 -0000

The game ended 47:47 so there should be a respotted Black. But after potting Black the computer player continues playing and passed the shot to me.

Ball reset if close to pocket

Mst — Sun, 19 Aug 2012 20:56:44 -0000

If the white ball stays very narrow to a pocket it is a little inside the table. There is no need to do so. It's up to the player to get out of this situation.

Can not load its own config file

Émeric Dupont — Sun, 10 Jun 2012 10:25:15 -0000

foobillardplus can not load the default config file it creates on the first start.

Steps to reproduce (Revision 144)
Remove any trailing .foobillardrc
Checkout revision 144 (Start from a clean revision)
Compile and start foobillardplus
aclocal --force; autoconf -f; autoheader -f; automake -a -c -f; ./configure; make; src/foobillardplus

Quit from the game, to have it write its default config file
Start foobillardplus, so that it loads using config file
src/foobillardplus

Using attached patch, to continue parsing confg file after the first error encountered:

[stdout]
Player variables initialized
/home/emeric/.foobillardrc
Base-Configuration initialized
processing option 0=human
src/foobillardplus: unrecognized option 'з� �� YG�▒'
processing option 63=(null)
src/foobillardplus: unrecognized option '--nasrc/foobilla'
processing option 63=(null)
src/foobillardplus: unrecognized option '--posli'
processing option 63=(null)
processing option 19=--ai1P�]� YG�
src/foobillardplus: unrecognized option '-� �� )��v'
processing option 63=(null)
processing option 23=off
processing option 25=m
processing option 26=--portnum=56341
src/foobillardplus: unrecognized option '--geometr��24x750'
processing option 63=(null)
processing option 30=firefox
processing option 31=1
src/foobillardplus: unrecognized option '--`DG� YG�tible=off'
processing option 63=(null)
src/foobillardplus: unrecognized option '--processing option 63=(null)

m=56341
28'
processing option 63=(null)
processing option 36=off
processing option 37=off
processing option 38=off
processing option 39=off
processing option 40=match
processing option 41=off
processing option 42=30.000000
processing option 43=on
processing option 44=on
processing option 45=on
processing option 46=2
processing option 47=on
processing option 48=on
processing option 49=on
processing option 50=10
processing option 51=90
processing option 52=10
processing option 53=off
processing option 54=off
processing option 55=0.000000
processing option 56=on
processing option 57=off
processing option 58=on
processing option 59=0
processing option 60=on
processing option 61=1
processing option 62=en
Configuration processing
Language initialized
[/stdout]

But at least it loads a good part of the config. This does not explain why the rest looks so corrupted.

Problems on MS-Windows - crash

Holger Schäkel — Thu, 26 Jan 2012 01:53:14 -0000

On some systems (specially with ATI graphics acceleratos) and Windows foobillard++ crashes on every start. This is a problem with SDL 1.2.14 and SDL_GL_ACCELERATED_VISUAL. A few days ago SDL 1.2.15 is released and this error solved.

A new pre foobillard++ 3.43beta for windows follow the next days.

balls dont look right.

Anonymous — Sun, 22 Jan 2012 10:05:20 -0000

i have the latist foobillardplus from Arch Linux and the balls look like juggling balls i cant find any settings to change them back to normal balls, which means the only game i can really play is crambol because you cant tell the difference which is the legal ball.

my graphics and system all up to date, im using a nVidia 9200 graphic card with drivers.

dead end in tournament

Bat Guano — Wed, 11 Jan 2012 21:08:53 -0000

I attach a screen shot which documents a strange situation. During a tournament, I had to await the AI players' rounds to finish before I could play the next round against an AI-player.
However, when the black ball suddenly comes to rest in the position in the screen shot, none of the AI players is able to direct the cue ball in its direction. Instead, each at his turn sends the cue ball directly into the pocket above the black ball... That you see both players named "Sally Silver" may have to do with my speed-setting, as I want the AI players to finish their games quickly during a tournament. And I cannot control which picture the screen-capture will eventually produce (on several I could not even see the cue-ball), so I let the AI-players continue their dumb "shoot the cue-ball to the pocket" game and took many screen shots to compare.

End of a Tournament

Bat Guano — Sat, 07 Jan 2012 22:20:41 -0000

I played a tournament of snooker and got to play the last game, which I lost.

Normally, the last AI-player would have been the overall winner of the tournament. But instead, a new game started, again me against the same last AI-player. I could also perform the initial shoot but did not succeed in pocketing a red ball.

But the AI-player at his turn, did nothing. The "extra game" stopped right there. I know that the tournament history should not yet be fully functional, but I suspect a bug with wider consequences. PSE check if there is a relation between the two. In the history, the tournament has (as expected) no representation. Unfortunately, reproducing the phenomenon in all the details will be quite difficult. ;-)) And Snooker-tournaments are quite lengthy...

Black window/screen when history is open

Bat Guano — Wed, 04 Jan 2012 02:25:37 -0000

The history function works and is a really wonderful addition !

But as long as the browser is running, I cannot return to the game-window, which is completely black. Also, the window cannot be closed as long as the browser remains open. A full-screen display is changed to window-mode upon opening the history. The window is, of course, as black as when foobillardplus was running in a window from the start.

When the browser is closed, all returns to normal. Foobillard is back either in window-mode or full-screen.

display error, disrupted table-surface

Bat Guano — Wed, 04 Jan 2012 02:19:01 -0000

Revision 112:
Frequently, upon adjusting the table in preparation of the next strike, a display error occurs, as is documented in the attached screen-shot. This has happened in previous versions, too.

(And thanks for the screen-shot function. Works like a charm)

Pushed ball from the table

Bat Guano — Thu, 15 Dec 2011 22:08:19 -0000

I come here straight from a game of Snooker, where I had to play the green ball but chose my angle too steep. The ball hit the bank violently and rolled over to disappear. I instinctively even turned the table to see if it ... I don't know... "rolls over the floor" or something. :-)

But instead, I was accorded the point for the green ball and the game continued, as if I had been successful.