TheKackler

Bleh.... if it complains about the variables .vi change the name of LunarLander_Globals.vi to MouseGames_Globals.vi

Game still in development... but feel free to check it out. It will run more smoothly after I remove extra controls/local variables. Bounding box is current visible (RED) but visibility is a Boolean that can be disabled. Launch the VI: _LunarLander.vi Run application and use arrow keys ←, ↑, → -TK LunarLander.zip

nm... i see it in advanced editor

which button do I press to attach .zip files? (I feel like such a noob! )

@Michael I'll try and upload it tonight. @vugie Wow that is some neat stuff! I'll have to read up!

(I see that i have posted this in the wrong area... Oh well... one's first post seldom goes swimingly) @Michael: Do you have a link to LAVA CR etiquite? My code is deep in development and has some horrific syntax and improperly named VIs and controls. Is "unreleasable" code ok to release to CR? I assume it is easy enough to "upRev" when available. Some have suggested I Blog about my Lunar Lander antics but I'm not sure it is blog worthy... maybe worthy of a thread here? dunno... I am interested in having my code critiqued but I'm afraid the easy ugly gets in the way. @Yair: Thanks! I sa

Hi Guys! I am new the forums... and this is my first post! For fun I am rewriting Lunar Lander in LabVIEW... do you guys know vector based games out there? I am trying to emulate a game engine similar to what I have dabbled with on the XBOX (Loops below run async with eachother (I think)). User input loop Physics Calculation Loop Screen update Loop I have quite a bit done but I wasn't exactly sure what properties I needed to have for everything so I keep adding stuff and breaking stuff... But I have a lander with thrust & rotation, gravity and basic collision detection. I realize now