Sunday, January 21st, 2007
Howdy all.
Kukyona at CodeAnxiety has posted another update on the Terrain Component for XNA. It’s looking very cool indeed. Check it out here…
p.s. I’m still working on Part 2 of my XNA Collision Detection tutorial.
Howdy all.
Kukyona at CodeAnxiety has posted another update on the Terrain Component for XNA. It’s looking very cool indeed. Check it out here…
p.s. I’m still working on Part 2 of my XNA Collision Detection tutorial.
Greetings earthlings.
My game build releases have been a bit sparse lately. So you’re possibly wondering what I’ve been working on. Well, as the title suggests – Collision Detection.
The technique used in the current release of my game is as simple as they come, and it’s been bugging me. I haven’t released it yet, but the next release of my game will have much improved collision detection.
But boy, has it been a struggle! There has been a real lack of collision detection tutorials relating to 3D models under XNA, so I’ve had to learn the hard way. So I’m going to attempt to share what I’ve learnt, and hopefully save some other poor souls the pain.
I don’t claim to be an expert on this subject at all – not by a long stretch. But hopefully I’ll be at least close to correct. Also, this is not really a tutorial either. Don’t expect a working sample with source code. I may get round to that later. Right now my code is a bit embarrassing, given the experimental nature of what I was trying to do.
these enhancements to my game are not yet released. So for now you’ll just have to trust me when I say it is an improvement. Stay tuned.
The simplest collision detection technique of all is to simply imagine a radius around all your object’s world positions. Then it is just a matter of checking whether any two objects have come within radius distance of each other. This is how my current release of Air Legends works, and if you watch closely it’ll be fairly evident. Depending on the orientation of the two planes a collision will still occur when clearly the planes were not even close.
XNA provides two classes specifically for collision detection. BoundingSphere & BoundingBox. (more…)
Howdy folks.
Well, it’s been a long time since I blogged about anything other than my own game development. Frankly I’m quite overcome with the flood of useful information coming out now that XNA v1.0 (full, not beta) is out in the wild.
In the back of my mind I’ve known for some time I’ll be needing some sort of Terrain rendered in my game (I want to be able to land the planes to refuel/rearm etc…). A bit of a daunting TODO that one! So naturally this news caught my eye.
New Terrain Component – Coming Soon! at CodeAnxiety
Sounds like yet another blog to keep an eye on. If only I had more eyes.
Happy New Year all! Hope you all got lots of pressies and are having a great 2007 so far.
As promised, here’s a new release to play with. Here’s what’s in it…
Big thanks to Ultrahead for alerting me to the full-screen problem and suggesting the good work-around. The game now forces the Refresh rate to something most people’s systems should be able to handle: 75hz. If even this is too high there is a Settings.Xml setting you can tweak. If 60hz doesn’t work then probably nothing will. I chose 75hz since 60hz has evil flickering. You could go higher if you know what you are doing and what your monitor is capable of, but do so at your own risk. NOTE: the game always tries to use the current Windows Desktop resolution.
Feel free to grab the new release from the Latest Builds page here.
G’day all.
Here’s the deal…
Go grab the new (& coolest) release from the Latest Builds page here.
My first cut at sound, but I’m actually pretty stoked about how it’s turned out. The crazy perfectionist in me will continue to refine the sounds of course.
I hope you like it. It’s almost feeling like a real game to me (although I have so much more left to do.)
Now remember, your comments, ideas & feedback are always welcome.
Hi there.
With 3 altered lines of code I’ve made the Fireball & Explosion effects look a whole lot better. The difference between the two effects was really too similar. They’re more distinct now, and I’m much happier with them.
Get the new release from the Latest Builds page here.
Enjoy!
Shawn Hargreaves seems to be blogging with a vengeance today. Possibly going for some kind of record.
Anyway, among other things, he alerts us to another XNA Team member’s blog: Eli’s Cornflower Blue blog opens with part 1 of an article explaining Alpha Blending, how it works, and it’s relationship to the Depth Buffer.
I’ve only skim read it so far, but it looks like some very good info. Exactly what the doctor ordered actually, because when I was converting from XNA Beta 1 to 2 I had all sorts of problems with weird Alpha Blending symptoms. All fixed now, but I never really understood the problem.
I’m looking forward to studying this one ASAP.
Howdy all.
I’ve released another new build of the game. You can get it from the Latest Builds page.
So I got bored of completing the “skywriting” (for my kids) feature mentioned earlier. Bit of a tangent really. It’s kind of there. Call me lazy - call me bad daddy, but dedicating a new game mode + menu to it just wasn’t thrilling enough for me right now. (besides, the kids somehow broke one of my 360 controllers, and my son chewed the thumbstick on the remaining working one. grrrrrrr) Also the fancy new “3D” rendered menu I was working on was a bit more difficult than I’d hoped. ”Skywriting” will still be in the next release, but remains blended with the rest of the gameplay. Just a differen’t button press to pump out the coloured smoke – if you feel so inclined.
Now, what I am enjoying is adding EXPLOSION/Fireball effects!!!! That will be in the next release in some form or other.
I started off doing a particle system for an explosion, and what eventuated was an awesome effect of the plane engulfed in flames. I’m extremely happy with it, so if that isn’t motivation then I don’t know what is.
Think I might use the effect shortly before an explosion. Right now I’m thinking the explosion will be the same effect, but tweaked for more impact, maybe some spinning shrappnel (to replace the plane model)
Might post a screenshot soonish – stay tuned folks.
p.s. oh, and it’s official, unfortunately Santa isn’t going to be bringing me an XBOX 360 for Christmas this year. Which means ”Air Legends” will stay PC only for a bit longer than I’d hoped. :(
The relative silence is because lately I’ve been far too busy at both work & play.
I’d like to say the “play” has all been XNA, but I’ve been enjoying Battlefield 2142 a bit too much for that.
What I have done is add the “skywriting” feature (my 6 year old daughters idea) to my “Air Legends” game. Basically the plane puffs out red smoke trails while you press a particular button, so you can do lovely pacifist pictures in the sky.
A very easy feature to do with some tweaks to my existing smoke particle system. So a nice quick win on the progress front.
It’s certainly not a historically accurate feature, but that’s why it’ll be presented like a seperate game mode with no enemy aircraft. (actually it should probably be a different themed game altogether). Anyway, doing the menu for it is taking longer than the feature itself. Go figure.
It’s December at last. So not long to go now for the Full release of XNA. December 12th, I believe.
David “LetsKillDave” Weller posts some exciting news that the migration of code built on XNA Beta 2 to the Full release, should be relatively painless.
Those of you that are fearing the RTM version of XNA will result in the same kind of pain as the Beta 1 to Beta 2 transition, take heart. There are VERY few API changes this time around. All the “beta 2″ code that I’ve tested so far has worked without needing code modification (or very minor modification). Those of you that have invested time in writing Beta 2 games or tutorials will most likely find your code works perfectly.
He also introduces us to another great XNA resource. Michael Anderson’s blog is putting out some very cool info with source code included.
Check out “Manders vs. Machine“. Definately one to follow.