Customise Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.

No cookies to display.

[ad_1]

One of the simplest ways that I got here up with is, in line with the observer sample, to inform all lessons the place the thing was saved about its destruction and take away references to it from there.

That is what I at all times do.

[System.Serializable] public class DestroyableEvent : UnityEvent<Destroyable> {}
public class Destroyable : MonoBehaviour {
    [SerializeField] non-public DestroyableEvent destroyedEvent = new DestroyableEvent();
    public DestroyableEvent DestroyedEvent => destroyedEvent;

    void OnDestroy() {
        destroyedEvent.Invoke(this);
    }
}

Then in another class you might have one thing like this:

[SerializeField] non-public Destroyable prefab;
non-public Record<Destroyable> objects = new Record<Destroyable>();

public void SpawnObject() {
    var newObject = Instantiate(prefab);
    newObject.DestroyedEvent.AddListener(objects.Take away);
    objects.Add(newObject);
}

If objects are created and destroyed incessantly, it is best to use a pooling system as an alternative, however you continue to want occasions to trace when an object is returned to the pool so you’ll be able to take away it from any related lists.

One other resolution you should utilize is to periodically scan lists for null entries and take away them, or take away them if you attempt to entry an entry within the record and decide that it is null. I favor to make use of an event-driven method as proven above.

[ad_2]

Leave a Reply

Your email address will not be published. Required fields are marked *