R0J0hound's Profile

- R0J0hound
- - Joined 15 Jun, 2009
  - 90 topics • 7,308 posts
- 1
- 24 Jun, 2010
- Quote
Here's an example made by Rich :

http://www.scirra.com/forum/viewtopic.php?f=16&t=2210
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- R0J0hound
- - Joined 15 Jun, 2009
  - 90 topics • 7,308 posts
- 1
- 24 Jun, 2010
- Quote
Here's another way to do it:

Initially give "Sprite" the attribute solid. Sprite only needs 1 private variable 'time'.

EDIT:

Also add a box object and add it to a container with sprite. The box objects will serve as the collision detection for sprite because when sprite is set to no collision an overlapping condition can never be true.

Here's what I came up with:

http://dl.dropbox.com/u/5426011/examples/hideplatform.cap
- R0J0hound
- - Joined 15 Jun, 2009
  - 90 topics • 7,308 posts
- 1
- 24 Jun, 2010
- Quote
Constant 8 fps

Pentium 3 866 Mhz

512 Mb Ram

Nvidia GeForce FX 5200 (128 Mb)

R0J0hound
- Joined 15 Jun, 2009
- 90 topics • 7,308 posts
1

21 Jun, 2010
Quote

The nice thing about using behaviors is you don't need to worry about TimeDelta, because it's handled within the behavior.

You can simplify your events and it will behave exactly the same and be more readable:

+ MouseKeyboard: Key Up arrow is down
-> Sprite: Set force Sprite.value('Thrust') towards (Sprite.X + cos(Sprite.Angle), Sprite.Y + sin(Sprite.Angle))
+ MouseKeyboard: Key Left arrow is down
-> Sprite: Set torque 0-Sprite.value('Rotation')
+ MouseKeyboard: Key Right arrow is down
-> Sprite: Set torque Sprite.value('Rotation')[/code:1fvwdf3w]

- R0J0hound
- - Joined 15 Jun, 2009
  - 90 topics • 7,308 posts
- 1
- 20 Jun, 2010
- Quote
Sagal's right, just use the "every" condition, much simpler. I compared the two methods and found that they behaved pretty much the same. I'm continuously impressed on how so many tasks are very simple to do in construct.

R0J0hound
- Joined 15 Jun, 2009
- 90 topics • 7,308 posts
1

20 Jun, 2010
Quote

Actually the 200 and 100 are linear and angular acceleration, not speeds.

For angular deceleration:

+ MouseKeyboard: [negated] Key Left arrow is down
+ MouseKeyboard: [negated] Key Right arrow is down
-> Sprite: Subtract 2*'AngularVelocity'*TimeDelta from 'AngularVelocity'
[/code:3q26kvpc]
2 is the deceleration amount .

On a side note the physics behavior is way better suited for this type of movement, as it takes very little to set up.

- R0J0hound
- - Joined 15 Jun, 2009
  - 90 topics • 7,308 posts
- 1
- 20 Jun, 2010
- Quote
For that type of movement only addition and subtraction of vectors are needed. No need for dot or cross product although those are easily implementable.

Here's an example for you viewing pleasure:

http://dl.dropbox.com/u/5426011/examples/asteroidsMovementEx.cap
- R0J0hound
- - Joined 15 Jun, 2009
  - 90 topics • 7,308 posts
- 1
- 20 Jun, 2010
- Quote
Must sleep so here's the example (might explain later):

https://www.dropbox.com/s/3mlg8usurpq45 ... d.cap?dl=1

/examples/fake3droad.cap

Enjoy.

R0J0hound
- Joined 15 Jun, 2009
- 90 topics • 7,308 posts
1

20 Jun, 2010
Quote

I'm using the conditional operator.

It's in this format:

condition ? ifTrue : ifFalse[/code:24ozcys7]
It checks the condition, if it's true then the expression uses ifTrue value, and if it's false the ifFalse value is used.  So in my example if "global('triggercount')=1" is true 0 is used, and if it's false 1 is used.

- R0J0hound
- - Joined 15 Jun, 2009
  - 90 topics • 7,308 posts
- 1
- 20 Jun, 2010
- Quote
Use the timer behavior.

Here's an example to illustrate:

http://dl.dropbox.com/u/5426011/example ... xample.cap
- R0J0hound
- - Joined 15 Jun, 2009
  - 90 topics • 7,308 posts
- 1
- 20 Jun, 2010
- Quote
It's a bug with the RTS behavior. The "arrived at waypoint" is always being triggered twice for each waypoint. So with you events two 'Sprite2' objects are being destroyed when a waypoint is reached. A solution would to only destroy 'Sprite2' every other time "arrived at waypoint" is triggered.

Here is your example with a workaround implemented:

http://dl.dropbox.com/u/5426011/examples/waypointWorkaround.cap

R0J0hound
- Joined 15 Jun, 2009
- 90 topics • 7,308 posts
1

18 Jun, 2010
Quote

It seems that this condition:

+ Sprite: arrived at a waypoint[/code:3i8ucuqg]
is always triggered twice, so it look like it's an issue with the RTS plugin.

R0J0hound

Member since 15 Jun, 2009

R0J0hound has 155 followers

View followers

Progress

R0J0hound's Recent Forum Activity

Try Construct 3

R0J0hound

Connect with R0J0hound

Trophy Case

Your Location

Products

Construct 3

Education

Affiliates

Our Company

Community

Scirra Ltd

Legal