This is a random list of "common" limitations that Resonite has. This isn't meant to scare you away from Resonite, but serves as a page of common limitations. It's goals are similar to the Myths page. It is likely not-complete.
Visuals
Shaders
Resonite currently does not currently support any custom shaders, this means that you're unable to use any of the shaders you might have used on other platforms.
Generally, this isn't as drastic as it would be on other platforms due to Resonite features that allow you to edit shaders on the fly dynamically with ProtoFlux, or Components. This can still allow effects such as Rainbow animations, scrolling textures, twinkles/sparkles.
Post-Processing
You cannot, edit the post-processing settings of Resonite. This includes things like:
- Bloom
- Ambient Occlusion
General Programming
Text-based programming
ProtoFlux, is the only way to program in Resonite, there is not Text-based programming. If you want to write code you'll need to use Protoflux. Again, there are exceptions to this in the Mod / Plugin space but for general use ProtoFlux is the only way.
Collections
There is currently no way to control common collection types such as:
- Arrays
- Lists
- Maps
You will sometimes see components or ProtoFlux nodes that seem to have collection/list style mechanics but these are limited.
Dynamic Component/Property Access
You cannot currently dynamically access the properties or elements of an object. There are exceptions to this with certain nodes or components that can but there is no generic access. There are ways around this in most cases, but do keep it in mind.
Resonite Features
This is sort of a meta-list of notes about random Resonite features. These aren't limitations that someone new to Resonite might notice, but are still here for reference.
Cloud Variables
Cloud variables are better explained on their detailed page.