Resonite Wiki - Recent changes [en]

Face and Eye Tracking (Setup)

Rellik — Thu, 05 Nov 2026 07:40:15 GMT

Gotta include StaeamVR...

← Older revision		Revision as of 07:40, 5 November 2026
(2 intermediate revisions by the same user not shown)
Line 52:		Line 52:
	\|-		\|-
	\|Steam Frame		\|Steam Frame
	\|[[Face and Eye Tracking (Setup)#Steam Frame\|~~Mod~~]] ~~(Native coming soon<small><sub>(tm)</sub></small>)~~		\|[[Face and Eye Tracking (Setup)#Steam Frame\|Native SteamVR or Mods]]
	\|		\|
	\|}		\|}
Line 110:		Line 110:

	# Install [https://github.com/Project-Babble/Babble-Frame-Runtime Babble Frame Runtime] on the headset		# Install [https://github.com/Project-Babble/Babble-Frame-Runtime Babble Frame Runtime] on the headset
	# ~~Add -ForceBabble to Resonite launch options and enable~~ Babble OSC as an output in the Babble Frame Runtime ~~Settings~~		# Enable Babble OSC as an output in the Babble Frame Runtime settings
	# (~~Latest version of Babble Frame Runtime should not require this mod~~) ~~<s>~~Install ~~Resonite mod:~~ [https://github.com/noblereign/ResoniteBaballoniaEyeExpressions/releases~~/tag/v2.0.0~~ ResoniteBaballoniaEyeExpressions]~~</s>~~		# Add -ForceBabble to Resonite's [https://help.steampowered.com/en/faqs/view/7D01-D2DD-D75E-2955 launch options]
			# (Optional) Install 2.1.0 or later of [https://github.com/noblereign/ResoniteBaballoniaEyeExpressions/releases ResoniteBaballoniaEyeExpressions] for additional features

	===== FrameEyeOSC =====		===== FrameEyeOSC =====

ProtoFlux:RaycastOne

LumenalMushroom — Thu, 05 Nov 2026 05:07:05 GMT

Minor rewordings of various things to emphasize the vector space of various inputs and outputs.

ProtoFlux:RaycastAll

LumenalMushroom — Thu, 05 Nov 2026 05:00:49 GMT

Adding information about input spaces for Direction and Origin, rewording how to use the Hits output, and information on how the outputs are ordered.

ProtoFlux:AsyncForEach

LumenalMushroom — Thu, 05 Nov 2026 04:45:06 GMT

Added dictionary specific information about this node.

← Older revision		Revision as of 04:45, 5 November 2026
Line 18:		Line 18:
	\|}}		\|}}

	The '''Async ForEach''' node takes in a [[Collection]] and if the node should be done in reverse or not. When called, it will iterate through the list, providing the element of that list asyncronously.		The '''Async ForEach''' node takes in a [[Collection]] and if the node should be done in reverse or not. When called, it will iterate through the list, providing the element of that list asyncronously. For dictionaries, the order of elements provided is not guaranteed, treat each iteration as independent of any other. For lists, the order begins with index 0 and ends with the last index, or in reverse if Reverse is true.

	== Inputs ==		== Inputs ==
Line 26:		Line 26:
	Calls an impulse to loop through a collection asyncronously.		Calls an impulse to loop through a collection asyncronously.

	=== Collection ([[Type:~~IList~~\|~~IList~~]]) ===		=== Collection ([[Type:ICollection\|ICollection]]) ===

	The collection to loop through.		The collection to loop through.
Line 42:		Line 42:
	=== LoopIteration ([[Impulses\|AsyncCall]]) ===		=== LoopIteration ([[Impulses\|AsyncCall]]) ===

	Fires ~~when the loop iterating through~~ each element of the collection ~~list~~.		Fires for each element in the collection.

	=== LoopFailed ([[Impulses\|Continuation]]) ===		=== LoopFailed ([[Impulses\|Continuation]]) ===
Line 54:		Line 54:
	=== Element (Generic) ===		=== Element (Generic) ===

	The element of the collection ~~currently~~ being iterated through.		The element of the current iteration. If the collection being iterated through is a dictionary, this output will be a [[Type:KeyValuePair\|KeyValuePair]] matching the key and value types of the dictionary. An [[ProtoFlux:UnpackKeyValuePair\|UnpackKeyValuePair]] node must be used in this case.

	[[Category:ProtoFlux:Flow]]		[[Category:ProtoFlux:Flow]]

ProtoFlux:ForEach

LumenalMushroom — Thu, 05 Nov 2026 04:38:16 GMT

New info about dictionary specific cases with this node.

