Red Hat Bugzilla – Bug 200204
strange error message
Last modified: 2007-11-30 17:11:38 EST
Description of problem:
Another aspect having been mentioned during the review, in
Running it issues this error message:
Your plib (version 1.8.4) has a bug in the 3ds loader. Workaround enabled.
you had replied:
> Hmm, besides that does it work?
Well, it doesn't segfault, and doesn't expose issue which would qualify it as
I am hearing sound drop-outs, and am observing some kind of "sparkling".
Hard to describe, may-be "32bit wide and 1bit high white bit blob random noise"
desturbing the display matches.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run sturmbahnfahrer
I've had some sound issues myself during packaging, with which upstream has been
very helpfull and lead to the release of the 1.1 version (I started with
packaging the 1.0 version). Unfortunatly I cannot reproduce those you're
I've requested upstream to contact you (preferably through this BZ ticket) and
try to work things out with you. Sofar upstream has been very responsive.
Created attachment 133052 [details]
Screenshot exposing the "sparkling"
Note the "bright" (white?) artefacts near to the end of the "board".
Apparently, unlike previously stated, they aren't fixed width.
The wander accross the screen, always near to edges (e.g. along the edges of
the board) or near to animated elements (e.g. below the clock), whenever the
image changes/is moving.
To me they look like rendering artefacts.
The plib workaround message is harmless.
The sound drop outs can occur if the host machine is too slow.
Can you describe your hardware? CPU? MHz? graphics card?
The visual artefacts are puzzling. I cannot explain those. Could
it be hardware failure? Do other 3D apps run fine without visual
I noticed that on your screenshot, your fps is 3. Is this a
bogus measurement due to the screen grabbing that occurred?
Or is your framerate during play actually 3 fps?
In the latter case:
Frequent sound drop outs are to be expected.
The sound drop outs can in this case be avoided by increasing the
framelag argument of SoundEngineAlsa. Edit main.cxx at line 651
and double the 5000 value.
However: a higher nr will delay the sounds somewhat wrt visual
cues. Also, 3 fps is not really playable, so it may be in vain
to increase this val.
(In reply to comment #3)
> The plib workaround message is harmless.
> The sound drop outs can occur if the host machine is too slow.
> Can you describe your hardware? CPU? MHz? graphics card?
It's an older 1GHz Intel P4, w/ a GeForce4 MX 4000 (Using kmod-nvidia)
> The visual artefacts are puzzling. I cannot explain those. Could
> it be hardware failure? Do other 3D apps run fine without visual
Well, normally yes. I am using this machine for 3D application development
myself and so far haven't noticed such artefacts in other applications.
> I noticed that on your screenshot, your fps is 3. Is this a
> bogus measurement due to the screen grabbing that occurred?
Probably. The normal framerate with sturmbahnfahrer is, depending on the
complexity of the scene, somewhere in the 25-35fps range, typically near 30fps.
Bram, Any progress on this?
Graphics artefacts have not been reproducable.
About the sound: the reporter could try increasing the '5000' value
I recommended earlier.
Changing status to assigned, as this is not really new any more.
Ralf could you please try increasing the '5000' value as recomended in an
earlier comment? And then report back with the results?
Closing due to lack of response from reporter.