今天，我们宣布Unity 4.6.2的公开发布， 现在可以下载 。 这是使用我们新的IL2CPP技术的首个公开发布的iOS 64位支持版本 。 (Today we announce the public release of Unity 4.6.2, available for download as of right now. It is the first public release with iOS 64-bit support, using our new IL2CPP technology.)

IL2CPP is an innovative scripting technology developed in-house by Unity. It delivers greatly improved performance for all scripting inside your projects, and is compatible with the current Mono-AOT solution used on iOS builds.

IL2CPP是Unity内部开发的创新脚本技术。 它为您项目中的所有脚本提供了大大提高的性能，并且与iOS版本上使用的当前Mono-AOT解决方案兼容。

IL2CPP enables us to rapidly port our scripting solution to new platforms (like our WebGL support) and architectures, of which ARM64 (the architecture that underpins 64-bit on iOS devices) is one. With Unity 4.6.2 you’ll thus be able to make a Universal build that works on both 32-bit and 64-bit iOS devices.

IL2CPP使我们能够快速将脚本解决方案移植到新平台(例如WebGL支持)和体系结构，其中ARM64(在iOS设备上支持64位的体系结构)就是其中之一。 借助Unity 4.6.2，您将能够制作一个在32位和64位iOS设备上均可使用的通用版本。

令人印象深刻的性能改进 (Impressive performance improvements)

During our alpha and beta cycles we’ve benefited from lots of really useful feedback from the Unity Community. And, users testing our iOS 64-bit and IL2CPP support frequently reported their scripts running much faster with the new scripting backend.

在Alpha和Beta周期中，我们受益于Unity社区的许多非常有用的反馈。 而且，测试我们的iOS 64位和IL2CPP支持的用户经常报告说，使用新的脚本后端，其脚本的运行速度要快得多。

For example, Andrew Witte, who was running the RayTraceBenchmark on his 32-bit iOS device (benchmark performed on an iPad Mini, 1st gen), achieved the following:

例如，在32位iOS设备上运行RayTraceBenchmark ( 在第一代iPad Mini上执行基准测试)的 Andrew Witte实现了以下目标：

Of course, what we care about most is your scenarios, but during our benchmarking we also saw significant performance improvements.

当然，我们最关心的是您的方案，但是在基准测试期间，我们还看到了显着的性能改进。

This is the simple total time of a JPEG Encoder written in UnityScript (this benchmark was performed on an iPad Air 2):

这是用UnityScript( 该基准测试是在iPad Air 2上执行的 ) ：

This is the Mandelbrot benchmark that is part of the Unity benchmark used for testing WebGL; it shows a significant performance increase on IL2CPP (this benchmark was performed on an iPad Air 2) :

这是Mandelbrot基准，它是用于测试WebGL的Unity基准的一部分； 它显示了IL2CPP的显着性能提升( 此基准测试是在iPad Air 2上执行的 )：

开始使用iOS 64位支持 (Get started with iOS 64-bit support)

In this new build, enabling the IL2CPP scripting backend and iOS 64-bit support on your project is just a couple of clicks away. In the Player Settings for iOS you’ll find two new dropdowns: “Scripting Backend” and “Architecture”.

在这个新版本中，只需单击几下即可在项目上启用IL2CPP脚本后端和iOS 64位支持。 在iOS的播放器设置中，您会发现两个新的下拉菜单：“脚本后端”和“架构”。

Switching the scripting backend to IL2CPP unlocks the 64-bit iOS support. By default it builds for “Universal” Architecture, which means your builds will include both the ARMv7 and ARM64 binary slices in your application.

将脚本后端切换到IL2CPP将解锁对64位iOS的支持。 默认情况下，它是针对“通用”体系结构构建的，这意味着您的构建将在您的应用程序中同时包含ARMv7和ARM64二进制片。

If your existing project depends on native plugins, you might need to upgrade them to a version that supports 64-bit iOS and IL2CPP. We partnered with Unity plugin developer Prime31 to get all their plugins upgraded for use on iOS64. You can download them here.

如果您的现有项目依赖于本机插件，则可能需要将其升级到支持64位iOS和IL2CPP的版本。 我们与Unity插件开发人员Prime31合作，将其所有插件升级为可在iOS64上使用。 您可以在此处下载它们 。

Once this is done, export your project to Xcode. Note that because IL2CPP outputs scripts as C++ into your Xcode project, you’ll need to set the configuration to Release to utilize the full performance optimization of the Clang compiler on the IL2CPP generated code.

完成此操作后，将您的项目导出到Xcode。 请注意，由于IL2CPP将脚本作为C ++输出到Xcode项目中，因此您需要将配置设置为Release，以在IL2CPP生成的代码上利用Clang编译器的全部性能优化。

You can see how to set it up in the following two screenshots from Xcode 6:

您可以在Xcode 6的以下两个屏幕截图中看到如何进行设置：

Now you’re ready to run your application on a device. Use the Architecture “Universal” player setting, and the appropriate code will run automatically whether you’re using a 64-bit or 32-bit device. You can get a more detailed iOS 64 bit upgrade guide from the Unity manual.

