Implement deactivate actor method
See original GitHub issueThe actor API allows it to deactivate an actor. The testing code also has implemented an API call to deactivate an actor. It would be great if the SDK could provide a method in the ActorProxy
class which allows it to deactivate an actor without implementing an API call by itself.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Disable an Actor - C++
Coming from a Unity background, I am wondering if there is a way to disable an actor (rendering, physics, tick, etc.) ...
Read more >Coming from Unity - disabling actors within the editor
Now open any actor you want to be disable-able and click "Add Component" and search for "EditorDisableActor". Once you have added the component, ......
Read more >Deactivate actor using Python - Game Engine
Hello, For 0.3 you can disable the actual 'actor' physics setting at run-time. With 0.2 or 0.3 you can disable an object's physics...
Read more >Actors API reference
Deactivate actor. Deactivates an actor by persisting the instance of the actor to the state store with the specified actorId. HTTP Request.
Read more >Actor runtime configuration parameters
Actors that have been idle longer than actor_idle_timeout will be deactivated. The duration when in the process of draining rebalanced actors. This specifies ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s all about freeing up resources. We have thousand of actors which run in parallel. We know exactly the lifetime of these actors. So with killing them we can free resources.
@yaron2 - what @halspang is saying this is exactly the conclusion that I came to.
There is no contract provided by the runtime for a client to deactivate an actor. If this is a desirable thing it should be part of the surface area for the client.