Hey guys, I just publish the game on Greenlight, please support this game

https://youtu.be/mdhajVFIMeo

Looks good, I voted

Looks and feels great so far!

This one has a good introduction:

https://thebookofshaders.com/

Problem Description

If tilemap is on a rotated layer with solid behavior, and sprite on another non-rotated layer with platform behavior, it doesn't collide correctly.

Something weird with collisions/layers- not just platform/tilemap?

Attach a Capx

https://1drv.ms/u/s!AhHSZHEulqh_gTc7qP-MQXv-igxG

Description of Capx

tilemap and sprite collision

Steps to Reproduce Bug

• run layout

Observed Result

sprite doesn't move

Expected Result

sprite should fall and collide with tilemap

Affected Browsers

• Chrome: (YES)
• FireFox: (YES)
• Internet Explorer: (YES)

Operating System and Service Pack

vista sp2

Construct 2 Version ID

r227

I know, you probably don't have much time to fix stuff with this plugin R0J0hound , but thought I would mention that if I have chipmunk objects on two separate layers, and one layer has a different angle set, objects only use the angle of the layer they are currently on.

So when colliding, the layer angle isn't taken into account if the object they're colliding with is on a different layer.

Hope that makes sense.

I test this with tilemap on a rotated layer, and an object on another non-rotated layer. Object acts as if tilemap isn't rotated. If the object is put on same layer as tilemap, then it acts as if it is rotated.

Maybe it is a C2 issue?

edit:

alright, I'll do that- thanks <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

edit: https://github.com/nwjs/nw.js/issues/5011

Ashley , How would I report it? I don't know what is involved in the problem. Obviously audio, but technically what does that mean? Wouldn't you have a better ability to describe the issue to them than me?

I can report it, but I need more info as to what you think is happening, so that I can explain it to them.

Ashley ,

I'll try to explain how I am using things:

I have a layer named "gui" on my first layout (and every other layout).

This layer holds all my menu/gui stuff, which is basically a bunch of spritefonts.

The spritefonts are part of a family and have a lot of instance variables.

The spritefonts are also global objects, because I need all the variables to remain set accordingly.

Due to the spritefonts being global variables, I cannot set the layer to be global, otherwise if I do then I would get duplicated spritefonts.

I want to have the "gui" layer properties carryover to any other "gui" layer in the project, because I have the parallax set to 0,0 on it.

Due to this, It makes it time-consuming to adjust all the "gui" layers on every layout if I need to change a property. If I have 100 layouts with "gui" layer. It would just take one change to set all their properties if I could make the layer properties global without it creating/duplicating the instances.

The spritefonts have to be global to keep their variables set appropriately, so I can't use global layers as it is currently implemented.

If instead, there were the options to Let Layers have a Global Layer Properties Setting, Global Layer Objects Setting, Global Layer Effects Setting, then it would improve the workflow. I would be able to use global objects, and have the layer properties carryover

Hope that helps you understand the issue here.

edit: or maybe just have it check if object is global, and not recreate any global objects. That might suffice?

something like this maybe?

did you set the correct tile width/height in the tilemap properties?

The latest one provided by scirra, 0.15.0

Ashley, If the layer has a set background color, parallax, opacity, effects, etc.. I want to carry-over those settings to any other layer with the same name. At the moment that isn't possible without it also duplicating the objects on the layer.

My point is that you should give users the option of whether they want one or the other carried over, or both. Don't force it on the user.

Instead of just a global setting. Let Layers have a Global Layer Properties Setting, Global Layer Objects Setting, Global Layer Effects Setting.