I'd like to start with the view debugger.

我想先讲视图排障工具。

Like, I don't remember every single command in a debugger.

就像我不记得排错程序中的每一个命令。

We can only see it in the entity debugger.

我们只能实体调试中看它。

Let me go ahead now and get out of the debugger.

我继续，离开调试。

And we'll see one other feature of the debugger today.

今天我们将看调试的另一个特性。

The point is the debugger led you to this point.

关键是调试带了这一点。

And that's why the debugger has jumped to that line.

这就是调试跳这一行的原因。

How do I fix the logic now thanks to the debugger having led me down this road?

由于调试引导我走上了这条路，我如何修复逻辑？

There's a different debugger for every operating system but they're not easy to learn unless you start, you know, just doing it yourself and training yourself and practicing.

每个操作系统都有不同的排错程序 但是它们不容易学，除非开始，知道，自己动手，训练自己并练习。

The view debugger will now also include details from SpriteKit scenes, and the view debugger is a perfect way to expand and rotate your scenes, scope ranges, even look at clipped regions.

视图排障工具还会包括 SpriteKit 场景的细节，视图排障工具是扩展并反转的场景范围，甚至查看裁剪区域的完美方式。