This could be due to one of several reasons: You are not logged in.

Are you trying to edit someone elses post, access administrative features or some other privileged system If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Log in User Name: Password: Forgotten Your Password Remember Me The administrator may have required you to register before you can view this page.

BlueFox -- Default Style CGPersia Forums -.

Not errors, just warnings, but Im not sure if that many warnings will effect my submissions to Apple.

It is the first public release with iOS 64-bit support, using our new IL2CPP technology.

It delivers greatly improved performance for all scripting inside your projects, and is compatible with the current Mono-AOT solution used on iOS builds.

With Unity 4.6.2 youll thus be able to make a Universal build that works on both 32-bit and 64-bit iOS devices.

And, users testing our iOS 64-bit and IL2CPP support frequently reported their scripts running much faster with the new scripting backend.

In the Player Settings for iOS youll find two new dropdowns: Scripting Backend and Architecture.

By default it builds for Universal Architecture, which means your builds will include both the ARMv7 and ARM64 binary slices in your application.

We partnered with Unity plugin developer Prime31 to get all their plugins upgraded for use on iOS64.

Unity 4.6.2 Full Performance Optimization

Note that because IL2CPP outputs scripts as C into your Xcode project, youll need to set the configuration to Release to utilize the full performance optimization of the Clang compiler on the IL2CPP generated code.

Use the Architecture Universal player setting, and the appropriate code will run automatically whether youre using a 64-bit or 32-bit device.

You can get a more detailed iOS 64 bit upgrade guide from the Unity manual.

Anything requiring asynchronous sockets through Delegate BeginInvokeEndInvoke currently doesnt function.

This might necessitate workarounds to prevent stripping of used types.

We are planning to completely disable its selection for IL2CPP in a future build.

The main reason being that there is a far greater amount of source code to compile.

In the meantime, beta users have had great success debugging their script code using the Xcode debugger.

Ever since Apples Oct 20 announcement that new iOS apps uploaded to the app store must have 64-bit support, weve been working around the clock, picking off bug-reports at an unprecedented rate while pushing out new builds weekly.

Apple states that you can continue to do this up until June 1.

Unity 4.6.2 Update The Bar

Weve thus chosen to update the bar-chart, leaving only the comparison with Mono 2.6 with IL2CPP (which are both tested in Unity).

Assuming you dont have to do anything besides going into Xcode and putting release to standard architecture arm7,arm64 adding il2cpp added 90 megs to our build size making it impossible to stay under the 100 meg limit when our entire app fit below that limit art, sound, music etc before.

How can there really be 90 megs of code compared to 30 before.

Build time also hugely increased can see tons of.cpp files being processed.

Mostly Value conversion issues I selected L2CPP and universal.

Crack Unity 4.6.2