TWiki > Team3 > ProjectTwo > GolfGame	TWiki webs: Main | TWiki
	Team3 . { Changes | Index | Search | Go }

• Timer - we need to get this implemented soon so we get a standardized performance
• Hole - we need to make the mechanism for winning the game. Most likely a black circle drawn on the ground and some code to prevent the ball from colliding in that area
• ball/club that z is providing need to be integrated
• Stopping - need to add a flag for stopping so that we don't get a jittery ball when it should be stationary
• Camera - needs to track the ball (Kangas this is all yours)
• milkshape? we should play around with this and see what it can do, so we can use it for the final game!

We seem to be in pretty good shape even though the list still seems pretty long. Timer really needs to get done soon, that's a very important aspect that keeps getting overlooked because there have been more pressing issues.

-- JannaDeVries - 31 Mar 2004

Ok, we're having our weekly Friday afternoon meeting to work on our list of remaining issues. Here's an updated list:

• Timer -- we're not sure we want to do this. None of us really understands how it works and we are (rightfully) afraid of changing something that works.
• Hole -- It's there and kind of working. Shouldn't be too difficult. Janna got this working/drawing.
• Ball/Club -- huge issue still needing lots of attention.
• Stopping -- done by Janna.
• Camera -- Kangas got the camera tracking the ball now, should be in great shape for Tuesday.
• Modeling -- we are still not off the ground on this, surely going to take some time over the weekend.

Thus, we're in good shape. The most pressing aspects are unrelated to our physics engine, namely implementing the game aspects of the game :). Here's a prioritized list of tasks:

1. Ball/Club -- got to get the interface working. Janna is working on integrating Z's classes.
2. Modeling -- we need a course, period.
3. Extra UI -- we probably need a splash-screen, a stroke counter, ability to reset, etc.
4. Documentation -- we need a user's guide and a design document. I plan on taking care of these.

Add new items as they come to you and maybe bold out anything you've finished.

-- EvanParry - 02 Apr 2004

Put all of the camera code into a Camera class. This makes our design more object-oriented, and will allow for more interesting things to be done with the viewpoint. Decisions about what the camera should be doing are made in NewWorld?, and will be expanded as the project progresses.

-- EvanParry - 02 Apr 2004

Ok, we are meeting again now, Saturday at 3:00. Kangas has been working on some Milkshape testing and he believes we can easily get good models from there. Thus we have two major steps left to perform:

• Milkshape Course -- we need to figure out the Milkshape file formats and how to read in or convert Milkshape files to something we can use. Kangas seems to believe this will be fairly straightforward.
• Swinging -- we need to implement adjusting the shot and swinging the club.

Janna and I have got rudimentary swinging working using the spacebar. We need to integrate this with Adam's camera rotation code so we can actually hit the ball in the direction the club is facing.

-- EvanParry - 03 Apr 2004

Adam has worked extensively on the club swinging and we think we can get it to rotate about the ball. I have examined the Milkshape 3D ASCII file format and I'm convinced we can easily use it given the close similarity to the format we are using already. I need to ask some more knowledgeable people about how the file works completely since Milkshape doesn't bother to provide a detailed file format document.

In all, we have a few hurdles left to clear, but we're making excellent progress.

-- EvanParry - 04 Apr 2004

Ok, it's Sunday afternoon. This morning I implemented the Milkshape 3D ASCII scene loader and successfully loaded the Mill scene Adam created last night in Milkshape. We encountered some strange collision problems due to Milkshape's invalid triangle generation, but we believe we have that all worked out.

Our remaining issues:

• Club Rotation/Swinging -- swinging sort of works at this point, but it's operation is independent of the rotation of the club. We really need to integrate this two systems, so we know which direction we are swinging the club and therefore where the ball should go. Adam is having trouble with the math, so we hope to work that out.
• UI elements -- it would still be very nice to have a power bar and a stroke indicator on screen. We haven't really done anything on this.
• Comments -- all the code really could use more commenting.
• Documentation -- we still need to write the design document and the user's guide.

We have most of the game in working order at this point and have clearly delineated what remains to be accomplished.

-- EvanParry - 04 Apr 2004

We met last night for 2 hours. During that time we got the complex scene to load and got club rotation and swinging working. At that point we were pretty sure our game was fully-functional.

Adam and I have been working this morning on fixing things up, because we found problems with our scene and collision detection last night. We have a simpler scene now we a ramp. Hitting the ball works, reseting the ball after it flies off works, winning the hole works. We have some strange pauses in execution and the camera still behaves oddly. We hope to resolve those in a meeting with Z today, but we might not have time before the deadline. We are happy with our current product, so we can turn in as-is if necessary.

-- EvanParry - 06 Apr 2004