1 / 10

U.S.S.R

U.S.S.R. Milestone 3 Presentation. Background. Creating a arcade racing game involving the specialization areas of our choice: AI Procedural Content GPU/Shader programming. What went wrong?. XNA/JigLibX is not the way to go. Things took longer to implement/debug than planned.

oakley
Download Presentation

U.S.S.R

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. U.S.S.R Milestone 3 Presentation

  2. Background • Creating a arcade racing game involving the specialization areas of our choice: • AI • Procedural Content • GPU/Shader programming

  3. What went wrong? • XNA/JigLibX is not the way to go. • Things took longer to implement/debug than planned. • Source engine games + USSR destroys the dx9 device forcing user to reboot or get seizures . • Trying to keep things simple, we over complicated stuff.

  4. Graphics/Shaders • What’s implemented: • Shadows • Particles • Fullscreen glow • Why not more?

  5. Procedural Content • What’s implemented: • Tracks • Textures • Vehicles • ”Skybox” • No terrain around the track 

  6. AI • What’s implemented: • Track following • Fuzzy logic • Situation based steering • Interaction • Limited obstacle avoidance • No difficulty settings

  7. What went Right • We have a game and it is playable. • Techno Bauer Anthem!!!

  8. Show us the game already

  9. Lessons learned • Do not use XNA for bigger projects if not specificly targeting the Xbox 360. • Take the easy way out, there are shadercreation tools out there. No need for doing everything by hand. • Ananlyze dependencies better to get a more complete timeplan. • When making an AI that doesn’t cheat, don’t cripple it. Give it all the data it needs to cheat, just don’t let it.

  10. Questions? • ”Knowledge is power”

More Related