you are using block.width instead of block.height in the Y co-ord in your create-object statement

it should be SPAWNY - loopindex("Y")*(block.height +1)

R

PS: another way would be to find which object you are standing on, assuming that the surface is a series of connected blocks. if that is the case, then you can just find the angle of the object you are in contact with, then adjust your own angle accordingly.

R

a trick would be to know the slope at all points in advance.. if you knew that, then by using a lookup table you could figure out the angle. it'd work for predefined layouts and surfaces that do not change.

a lookup table would be resource efficient.

yup, as long as the objects exist in the layout, then the included events will work. if they do not, you can get weird effects as the object will not exist and thus event checks on those objects will always return false

R

just create a new event sheet with the functions or events you want to share

then just "include" the event sheet.

https://www.scirra.com/manual/82/includes

because it's irrelevant.. you can use a sprite and use it as a button (on click, etc).

with just the screen grab it's hard to say.. it should work as I've done something similar.

I guess from your description of the error, it is your event checking that's gone wrong and not the browser issue. so the checking of the dictionary text is likely wrong.

R

Ashley, Kyatric,

I would love to see the relevant events disabled and flagged, rather than deleted.

the problem arises when you have objects that go across event-sheets. the search tools don't work for that and it's possible to see a forgotten dependency in a large piece of game logic get destroyed because you deleted an object.

so I understand why it's done the way its done, but it's a huge risk and i'm terrified of deleting objects because of it.

PS: backups of old versions are essential.

R

i know all ads don't cost the same to place, I guess that means some ads are more valuable to display. I'm guessing at that as I've never been on that side of the business. Could that be somehow a factor?

this brings me back to my old days of Amstrad coding... anyway

if the shape is regular (ie a box) then you could build a filling routine where you fill it up with predefined polygons (say a 1x1 image, or even better a 1x1 image that you can stretch to a width). what you do is a bit like a path-finding algorithm... you figure which side of the line is your box... and then you move left and right to find an edge (c2 can do that) and then you can move up and down. or you can travel along an edge and infill. It begins to fail with complicated shapes, and it will not be fast as writing it natively.

it's not easy but it is doable. I suspect it's beyond a beginner

PS: as an early newbie, I never got my fill algorithms to work correctly.

quick question, how are you getting 30% usage... a single core of a quad-core maxxed out should yield 25% cpu (at least that's how window's will report it, I'm not sure how C2 reports it).

so if you have a maxed out core, then you are going to hit frame-rate issues.

assuming a lot of games are played on laptops... a simple issue is that they'll get hot and noisy as fans power up. so that sounds high to me.

R

couldn't finish the level, only got 235 coins... the last ones seemed stuck in top-left corner.

was using IE11. played nicely other than for that.

R