Advertisement

ColDet Algorithms & Learning?

Started by November 17, 2000 04:18 PM
2 comments, last by cearny 24 years, 1 month ago
Hi, I need your help again, oh ye great game programming gurus & masters <--END OF INCANTATION -->. I have met the point in witch I need to implement some more than basic (sphere-sphere) collision detection in my 3D engine. To simplify the question, my engine renders (extremely) large-scale landscapes using a modified ROAM algorithm. My first question (Q1) is: "What Collision detection algorithm would suit best for this kind of engine?". Another question (call it Q2) is: "Where should I start learning, as I''m kinda NULL in this region?". And the third question (Q3): "Can I annoy you with silly little questions, in case I don''t understand something?"... Thanks a lot, Adrian "cearny" Cearnau
[ Libraries - STLport | boost | SDL | wxWindows ]
[ Manuals - MSDN | STL Docs ]
[ Compilers - VS.NET | MingW | DJGPP ]
[ Editors/Tools - EditPlus 2 | Anjuta | Dev-C++ ]
3D Game Engine Design has a full set of collision detection and comes with source.
Keys to success: Ability, ambition and opportunity.
Advertisement
That is the title of a book?

Ok, thanks, but there have to be some tutorials on the web (I don''t mind buying the book, but it''ll take some time until *it* reaches me ).
[ Libraries - STLport | boost | SDL | wxWindows ]
[ Manuals - MSDN | STL Docs ]
[ Compilers - VS.NET | MingW | DJGPP ]
[ Editors/Tools - EditPlus 2 | Anjuta | Dev-C++ ]
Sorry, didn''t notice where you were from. Yes, it is a book and yes, it might take a bit of time for it to get to you. You might try searching the SourceForge. Everything there is open source and one of the projects is Crystal Space 3D Engine. As open source I believe all that is demanded is that if you make improvements that you give them a copy of the improvements. You should of course use reason and not do anything you would not feel was fair use if it was your project. I would view anything short of copying to be acceptable in their situation. I would feel cutting and pasting or constantly flipping back and forth while coding would be a stretch. Studying it, understanding it and then coding your own should be acceptable assuming you don''t have a photographic memory. I feel learning from someone else''s work and copying it is a world apart.
Keys to success: Ability, ambition and opportunity.

This topic is closed to new replies.

Advertisement