LogiX

From NeosVR Wiki
Jump to navigation Jump to search
Other languages:
English • ‎日本語 • ‎한국어

LogiX is the name of Neos' visual programming system, which is used for creating and modifying LogiX nodes and making connections between them.

RubikLogix.png

In Neos, to access LogiX and the LogiX node menu (shown above) you need to first equip the LogiX Tooltip

NodeMenu

Actions Assets Audio Avatar Color Components Debug
Flow Formatting Input Input Devices Interaction Locomotion Math
Meta Network Operators Physics Playback References Rendering
Slots String Tools Transactions Transform UI Undo
Users Utility Variables Visualization World Cache Delay Value
Demultiplex Display Display Impulse Impulse Relay Multiplex Pick Random Relay
Updating Relay
LogiX Page

LogiX Fundamentals

Impulses

Impulses are directed, instant evaluations of Logix nodes and input values that run locally for the user who "owns" them.

The user that the impulse belong to evaluates data as it appears to them at that moment, since the impulse takes place locally. However, the impulse can run through nodes that cause a datamodel change, which will replicate to other players. Writing a value, setting the transform of a slot, or any other operation that "sets" a value or transform/hierarchy/slot change in the datamodel will be replicated.

Values

These are data values that come from fields in Components via interfaces or as the outputs of Logix nodes. They can be generic C# system types or custom Neos types. Depending on how the value is calculated, via logix or a component, the data can appear differently for different players - This is most apparent when a field is driven, or something involving the Local User is used as an input. Types

Nodes

Nodes are what creates a Logix program, they do various calculations or operations. Some nodes only run calculations based on their input values and provide the outputs readily, others are "passthrough" nodes that require an impulse to trigger or affect their operation. Often passthrough nodes perform a change in the datamodel, though this is not always the case.

Passthrough nodes can be chained together using the corresponding impulse passthrough outputs, to control the order of operations.

Passthrough nodes and other impulse-generating nodes, such as events, can have data outputs that only present valid data within their accompanying output impulse's Evaluation Context - You must process them using the same impulse that the node was triggered with or the data will be gone.