现在，您可以在设备上运行应用程序了。 使用“通用”架构播放器设置，无论您使用的是64位还是32位设备，相应的代码都会自动运行。 您可以从Unity手册中获得更详细的iOS 64位升级指南 。

注意事项： (Things to be aware of:)

• WebRequest/WebClient API is currently available but not functioning. Anything requiring asynchronous sockets through Delegate BeginInvoke/EndInvoke currently doesn’t function. We will address this in an upcoming patch release.

  WebRequest / WebClient API当前可用，但不起作用。 目前，通过Delegate BeginInvoke / EndInvoke需要异步套接字的所有操作均不起作用。 我们将在即将发布的补丁程序版本中解决此问题。

• Delegate BeginInvoke/EndInvoke will not work though other delegate functions are working well. We will address this in an upcoming patch release.

  委托BeginInvoke / EndInvoke将不起作用，尽管其他委托函数也可以正常工作。 我们将在即将发布的补丁程序版本中解决此问题。

• RakNet networking has not yet been ported to IL2CPP, and causes issues if you or 3rd party assemblies reference it. We will address this in an upcoming patch release.

  RakNet网络尚未移植到IL2CPP，如果您或第三方程序集引用它，则会导致问题。 我们将在即将发布的补丁程序版本中解决此问题。

• Stripping is always performed when on the IL2CPP backend. This might necessitate workarounds to prevent stripping of used types.

  始终在IL2CPP后端上执行剥离。 这可能需要解决方法，以防止剥离使用的类型。

• When stripping is set to micro-mscorlib, compilation might fail on missing types. We are planning to completely disable its selection for IL2CPP in a future build.

  当将剥离设置为micro-mscorlib时，对于丢失的类型，编译可能会失败。 我们计划在将来的版本中完全禁用其对IL2CPP的选择。

• Xcode takes longer to build. The main reason being that there is a far greater amount of source code to compile.

  Xcode需要花费更长的时间来构建。 主要原因是要编译大量的源代码。

• Managed Debugger is not supported. We have it on our roadmap. In the meantime, beta users have had great success debugging their script code using the Xcode debugger.

  不支持托管调试器。 我们将其列入路线图。 同时，beta用户使用Xcode调试器调试脚本代码取得了巨大的成功。

• Enabling the Xcode Internal profiler will result in compilation errors when using the IL2CPP scripting backend.

  使用IL2CPP脚本后端时，启用Xcode内部事件探查器将导致编译错误。

We are very aware that some of the items on the above list will cause shipping delays for some. Ever since Apple’s Oct 20 announcement that new iOS apps uploaded to the app store must have 64-bit support, we’ve been working around the clock, picking off bug-reports at an unprecedented rate while pushing out new builds weekly.

我们很清楚，上面所列的某些物品会导致某些物品的运输延迟。 自苹果公司10月20日宣布上传到应用商店的新 iOS应用程序必须具有64位支持以来，我们一直在全天候工作，以前所未有的速度挑选错误报告，同时每周推出新版本。

Everyone working on this deeply cares about getting every single issue resolved as quickly as humanly possible.

每个从事此工作的人都非常关心如何尽快解决每个问题。

If you already have your iOS project on the App Store, we recommend that you keep shipping updates using the Mono backend on ARMv7. Apple states that you can continue to do this up until June 1. We further recommend that you commence internal testing of your project using the IL2CPP backend as soon as practically possible.

如果您已经在App Store上拥有iOS项目，我们建议您使用ARMv7上的Mono后端继续发布更新。 Apple声明，您可以在6月1日之前继续执行此操作。我们进一步建议您在实际可行的情况下尽快开始使用IL2CPP后端对项目进行内部测试。

We’re continuing our weekly builds and you can check out our patch releases regulary on http://unity3d.com/unity/qa/patch-releases. Please feel free to reach out to us on this forum thread. We answer queries daily.

我们将继续每周的构建，您可以在http://unity3d.com/unity/qa/patch-releases上定期查看我们的补丁程序发行版。 请随时通过此论坛主题与我们联系。 我们每天都会回答查询。

Update; we had mirrored some of the benchmarks (Xamarin.iOS 7.0.2.7 LLVM/No-LLVM) in the RayTraceBenchmark that are pointed out to be incorrect, as they are made in debug mode. We’ve thus chosen to update the bar-chart, leaving only the comparison with Mono 2.6 with IL2CPP (which are both tested in Unity).

更新； 我们已经在RayTraceBenchmark中镜像了一些基准(Xamarin.iOS 7.0.2.7 LLVM / No-LLVM)，这些基准被指出是不正确的，因为它们是在调试模式下进行的。 因此，我们选择了更新条形图，仅保留了与具有IL2CPP的Mono 2.6的比较(两者均在Unity中进行了测试)。

Update2: after verifying the RayTraceBenchmark we labeled as Mono 3.2 ran in Release mode and testing on a range of devices, we have reverted the post to reflect the original numbers.

更新2：验证我们标记为Mono 3.2的RayTraceBenchmark在Release模式下运行并在一系列设备上进行测试后，我们已还原帖子以反映原始编号。

翻译自: https://blogs.unity3d.com/2015/01/29/unity-4-6-2-ios-64-bit-support/