Stencyl 3.4.0 is now out. Get it now!

Suggestion Issue: Blocks to disable "actor always active" and "continuous collision detection".


Pages: 1 2

LIBERADO

  • Expert Stencyler
  • *
March 16, 2016, 10:18:05 am
After reading this thread:
http://community.stencyl.com/index.php/topic,46945.msg260484.html#msg260484

I think it would be a good idea to add in Stencyl blocks to disable the "actor always active" and the "continuous collision detection" options.

I guess such blocks would be useful. I also would use them.
« Last Edit: March 16, 2016, 10:22:33 am by LIBERADO »


BMJ

  • Subscriber - Stencyl Indie
  • *
May 06, 2016, 06:11:28 am
I also think this is a great idea. Many times I have wanted an offscreen actor to be set to "always simulate" in order to set him up correctly for a scene, but then stop simulating once the setup is complete. I know there are other ways to do it, but this would be much simpler.


rob1221

  • Master Stencyler
  • *
March 04, 2017, 07:54:03 am
A disable option has been added to these blocks in b9309.
  • Status changed from New to Resolved
  • Issue Assigned from (none) to rob1221


LIBERADO

  • Expert Stencyler
  • *
March 04, 2017, 08:04:47 am
Great!


LIBERADO

  • Expert Stencyler
  • *
March 04, 2017, 08:50:10 am
Hey @rob1221, it seems that it doesn't work properly. The "active [always]" option works only when is used in a "when created" event, but it doesn't work when is used in any other event. Once an actor is set to "active [on screen]" and exits the screen, cannot be set to "active [always]", it remains stationary when using the blocks to set its speed.

Please, can you fix it?
« Last Edit: March 04, 2017, 09:16:14 am by LIBERADO »


rob1221

  • Master Stencyler
  • *
March 04, 2017, 09:18:18 am
Is the actor changing its own state or is it being changed from somewhere else?  It makes sense to me that an actor can't turn itself back on if disabled.
  • Status changed from Resolved to Need Info


LIBERADO

  • Expert Stencyler
  • *
March 04, 2017, 09:20:01 am
Is the actor changing its own state or is it being changed from somewhere else? 
From the scene events.
« Last Edit: March 04, 2017, 09:35:55 am by LIBERADO »


LIBERADO

  • Expert Stencyler
  • *
March 04, 2017, 09:30:02 am
When an actor which is set to "active [on screen]" exits the screen, I use this event in the scene:



But the actor does not move anymore.

« Last Edit: March 04, 2017, 09:31:28 am by LIBERADO »


rob1221

  • Master Stencyler
  • *
March 04, 2017, 11:21:36 am
This only happens with box2D actors and I can't tell why.  Tomorrow I'll spend more time trying to figure this out.

I think this might be the same issue you reported elsewhere: http://community.stencyl.com/index.php?issue=658.0
  • Status changed from Need Info to Assigned
« Last Edit: March 04, 2017, 11:25:20 am by rob1221 »


rob1221

  • Master Stencyler
  • *
March 05, 2017, 09:25:02 am
Fixed in b9310.
  • Status changed from Assigned to Resolved


LIBERADO

  • Expert Stencyler
  • *
March 05, 2017, 12:26:20 pm
OK, it seems to work fine now. Thanks!


LIBERADO

  • Expert Stencyler
  • *
March 05, 2017, 04:32:39 pm
There is a problem, Flash Player shows an error message when any pre-built Behavior that contains the old "make [self] always active" block is attached to any actor. Such message says (in Spanish) that makeSimulate is not a function. Please see the image below.

(Note: If the block is removed from the pre-built Behavior and placed again by dragging it from the Palette, then it works without errors)

« Last Edit: March 05, 2017, 06:23:38 pm by LIBERADO »


LIBERADO

  • Expert Stencyler
  • *
March 05, 2017, 06:28:34 pm
 Another problem.

