ProtoFlux/fr

Introduction

Le logo officiel de ProtoFlux

ProtoFlux est un language de scripting graphique qui peut être manipulé dans l'espace 3D avec l'outil ProtoFlux.

ProtoFlux est la cerise sur le gateau de nous outils créatifs - le language de programmation visuel le plus puissant que notre équipe expérimenté a crée et vous permettant de prototyper et construire tout ce que vous voulez, de simples interactions a des jeux complexes - avec une collaboration et exécution en temps réel.

Vous pouvez tout créer, d'avatars ou monde a des systèmes complexes.

— https://resonite.com/features.html

Utilisation

ProtoFlux est représenté dans le monde avec des nodes qui peuvent être matérialisées avec le navigateur de nodes ProtoFlux.

Vous pouvez matérialiser un outil ProtoFlux en allant dans le dossier Resonite Essentials de votre Inventaire pour commencer a programmer.

Pour voir une liste de nodes, allez sur liste de nodes en mode navigateur pour une vue comme dans le jeu ou liste de nodes par ordre alphabétique pour une liste complète. Toutes les pages de node ont des liens vers les deux listes.

ProtoFlux peut être simplement emballé et déballé dans un Slot, objet, avatar, monde ou n'importe ou vous le souhaitez.

You can also quick select nodes that already exist by tapping Secondary while pointing at the node. 

Nodes can be connected by pointing the laser at a node's connection point and holding Primary (Trigger for most controllers, or Left Click), then dragging the wire and letting go of Primary while pointing at another node's connection point. They can then be cut by intersecting the red line that comes out the tip of the Protoflux Tip while holding Primary.

Interfacing With Components / Slots

To change or read the properties of a slot's or component's properties, grab with your controller (or right click) while pointing at a given field name with the Protoflux tip (For example, point at and grab the spot where it says 'Position' on a slot). While grabbing the field with the Protoflux tip, open your Context menu. This will give you three options.

Source: This will spawn a node that references the source of the property you were holding. This is used to both read the value of the field or to write to it using Protoflux.

Drive: This will spawn a node to allow you to continuously locally write a value to the variable you were holding.

Reference: This will spawn a node to allow you to get the reference to the field of the given value. This is useful for nodes like ProtoFlux:Tween Value that require a reference to the value it is changing.

Variables

To pack Protoflux, hold Secondary while pointing at a group of Protoflux using the Protoflux Tip. The Protoflux should become light blue, this indicates it has been selected (This also makes the Protoflux that is selected act as one object, allowing you to easily move groups of Protoflux around).

Once the Protoflux has been selected, make an empty Slot using the Inspector. This will be the slot the Protoflux is packed into. To then pack the Protoflux, grab the slot using the left side of the Inspector so that it's name is above the Protoflux Tip. While you are grabbing it, open your Context menu and select Pack Into. Once packed, the Protoflux will still function like normal, but will no longer show it's visuals and will apply some optimizations.

To then unpack it, grab the same slot you packed it into and open your context menu. There should now be an option to unpack the Protoflux.

Variables

Dans ProtoFlux, il y a trois types de variables génériques:

• Data Model Store
• Store
• Local

The simplest type of variable is a Data Model Store. It's automatically synced to all users upon being written to. Most simple scripts can be done entirely with these, but it can impact performance if overused.

The natural progression down the list is a Store. It's similar to standard variables in most languages. It does not get synced over the network, which alleviates the overhead of doing so, but could lead to desync.

Lastly, we have locals. They're instanced for different execution chains, so if your ProtoFlux is called twice at once, you can read from and write to the variable from both contexts, they will each use a unique instance of the variable that gets discarded when that execution ends.