Official Project Tiny 0.24 preview is available

/!\ Preview 0.25 available.
--------------------------------
We have just published a new preview “Project Tiny” that brings a host of new features and usual bug fixes.

Among the notable features, we introduced the first iteration of the particle system which mirrors a subset of the functionalities available with the built-in Particle System (aka shuriken). See the Particle System section of the Getting Started for details.

TinyAquarium Sample with Particle System​

On Mobile (iOS & Android), Accelerometer/Gyro are supported, as well as controlling screen orientation. These features are demonstrated in the TinyRacing sample which also showcased the added Audio Pitch control (3D was added in preview 0.23), setup on CarAI entities to vary the sound of their engines.

Managed debugging is now available (Debugging section of Getting Started for details) as well as initial support for the Unity Profiler.

We still recommend that you use the sample projects (available here https://github.com/Unity-Technologies/ProjectTinySamples) to discover features and as a starting point for you new projects, because they are the easiest way to get all components required for “Project Tiny”.

As always, go to the “Getting Started Guide” for details.

Breaking changes for upgrading projects made with Project Tiny 0.23 preview

Unfortunately they are a few breaking changes to BuildConfiguration assets in this release which could not be auto-upgraded and require user action:

• Breaking Change: BuildConfigurations assets will need to manually add a new DotsRuntimeRootAssembly component specifying the game's AssemblyDefinition. The game's AssemblyDefinition was previously specified in the DotsRuntimeBuildProfile.RootAssembly field but has been moved into a new BuildComponent DotsRuntimeRootAssembly to allow build configurations to more easily share settings across multiple Root Assemblies.
• Breaking Change: The DotsRuntimeScriptingDefines BuildComponent has been replaced by the DotsRuntimeScriptingSettings build component. BuildConfiguration assets requiring scripting defines will need to add this new component manually, along with any scripting defines you may require. This replacement is made to allow for scripting settings to all live in a common location.

0.24 Full Release Notes

• What's new:
  • Accelerometer/Gyro support for Android and iOS
  • Screen orientation support on mobile
  • Managed debugger support
  • Support Unity profiler
  • Pitch audio support
  • Burst on iOS
  • New particles system
• Fixed:
  • Support GUID assembly references in assembly definitions files
  • If the Unity editor platform is changed, compilation errors show up in dots runtime code
  • Memory leaks in Wasm builds
  • InputSystem.GetInputDelta() always returns 0 in editor
  • Re-init when default audio device changes
  • Show error if sRGB sampling is not supported on Asmjs builds
  • Fix lit transparent materials when fog enabled
  • Game view is stretched when changing from portrait to landscape or vice versa during runtime
• Samples:
  • New Particles sample
  • Add Motion sensors control to TinyRacing
  • Add 3d audio and pitch-shifting to TinyRacing

About 2D Foundational features: not compatible yet with 0.24
Please note that anyone using the 2D Foundational features (see forum announcement) which includes com.unity.2d.entities 0.22.0-preview.8, you need to continue using com.unity.tiny.all 0.22 and the related Getting started guide for Preview 0.22. We are working on upgrading these features to the latest com.unity.tiny.all and will post an update in the forum when available.

What’s next?
As we shared on replies to questions about the roadmap, we still don't have a firm date for our "V1" enabling hypercasual style scenarios (see Unite Copenhagen 2019 Project Tiny roadmap session recording for details). We want to ensure first that the feature set is complete enough to enable projects to go in production, so the cut line isn't completely defined yet.
However we’ve updated the Feature Summary section of the getting started guide, with a bit more details about what’s planned. We'll share more as soon as possible. Thanks for your patience.
Sharing feedback
This forum is the best place to open discussions and ask questions. When you encounter a bug, please use the Unity Bug Reporter in the Unity Editor, accessible via Help > Report a Bug. Include “Project Tiny” in the title to help our staff triage things appropriately!

For more details on how to report a bug, please visit this page..

Thanks again for your feedback and engagement!

 

Hi,
Controlling screen orientation on browser is tricky
Also there is an API we can map to defined (https://www.w3.org/TR/screen-orientation/
The Screen Orientation API provides the ability to read the screen orientation type and angle, to be informed when the screen orientation changes, and to lock the screen to a specific orientation) it's not supported to the same level by all browsers (see https://caniuse.com/#feat=screen-orientation). We are looking into making it easier, but it's likely this kind of behavior will require extra Javascript code and user interactions to produce the desired effect, like showing a "please rotate the screen in landscape to play" because you won't be able to force it.

Providing detailed samples on how to interop with Javascript in Project Tiny is on our todo list!
(for now i suggest you look at how Maras, did callback from JS Library in this thread https://forum.unity.com/threads/open-source-first-tiny-project.825552/)
Stay tuned

Thanks for the feedback

 

It's in progress right now I expect it to be part of Tiny 0.26

 

It's being worked on but no ETA on when we will be releasing it

 

So far, no plans for terrain support for this year

It's a separate system but uses the same editor authoring
so from the user side you just need to add particles system and tweak it and it will work in hybrid and the dots runtime

 

yup the same settings but you need to double click on the subscene to make it active

 

Planned but no timeline, see this thread https://forum.unity.com/threads/vr-support-plans.862477/#post-5685967