Merge branch 'main' into patch-1

Author: IgnisRBX

content/en-us/engine.md

@@ -1,6 +1,7 @@
 ---
 title: Mouse and keyboard input
 description: Explains Roblox support for computer mice and keyboards.
+machineTranslated: true
 ---
 
 A large percentage of Roblox sessions are played on devices with a mouse and keyboard, so it's important to properly support these inputs when designing an experience for a wide audience. Once you're comfortable with mouse and keyboard inputs, make your experience compatible across multiple platforms by setting up [mobile](../input/mobile.md) and [gamepad](./gamepad.md) inputs.
@@ -102,7 +103,7 @@ You can customize the appearance and behavior of a user's mouse icon within your
 
 You can change the user's mouse icon in a `Class.LocalScript` by setting the `Class.UserInputService.MouseIcon|MouseIcon` property in `Class.UserInputService` to a custom Roblox asset ID. For example, the following `Class.LocalScript` changes the user's default mouse icon to a circle with a blue dot in the middle:
 
-```lua highlight='3'
+```lua highlight="3"
 local UserInputService = game:GetService("UserInputService")
 
 UserInputService.MouseIcon = "rbxassetid://3400146391"
@@ -112,7 +113,7 @@ UserInputService.MouseIcon = "rbxassetid://3400146391"
 
 You can hide the user's mouse icon by setting the `Class.UserInputService.MouseIconEnabled` to `false` in a `Class.LocalScript`. For example, the following code switches the mouse icon from visible to invisible and back every two seconds:
 
-```lua highlight='5,7'
+```lua highlight="5,7"
 local UserInputService = game:GetService("UserInputService")
 
 while true do
@@ -129,7 +130,7 @@ You can lock the mouse icon's position to the screen using `Class.UserInputServi
 
 If a user's mouse icon is locked in a position, `Class.UserInputService.InputChanged` still fires when the user moves the mouse, passing in the distance the mouse has moved. For example, the following code sample locks the user's mouse icon after one second, then Studio prints the mouse delta whenever the user moves their mouse:
 
-```lua highlight='5'
+```lua highlight="5"
 local UserInputService = game:GetService("UserInputService")
 
 task.wait(5)

content/en-us/input/mouse-and-keyboard.md

@@ -1,6 +1,7 @@
 ---
 title: Solid modeling
 description: Solid modeling is the process of joining parts together to form complex shapes.
+machineTranslated: true
 ---
 
 **Solid modeling** is the process of joining [parts](../parts/index.md)
