Recent changes to bugs

updateScore belongs in a timer, not in PigKeyNavBehaviour

Ted — Tue, 06 May 2008 21:57:15 -0000

Design/source review.

* View processElapsedFrames() in apps/PigShooter/Sources/PigKeyNavBehaviour.java

EXPECTED: no external calls.

ACTUAL: Key-nav-behaviour is tasked with updating the HUD display. This "sets a bad example for the chilluns" and, in general, is bad MVC.

What we want to do is make that call inside a timer created in the main PigShooter initialization. It is its own "controller."

Even better would be to make the HUD ("scorecard") be its own object, and IT can set up the timer at inception.

HUD display distorted when player moves

Ted — Tue, 06 May 2008 21:52:49 -0000

* Build & run PigShooter
- NOTE: It is easier to see the problem if you modify processElapsedFrames() in apps/PigShooter/Sources/PigKeyNavBehaviour.java to change
eTime > 999
to
eTime > 20
This forces the redraw to happen at 50fps, vice just 1fps
* Drive around (arrow keys)
- shift-key to toggle "run" mode
- In particular, turn & shoot. In addition to the timer (eTime > ...), shooting causes a scorecard udpate.

EXPECTED: Smooth display of HUD

ACTUAL: The HUD rotates & moves with player movement, giving a jittery, unpleasant experience.

In apps/PigShooter/Sources/PigShooter.java, in replaceScoreCard(), there is a switch statement which details the several attempts made to solve this problem, none of which give satisfactory results. It's not clear if this is a bug in J3D or not.

Terrain texture does not map as expected

Ted — Tue, 06 May 2008 21:40:17 -0000

* Build & launch PigShooter
- View the ground/terrain from several different angles.

EXPECTED: Neatly gridded terrain textures.

ACTUAL: The terrain texture looks correct on some triangles, but is stretched -- sometimes to the extreme -- in others.

This is almost certainly related to accepting the default tx/ty values for the IndexedTriangleStripArray in libs/T3D/Sources/T3DTerrainMesh.java. The ideal solution would be for the T3DTerrainMesh object to have "normal" default behaviour, but to allow the developer-user to override, if they desire. This fix would almost certainly be in (or called from) createGeometryIND_TRI_STRIP()