sci-fair-guy

You can now right-click and point your mouse in the direction you want to go. Right-click again to turn the mouse off. I don't think this is what Zerg had in mind by Mouse-look, but it beats holding the arrow keys down to do a complete circle. = or + will accelerate forward, - decelerates, 0 stops forward motion (non-RCS motion). RCS is reaction control system - that's attitude control, not propulsion. I added simple indicators for attitude and position. Click the RCS mode indictor (Lin / Rot) to change RCS mode. Read the project ReadMe.txt file for details and new things I forgot about. My son added shooting to his copy, so that may make it into the next update. I lasers are being used for navigation now, so adding a more powerful mode to clear space debris may not be beyond resonable developments.

Thanks for the kudos. It's not exactly "Orbiter" (http://orbit.medphys.ucl.ac.uk/orbit.html it's free!), nor will it ever be for reasons I think Zerg understands. However, I think Greenfoot is about principles and education, not high-end entertainment - so 2.5-D is getting at the basics and may whet the appetite for those who want to explore Java3D, DirectX, etc.. I started out programming games and simulations (long ago ;-) because it could get me deeper into computer tech and programming than doing business apps, database stuff, etc. that I don't care for very much. So, I believe in starting students on games - the sky is not the limit ;-) I haven't spent a lot of time on the interface yet, but as an Orbiter fan, it may go that way - just to see what it can do. Go for it qnanqing - you do good work! My son has been bugging me to put shooting in it. Almost everything he write is a shooter game - or wants to be! Don't know what mouse-look is. I think I'll learn a lot in this forum. One more thing - to "depth charge" a 2.5-D to 3-D requires a 3-D object mapping, like a u-v surface. That can be done in Blender (a free 3-D CAD-like tool). However, (and I'm no expert) that's where Java3D and DirectX etc. excel. In Greenfoot, you'd have to redraw and setImage() every act() on potentially hundreds of objects. In "Feeding Frenzy", my dual-core computer slowed down considerably when more than 250 or so fish were doing somewhat less than that and stopped for periods of time loading 100 or so "pop" sounds for each explosion when the bubbles reached the surface. Maybe a Greenfoot developer could forecast what the bottlenecks might be for pushing the limits with drawing graphics. Smaller images seem to take much less time.