I managed to piece something together using some things I learned browsing the forum, seems the physics behaviour route might be more ideal anyways since the collisions are already handled much better that I could probably implement them

http://www.mediafire.com/file/o1zvm0muyjb/Ast_Physics_1.cap

Any ways to improve this? The torque/rotation doesn't use DeltaTime, I'm not sure about that :S

I don't know, something feels a tad bit jagged and unnatural about the thrust, what do people think?

Actually the 200 and 100 are linear and angular acceleration, not speeds.

Yup haha I figured it out after I'd made the post, sorry for that

Thanks for the additional help, it works quite nicely

I was looking for a way to implement this explanation but I never could get my head round C++ code examples having really understood OO programming :S

http://www.gamedev.net/community/forums/topic.asp?topic_id=183827

Absolute genius, thanks mr. hound

I love it, it's got a great feel to it, I've just added some additional private variables 'ThrustSpeed' and 'RotationSpeed' and adjusted the events so that the numbers 100 and 200 should be easier to play around with. Any idea how I could get the rotation to decelerate when the left/right arrow isn't being pressed? It'd be good to be able to prevent the ship spinning out of control so easily

Hey everyone. I've been looking everywhere for tutorials and they seem rare, even for code, never mind construct!

I'm looking to prototype a simple space shooter type movement, something like Asteroids, Thrust etc. I've gotten a basic setup done with custom movement, and I think I understand how that particular object works... but I'm trying to implement the correct physics, using events and avoiding using many of the built in behaviours. This is only because I prefer to know what's going on and don't like the idea of something changing in another version and breaking everything

So I suppose what I'm stuck on is how to implement the movement of a single sprite... I want to use vectors maths but I'm unsure what the correct way to implement them would be. I assume you should set up separate private variables like XPostion, YPosition, Angle... is there any advantage to making a few vector functions (dot product, cross product etc) or can Construct do all this anyway? (I've not been through every single event yet so I might be mistaken)...

Also I'm a bit confused about the way angles are implemented, with 0 being right rather than up like I was used to. Will this cause problems when calculating rotations and inertia and all that? Furthermore it all has to work with delta time, have acceleration/deceleration for rotation as well as the same for movement itself.

Any ideas would be helpful, it's been a while since I've looked at any maths in detail

Cheers

Thanks for the help Minor, glad to know it's possible

I think I've found the tutorial, I'll put the link here for anyone who might want the same info

http://www.scirra.com/forum/viewtopic.php?f=8&t=4328

Hi all,

I was wondering just how moddable you could make a Construct game. Couldn't find much info on this topic - I was curious how much work it'd take to do do the following:

1. Store levels as external data files and load them at runtime - more than likely just simple tile based maps, setting all the relevant Construct properties that way. Is it even possible?

2. More importantly, would it be possible to do something like in a space shooter, store different ships as data/graphics files (let's say you could have speed, acceleration, armour etc etc) then load different ones at runtime, add new ones when required rather than 'hard-coding' (for lack of a better term) directly in Construct?

Cheers

Good evening, esteemed members of the board!

I've been lurking around here for the last few days reading up on allsorts and thought it'd be a good idea to join and become absorbed in the warm, glowing light of the Construct community

So where to start... well I'm 23, a student (but I did have a full time job for two and a half years before going to uni, so that should count for something!) and I suppose I've always been a bit of a game lover, as well as a creative type. So naturally, upon reading a little programming article in a 1995 issue of PC format, I became consumed by the idea that I could make games myself. This was taking into account the fact that I was about 9, and I'd previously found some kindof BASIC for the Atari ST a few years earlier and thought that by typing a detailed description of a game idea in English, it would magically make a game for me.

Anyways, this article compared the usuals - C++, VB, Delphi etc etc... and Klik n Play got a mention at the end. There was a full page ad for it in there too, and the words 'NO PROGRAMMING KNOWLEDGE REQUIRED!' really stand out to a child... it wasn't until a few years later ('98, '99) that I actually got KnP and started knocking together little games to try and outdo one of my friends. A year or two later, I got onto DarkBASIC... and later DarkBASIC Pro, eventually moving onto PureBASIC and iBASIC, in which I started to make an OpenGL based hardware-accelerated 2d engine... I think it got to the point of having a TGA loader and a revolving MegaMan flying across the screen before that project got buried. A couple of years back I had a go at using Haaf's Game Engine with PureBASIC to make something but again lost interest...

For a while after, I didn't touch programming and it seems that all the ideas I've had swimming round in my head would never come to fruition. After playing little games like Knytt, I've liked the idea of using something simple to create a simple little game, or maybe a few, that I wouldn't lose interest in so much. I've had a go at Game Maker, but got annoyed at the apparent complexity of some things and even more by the fact that I'd have to pay a second time to get access to the newest version. I looked into MMF2 this week and it seems great, it's just a long time since I've used the KnP style events system and still find myself thinking about variables and code when I'm trying to figure things out Plus it's also missing that hardware accelerated edge that makes 2d games really shine these days!

I heard Construct mentioned in a discussion on the Nifflas forum (the guy who made Knytt) who was thinking of moving to something else from MMF2. Drawn in by the cool DX effects and open sourceyness, here I am, pondering what I might start making

So yeah, that's pretty much it... I wouldn't call myself a coder, I can do basic stuff but never really got to any decent level with it, I can draw/get arty quite well, and because I'm a sound & video technology student I do an awful lot of professional-level video/sound/music work as part of my course. So any questions about any of that jazz, drop me a PM or something, but I'm looking forward to getting stuck into Construct, sorry for the near-life story, and hello everyone