(What I mean is: the program wont splice the large texture image into tiles that are easy to define when working with the collision polygon method, it will only create tiles that are the same size, which is what it's supposed to do, but this becomes a problem when you're not able to create multiple, separate collision polygon areas in one single tile)
I've read the following post, "Alternative to collision polygon?", and Joannesalfas suggestion is of course a solution to the problem, but it just gets headachingly cumbersome when you're dealing with about 200 tiles.
Do I need to downgrade to Construct 1? As I understand it, the first version of Construct is not using the collision polygon method, it is not using html5, which apparently, according to Ashley, isn't fast enough yet for "full polygon collision detection", or something like that.
Thank you for any advice you have on this matter!