lukeskt / reactive-mise-en-scene Goto Github PK

Move the loader algorithms out of specific loaders and into some kind of container class (ScriptableObject?) to deduplicate code and improve reuse.

There is a hack fix implemented where code tries to find render component on same object, then looks up if you have specified one manually, then if those fail gets the first render component it finds on child.

Not ideal, is there a way to composite child object render components together?

Sometimes Time.time.now comparison on enter and exit focus in FocusMeasures component gives wildly larger times than feasible. Seems to happen very rarely. Will test a variety of setups of objects and see if can track down.

Links that might help resolve:

• https://docs.unity3d.com/ScriptReference/Time.html
• https://gamedev.stackexchange.com/questions/141807/what-happens-when-time-time-gets-very-large-in-unity

Tracking player object through locales / areas via triggers or other mechanism?

Visualiser - in editor?

Should show a visualisation of the tendency mix or dominant tendency moment to moment for each locale, and how that opens up access to others, etc.

Probably an unweighted graph and/or hypergraph that becomes weighted over time as tendencies play out and scenes loaded in response.

Add lines from objects to locale also?

Track which locale last visited before loading next, use that to determine tendency loading?

A basic version of Nimbus interactions in development. This needs finishing and implementing in a similar way to Focus and FocusMeasures, but might need a separate data handler / etc. Is there a relevant use-case beyond immediate interactions for Nimbus in this plugin's system?

Create prefabs for common use cases, e.g. a scene/locale hierarchy as a starting point for building an experience.

Mix of tendency with custom playables for timelines for complex over-time interactions?

Load different signals to timeline or reference different signal senders or receivers dependent upon tendency mix?

Needs investigation, might be able to remove need for singleton pattern.

Need a logging system to track object, locale and global tendency over time and log it to CSV or another file format for debug, studies, etc.

Rather than a discrete / Start-based loading, offer a toggle to enable continuously updated loading of objects and other elements based on tendency. Might want to get the current locale after the specified locale for this, so a locale can evolve its config over time as you attend to objects within it.

Also consider: Timeline and signals system expansion to handle tendency tracking over time to make reactions more dynamic.

Investigate cross-fading of local HDRP volumes between scenes/locales (and tendencies?) and/or combining values of volume profiles? single profile with tendency values applied/combined and applied to different parts of it?

There is a hack fix implemented where code tries to find collider component on same object, then looks up if you have specified one manually, then if those fail gets the first collider component it finds on child. Similar issue to Issue #3.

Is there a way to composite child object collider components together to get an overall collider shape/size?

Getting an index out of bounds error sometimes when loading objects proportionally with prefab loader. Suspect an error in the list generation in proportional / inverse proportion algos.

Line 150/151 may be culprit?

Write object states out to JSON or binary blob or other serialization to save memory if required, may also help with reloading a scene with previous states.

If loading previous scene/locale, get attention data and set in reactive objects to restore state. Maybe cross-session persistence too?

See possible solutions:

• https://stackoverflow.com/questions/34426570/best-way-to-save-data-in-unity-game,
• https://danielilett.com/2019-10-26-unity-tips-5-persistent-data/

Currently does not have parity with other loader custom editors, e.g. with hidden dropdown logic etc.

Create a loader script that asynchronously loads Unity scenes based on specified locale/global tendency.

Are either of these worthwhile e.g. in improving architecture and avoiding use of performance-affecting UnityEvents?

Might this improve e.g. complex large number asset loading?

No errors when there is a mismatch between the settings file on the attention data manager and focus objects, loaders, etc. Need to either find a way to set the config file at the attention data manager script / singleton level, or do error handling so it doesn't fail silently but gives proper feedback to diagnose the issue.