I don't know if this is what you want but I have a sort of flip-screen camera set up that scrolls smoothly when the player hits a certain part of the screen. Basically if the player is within a certain x/y range the camera will move smoothly to the center of that particular screen and stay there until the player exits that boundary, whereby it will then float (using lerp) over to the next designated 'center of the screen'. I've attached a screenshot of my workings - It's probably a horribly inefficient way to do things, but it actually works very well for my purposes. The downsides to this method is it's locked in to a particular resolution (1366 x 768 in this case) and all the values are hard coded and probably getting triggered per tick. If I knew what I was doing I could probably set them up in an array or work out a formula etc, but for now it's doing the trick for me.[attachment=0:3ofrias3][/attachment:3ofrias3]

In your project properties (get there by clicking on a blank area of the screen then look in properties window), put PIXEL ROUNDING to off and it should fix the jittering.

Thanks Lucid, I'd completely forgotten about the plugin, all good now

I'm having issues importing correctly. I'm using the latest beta of construct and the latest version of Spriter pro. I have the special exports checked in Spriter and am exporting an scml and a scon file - when I import to construct it seems to work, but all the spriter images default to invisible. Is anyone else having this issue? I thought it might have been my file but I downloaded the spriter player example and imported that, the coordinates are messed up when it's brought in to Construct 169, but then if I resave it in the latest version of Spriter it also goes invisible.

If you break your collision objects down into basic shapes such as triangles or squares and make them invisible you could run a script at the beginning of the layout to pin each collision area to the correct shape (sorry bout the pseudo script but something like)

On Start of Layout - Triangle_Object - spawn Triangle_Collision on layer 0 (image point 0)

For each Triangle

I don't know if it would be more or less efficient than other methods though as I guess you'd essentially be doubling your objects.

helena, actually you're right I can't seem to work out how to change drive either. I have autotilegen installed to F drive and all my image files are also on this drive and it works fine, but it's true I can't seem to switch to other drives - so I guess the solution for now is to install it to the drive where you're images are and it will work. I contacted the dev via indiegogo https://www.indiegogo.com/individuals/6316373 - just click on 'contact user' (you may need an indiegogo account to do this not sure, but it beats going on twitter).

I picked up a copy last week and it's an excellent time saver, the developer is also really good to deal with. I believe slopes may be implemented in further releases (it's still in beta) which will really make this thing powerful. One thing not apparent in the demo videos is that you can load your own images in there, you don't necessarily have to push pixels, so you can get everything polished up in you main image editor and then not have to worry about spending time on the fiddly technical bits like making all your tiles seamless.

Unfortunately that technique isn't quite suitable for what I need. I'm aiming for a very smooth transition from fast to slow, not an abrupt one and running two audio files in parallel would work fine if they were the same speed but as they won't be they will lose sync (unless the second file was just pitch-shifted eg running at the same speed but at a lower pitch, which isn't really the effect I want). The audio engine in construct 2 seems to do a cool timestretching effect which is quite nice, the 50% speed is still pretty good I just wonder why there's that limitation, I can't really think of any good reason for it.

I'm interested in more info about this as well. I have some music which I'm lerping between two timescales but as you said anything lower than a timescale of 0.5 or higher than 3 or 4 results in silence. It's a shame, because it's a really cool audio effect, but too subtle when you can only slow it down 50%. Is there a technical reason for these limitations, or is it something that may be addressed in future?

Thanks heaps for a very detailed and useful explanation! That helps a lot!

Thanks for the example, it has taught me some new things - any idea why the floor expression isn't working though? If anything I thought using it would be more accurate!

Same here - says it's the "heri" virus.