Unity-jump-proj

This commit is contained in:
2024-09-09 11:07:16 +03:00
parent 2c29906bbf
commit fd96a5627d
13707 changed files with 866380 additions and 0 deletions

View File

@ -0,0 +1,5 @@
---
title: ff-add-node
---
Right-click anywhere in the [Graph Editor](../../vs-interface-overview.md#the-graph-editor) to open the fuzzy finder. Then, select your node in the fuzzy finder to add it to your graph.

View File

@ -0,0 +1,5 @@
---
title: open-graph-w-node
---
[Open a Script Graph](../../vs-open-graph-edit.md) where you've already added your node.

View File

@ -0,0 +1,5 @@
---
title: vs-tasks-note-end
---
The examples below are based on the previous examples for a Custom C# node. For more information, see [Create a new simple Custom C# node](../../vs-create-custom-node-empty.md).

View File

@ -0,0 +1,5 @@
---
title: right-click-project
---
Right-click a folder in the Project window's folder list or anywhere in the Project window's preview pane.

View File

@ -0,0 +1,5 @@
---
title: tasks-note-end
---
The examples below are based on the previous example to create a Custom Scripting Event node. For more information, see [Create a Custom Scripting Event node](../../vs-create-own-custom-event-node.md)

View File

@ -0,0 +1,5 @@
---
title: nodes-desc-end
---
It triggers the next node connected to it after the action occurs in the application. It doesn't send or receive any other data.

View File

@ -0,0 +1,9 @@
---
title: nodes-input-output-trigger
---
<tr>
<td><strong>Trigger</strong></td>
<td>Output Trigger</td>
<td>The control output port. Make a connection to specify what Visual Scripting should do after the configured Input event occurs in your application.</td>
</tr>

View File

@ -0,0 +1,5 @@
---
title: nodes-note-manual
---
node is an [Input Manager](https://docs.unity3d.com/Manual/class-InputManager.html) node. For more information about how to use the Input Manager with Visual Scripting, see [Capture user input in an application](../../vs-capture-player-input.md).

View File

@ -0,0 +1,32 @@
---
title: nodes-input-action-change
---
<table>
<thead>
<tr>
<th><strong>Name</strong></th>
<th><strong>Type</strong></th>
<th colspan="2"><strong>Description</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td rowspan="4"><strong>Input Action Change Type</strong></td>
<td rowspan="4">Input Action Change Option</td>
<td colspan="2">Set an Input Action Change Type to choose the interaction type that triggers the node.</td>
</tr>
<tr>
<td><strong>On Pressed</strong></td>
<td>The node triggers when a user presses the button from the selected <strong>Input Action</strong> input asset.</td>
</tr>
<tr>
<td><strong>On Hold</strong></td>
<td>The node triggers when a user holds the button from the selected <strong>Input Action</strong> input asset.</td>
</tr>
<tr>
<td><strong>On Released</strong></td>
<td>The node triggers when a user releases the button from the selected <strong>Input Action</strong> input asset.</td>
</tr>
</tbody>
</table>

View File

@ -0,0 +1,8 @@
---
title: nodes-input-system-output-trigger-port
---
<tr>
<td><strong>Trigger</strong></td>
<td>Output Trigger</td>
<td>The control output port. Make a connection to specify what Visual Scripting does after the configured Player Input event, such as a button press, occurs in the application.</td>
</tr>

View File

@ -0,0 +1,8 @@
---
title: nodes-input-system-ports
---
| **Name** | **Type** | **Description** |
| :------ | :------- | :------------- |
| **Target** | Player Input | The Player Input component that Visual Scripting uses to display a list of input actions. The default is **This**, which is the Player Input component attached to the GameObject where Visual Scripting runs the Script Graph. You can also connect a node that outputs a Player Input component.|
| **Input Action** | Input Action | An input action. Use the dropdown to select an input action from the Player Input component specified in **Player Input**, or connect a node that outputs an input action.|

View File

@ -0,0 +1,5 @@
---
title: nodes-note-package
---
is an [Input System package](https://docs.unity3d.com/Packages/com.unity.inputsystem@latest) node. For more information about how to use the Input System package in Visual Scripting, see [Capture user input in an application](../../vs-capture-player-input.md).

View File

@ -0,0 +1,5 @@
---
title: nodes-additional-settings
---
node has additional settings. Access these settings from the [Graph Inspector](../vs-interface-overview.md#the-graph-inspector):

View File

@ -0,0 +1,5 @@
---
title: nodes-controls
---
node has the following controls:

View File

@ -0,0 +1,9 @@
---
title: nodes-coroutine
---
<tr>
<td><strong>Coroutine</strong></td>
<td>Toggle</td>
<td>Enable <strong>Coroutine</strong> if you want Visual Scripting to run this node and any of its connected nodes as a coroutine. Coroutine nodes don't execute all their code in a single frame, so they can spread an effect over several frames. Coroutines can also help optimize your code. For more information on coroutines, see the Unity User Manual section on <a href="https://docs.unity3d.com/Manual/Coroutines.html">Coroutines</a>.</td>
</tr>

View File

@ -0,0 +1,5 @@
---
title: nodes-inputs
---
node has the following input ports:

View File

@ -0,0 +1,5 @@
---
title: nodes-outputs
---
node has the following output ports:

View File

@ -0,0 +1,4 @@
---
title: nodes-related
---
The following nodes are related or similar to the

View File

@ -0,0 +1,5 @@
---
title: nodes-single-control
---
node has one control:

View File

@ -0,0 +1,5 @@
---
title: nodes-single-input
---
node has one input port:

View File

@ -0,0 +1,5 @@
---
title: nodes-single-output
---
node has one output port:

View File

@ -0,0 +1,6 @@
---
title: blackboard-tip
---
> [!TIP]
> If the Blackboard isn't visible in the Graph window, select **Blackboard** (![The Blackboard icon](../images/vs-blackboard-icon.png)) from the toolbar.

View File

@ -0,0 +1,5 @@
---
title: create-c-script
---
Go to **Create** &gt; **C# Script**.

View File

@ -0,0 +1,6 @@
---
title: graph-inspector-tip-html
---
<div class="TIP"><h5>TIP</h5><p>If the Graph Inspector isn't visible in the Graph window, select <strong>Graph Inspector</strong> (<img src="../images/vs-graph-inspector-icon.png" alt="The Graph Inspector icon. A circle with a lower-case letter 'i' inside.">) from the toolbar.</p></div>

View File

@ -0,0 +1,6 @@
---
title: graph-inspector-tip
---
> [!TIP]
> If the Graph Inspector isn't visible in the Graph window, select **Graph Inspector** (![The Graph Inspector icon](../images/vs-graph-inspector-icon.png)) from the toolbar.

View File

@ -0,0 +1,8 @@
---
title: open-existing-external-code
---
Double-click the C# file. Unity opens the file in the program you specified in your preferences, under **External Script Editor**.
> [!NOTE]
> For more information on script editors in Unity, see the [Integrated development environment (IDE) support](https://docs.unity3d.com/Manual/ScriptingToolsIDEs.html) in the Unity User Manual.

View File

@ -0,0 +1,5 @@
---
title: open-fuzzy-finder
---
Right-click anywhere in the Graph Editor to open the fuzzy finder.

View File

@ -0,0 +1,5 @@
---
title: open-graph-inspector
---
Select **Graph Inspector** (![The Graph Inspector icon](../images/vs-graph-inspector-icon.png)) from the toolbar.

View File

@ -0,0 +1,5 @@
---
title: open-graph
---
[Open a graph file](../vs-open-graph-edit.md) in the Graph window.

View File

@ -0,0 +1,5 @@
---
title: open-hierarchy-window
---
Go to **Window** &gt; **General** &gt; **Hierarchy**, or press Ctrl+4 (macOS: Cmd+4) to open the [Hierarchy window](https://docs.unity3d.com/Manual/Hierarchy.html).

View File

@ -0,0 +1,5 @@
---
title: open-inspector-window
---
With the GameObject selected in the Hierarchy window, go to **Window** &gt; **General** &gt; **Inspector**, or press Ctrl+3 (macOS: Cmd+3) to open the [Inspector window](https://docs.unity3d.com/Documentation/Manual/UsingTheInspector.html).

View File

@ -0,0 +1,8 @@
---
title: open-new-external-code
---
Double-click the new C# file. Unity opens the file in the program you specified in your preferences, under **External Script Editor**.
> [!NOTE]
> For more information on script editors in Unity, see the [Integrated development environment (IDE) support](https://docs.unity3d.com/Manual/ScriptingToolsIDEs.html) in the Unity User Manual.

View File

@ -0,0 +1,5 @@
---
title: open-project-settings
---
Go to **Edit** &gt; **Project Settings**.

View File

@ -0,0 +1,5 @@
---
title: open-project-window
---
Go to **Window** &gt; **General** &gt; **Project**, or press Ctrl+5 (macOS: Cmd+5) to open the [Project window](https://docs.unity3d.com/Manual/ProjectView.html).

View File

@ -0,0 +1,5 @@
---
title: open-state-menu
---
With a State Graph [open in the Graph window](../vs-open-graph-edit.md), right-click on an empty space in the Graph Editor to open the context menu.

View File

@ -0,0 +1,5 @@
---
title: regen-node-library
---
Follow the process described in [Configure project settings](../vs-configuration.md#Regen) to regenerate your Node Library.

View File

@ -0,0 +1,5 @@
---
title: return-unity
---
Return to the Unity Editor.

View File

@ -0,0 +1,5 @@
---
title: save-script
---
Save your script file.

View File

@ -0,0 +1,5 @@
---
title: visual-scripting-window
---
Go to **Window** &gt; **Visual Scripting** &gt; **Visual Scripting Graph**.

View File

@ -0,0 +1,4 @@
---
title: with-graph-open-ff
---
With a Script Graph [open in the Graph window](../vs-open-graph-edit.md), right-click on an empty space in the Graph Editor to open the fuzzy finder.