@@ -173,7 +174,7 @@ When performing a `Class.BasePart:UnionAsync()|UnionAsync()`, `Class.BasePart:In
 
 To demonstrate `Class.BasePart:UnionAsync()|UnionAsync()`, the following `Class.Script` uses the **Part1** `Class.BasePart` from the workspace, unions it together with the **Part2**, **Part3**, and **Part4** `Class.BasePart|BaseParts`, then parents the resulting `Class.UnionOperation` to the workspace at the original position of **Part1**.
 
-```lua highlight='6'
+```lua highlight="6"
 local Workspace = game:GetService("Workspace")
 
 local mainPart = Workspace.Part1
@@ -201,7 +202,7 @@ end
 
 To demonstrate `Class.BasePart:IntersectAsync()|IntersectAsync()`, the following `Class.Script` uses the **Part1** `Class.BasePart` from the workspace, intersects it with the **Part2** and **Part3** `Class.BasePart|BaseParts`, then parents the resulting `Class.IntersectOperation` to the workspace at the original position of **Part1**.
 
-```lua highlight='6'
+```lua highlight="6"
 local Workspace = game:GetService("Workspace")
 
 local mainPart = Workspace.Part1
@@ -229,7 +230,7 @@ end
 
 To demonstrate `Class.BasePart:SubtractAsync()|SubtractAsync()`, the following `Class.Script` uses the **Part1** `Class.BasePart` from the workspace, negates the **Part2**, **Part3**, and **Part4** `Class.BasePart|BaseParts` from it, then parents the resulting `Class.UnionOperation` to the workspace at the original position of **Part1**.
 
-```lua highlight='6'
+```lua highlight="6"
 local Workspace = game:GetService("Workspace")
 
 local mainPart = Workspace.Part1

content/en-us/parts/solid-modeling.md

@@ -9,9 +9,11 @@ Designing for performance means following a handful of best practices **as you b
 
 Lower-end devices, particularly mobile devices, have severe memory limitations and are succeptible to crashes due to out of memory (OOM) errors:
 
-- If you want to support lower-end devices, choose a baseline set of devices with certain performance characteristics, test your experience on them throughout the development process, and pay close attention to frame rate and memory usage. As you find problem areas in your experience, use those areas to identify the limits of your devices.
+- If you want to support lower-end devices, choose at least one "baseline" device, test your experience on it throughout the development process, and pay close attention to frame rate and memory usage. As you find problem areas in your experience, use those areas to identify the limits of your device.
 
-  For example, you might test an experience with the **Render** (<kbd>Shift</kbd><kbd>F2</kbd>) and **Summary** (<kbd>Shift</kbd><kbd>F2</kbd>) debug stats enabled. If the frame rate starts to drop in a particularly cluttered area, you could examine the **Draw (scene)** numbers and determine that you need to stay below 600 draw calls and 650,000 triangles. Or you could examine the **Developer Console** (<kbd>F9</kbd>) and note that memory usage is a bit high unless you enable [streaming](../workspace/streaming.md). Having a clear understanding of device limits can help you stay under them as you continue to build your experience.
+  For example, you might test an experience with the **Render** (<kbd>Shift</kbd><kbd>F2</kbd>) and **Summary** (<kbd>Shift</kbd><kbd>F2</kbd>) debug stats enabled. If the frame rate starts to drop in a particularly cluttered area, you could examine the **Draw (scene)** numbers and determine that you need to stay below 1,000 draw calls and 1,000,000 triangles for the experience to run well on your baseline device.
+
+  Or you could examine the **Developer Console** (<kbd>F9</kbd>) and note that memory usage is a bit high unless you enable [streaming](../workspace/streaming.md). Having a clear understanding of device limits can help you stay under them as you continue to build your experience.
 
   ![A Roblox experience with three overlays active.](../assets/optimization/perf-hud.png)
 
@@ -23,8 +25,6 @@ Roblox does not have access to all of a device's memory. Some amount is required
 
 More generally, testing on a variety of devices can help you check that the experience matches your visual and performance expectations at different graphics quality levels. For a much more detailed example of how you might think about optimizing your experience for low-end mobile devices, see [Real World Building and Scripting Optimization](https://devforum.roblox.com/t/real-world-building-and-scripting-optimization-for-roblox/3127146).
 
-<a target="_blank" href="https://devforum.roblox.com/t/real-world-building-and-scripting-optimization-for-roblox/3127146"><img src="../assets/optimization/chicken-rocket.jpg" width="400" alt="Header image for Real World Building and Scripting Optimization." /></a>
-
 ## Streaming and teleportation
 
 - [Instance streaming](../workspace/streaming.md) lets Roblox dynamically load and unload 3D content and is a great option for most experiences, especially larger ones. Streaming improves join times, reduces memory footprint, and increases frame rates. For more information, see [Improving performance](improve.md#instance-streaming).
@@ -37,11 +37,11 @@ More generally, testing on a variety of devices can help you check that the expe
 
 - As you create assets, convert them into [packages](../projects/assets/packages.md). Making packages part of your workflow helps avoid the common issue of duplicate assets with different IDs, which can hurt performance.
 
-- When you add meshes and textures, use and reuse them rather than importing duplicate copies. By resizing, rotating, and overlapping, you can create rich, varied environments that require very few [draw calls](improve.md#draw-calls). For more information, see [Remove duplicate textures](../tutorials/environmental-art/optimize-your-experience.md#remove-duplicate-textures).
+- When you add meshes and textures, use and reuse them rather than importing duplicate copies. By resizing, rotating, and overlapping, you can create rich, varied environments that require very few [draw calls](improve.md#draw-calls). For more information, see [Remove duplicate textures](../tutorials/curriculums/environmental-art/optimize-your-experience.md#remove-duplicate-textures).
 
 ## Transparency
 
-- Avoid transparency values other than 0 (visible) and 1 (invisible). When you use partial transparency, be especially careful to avoid [high transparency overdraw](../tutorials/environmental-art/optimize-your-experience.md#delete-layered-transparencies).
+- Avoid transparency values other than 0 (visible) and 1 (invisible). When you use partial transparency, be especially careful to avoid [high transparency overdraw](../tutorials/curriculums/environmental-art/optimize-your-experience.md#delete-layered-transparencies).
 
 ## Scripting
 

content/en-us/performance-optimization/design.md

@@ -567,8 +567,9 @@ events:
       Fires every frame, after the physics simulation has completed.
     description: |
       The `PostSimulation` event fires every frame, after the physics simulation
-      has completed. The `deltaTimeSim` argument indicates the time that has
-      elapsed since the previous frame.
+      has completed. The `deltaTimeSim` argument indicates the time that the
+      current frame has stepped the physics simulation, not accounting for
+      physics throttling.
 
       This event is useful for making final adjustments to the outcome of the
       simulation. Following this phase, the engine triggers the
@@ -579,7 +580,8 @@ events:
         type: double
         default:
         summary: |
-          The time (in seconds) that has elapsed since the previous frame.
+          The time (in seconds) that the current frame has stepped the physics
+          simulation, not accounting for physics throttling.
     tags: []
     deprecation_message: ''
     security: None
@@ -592,7 +594,7 @@ events:
     description: |
       The `PreAnimation` event fires every frame, prior to the physics
       simulation but after rendering. The `deltaTimeSim` argument indicates the
-      time that has elapsed since the previous frame.
+      time that the current frame has stepped animations.
 
       This event is useful for modifying animation objects, such as adjusting
       their speed or priority. Once the `PreAnimation` event is complete, the
@@ -607,7 +609,7 @@ events:
         type: double
         default:
         summary: |
-          The time (in seconds) that has elapsed since the previous frame.
+          The time (in seconds) that the current frame has stepped animations.
     tags: []
     deprecation_message: ''
     security: None
@@ -656,7 +658,8 @@ events:
       The `PreSimulation` event (replacement for
       `Class.RunService.Stepped|Stepped`) fires every frame, prior to the
       physics simulation. The `deltaTimeSim` argument indicates the time that
-      has elapsed since the previous frame.
+      the current frame will step the physics simulation, not accounting for
+      physics throttling.
 
       This event is useful for adjusting properties like velocity or forces just
       before they're applied as part of the simulation. The simulation then
@@ -669,7 +672,8 @@ events:
         type: double
         default:
         summary: |
-          The time (in seconds) that has elapsed since the previous frame.
+          The time (in seconds) that the current frame will step the physics
+          simulation, not accounting for physics throttling.
     tags: []
     deprecation_message: ''
     security: None
@@ -679,7 +683,13 @@ events:
   - name: RunService.RenderStepped
     summary: |
       Fires every frame, prior to the frame being rendered.
-    description: ''
+    description: |
+      Fires every frame, prior to the frame being rendered.
+
+      ##### Migration Note
+
+      This event has been superseded by `Class.RunService.PreRender|PreRender`
+      which should be used for new work.
     code_samples: []
     parameters:
       - name: deltaTime
@@ -688,17 +698,21 @@ events:
         summary: |
           The time (in seconds) that has elapsed since the previous frame.
     tags: []
-    deprecation_message: |
-      This event has been superseded by `Class.RunService.PreRender|PreRender`
-      which should be used for new work.
+    deprecation_message: ''
     security: None
     thread_safety: Unsafe
     capabilities: []
     writeCapabilities: []
   - name: RunService.Stepped
     summary: |
       Fires every frame, prior to the physics simulation.
-    description: ''
+    description: |
+      Fires every frame, prior to the physics simulation.
+
+      ##### Migration Note
+      
+      This event has been superseded by `Class.RunService.PreSimulation|PreSimulation`
+      which should be used for new work.
     code_samples: []
     parameters:
       - name: time
@@ -713,10 +727,7 @@ events:
         summary: |
           The time (in seconds) that has elapsed since the previous frame.
     tags: []
-    deprecation_message: |
-      This event has been superseded by
-      `Class.RunService.PreSimulation|PreSimulation` which should be used for
-      new work.
+    deprecation_message: ''
     security: None
     thread_safety: Unsafe
     capabilities: []