Difference between revisions of "Tips & Tricks"
(Marked this version for translation) |
|||
| Line 2: | Line 2: | ||
<translate> | <translate> | ||
| + | <!--T:1--> | ||
'''Open Inspector for Referenced Component''' | '''Open Inspector for Referenced Component''' | ||
| + | <!--T:2--> | ||
When the inspector is displayed click on the small vertical arrow symbol on the left of a reference. | When the inspector is displayed click on the small vertical arrow symbol on the left of a reference. | ||
This will open up an inspector for the referenced component. | This will open up an inspector for the referenced component. | ||
The same action can also be triggered by grabbing a reference (shown in blue) and pressing the secondary action on the controller. | The same action can also be triggered by grabbing a reference (shown in blue) and pressing the secondary action on the controller. | ||
| + | <!--T:3--> | ||
Example: Open the inspector for a referenced material. | Example: Open the inspector for a referenced material. | ||
| + | <!--T:4--> | ||
'''Performance Profiling your World''' | '''Performance Profiling your World''' | ||
| + | <!--T:5--> | ||
Q: Any more tips on performance profiling techniques? I'm seeing Hex glitch every 5 seconds currently so hoping I can whittle that down more, or if I need to just remove some of the more intensive animations? | Q: Any more tips on performance profiling techniques? I'm seeing Hex glitch every 5 seconds currently so hoping I can whittle that down more, or if I need to just remove some of the more intensive animations? | ||
| + | <!--T:6--> | ||
A: There is a FPS counter visible when the dash menu is open. There is also a component that shows the network traffic. | A: There is a FPS counter visible when the dash menu is open. There is also a component that shows the network traffic. | ||
However next to this there aren't any tools in Neos for that right now. Your best bet is to have a checklist: | However next to this there aren't any tools in Neos for that right now. Your best bet is to have a checklist: | ||
| + | <!--T:7--> | ||
1. How many separate objects are in your scene? Is it excessive? (2,000+?) | 1. How many separate objects are in your scene? Is it excessive? (2,000+?) | ||
| + | <!--T:8--> | ||
2. How dense is geometry? (GPU handles a lot, but it can impact FPS) | 2. How dense is geometry? (GPU handles a lot, but it can impact FPS) | ||
| + | <!--T:9--> | ||
3. Check # of point lights, shadows are expensive to render, lights with a large range are expensive to render | 3. Check # of point lights, shadows are expensive to render, lights with a large range are expensive to render | ||
| + | <!--T:10--> | ||
4. Reflections? | 4. Reflections? | ||
| + | <!--T:11--> | ||
5. High overhead materials? (IE: displacement on a heavy mesh) | 5. High overhead materials? (IE: displacement on a heavy mesh) | ||
| + | <!--T:12--> | ||
6. Do you use procedural meshes? You can bake them into static meshes to increase performance. | 6. Do you use procedural meshes? You can bake them into static meshes to increase performance. | ||
| + | <!--T:13--> | ||
7. Reusing the same a mesh and material increases performance as this enables GPU instancing. | 7. Reusing the same a mesh and material increases performance as this enables GPU instancing. | ||
</translate> | </translate> | ||
Revision as of 13:47, 23 December 2019
Open Inspector for Referenced Component
When the inspector is displayed click on the small vertical arrow symbol on the left of a reference. This will open up an inspector for the referenced component. The same action can also be triggered by grabbing a reference (shown in blue) and pressing the secondary action on the controller.
Example: Open the inspector for a referenced material.
Performance Profiling your World
Q: Any more tips on performance profiling techniques? I'm seeing Hex glitch every 5 seconds currently so hoping I can whittle that down more, or if I need to just remove some of the more intensive animations?
A: There is a FPS counter visible when the dash menu is open. There is also a component that shows the network traffic. However next to this there aren't any tools in Neos for that right now. Your best bet is to have a checklist:
1. How many separate objects are in your scene? Is it excessive? (2,000+?)
2. How dense is geometry? (GPU handles a lot, but it can impact FPS)
3. Check # of point lights, shadows are expensive to render, lights with a large range are expensive to render
4. Reflections?
5. High overhead materials? (IE: displacement on a heavy mesh)
6. Do you use procedural meshes? You can bake them into static meshes to increase performance.
7. Reusing the same a mesh and material increases performance as this enables GPU instancing.