It's a pretty complex question. You need a deep understanding of how to implement a Boolean switch with variables.
I would also take a good look at how Timelines work. Its like the ultimate thing for doing tutorials.
> > Click "Edit" on the first comment. > > 💯 Sofa_king What?
> > Click "Edit" on the first comment.
>
> 💯
Sofa_king What?
I know right?
That layer(HUD) shouldn't scroll. Set it to 0%
Just remember the hud layer will then only show what the initial viewport has.
Wat?
All those features exist in C3 officially, and work with much less work than hacking it together in C2.
If you're expecting an end result that's seamless across all platforms you're sadly mistaken.
Oh-oh might be time to go off grid, off the radar, rig for silent running, become the ninja...
Or just ask why.
I think what we need is a way to use palettes.
The color tools are kind of a mess any way, not that there's a perfect solution.
construct3.ideas.aha.io
I agree it's not very useful at the moment.
I think they might be talking about the actual editor.
Many parts can't be zoomed. In particular editing text in an input box can get a bit hard to make out.
The main thing is that the app stores frown on anything related to gambling.
Might want to check out the Line Of Sight behavior.
No idea how the physics behavior works with "circular", but there's no such thing as a circle polygon.
Its either something based on pythag, or a poly with a fairly low amount of points.
Develop games in your browser. Powerful, performant & highly capable.
The parallax would be made using a value between 0-0.9 multiplied by the main layer angle, and then added to the parallax sub-layers angle.
Or subtracted... depending on the angle. It's a bit complicated, hence the thought about a feature request.
Acceleration is the time it takes to get to max speed.
You would have to do it manually since it doesn't exist as a feature using a variable as the offset multiplier.
You can even do parallax for layer rotations.
Interesting concept for a feature request perhaps.