← Older revision		Revision as of 04:38, 5 November 2026
Line 18:		Line 18:
	\|}}		\|}}

	The '''ForEach''' node takes in a [[Collection]] and if the node should be done in reverse or not. When called, it will iterate through the collection, providing the ~~element~~ of ~~that list~~.		The '''ForEach''' node takes in a [[Collection]] and if the node should be done in reverse or not. When called, it will iterate through the collection, providing each element in the collection on the Element output during each iteration. For dictionaries, order of elements provided is not guaranteed, so treat each iteration as independent of any other. For lists or arrays, the order starts from index 0 and ends with the last index, or in reverse order if Reverse is true.

	It directly calls the [https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/statements/iteration-statements#the-foreach-statement C# foreach] function.		It directly calls the [https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/statements/iteration-statements#the-foreach-statement C# foreach] function.

	It has an [[Impulses#Async\|async]] version too, see: [[ProtoFlux:AsyncForEach\|AsyncForEach]]		It has an [[Impulses#Async\|async]] version too, see: [[ProtoFlux:AsyncForEach\|AsyncForEach]].
	{{Note\|If you are working with Lists, and you want the Index of the element you are refrencing, use [[ProtoFlux:ForEachWithIndex\|ForEachWithIndex]] instead.\|suggestion}}		{{Note\|If you are working with Lists, and you want the Index of the element you are refrencing, use [[ProtoFlux:ForEachWithIndex\|ForEachWithIndex]] instead.\|suggestion}}

Line 31:		Line 31:
	Calls an impulse to loop through a collection.		Calls an impulse to loop through a collection.

	=== Collection ([[Type:~~IList~~\|~~IList~~]]) ===		=== Collection ([[Type:ICollection\|ICollection]]) ===

	The collection to loop through.		The collection to loop through.
Line 51:		Line 51:
	=== LoopFailed ([[Impulses\|Continuation]]) ===		=== LoopFailed ([[Impulses\|Continuation]]) ===

	Fires when the loop failed. For example this is triggered when when the collection being iterating through is modified. <ref>https://github.com/Yellow-Dog-Man/Resonite-Issues/discussions/7371</ref>		Fires when the loop failed. For example, this is triggered when when the collection being iterating through is modified. <ref>https://github.com/Yellow-Dog-Man/Resonite-Issues/discussions/7371</ref>

	=== LoopEnd ([[Impulses\|Continuation]]) ===		=== LoopEnd ([[Impulses\|Continuation]]) ===
Line 59:		Line 59:
	=== Element (Generic) ===		=== Element (Generic) ===

	The element of the collection currently being iterated through.		The element of the collection currently being iterated through. If the collection being iterated through is a dictionary, this output will be a [[Type:KeyValuePair\|KeyValuePair]] matching the key and value types of the dictionary. The [[ProtoFlux:UnpackKeyValuePair\|UnpackKeyValuePair]] node must be used to see the underlying data in this case.

	[[Category:ProtoFlux:Flow]]		[[Category:ProtoFlux:Flow]]

Type:SyncFieldDictionary

LumenalMushroom — Thu, 05 Nov 2026 04:22:08 GMT

Fixed the link to SyncRefDictionary

← Older revision		Revision as of 04:22, 5 November 2026
Line 1:		Line 1:
	A SyncFieldDictionary is a type of [[Collections\|Collection]] that maps data model values (string, int, float, etc) to data model values. Every key in a dictionary is unique and maps to a specific value, which doesn't have to be unique. For string and Uri, null may be used as a key. For [[Type:Nullable`1\|Nullable]] types, null may not be used as a key.		A SyncFieldDictionary is a type of [[Collections\|Collection]] that maps data model values (string, int, float, etc) to data model values. Every key in a dictionary is unique and maps to a specific value, which doesn't have to be unique. For string and Uri, null may be used as a key. For [[Type:Nullable`1\|Nullable]] types, null may not be used as a key.

	If you are looking to map data model values to data model references ([[Slot]], [[Type:IAssetProvider`1\|IAssetProvider]], etc), see [[SyncRefDictionary]].		If you are looking to map data model values to data model references ([[Slot]], [[Type:IAssetProvider`1\|IAssetProvider]], etc), see [[Type:SyncRefDictionary\|SyncRefDictionary]].

	SyncFieldDictionaries are synchronized between all players in a session, and their contents persist across duplicating and saving, like other fields. The contents of any SyncFieldDictionary cannot be viewed or edited using an inspector at this time, which is why an inspector on one says "Dictionaries not supported yet". This is misleading, as dictionaries may be read and edited with the use of specific nodes, see the [[:Category:ProtoFlux:Collections\|Collections]] for a list of all the nodes which can work with collections.		SyncFieldDictionaries are synchronized between all players in a session, and their contents persist across duplicating and saving, like other fields. The contents of any SyncFieldDictionary cannot be viewed or edited using an inspector at this time, which is why an inspector on one says "Dictionaries not supported yet". This is misleading, as dictionaries may be read and edited with the use of specific nodes, see the [[:Category:ProtoFlux:Collections\|Collections]] for a list of all the nodes which can work with collections.

	A SyncFieldDictionary may be placed on a slot via attaching a [[Component:ValueDictionary\|ValueDictionary]] component to it and providing the appropriate types. From there, the SyncFieldDictionary on that component may be referenced statically like any other reference, or exposed via a [[Dynamic variables\|Dynamic variable]] matching the dictionary's exact type.		A SyncFieldDictionary may be placed on a slot via attaching a [[Component:ValueDictionary\|ValueDictionary]] component to it and providing the appropriate types. From there, the SyncFieldDictionary on that component may be referenced statically like any other reference, or exposed via a [[Dynamic variables\|Dynamic variable]] matching the dictionary's exact type.

Type:SyncRefDictionary

LumenalMushroom — Thu, 05 Nov 2026 04:21:22 GMT

Added some basic information about SyncRefDictionaries, please format nicely when time permits, as I am sleepy at the time of writing.

New page

A SyncRefDictionary is a type of [[Collections|Collection]] that maps data model values (string, int, float, etc) to data model references ([[Slot]], [[Type:IWorldElement|IWorldElement]], etc). Every key in a dictionary is unique and maps to a specific value, which doesn't have to be unique. For string and Uri, null may be used as a key. For [[Type:Nullable`1|Nullable]] types, null may not be used as a key.

If you are looking to map data model values to data model values, see [[Type:SyncFieldDictionary|SyncFieldDictionary]]. There is currently no way to use data model references as keys in a dictionary.

SyncRefDictionaries are synchronized between all players in a session, and their contents persist across duplicating and saving, like other fields. The contents of any SyncRefDictionary cannot be viewed or edited using an inspector at this time, which is why an inspector on one says "Dictionaries not supported yet". This is misleading, as dictionaries may be read and edited with the use of specific nodes, see [[:Category:ProtoFlux:Collections|Collections]] for a list of all the nodes which can work with collections.

A SyncRefDictionary may be placed on a slot via attaching a [[Component:ReferenceDictionary|ReferenceDictionary]] component to it and providing the appropriate types. From there, the SyncRefDictionary on that component may be referenced statically like any other reference, or exposed via a [[Dynamic variables|Dynamic variable]] matching the dictionary's exact type.

Type:SyncFieldDictionary

LumenalMushroom — Thu, 05 Nov 2026 04:06:15 GMT

Added some basic information about the SyncFieldDictionary collection from my limited testing and working with it. My formatting is likely off as I am sleepy, please fix when time permits.

New page

A SyncFieldDictionary is a type of [[Collections|Collection]] that maps data model values (string, int, float, etc) to data model values. Every key in a dictionary is unique and maps to a specific value, which doesn't have to be unique. For string and Uri, null may be used as a key. For [[Type:Nullable`1|Nullable]] types, null may not be used as a key.

If you are looking to map data model values to data model references ([[Slot]], [[Type:IAssetProvider`1|IAssetProvider]], etc), see [[SyncRefDictionary]].

SyncFieldDictionaries are synchronized between all players in a session, and their contents persist across duplicating and saving, like other fields. The contents of any SyncFieldDictionary cannot be viewed or edited using an inspector at this time, which is why an inspector on one says "Dictionaries not supported yet". This is misleading, as dictionaries may be read and edited with the use of specific nodes, see the [[:Category:ProtoFlux:Collections|Collections]] for a list of all the nodes which can work with collections.

A SyncFieldDictionary may be placed on a slot via attaching a [[Component:ValueDictionary|ValueDictionary]] component to it and providing the appropriate types. From there, the SyncFieldDictionary on that component may be referenced statically like any other reference, or exposed via a [[Dynamic variables|Dynamic variable]] matching the dictionary's exact type.

Category:Components/ja

Yoshi1123 — Wed, 04 Nov 2026 16:10:17 GMT

Created page with "基本的なアバターおよびユーザーシステム。"

← Older revision		Revision as of 16:10, 4 November 2026
Line 16:		Line 16:
	\|Cloud\|クラウドユーザー情報、サーバーステータス		\|Cloud\|クラウドユーザー情報、サーバーステータス
	\|Common UI\|[[Special:MyLanguage/UIX\|UIX]]/タッチ可能なボタンイベント、UIドライバー		\|Common UI\|[[Special:MyLanguage/UIX\|UIX]]/タッチ可能なボタンイベント、UIドライバー
	\|Data\|~~<span lang="en" dir="ltr" class="mw-content-ltr">Dynamic Variables, item Metadata, value fields.</span>~~		\|Data\|動的変数（Dynamic Variables）、アイテムのメタデータ、値フィールド（ValueField）。
	\|Debug\|~~<span lang="en" dir="ltr" class="mw-content-ltr">Component Debugging</span>~~		\|Debug\|デバッグコンポーネント
	\|Generators\|~~<span lang="en" dir="ltr" class="mw-content-ltr">Procedural Generators.</span>~~		\|Generators\|プロシージャルジェネレーター
	\|Input\|~~<span lang="en" dir="ltr" class="mw-content-ltr">Controls for Desktop, VR inputs, haptic, inputs interactions.</span>~~		\|Input\|デスクトップ操作、VR入力、触覚フィードバック、および入力インタラクション
	\|Interaction\|~~<span lang="en" dir="ltr" class="mw-content-ltr">~~Grip Pose Reference.~~</span>~~		\|Interaction\|Grip Pose Reference.
	\|Localization\|~~<span lang="en" dir="ltr" class="mw-content-ltr">Translations.</span>~~		\|Localization\|翻訳
	\|Locomotion\|~~<span lang="en" dir="ltr" class="mw-content-ltr">User Locomotions, Locomotion modifiers, Character Controller interactions.</span>~~		\|Locomotion\|ユーザーの移動機能（Locomotion）、移動操作の調整パラメータ、キャラクターコントローラーとのインタラクション
	\|Media\|<span lang="en" dir="ltr" class="mw-content-ltr">Audio clip player variations, Media Drivers.</span>		\|Media\|<span lang="en" dir="ltr" class="mw-content-ltr">Audio clip player variations, Media Drivers.</span>
	\|Metadata\|<span lang="en" dir="ltr" class="mw-content-ltr">Metadata about the object.</span>		\|Metadata\|<span lang="en" dir="ltr" class="mw-content-ltr">Metadata about the object.</span>
Line 38:		Line 38:
	\|UIX\|ResoniteのUIシステムである[[Special:MyLanguage/UIX\|UIX]]用のコンポーネントです。		\|UIX\|ResoniteのUIシステムである[[Special:MyLanguage/UIX\|UIX]]用のコンポーネントです。
	\|Uncategorized\|<span lang="en" dir="ltr" class="mw-content-ltr">Unsorted Components that need sorting.</span>		\|Uncategorized\|<span lang="en" dir="ltr" class="mw-content-ltr">Unsorted Components that need sorting.</span>
	\|Users\|~~<span lang="en" dir="ltr" class="mw-content-ltr">Basic Avatar & User systems.</span>~~		\|Users\|基本的なアバターおよびユーザーシステム。
	\|Userspace\|<span lang="en" dir="ltr" class="mw-content-ltr">Virtual Keyboard inputs.</span>		\|Userspace\|<span lang="en" dir="ltr" class="mw-content-ltr">Virtual Keyboard inputs.</span>
	\|Utility\|<span lang="en" dir="ltr" class="mw-content-ltr">Value/Reference Multiplexer, Hyperlinks.</span>		\|Utility\|<span lang="en" dir="ltr" class="mw-content-ltr">Value/Reference Multiplexer, Hyperlinks.</span>

Resonite ready avatar bases

Mint Shock — Tue, 03 Nov 2026 20:25:55 GMT

Sylora - Furrred Snake

@@ Line 1,076: / Line 1,076: @@
+|
 * [[ResonitePackage]]
 |}

File:Sylora - Furrred Snake - Avatar Base.webp

Mint Shock — Tue, 03 Nov 2026 20:20:32 GMT

Mint Shock uploaded File:Sylora - Furrred Snake - Avatar Base.webp

New page

Sylora - Furrred Snake - Avatar Base

Template:SwizzleDriverDescription

.hecko — Tue, 03 Nov 2026 17:32:24 GMT

nitpick

← Older revision		Revision as of 17:32, 3 November 2026
Line 1:		Line 1:
	The '''{{PAGENAME}}''' component drives a [[Type:{{ucfirst:{{{3}}}}}{{#ifexpr:{{#invoke:String\|find\|{{{3}}}\|Q}}+{{#invoke:String\|find\|{{{3}}}\|color}}\|\|{{{4}}}}}\|{{ucfirst:{{{3}}}}}{{#ifexpr:{{#invoke:String\|find\|{{{3}}}\|Q}}+{{#invoke:String\|find\|{{{3}}}\|color}}\|\|{{{4}}}}}]] ~~value~~ based on the channels of the input [[Type:{{ucfirst:{{{1}}}}}{{{2}}}\|{{ucfirst:{{{1}}}}}{{{2}}}]]. Each output channel (counting from 0) is assigned to an input channel (or -1 for {{#ifeq:{{{3}}}\|bool\|false\|zero}}), allowing for arbitrary rearrangement (i.e. [[wikipedia:Swizzling (computer graphics)\|swizzling]]). It's equivalent to [[ProtoFlux:Unpack{{{2}}}\|unpacking]] the input value and [[ProtoFlux:Pack{{{4}}}\|packing]] it again with ProtoFlux.		The '''{{PAGENAME}}''' component drives a [[Type:{{ucfirst:{{{3}}}}}{{#ifexpr:{{#invoke:String\|find\|{{{3}}}\|Q}}+{{#invoke:String\|find\|{{{3}}}\|color}}\|\|{{{4}}}}}\|{{ucfirst:{{{3}}}}}{{#ifexpr:{{#invoke:String\|find\|{{{3}}}\|Q}}+{{#invoke:String\|find\|{{{3}}}\|color}}\|\|{{{4}}}}}]] field based on the channels of the input [[Type:{{ucfirst:{{{1}}}}}{{{2}}}\|{{ucfirst:{{{1}}}}}{{{2}}}]]. Each output channel (counting from 0) is assigned to an input channel (or -1 for {{#ifeq:{{{3}}}\|bool\|false\|zero}}), allowing for arbitrary rearrangement (i.e. [[wikipedia:Swizzling (computer graphics)\|swizzling]]). It's equivalent to [[ProtoFlux:Unpack{{{2}}}\|unpacking]] the input value and [[ProtoFlux:Pack{{{4}}}\|packing]] it again with ProtoFlux.

ProtoFlux:LocalImpulseTimeoutSeconds

Shaun — Tue, 03 Nov 2026 06:04:04 GMT

redirect

New page

#REDIRECT [[ProtoFlux:LocalImpulseTimeout]]

Alpha Branches

Electra — Tue, 03 Nov 2026 05:10:27 GMT

Notes about how to save items with NeverSaveAnything, mostly

← Older revision		Revision as of 05:10, 3 November 2026
Line 1:		Line 1:
	Alpha Branches are a way to preview and test features with our community.		Alpha Branches are a way to preview and test features with our community with a goal towards speeding up development.

	== Branch List ==		== Branch List ==
Line 20:		Line 20:
	* Alpha Branches should be used at your own risk		* Alpha Branches should be used at your own risk
	** While we aim to avoid backwards incompatible changes, Alpha Branches may have them		** While we aim to avoid backwards incompatible changes, Alpha Branches may have them
	** We recommend using [[Command_line_arguments#Testing/Debugging\|NeverSaveAnything]], when on an Alpha Branch		** We recommend using [[Command_line_arguments#Testing/Debugging\|NeverSaveAnything]], when on an Alpha Branch.
			** If you wish to save an item from an Alpha build, it is recommended to use Export. If NeverSaveAnything is on, this is the only way you can do it.
	* Ensure you read the update notes from the engineer, these should tell you what's changed and what they're looking for.		* Ensure you read the update notes from the engineer, these should tell you what's changed and what they're looking for.

Command line arguments

Electra — Tue, 03 Nov 2026 05:05:48 GMT

Minor wording changes

← Older revision		Revision as of 05:05, 3 November 2026
(One intermediate revision by the same user not shown)
Line 82:		Line 82:
	<translate><!--T:156--> Some of these are harmless, some are dangerous. Only use them if you have been told to or know what you are doing. </translate>		<translate><!--T:156--> Some of these are harmless, some are dangerous. Only use them if you have been told to or know what you are doing. </translate>

			* '''<code>-NeverSaveAnything</code>''' - <translate> Prevents '''<u>ANY AND ALL</u>''' records from syncing, especially useful for testing on alpha builds. '''CAN CAUSE DATA LOSS'''</translate>
	* '''<code>-NeverSaveSettings</code>''' - <translate><!--T:143--> Prevents settings from being saved and synced, useful for testing purposes and on prerelease builds.</translate>		* '''<code>-NeverSaveSettings</code>''' - <translate><!--T:143--> Prevents settings from being saved and synced, useful for testing purposes and on prerelease builds.</translate>
	* '''<code>-NeverSaveDash</code>''' - <translate><!--T:144--> Prevents dashboard changes from being saved and synced, useful for testing purposes and on prerelease builds.</translate>		* '''<code>-NeverSaveDash</code>''' - <translate><!--T:144--> Prevents dashboard changes from being saved and synced, useful for testing purposes and on prerelease builds.</translate>
Line 100:		Line 101:
	* '''<code>-NoUI</code>''' - <translate><!--T:91--> Hides the [[Userspace]] UI</translate>		* '''<code>-NoUI</code>''' - <translate><!--T:91--> Hides the [[Userspace]] UI</translate>
	* '''<code>-SkipIntroTutorial</code>''' - <translate><!--T:96--> Prevents the intro tutorial from starting</translate>		* '''<code>-SkipIntroTutorial</code>''' - <translate><!--T:96--> Prevents the intro tutorial from starting</translate>
	* '''<code>-Forceintrotutorial</code>''' - <translate><!--T:97--> Forces the intro tutorial to run</translate>		* '''<code>-Forceintrotutorial</code>''' - <translate><!--T:97--> Forces the intro tutorial to run every time</translate>
	* '''<code>-ForceLANOnly</code>''' - <translate><!--T:65--> Ensures all sessions, by default, will be announced only on the LAN network and will <strong>not</strong> be accessible from the internet.</translate><!-- TODO: Is "by default" accurate"? I.e., if this cannot be changed after startup, "by default" should be removed here.-->		* '''<code>-ForceLANOnly</code>''' - <translate><!--T:65--> Ensures all sessions, by default, will be announced only on the LAN network and will <strong>not</strong> be accessible from the internet.</translate><!-- TODO: Is "by default" accurate"? I.e., if this cannot be changed after startup, "by default" should be removed here.-->

Line 106:		Line 107:
	=== Privacy === <!--T:160-->		=== Privacy === <!--T:160-->
	</translate>		</translate>
	* '''<code>-Invisible</code>''' - <translate><!--T:98--> Force your online status to be invisible on login.</translate>		* '''<code>-Invisible</code>''' - <translate><!--T:98--> Force your online status to be invisible on login regardless of settings.</translate>
	* '''<code>-DisablePlatformInterfaces</code>''' - <translate><!--T:145--> Disables all platform interfaces. This includes things like Discord and Steam rich presence, but also includes platform interfaces such as the clipboard manager. This argument essentially stops Resonite from advertising itself to the host system completely.</translate>		* '''<code>-DisablePlatformInterfaces</code>''' - <translate><!--T:145--> Disables all platform interfaces. This includes things like Discord and Steam rich presence, but also includes platform interfaces such as the clipboard manager. This argument essentially stops Resonite from advertising itself to the host system completely.</translate>

Alpha Branches

Kaizo — Tue, 03 Nov 2026 01:30:32 GMT

Fix link to NeverSaveAnything cli flag

← Older revision		Revision as of 01:30, 3 November 2026
Line 20:		Line 20:
	* Alpha Branches should be used at your own risk		* Alpha Branches should be used at your own risk
	** While we aim to avoid backwards incompatible changes, Alpha Branches may have them		** While we aim to avoid backwards incompatible changes, Alpha Branches may have them
	** We recommend using [[NeverSaveAnything]], when on an Alpha Branch		** We recommend using [[Command_line_arguments#Testing/Debugging\|NeverSaveAnything]], when on an Alpha Branch
	* Ensure you read the update notes from the engineer, these should tell you what's changed and what they're looking for.		* Ensure you read the update notes from the engineer, these should tell you what's changed and what they're looking for.

Alpha Branches

ProbablePrime — Tue, 03 Nov 2026 00:45:42 GMT

← Older revision		Revision as of 00:45, 3 November 2026
(2 intermediate revisions by the same user not shown)
Line 12:		Line 12:
	Depending on their status, you may not see them within the Steam selector.		Depending on their status, you may not see them within the Steam selector.

	## Guidelines for using		== Guidelines for using ==
			{{Quote
	With great power comes great responsibility - Uncle Ben.		\|With great power comes great responsibility
			\| Uncle Ben
			}}

	* Alpha Branches should be used at your own risk		* Alpha Branches should be used at your own risk
Line 21:		Line 23:
	* Ensure you read the update notes from the engineer, these should tell you what's changed and what they're looking for.		* Ensure you read the update notes from the engineer, these should tell you what's changed and what they're looking for.

	## Switching to an Alpha Branch		== Switching to an Alpha Branch ==

	# In your steam Library, find Resonite and right click on it		# In your steam Library, find Resonite and right click on it

Alpha Branches

ProbablePrime — Tue, 03 Nov 2026 00:42:51 GMT

Created page with "Alpha Branches are a way to preview and test features with our community. == Branch List == Each engineer on the engineering team has their own alpha branch: * alpha-prime * alpha-froox * alpha-ryuvi * alpha-cyro * alpha-jae * alpha-gawdl3y Depending on their status, you may not see them within the Steam selector. ## Guidelines for using With great power comes great responsibility - Uncle Ben. * Alpha Branches should be used at your own risk ** While we aim to avoid..."

New page

Alpha Branches are a way to preview and test features with our community.

== Branch List ==
Each engineer on the engineering team has their own alpha branch:
* alpha-prime
* alpha-froox
* alpha-ryuvi
* alpha-cyro
* alpha-jae
* alpha-gawdl3y

Depending on their status, you may not see them within the Steam selector.

## Guidelines for using

With great power comes great responsibility - Uncle Ben.

* Alpha Branches should be used at your own risk
** While we aim to avoid backwards incompatible changes, Alpha Branches may have them
** We recommend using [[NeverSaveAnything]], when on an Alpha Branch
* Ensure you read the update notes from the engineer, these should tell you what's changed and what they're looking for.

## Switching to an Alpha Branch

# In your steam Library, find Resonite and right click on it
# Select Properties
# Select "Game Versions & Betas"
# In the list that appears select your alpha branch of choice

Steam will then update to that branch.

If you cannot see an Alpha Branch you may need to restart Steam.

User:Orange man from

Orange man from — Mon, 02 Nov 2026 16:47:03 GMT

User account Orange man from was created

List of Resonite communities

Delta — Mon, 02 Nov 2026 15:05:18 GMT

New link for fluxer, old one was expired/deleted

← Older revision		Revision as of 15:05, 2 November 2026
Line 18:		Line 18:
	[https://disconite.net/ Disconite] is a community-run [https://www.discourse.org/ Discourse] community forum for Resonite.		[https://disconite.net/ Disconite] is a community-run [https://www.discourse.org/ Discourse] community forum for Resonite.

	=== [https://fluxer.gg/~~ZeREeYlh~~ Fluxer] ===		=== [https://fluxer.gg/4gyp6eaD Fluxer] ===
	<!-- This place left empty for a description -->		<!-- This place left empty for a description -->

Main Page

Electra — Mon, 02 Nov 2026 07:22:14 GMT

<translate>T:89 Your first day</translate>: Quick note to use game instead of website to sign up

← Older revision		Revision as of 07:22, 2 November 2026
Line 25:		Line 25:

	* [[Special:MyLanguage/Installing Resonite \|<translate><!--T:121--> Install Resonite</translate>]]		* [[Special:MyLanguage/Installing Resonite \|<translate><!--T:121--> Install Resonite</translate>]]
	* [https://account.resonite.com <translate><!--T:4--> Make an account</translate>]		* [https://account.resonite.com <translate><!--T:4--> <s>Make an account</s></translate>] (Web signups are currently non-functional, Please create your account when you first start Resonite.)
	* [[Special:MyLanguage/Basic controls \|<translate><!--T:5--> Basic controls</translate>]]		* [[Special:MyLanguage/Basic controls \|<translate><!--T:5--> Basic controls</translate>]]
	* [[Special:MyLanguage/Avatar Importing Guide \|<translate><!--T:11--> Importing an avatar</translate>]]		* [[Special:MyLanguage/Avatar Importing Guide \|<translate><!--T:11--> Importing an avatar</translate>]]

Basic controls

Rellik — Mon, 02 Nov 2026 07:06:16 GMT

Added the current Steam Frame layout

← Older revision		Revision as of 07:06, 2 November 2026
Line 5:		Line 5:
	</translate>		</translate>

	<gallery mode="slideshow" showthumbnails>		<gallery mode="slideshow" showthumbnails="">
	File:~~Desktop_Controls~~.png\|Desktop Controls		File:Desktop Controls.png\|Desktop Controls
	File:Index Controls.png\|Valve Index Controllers		File:Index Controls.png\|Valve Index Controllers
	File:Vive Controls.png\|Vive Wand Controllers		File:Vive Controls.png\|Vive Wand Controllers
Line 15:		Line 15:
	File:Quest 2 Controls.png\|Meta Quest Controllers		File:Quest 2 Controls.png\|Meta Quest Controllers
	File:Cosmos Controls.png\|HTC Vive Cosmos Controllers		File:Cosmos Controls.png\|HTC Vive Cosmos Controllers
			File:Frame Controller (temp).png\|Valve Steam Frame (Interim)
	</gallery>		</gallery>

Line 58:		Line 59:
	* <translate><!--T:32--> '''Touchpad''' - Secondary/jump</translate>		* <translate><!--T:32--> '''Touchpad''' - Secondary/jump</translate>
	* <translate><!--T:33--> '''Thumbstick''' - Move/rotate</translate>		* <translate><!--T:33--> '''Thumbstick''' - Move/rotate</translate>
			== <translate><!--T:28--> Valve Steam Frame</translate> ==

			* <translate><!--T:29--> '''Menu button''' - Opens Dash</translate>
			* <translate><!--T:30--> '''Trigger''' - Primary (Also toggles laser)</translate>
			* <translate><!--T:31--> '''Grip''' - Grab</translate>
			* <translate><!--T:32--> X/Right D-pad - Context Menu</translate>
			* <translate><!--T:33--> '''Thumbstick''' - Move/rotate (Press to jump/secondary)</translate>

File:Frame Controller (temp).png

Rellik — Mon, 02 Nov 2026 06:45:08 GMT

Rellik uploaded File:Frame Controller (temp).png Temporary Frame Controller diagram until an official one is made.

New page

== Summary ==
Temporary Frame Controller diagram until an official one is made.

MEROOM

EpicEaston197 — Mon, 02 Nov 2026 02:18:01 GMT

added more info about the world

← Older revision		Revision as of 02:18, 2 November 2026
(One intermediate revision by the same user not shown)
Line 9:		Line 9:
	}}		}}

	The '''MEROOM''' is a world by [[epicEaston197]].		The '''MEROOM''' is a world by [[User:EpicEaston197\|epicEaston197]].

	The world can be accessed with:<code>resrec:///U-epicEaston197/R-b0792dba-0dc9-4ca0-8d43-c90a8a0d57da</code>		The world can be accessed with:<code>resrec:///U-epicEaston197/R-b0792dba-0dc9-4ca0-8d43-c90a8a0d57da</code>

			MEROOM Is a world mainly comprised of procedural meshes meaning that the majority of the world was completely made in game excluding things like furniture assets.

			It comprises of three rooms the main room, The lockable bedroom, and the blue bedroom,

			The world features a lot of customizability like lighting color and reflection probe toggles in every room including the color of lamps

			The world was also created without the use of generative AI as indicated on the wall mounted placard


	[[Category:Featured Worlds]]		[[Category:Featured Worlds]]
	[[Category:Community Worlds]]		[[Category:Community Worlds]]

Resonux

Baplar — Sun, 01 Nov 2026 23:33:09 GMT

Resonite Linux Meetups: Monday DST clarification

← Older revision		Revision as of 23:33, 1 November 2026
Line 6:		Line 6:

	These meetups happen twice a week:		These meetups happen twice a week:
	* Sunday at 14:00 UTC		* Sunday at 14:00 UTC (DST-insensitive)
	* Monday at 23:00 UTC		* Monday at 19:00 EST/EDT (follows USA DST, so 23:00 UTC in the summer and 00:00 UTC in the winter)

	The meetup announcements and the group pictures for every meetup since the beginning of the events are all on [https://discord.com/channels/1065291958328758352/1414280623107084373 the Resonite Linux Meetup thread] on [https://discord.gg/pqgzYEYdS the LVRA Discord server].		The meetup announcements and the group pictures for every meetup since the beginning of the events are all on [https://discord.com/channels/1065291958328758352/1414280623107084373 the Resonite Linux Meetup thread] on [https://discord.gg/pqgzYEYdS the LVRA Discord server].

Color Splat Materials

Electra — Sun, 01 Nov 2026 15:23:48 GMT

Quick note to in game tool

← Older revision		Revision as of 15:23, 1 November 2026
Line 1:		Line 1:
			{{Note\|This can be now done fully using the in game [[Channel packing#Tools]] tool.\|suggestion}}
	== Preface == <!--T:1-->		== Preface == <!--T:1-->

ProtoFlux:DelayObject

Shaun — Sun, 01 Nov 2026 10:45:13 GMT

redirect

New page

#REDIRECT [[ProtoFlux:DelayValue]]

RedX

Delta — Sat, 31 Oct 2026 14:26:46 GMT

Combine the website links at the top and make source github links more clear

← Older revision		Revision as of 14:26, 31 October 2026
Line 2:		Line 2:

	Two versions are currently available:		Two versions are currently available:
	* The [https://github.com/MrVoltz/redx ~~original version~~] ~~by MrVoltz~~		* The [https://redx.cloudns.org/ original version] by [[User:MrVoltz\|MrVoltz]] ([https://github.com/MrVoltz/redx GitHub])
	* The [https://~~github~~.~~com/AdamK2003~~/~~redx updated~~ fork] by [[User:AdamSkI2003\|AdamSkI2003]] with relevancy options, asset downloads and other improvements		* The [https://redx.adamski2003.lol/ fork version] by [[User:AdamSkI2003\|AdamSkI2003]] ([https://github.com/AdamK2003/redx GitHub]) with relevancy options, asset downloads and other improvements

	~~Available:~~		Both versions are also available in game with [[Facets]]

	* ~~on the web via the [https://redx.cloudns.org/ original version] or the [https://redx.adamski2003.lol/ fork]~~		* Original facet <code>resrec:///U-MrVoltz/R-f0e31077-3656-432e-84c4-8e5fa684f8dd</code>
	* in Resonite via the original facet <code>resrec:///U-MrVoltz/R-f0e31077-3656-432e-84c4-8e5fa684f8dd</code> ~~or the facet for the~~ fork <code>resrec:///U-AdamSkI2003/R-7AC884DF712F5F78E4D089C995C8B7171BC6F21CA975EE37F3D3900CA82F886E</code>		* [[User:AdamSkI2003\|AdamSkI2003]] fork <code>resrec:///U-AdamSkI2003/R-7AC884DF712F5F78E4D089C995C8B7171BC6F21CA975EE37F3D3900CA82F886E</code>

	Since not all public folders are intended to be searchable by everyone, a folder owner can opt out from RedX by creating a subfolder named <code>.noindex</code>.<ref>https://github.com/MrVoltz/redx/blob/fb8163c8d2871888d4db99017149b5aa982c4d90/data/ignorelist.js</ref>		Since not all public folders are intended to be searchable by everyone, a folder owner can opt out from RedX by creating a subfolder named <code>.noindex</code>.<ref>https://github.com/MrVoltz/redx/blob/fb8163c8d2871888d4db99017149b5aa982c4d90/data/ignorelist.js</ref>

	[[Category:Search engines]]		[[Category:Search engines]]

Culling

Hypevhs — Fri, 30 Oct 2026 16:12:38 GMT

Fix HeadlessUserCulling broken link

← Older revision		Revision as of 16:12, 30 October 2026
Line 49:		Line 49:
	* sctanf's culling system: <code>resrec:///U-sctanf/R-88d5a6ed-074f-497c-9496-ae9e6007e866</code>		* sctanf's culling system: <code>resrec:///U-sctanf/R-88d5a6ed-074f-497c-9496-ae9e6007e866</code>
	* [[CJ Avatar Culling]]: <code>resrec:///U-Crusher/R-800E5546BCDFE9CB8E385FDBE91A391FEBFADB15CB072EFC8864F011C58EC5AA</code>		* [[CJ Avatar Culling]]: <code>resrec:///U-Crusher/R-800E5546BCDFE9CB8E385FDBE91A391FEBFADB15CB072EFC8864F011C58EC5AA</code>
	* [https://~~github~~.~~com~~/~~Raidriar796~~/HeadlessUserCulling HeadlessUserCulling] (by Raidriar)		* [https://codeberg.org/Raidriar/HeadlessUserCulling HeadlessUserCulling] (by Raidriar)
	** No setup in-world, exists as part of the host client that gets spawned out on hosting a world.		** No setup in-world, exists as part of the host client that gets spawned out on hosting a world.
	** Highly recommended if culling is done on a headless host, as it provides a few extra niceties for multi-session hosting.		** Highly recommended if culling is done on a headless host, as it provides a few extra niceties for multi-session hosting.

Component:PositionAtUser

Electra — Fri, 30 Oct 2026 13:12:13 GMT

https://discord.com/channels/1040316820650991766/1154514026177507438/1564537364553146470 Still need to update the image. Think desc is right?

← Older revision		Revision as of 13:12, 30 October 2026
Line 20:		Line 20:
	\|PositionDrive\|{{RootFieldType\|FieldDrive`1\|[[Type:Float3\|Float3]]}}\|TypeAdv8=true\| Target Float3 to drive with the calculated position value		\|PositionDrive\|{{RootFieldType\|FieldDrive`1\|[[Type:Float3\|Float3]]}}\|TypeAdv8=true\| Target Float3 to drive with the calculated position value
	\|RotationDrive\|{{RootFieldType\|FieldDrive`1\|[[Type:FloatQ\|FloatQ]]}}\|TypeAdv9=true\| Target FloatQ to drive with the calculated rotation value.		\|RotationDrive\|{{RootFieldType\|FieldDrive`1\|[[Type:FloatQ\|FloatQ]]}}\|TypeAdv9=true\| Target FloatQ to drive with the calculated rotation value.
			\|RunAfterFinalPoseUpdate\|Bool\|Ensures the final position is only calculated after everything else, helping to prevent it 'lagging behind' the user.
	}}		}}
	== Behavior ==		== Behavior ==

ProtoFlux:Input

Mint Shock — Fri, 30 Oct 2026 07:04:03 GMT

How to get inputs

← Older revision		Revision as of 07:04, 30 October 2026
Line 5:		Line 5:

	The '''Input''' node holds a [[value type\|value]] or [[reference type\|reference]] type that can be output to any other input. Unlike [[:Category:ProtoFlux:Variables\|variables]], these can be directly modified to see instant changes without the need for a [[ProtoFlux:Write\|write node]].		The '''Input''' node holds a [[value type\|value]] or [[reference type\|reference]] type that can be output to any other input. Unlike [[:Category:ProtoFlux:Variables\|variables]], these can be directly modified to see instant changes without the need for a [[ProtoFlux:Write\|write node]].

			They can be created by dragging out a wire of any input on another Protoflux node (while holding a [[ProtoFlux Tool\|protoflux tool]]. Then press [[Basic controls\|Secondary]] to create the input.

	{{Note\|This is similar to [https://en.wikipedia.org/wiki/Hard_coding hard-coding] values in programming, or when you need [https://en.wikipedia.org/wiki/Magic_number_(programming) just a number] for debugging or another reason. It is instead recommended to use values from slots [[:Category:ProtoFlux:Variables:DynamicVariables\|dynamically]] or built in from a [[Slot]], [[Component]], or another [[ProtoFlux]] node.\|suggestion}}		{{Note\|This is similar to [https://en.wikipedia.org/wiki/Hard_coding hard-coding] values in programming, or when you need [https://en.wikipedia.org/wiki/Magic_number_(programming) just a number] for debugging or another reason. It is instead recommended to use values from slots [[:Category:ProtoFlux:Variables:DynamicVariables\|dynamically]] or built in from a [[Slot]], [[Component]], or another [[ProtoFlux]] node.\|suggestion}}

Face and Eye Tracking (Setup)

Rellik — Fri, 30 Oct 2026 06:10:18 GMT

Project Babble: spelling mistake :P

← Older revision		Revision as of 06:10, 30 October 2026
(One intermediate revision by the same user not shown)
Line 106:		Line 106:

	Make sure OSC, eye, and face tracking options are on in Steam Link Settings, and the OSC ports match between Resonite and your Frame.		Make sure OSC, eye, and face tracking options are on in Steam Link Settings, and the OSC ports match between Resonite and your Frame.

			===== Project Babble =====

			# Install [https://github.com/Project-Babble/Babble-Frame-Runtime Babble Frame Runtime] on the headset
			# Add -ForceBabble to Resonite launch options and enable Babble OSC as an output in the Babble Frame Runtime Settings
			# (Latest version of Babble Frame Runtime should not require this mod) <s>Install Resonite mod: [https://github.com/noblereign/ResoniteBaballoniaEyeExpressions/releases/tag/v2.0.0 ResoniteBaballoniaEyeExpressions]</s>

	===== FrameEyeOSC =====		===== FrameEyeOSC =====

	# Install [https://github.com/sasaken1102r/frameeyeosc github.com/sasaken1102r/frameeyeosc] on the headset		# Install [https://github.com/sasaken1102r/frameeyeosc github.com/sasaken1102r/frameeyeosc] on the headset
	# Install Resonite mod [https://github.com/noblereign/EyeTrackVRResonite ~~github.com/noblereign/~~EyeTrackVRResonite]		# Install Resonite mod: [https://github.com/noblereign/EyeTrackVRResonite EyeTrackVRResonite]
			# [https://github.com/badhaloninja/ResoniteModSettings ResoniteModSettings] may be needed for additional configuration of EyeTrackVRResonite.
	~~===== Project Babble =====~~

	# ~~Install~~ [https://github.com/~~Project-Babble~~/~~Babble-Frame-Runtime Babble Frame Runtime~~] ~~on the headset~~
	~~# Add -ForceBabble to Resonite launch options.~~
	~~# (Latest version~~ of ~~Babble Frame Runtime should not require this mod) Install Resonite mod [https://github~~.~~com/noblereign/ResoniteBaballoniaEyeExpressions/releases/tag/v2.0.0 github.com/noblereign/ResoniteBaballoniaEyeExpressions]~~

	<translate>		<translate>

ProtoFlux:ValueDelta

Shaun — Fri, 30 Oct 2026 05:32:35 GMT

redirect

New page

#REDIRECT [[ProtoFlux:Delta]]

ProtoFlux:Repeat01 Float

Shaun — Fri, 30 Oct 2026 04:38:36 GMT

redirect

New page

#REDIRECT [[ProtoFlux:Repeat01]]

LightPrint

.hecko — Thu, 29 Oct 2026 23:20:52 GMT

if slots are a bad measure then don't mention them :p

← Older revision		Revision as of 23:20, 29 October 2026
Line 9:		Line 9:
	=== Main features ===		=== Main features ===

	* Lightweight: At only ~~300 slots ([[Slot_count\|do note slot count is NOT a very good metric for performance]])~~ LightPrint is the smallest and most lightweight print with a large feature set.		* Lightweight: At only 268 ProtoFlux nodes, LightPrint is the smallest and most lightweight print with a large feature set.
	* Comments: ~~even though it only has 268 flux nodes in~~ its ~~entirety~~ LightPrint includes nearly the same comment features as [[Redprint]] and [[Moduprint]] including pointer comments and area comments, though notably missing the description field of area comments.		* Comments: Despite its smallness, LightPrint includes nearly the same comment features as [[Redprint]] and [[Moduprint]] including pointer comments and area comments, though notably missing the description field of area comments.
	* [[File:LitePrint with flux.webp\|thumb\|LightPrint with Protoflux Nodes from the [[Local Home\|local home world]]]]Multiselect: LightPrint has a very intuitive multi-select system where you click/use trigger and hold while sizing the area you want.		* [[File:LitePrint with flux.webp\|thumb\|LightPrint with Protoflux Nodes from the [[Local Home\|local home world]]]]Multiselect: LightPrint has a very intuitive multi-select system where you click/use trigger and hold while sizing the area you want.
	* Snapping: Another feature included in this slim package is a standard 2d node snapping system to align the nodes to the prints grid.		* Snapping: Another feature included in this slim package is a standard 2d node snapping system to align the nodes to the prints grid.

UnitySDK

Cowardlycamper — Thu, 29 Oct 2026 21:09:02 GMT

updated link

← Older revision		Revision as of 21:09, 29 October 2026
(2 intermediate revisions by the same user not shown)
Line 13:		Line 13:
	For install guide see: https://learn.unity.com/tutorial/install-the-unity-hub-and-editor		For install guide see: https://learn.unity.com/tutorial/install-the-unity-hub-and-editor

			==== Installing from the Unity Package Manager ====
			{{Template:Note\|If you are switching from the old unitypackage installation method, you '''''MUST''''' delete the old installation before installing using this method\|danger}}
			{{Note\|from testing it would seem this installation method is broken at the moment, The instructions are being left here but please skip forward to [[UnitySDK#Installing_from_the_unitypackage\|Installing from unitypackage]] for working installation instructions. If this notice is still here, this installation method is still not working.\|warning}}
			Installation of the Resonite Unity SDK is done through the Unity Package Manager through git URL. To do so, open the Unity Package Manager here:
			[[File:Unity Package Manager.png\|alt=The Unity Package Manager button under the Window toolbar tab.\|center\|thumb\|The Unity Package Manager button under the Window toolbar tab.]]
			Once the Unity Package Manager is open, click the plus icon and select Add package from git URL as seen here:
			[[File:Unity Package Manager Add from git URL.png\|alt=The Add package from git URL option.\|center\|thumb\|The Add package from git URL option.]]
			You will get a menu asking for a git URL, paste in <code><nowiki>https://github.com/Yellow-Dog-Man/Resonite.UnitySDK.git?path=/Packages/ResoniteSDK#upm</nowiki></code> and press enter.

			==== Installing from the unitypackage ====
	Installing the Resonite Unity SDK package is as simple as dropping the [https://github.com/Yellow-Dog-Man/Resonite.UnitySDK/releases ResoniteSDK.unitypackage] file into the Assets pane in your project and choosing to import all files from the package.		Installing the Resonite Unity SDK package is as simple as dropping the [https://github.com/Yellow-Dog-Man/Resonite.UnitySDK/releases ResoniteSDK.unitypackage] file into the Assets pane in your project and choosing to import all files from the package.

File:Unity Package Manager Add from git URL.png

Cowardlycamper — Thu, 29 Oct 2026 20:40:35 GMT

Cowardlycamper uploaded File:Unity Package Manager Add from git URL.png

New page

A screenshot showing which button to press to import from a git URL

File:Unity Package Manager.png

Cowardlycamper — Thu, 29 Oct 2026 20:36:37 GMT

Cowardlycamper uploaded File:Unity Package Manager.png

New page

Shows the unity package manager button in the windows tab of the unity editor of 2022.3.29f1

Face and Eye Tracking (Setup)

Rellik — Thu, 29 Oct 2026 19:19:08 GMT

Steam Frame: Added official support option via SteamLink. will need confirmation of what other steps may be needed, if any.

← Older revision		Revision as of 19:19, 29 October 2026
Line 100:		Line 100:

	=== Steam Frame ===		=== Steam Frame ===
	~~Native support is planned. Details~~ are ~~unknown.~~		There are three available options, features will vary:

	~~Currently there~~ are ~~two options~~, ~~only install one to avoid conflicts:~~		===== SteamLink =====
			Native support via SteamLink has been implemented as of build 2026.10.27.1311.

			Make sure OSC, eye, and face tracking options are on in Steam Link Settings, and the OSC ports match between Resonite and your Frame.

	===== FrameEyeOSC =====		===== FrameEyeOSC =====
Line 112:		Line 115:

	# Install [https://github.com/Project-Babble/Babble-Frame-Runtime Babble Frame Runtime] on the headset		# Install [https://github.com/Project-Babble/Babble-Frame-Runtime Babble Frame Runtime] on the headset
	# Install Resonite mod [https://github.com/noblereign/ResoniteBaballoniaEyeExpressions/releases/tag/v2.0.0 github.com/noblereign/ResoniteBaballoniaEyeExpressions]		# Add -ForceBabble to Resonite launch options.
			# (Latest version of Babble Frame Runtime should not require this mod) Install Resonite mod [https://github.com/noblereign/ResoniteBaballoniaEyeExpressions/releases/tag/v2.0.0 github.com/noblereign/ResoniteBaballoniaEyeExpressions]

	<translate>		<translate>

← Older revision		Revision as of 16:10, 4 November 2026
Line 16:		Line 16:
	\|Cloud\|クラウドユーザー情報、サーバーステータス		\|Cloud\|クラウドユーザー情報、サーバーステータス
	\|Common UI\|[[Special:MyLanguage/UIX\|UIX]]/タッチ可能なボタンイベント、UIドライバー		\|Common UI\|[[Special:MyLanguage/UIX\|UIX]]/タッチ可能なボタンイベント、UIドライバー
	\|Data\|~~<span lang="en" dir="ltr" class="mw-content-ltr">Dynamic Variables, item Metadata, value fields.</span>~~		\|Data\|動的変数（Dynamic Variables）、アイテムのメタデータ、値フィールド（ValueField）。
	\|Debug\|~~<span lang="en" dir="ltr" class="mw-content-ltr">Component Debugging</span>~~		\|Debug\|デバッグコンポーネント
	\|Generators\|~~<span lang="en" dir="ltr" class="mw-content-ltr">Procedural Generators.</span>~~		\|Generators\|プロシージャルジェネレーター
	\|Input\|~~<span lang="en" dir="ltr" class="mw-content-ltr">Controls for Desktop, VR inputs, haptic, inputs interactions.</span>~~		\|Input\|デスクトップ操作、VR入力、触覚フィードバック、および入力インタラクション
	\|Interaction\|~~<span lang="en" dir="ltr" class="mw-content-ltr">~~Grip Pose Reference.~~</span>~~		\|Interaction\|Grip Pose Reference.
	\|Localization\|~~<span lang="en" dir="ltr" class="mw-content-ltr">Translations.</span>~~		\|Localization\|翻訳
	\|Locomotion\|~~<span lang="en" dir="ltr" class="mw-content-ltr">User Locomotions, Locomotion modifiers, Character Controller interactions.</span>~~		\|Locomotion\|ユーザーの移動機能（Locomotion）、移動操作の調整パラメータ、キャラクターコントローラーとのインタラクション
	\|Media\|<span lang="en" dir="ltr" class="mw-content-ltr">Audio clip player variations, Media Drivers.</span>		\|Media\|<span lang="en" dir="ltr" class="mw-content-ltr">Audio clip player variations, Media Drivers.</span>
	\|Metadata\|<span lang="en" dir="ltr" class="mw-content-ltr">Metadata about the object.</span>		\|Metadata\|<span lang="en" dir="ltr" class="mw-content-ltr">Metadata about the object.</span>
Line 38:		Line 38:
	\|UIX\|ResoniteのUIシステムである[[Special:MyLanguage/UIX\|UIX]]用のコンポーネントです。		\|UIX\|ResoniteのUIシステムである[[Special:MyLanguage/UIX\|UIX]]用のコンポーネントです。
	\|Uncategorized\|<span lang="en" dir="ltr" class="mw-content-ltr">Unsorted Components that need sorting.</span>		\|Uncategorized\|<span lang="en" dir="ltr" class="mw-content-ltr">Unsorted Components that need sorting.</span>
	\|Users\|~~<span lang="en" dir="ltr" class="mw-content-ltr">Basic Avatar & User systems.</span>~~		\|Users\|基本的なアバターおよびユーザーシステム。
	\|Userspace\|<span lang="en" dir="ltr" class="mw-content-ltr">Virtual Keyboard inputs.</span>		\|Userspace\|<span lang="en" dir="ltr" class="mw-content-ltr">Virtual Keyboard inputs.</span>
	\|Utility\|<span lang="en" dir="ltr" class="mw-content-ltr">Value/Reference Multiplexer, Hyperlinks.</span>		\|Utility\|<span lang="en" dir="ltr" class="mw-content-ltr">Value/Reference Multiplexer, Hyperlinks.</span>

← Older revision		Revision as of 07:04, 30 October 2026
Line 5:		Line 5:

	The '''Input''' node holds a [[value type\|value]] or [[reference type\|reference]] type that can be output to any other input. Unlike [[:Category:ProtoFlux:Variables\|variables]], these can be directly modified to see instant changes without the need for a [[ProtoFlux:Write\|write node]].		The '''Input''' node holds a [[value type\|value]] or [[reference type\|reference]] type that can be output to any other input. Unlike [[:Category:ProtoFlux:Variables\|variables]], these can be directly modified to see instant changes without the need for a [[ProtoFlux:Write\|write node]].

			They can be created by dragging out a wire of any input on another Protoflux node (while holding a [[ProtoFlux Tool\|protoflux tool]]. Then press [[Basic controls\|Secondary]] to create the input.

	{{Note\|This is similar to [https://en.wikipedia.org/wiki/Hard_coding hard-coding] values in programming, or when you need [https://en.wikipedia.org/wiki/Magic_number_(programming) just a number] for debugging or another reason. It is instead recommended to use values from slots [[:Category:ProtoFlux:Variables:DynamicVariables\|dynamically]] or built in from a [[Slot]], [[Component]], or another [[ProtoFlux]] node.\|suggestion}}		{{Note\|This is similar to [https://en.wikipedia.org/wiki/Hard_coding hard-coding] values in programming, or when you need [https://en.wikipedia.org/wiki/Magic_number_(programming) just a number] for debugging or another reason. It is instead recommended to use values from slots [[:Category:ProtoFlux:Variables:DynamicVariables\|dynamically]] or built in from a [[Slot]], [[Component]], or another [[ProtoFlux]] node.\|suggestion}}

← Older revision		Revision as of 05:07, 5 November 2026
Line 27:		Line 27:
	\|}}		\|}}

	The '''Raycast One''' node performs a single raycast check when an impulse is received. The input parameters determine from where, in what direction, and how far the ray should be cast as well as determining which colliders are valid hits. When a raycast detects a valid collider, it returns data pertaining to that hit and fires from the OnHit continuation output. If there is no valid hit, whether there were no colliders hit or the ones hit were not valid targets, the OnMiss continuation output fires.		The '''Raycast One''' node performs a single raycast check when an impulse is received. The input parameters determine from where, in what direction, and how far the ray should be cast as well as determining which colliders are valid hits. These inputs are in the space of the Root input. When a raycast detects a valid collider, it returns data pertaining to that hit and fires from the OnHit continuation output. If there is no valid hit, whether there were no colliders hit or the ones hit were not valid targets, the OnMiss continuation output fires.

	The data output values are only valid for a given raycast hit for the duration of the impulse chain downstream of OnHit.		The data output values are only valid for a given raycast hit for the duration of the impulse chain downstream of OnHit.
Line 44:		Line 44:
	=== Origin ([[Type:float3\|float3]]) ===		=== Origin ([[Type:float3\|float3]]) ===

	The starting position from which the ray is cast. Default is [0;0;0].		The starting position from which the ray is cast. Default is [0;0;0]. This point is in the space of the Root input.

	=== Direction ([[Type:float3\|float3]]) ===		=== Direction ([[Type:float3\|float3]]) ===

	The direction in which the ray is cast. Default is [0;0;0] which results in no ray being cast. ~~(Use for example [0;0;1] for directly forward~~.)		The direction in which the ray is cast. Default is [0;0;0] which results in no ray being cast. This vector is in the space of the Root input, and doesn't have to be normalized.

	=== MaxDistance ([[Type:float\|float]]) ===		=== MaxDistance ([[Type:float\|float]]) ===

	The maximum distance the raycast should travel from its origin. Default is the maximum float value which is extremely high.		The maximum distance the raycast should travel from its origin. Default is the maximum float value which is extremely high. It is a multiplier of Direction, adding Direction scaled by MaxDistance with Origin returns the end point of the raycast in the Root input's space.

	=== HitTriggers ([[Type:bool\|bool]]) ===		=== HitTriggers ([[Type:bool\|bool]]) ===
Line 94:		Line 94:
	=== HitPoint ([[Type:float3\|float3]]) ===		=== HitPoint ([[Type:float3\|float3]]) ===

	The global position at which the ray hit the collider.		The global position at which the ray hit the collider in global coordinate space.

	=== HitNormal ([[Type:float3\|float3]]) ===		=== HitNormal ([[Type:float3\|float3]]) ===

	The facing normal direction of the hit collider at the hit point.		The facing normal direction of the hit collider at the hit point in global coordinate space.

	=== HitTriangleIndex ([[Type:int\|int]]) ===		=== HitTriangleIndex ([[Type:int\|int]]) ===

	The triangle index on the mesh corresponding to the hit collider. This value is 0 unless the HitCollider is a MeshCollider.		The triangle index on the mesh corresponding to the hit collider. This value is 0 unless the HitCollider is a [[Component:MeshCollider\|MeshCollider]].

	== Usage ==		== Usage ==
	There are a few ways in which the Raycast One node may not work as expected, particularly relating to directions and distances.		There are a few ways in which the Raycast One node may not work as expected, particularly relating to directions and distances.

	Firstly, the global scale of the input Root slot is taken into account when calculating a raycast's path. For example, assume that the Root slot input has global position [0;0;0] and global scale [0.1;0.1;0.1]; if the Origin input is [0;0;0], the raycast will start at global [0;0;0], however, if the Origin input is [0;1;0] the raycast will start at global [0;0.1;0] not global [0;1;0].		Firstly, the global scale of the input Root slot is taken into account when calculating a raycast's path and distance. For example, assume that the Root slot input has global position [0;0;0] and global scale [0.1;0.1;0.1]; if the Origin input is [0;0;0], the raycast will start at global [0;0;0], however, if the Origin input is [0;1;0] the raycast will start at global [0;0.1;0] not global [0;1;0].
	Similarly, the input Root slot's global scale affects the Direction vector and MaxDistance values too. With the same example input Root slot, a Direction of [0;0;1] and a MaxDistance of 1 result in a ray which travels only 0.1 units.		Similarly, the input Root slot's global scale affects the Direction vector and MaxDistance values too. With the same example input Root slot, a Direction of [0;0;1] and a MaxDistance of 1 result in a ray which travels only 0.1 units.

	Secondly, the magnitude of the Direction vector affects the distance that the ray travels and the reported HitDistance output value. Assuming no input Root slot, a Direction input of [0;0;1] and MaxDistance of 1 will produce a ray 1 unit long. However, a Direction input of [0;0;2] and MaxDistance of 1 will produce a ray 2 units long. Additionally, the reported HitDistance value will be halved in the second case.		Secondly, the magnitude of the Direction vector affects the distance that the ray travels and the reported HitDistance output value. Assuming no input Root slot, a Direction input of [0;0;1] and MaxDistance of 1 will produce a ray 1 unit long. However, a Direction input of [0;0;2] and MaxDistance of 1 will produce a ray 2 units long. Additionally, the reported HitDistance value will be halved in the second case.
	[[Category:ProtoFlux:Physics]]		[[Category:ProtoFlux:Physics]]

← Older revision		Revision as of 05:00, 5 November 2026
Line 21:		Line 21:
	\|}}		\|}}

	The '''Raycast All''' node performs a multi raycast check when an impulse is received and gives a [[Collection]] of hits. The input parameters determine from where, in what direction, and how far the ray should be cast as well as determining which colliders are valid hits. When a raycast ~~detects a~~ valid collider, ~~it returns data pertaining to that hit and fires from the~~ OnHit ~~continuation output~~. If there is no valid hit, whether there were no colliders hit or the ones hit were not valid targets, the OnMiss continuation output fires.		The '''Raycast All''' node performs a multi raycast check when an impulse is received and gives a [[Collection]] of hits. The input parameters determine from where, in what direction, and how far the ray should be cast as well as determining which colliders are valid hits. These parameters are in the space of the Root input, transforming it transforms how the raycast behaves. When the raycast hits at least one valid collider, OnHit is fired. If there is no valid hit, whether there were no colliders hit or the ones hit were not valid targets, the OnMiss continuation output fires.

	The data output is a [[Collections\|Collection]] that contains a list of every hit along it's trajectory. ~~The~~ result can be decoded~~(after something like~~ [[ProtoFlux:ForEach\|ForEach]]) using [[ProtoFlux:UnpackRaycastHit\|UnpackRaycastHit]].		The data output is a [[Collections\|Collection]] that contains a list of every hit along it's trajectory, in order from closest collider to furthest. Each result can be decoded in a [[ProtoFlux:ForEach\|ForEach]] loop using [[ProtoFlux:UnpackRaycastHit\|UnpackRaycastHit]].

	{{Note\|If you only care about the first hit, use [[ProtoFlux:RaycastOne\|Raycast One]] instead.\|suggestion}}		{{Note\|If you only care about the first hit, use [[ProtoFlux:RaycastOne\|Raycast One]] instead.\|suggestion}}
Line 35:		Line 35:
	=== Origin ([[Type:float3\|float3]]) ===		=== Origin ([[Type:float3\|float3]]) ===

	The starting position from which the ray is cast. Default is [0;0;0].		The starting position from which the ray is cast. Default is [0;0;0]. This position is in the space of the Root input.

	=== Direction ([[Type:float3\|float3]]) ===		=== Direction ([[Type:float3\|float3]]) ===

	The direction in which the ray is cast. Default is [0;0;0] which results in no ray being cast. ~~(Use for example [0;0;1] for directly forward~~.)		The direction in which the ray is cast. Default is [0;0;0] which results in no ray being cast. This vector is in the space of the Root input, and doesn't have to be normalized.

	=== MaxDistance ([[Type:float\|float]]) ===		=== MaxDistance ([[Type:float\|float]]) ===

	The maximum distance the raycast should travel from its origin. Default is the maximum float value which is extremely high.		The maximum distance the raycast should travel from its origin. Default is the maximum float value which is extremely high. It is a multiplier to Direction, adding Direction scaled by MaxDistance with Origin gives the end point of the raycast.

	=== HitTriggers ([[Type:bool\|bool]]) ===		=== HitTriggers ([[Type:bool\|bool]]) ===

	Determines whether colliders with the Trigger, StaticTrigger or StaticTriggerAuto ColliderType ~~value~~ are valid hit targets. Default is False.		Determines whether colliders with the Trigger, StaticTrigger or StaticTriggerAuto [[Type:ColliderType\|ColliderType]] values are valid hit targets. Default is False.

	=== DebugDuration ([[Type:float\|float]]) ===		=== DebugDuration ([[Type:float\|float]]) ===

	Determines the duration in seconds that a debug visual will be shown after each raycast. Default is -1 which disables the debug visual. When enabled, the visual shows a yellow line indicating the full path of the raycast along with the hit point (red spheres) and hit normal direction (blue arrows).		Determines the duration in seconds that a debug visual will be shown after each raycast. Default is -1, which disables the debug visual. When enabled, the visual shows a yellow line indicating the full path of the raycast along with the hit point (red spheres) and hit normal direction (blue arrows).

	=== Root ([[Slot]]) ===		=== Root ([[Slot]]) ===

	The slot in whose coordinate space the Origin, Direction and MaxDistance values should be evaluated. Default is the world root slot, i.e. the values are treated as being in the [[Coordinate_spaces#Global_vs._Local \| global coordinate space]].		The slot in whose coordinate space the Origin, Direction and MaxDistance values should be evaluated. Default is the world root slot, i.e. the values are treated as being in the[[Coordinate_spaces#Global_vs._Local \| global coordinate space]].

	== Outputs ==		== Outputs ==
Line 69:		Line 69:
	=== Hits ([[Type:IReadOnlyList\|IReadOnlyList<RaycastHit>]]) ===		=== Hits ([[Type:IReadOnlyList\|IReadOnlyList<RaycastHit>]]) ===

	A List of every collider that the ray has hit.		A List of every collider that the ray has hit, in order from closest to furthest. The ordering is by the order of hit faces, not by collider origin.

	== Usage ==		== Usage ==
	[[Category:ProtoFlux:Physics]]		[[Category:ProtoFlux:Physics]]