Lol! usually its helpful when your looking for something expression wise to click on the system object to see the available expressions, you might be surprised how obvious and easy they are to find.

I'd Say as things are now with HTML, Construct Classic will allow you to make a much more professional and fuller featured game, but Construct itself will be buggy, and a hassle to use to the uninitiated. also it wont be ridiculously multi-platform with CC, which might be a big downside for some. With time C2 will undoubtedly surpass CC in all aspects.

angle(self.x,self.y,sprite.x,sprite.y)

> That solution is not an acceptable solution,.

Urled: how so ?

Please explain yourself.

As far as I'm aware, this is a perfectly well-fit solution to use in C2.

it's cause every second works with the system timer, so really, this is going to look kind of stupid and cheap if you shoot, because sometimes itll take one second to fire a first shot, or some times itll take an instant.

what needs to be done is

Always:

subtract from gun('timer') : TimeDelta

On Space pressed:

& gun variable 'timer' less or equal 0

spawn object bullet.

set gun('timer') to 1

this will make it so your gun can only shoot every second, but it will also make it so that if a second has passed since your last shot, the first shot will come out instantly as expected

something like this is usually ideal for a On hit Reloading type timer

don't even think of pulling out the frenchyann hammer

I know how to do this but refrain from telling you cause of the stupid way your behaving. it's new years day and getting no responses in 20 minutes pisses you off? k

i heard you like wolod so i put wolod in a wolod post so you can see a picture of wolod from a picture of wolod

to prevent subpixel movement with double scaled graphics, and have them obey the grid, you can set positions to round(player.xy/2)*2.

but again... this is kinda hacky i feel you. it's not so much a construct problem as a 'problem' with modern machines. you can use the window plugin to up scale stuff but that works differently on some machines (hardware problem). Ive noticed it on my laptop scaling in a "blurry" way that becomes crisp if the system volume widget appears (wtf?), but other than the laptop (which has an integrated card), im pretty sure most hardware scales as expected.

EDIT: oh, and in your example you might want to set the camera to scroll only to round(player.x),round(player.y) so that you don't get the sub pixel scrolling you're seeing sometimes (apparent in the 'doubling' of the text)

By this time, im sure all of you are aware of the SOPA bill currently making its way through US legislation. if not, i suggest you do a quick google search (while you still can!)

americancensorship.org

all you need to do is write in your email, thats it, thats all. add your voice. individually our voices are a drop in a puddle, but together they become a powerful wave. Spread the word on all your forums etc.

Physics by definition does not work on pixel information. it uses collision polygons, so regardless of what you do to the graphic, the object with physics applied will have the same collision polygon as it had intially.

you'll need to write code that modifies the polygon (there are actions to do this) or write your own physics engine thatll work with pixel data.

you're not explaining what the supposed behaviour is, but expect us to "fix it".

Arrays are also extremely slow in construct for stuff like this.

I highly doubt your implementation of the math is good if its not behaving as you expect. you'll need to look everywhere and try to find suspect areas. It's unreadable to anyone else but you as things are. i think your biggest problem is with the create/destroy every frame ,perhaps, not giving the distort map time to intialize. Honestly i could be completely wrong. good luck nonetheless :D

kayin, i remember seeing your much higher res 3d box backdrop version a million years ago, and i must say this new one seems wonderful.