When the CCD is enabled by default, this happens:
   


When the CCD is disabled by default, this happens:
   


These things happen when using this code, but if the block is used inside a mouse event, other anomalies occur when the block is used several times. For example, the "disable" option may enable the CCD instead of disabling it, or vice versa.

I hope this information can help you to solve these issues.
« Last Edit: March 05, 2017, 06:47:30 pm by LIBERADO »


rob1221

  • Master Stencyler
  • *
March 05, 2017, 07:13:18 pm
I'll take a look at the block conversion problem later, but it might have something to do with the fact that I only edited the English language files.

If you're testing continuous collision detection using tiles, keep in mind that tiles have CCD turned on with that block but cannot have CCD turned off with that block because other actors might still have CCD on.

I don't see why being in a mouse event would change how the block works, but if you have a sample game showing the problem that would help.
  • Status changed from Resolved to Confirmed


LIBERADO

  • Expert Stencyler
  • *
March 05, 2017, 07:22:06 pm
I'll take a look at the block conversion problem later, but it might have something to do with the fact that I only edited the English language files.
OK.

If you're testing continuous collision detection using tiles, keep in mind that tiles have CCD turned on with that block but cannot have CCD turned off with that block because other actors might still have CCD on.
No, I have not used tiles. I have found such anomalies by testing CCD between two actors only, no tiles.

I don't see why being in a mouse event would change how the block works, but if you have a sample game showing the problem that would help.
OK, I will upload a sample game, so you can check it.
« Last Edit: March 05, 2017, 07:26:40 pm by LIBERADO »


LIBERADO

  • Expert Stencyler
  • *
March 05, 2017, 09:47:44 pm
Really, I get an unpredictable result. Sometimes the "enable" option disables the CCD, or the "disable" option enables it. Other times, the block does nothing, or it seems to work only after using it twice. And other times, the block works the first time only, then it does not work anymore.

I have uploaded a basic sample game, please check it.
  • Version changed from 3.4.0 beta2 to 3.4.0 beta5
« Last Edit: March 06, 2017, 05:30:40 am by LIBERADO »


New attachment added by LIBERADO - March 05, 2017, 09:48:22 pm


LIBERADO

  • Expert Stencyler
  • *
March 06, 2017, 05:31:02 am
When you test the uploaded sample, click the screen to enable/disable CCD.
In this sample, the CCD of the bullet actor can be enabled but cannot be disabled later.
   
It seems that depending on the event used and the default CCD setting of the actors involved, a different anomaly occurs.
« Last Edit: March 06, 2017, 05:38:55 am by LIBERADO »


rob1221

  • Master Stencyler
  • *
March 06, 2017, 09:37:29 am
I think I fixed the crashing issue in  b9311, but let me know if there's anything wrong.  When the crashing issue is confirmed to be fixed then I'll move on to the CCD problem in the engine.
  • Status changed from Confirmed to Need Info


LIBERADO

  • Expert Stencyler
  • *
March 06, 2017, 10:12:51 am
Build 9311 checked. The crashing issue seems to be fixed now.
« Last Edit: March 06, 2017, 10:14:20 am by LIBERADO »


Issue updated by rob1221 - March 06, 2017, 11:02:37 am
  • Status changed from Need Info to Confirmed


Pages: 1 2

Details

  • Reported
    March 16, 2016, 10:18:05 am
  • Updated
    March 07, 2017, 02:06:45 pm

  • View Status
    Public
  • Type
    Suggestion
  • Status
    Resolved
  • Priority
    Normal
  • Version
    3.4.0 beta5
  • Fixed in
    (none)
  • Assigned to
    rob1221
  • Category
    Design Mode Blocks

Tags


Attachments

* CCD_issue.stencyl (377.88 kB - downloaded 3 times.)
* CCD_issue_Both_Actors_set_to_Normal.stencyl (380.31 kB - downloaded 3 times.)