Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - FlyingFree

Pages: 1
1
Ask a Question / How do you force data to be of actor type?
« on: June 03, 2012, 09:05:03 am »
In the attached custom global block I am retrieving the target of an actor, which is of type actor, from a behaviour and attempting to return it as type actor, the compiler rejects it because the get uses the return type anything so the type doesn't match the expected return type. How do I force the data from the get into an actor return type?

2
I posted a mouse shooting behaviour on Stencylforge but forgot to add a block, how do I update the posting? Or is the only way to delete the original share and post a new one?

3
I have a behaviour attribute of type "game attribute" that points to a game attribute of type "number", I can't seem to figure out how to access the number contents of the game attribute via the behaviour attribute pointer. I tried using the "set game attribute BLANK to BLANK" block but when I try to put the getter from the behaviour attribute in the first blank it won't accept it.

4
Ask a Question / Drawing blocks
« on: May 24, 2012, 10:04:19 am »
In some prepacked behaviours there is an extra category of code blocks called Drawing, when I create new behaviours, both actor and scene, this category is not there, how do I make it appear?

5
Ask a Question / Collision detection problem (updated)
« on: May 23, 2012, 02:02:40 pm »
In the attached behaviour the collision detection event for tracers with heroes works but the one for tracers with tiles doesn't. I've also tried attaching the "die on collision with group" prepackaged behaviour to the tracer actor and setting the target group to tiles, in both cases the tracers just fly through tiles and nothing happens. Tracers are sensors with collision boundaries and set to collide with players (hero), tiles and waypoints (another actor type). Collisions with hero and waypoint work, collision with tiles are ignored. Do sensors treat tiles differently?

6
Old Bugs (1.x/2.x) / Deactivated or Removed Behaviours Still Active
« on: May 18, 2012, 10:40:35 pm »
Behaviours that have been deactivated or removed from actors are still in effect, this seems random as to which behaviours/actors are affected.

7
Old Bugs (1.x/2.x) / Small oops in the prepackaged health manager
« on: May 13, 2012, 11:02:54 am »
In the When Updated event of the prepackaged Health Manager behaviour the code block is:

Set Percent Left to Current Health for Self / Current Health for Self

the code block should be:

Set Percent Left to Current Health for Self / Maximum Health for Self

8
My bullet actors have 2 collision detection behaviours, 1 is the prepackaged Die On Collision, the other deals damage to the actor collided with. The problem is the Die On Collision behaviour always processes first so the damage dealing behaviour never triggers as the bullet actor is already recycled by that point. If I include the damage dealing block in the Die On Collision behaviour it triggers, but I want to avoid altering the prepackaged behaviours, also I'm curious why this issue exists, is it a bug?

9
Ask a Question / Fire towards mouse works until the scene scrolls
« on: May 12, 2012, 11:37:35 pm »
This shooting behaviour works perfectly on a scene that is the same size as the screen, but once the screen scrolls on a larger scene the bullets fire out in seemingly random directions. I'm guessing the x,y coords being returned at based on scene location rather than screen location but I don't see any functions for discerning between screen and scene location. Any help would be appreciated.

10
Ask a Question / Burst fire behaviour not bursting
« on: May 11, 2012, 08:18:45 pm »
The attached behaviour is supposed to fire a 3 round (value of Burst Size) burst of bullets every 1 second (value of Firing Delay) in the direction of the mouse as long as the mouse button is down. For some reason the bursts aren't happening, I only ever get 1 shot no matter what I set Burst Size to or what delay I put in the loop between burst rounds. The behaviour always acts like Burst Size is set to 1 (I even tried removing the attribute and just putting in the literal value of 3, no effect). Any ideas?

11
I have tried values from 0.1 to 100 (the default is 20) and the speed of the ball never changes.

12
Ask a Question / Brick Block example game issues
« on: May 06, 2012, 01:26:46 am »
I found 3 issues with the Brick Block example game that don't seem to make any sense.

1) Changing the speed attribute on the ball doesn't seem to have any effect, the ball always moves at the same speed.

2) Disabling the "Updated" section of Bounce Off Wall behavior seems to have no effect.

3) Disabling the "Actor - Any" section of the Bounce Off Wall behavior seems to have no effect.

I suspect the 2 sections of the behavior don't actually do anything and are unnecessary, but the inability to change the speed of the ball by changing its speed attribute (I've tried 0.1 to 100) has me mystified.

Pages: 1