Escolar Documentos
Profissional Documentos
Cultura Documentos
-------------
Enhancements:
- Added a new option "Allow non-RGB video internally" on ARController. This allows
platforms where bi-planar YUV video offers higher-performance (including iOS and
Android) to be used. Note that this option cannot be used if native OpenGL
texturing is used. Additionally, with this method, a conversion to RGB for Unity's
use is necessary. Profiling of performance is recommended if you use this option.
New features:
- ARToolKit for Unity is now open source for the first time! Full source for the
ARToolKit for Unity C# scripts is provided, along with the required native plugin
binaries for each platform.
New features:
- New dynamic AR scene system allows much greater flexibility in operation. New
script components AROrigin, ARTrackedObject, and reworked ARCamera. See
http://www.artoolworks.com/support/library/ARToolKit_for_Unity_-_Dynamic_AR_scenes.
- Tracking of more than one NFT target at a time is now supported. To enable this
mode, check the NFT multi-page checkbox on the ARController object.
Enhancements:
- Help on using the scripts is available at
http://www.artoolworks.com/support/library/ARToolKit_for_Unity_-_Scripting_and_low-
level_API
- ARMarkers can now be added and removed after tracking has begun.
- On Windows, or on other platforms when OpenGL texturing is disabled, texture
upload to Unity is now much faster (uses UnityEngine.Color32 type instead of
UnityEngine.Color).
Bug fixes:
- An issue where changing ARCamera's marker tag wouldn't immediately change the
referred-to marker has been fixed.
- In ARTransitionalCamera, changed to use SystemInfo.deviceType ==
DeviceType.Handheld to identify touch-capable devices.
- For NFT Markers, ARMarker.NFTWidth and ARMarker.NFTHeight are now correctly in
Unity units.
- The pthreads library on Windows 64-bit builds was linking to the wrong VC
runtime. This has been fixed.
- Native functions that return boolean values will now be correctly interpreted
when compiling ARToolKit for Unity's C# scripts with Microsoft's compilers rather
than Mono. This fixes a bug affecting Windows Store apps.
Bug fixes:
- Corrects an issue when using the new Windows Media Foundation video module under
Unity on Windows 8.
Bug fixes:
- Corrects an issue introduced in version 5.1.3R2 which affected AOT compilation on
non-Android platforms.
Enhancements:
- Automatically switches to stereo mode on Epson Moverio BT-200.
Bug fixes:
- Android: Fixes a crashing bug which occurred sometimes when switching between AR
scenes in a single Unity project.
Major changes:
This release introduces a change in the way that AR scenes are initially arranged.
By default, a new marker placed in a scene will appear vertically in the Unity
environment. This is the same relationship between the marker and the camera's axes
as in other ARToolKit SDKs; the marker left/right axis is aligned with camera -x/+x
axis, and the marker down/up axis is aligned with the camera -y/+y axis. The one
difference is that Unity uses a left-hand coordinate system, with the camera +z
pointing into the marker, whereas on other ARToolKit SDKs, the +z axis points out
from the marker.
It is simple to produce a scene in Unity where the marker lies on the ground plane
(the X-Z plane); just apply a rotation about X of 90 degrees to the AR scene's root
object. The supplied examples all implement this technique.
Enhancements:
- The ARTransitionalCamera, which allows the viewer to move between exocentric (AR)
and egocentric (VR) mode in a scene has been improved. "Mouselook" mode should be
more reliable. Additionally, on desktop platforms, the user may navigate using
Unity's predefined movement controls (e.g. keys W, A, S, D) and the rate at which
the user moves is configurable by the user.
Bug fixes:
- Fixed a bug which caused markers to not load in the player in the rare case where
Unity loaded ARMarker objects before it loaded the ARController.
- Fixed a bug which caused multimarkers to be drawn incorrectly in the Unity Editor
when the marker origin was not at the world origin.
== ARToolKit for Unity v5.1.3 ==
Includes ARToolKit Professional v5.1.3. Changes relevant to ARToolKit for Unity are
listed below:
New features:
- Support for mono and stereo optical see-through displays has been added. At
present, only half-width side-by-side stereo mode is supported, as used in e.g. the
Epson Moverio BT-200 display. See
http://www.artoolworks.com/support/library/Using_an_optical_see-
through_display#ARToolKit_for_Unity. A new example Unity scene named
StereoOpticalScene is included in Assets/Example Scenes folder. It displays how to
set up a project for stereo optical.
- Android: Access to the CameraPreferences window is now provided via a button on
the onscreen GUI. (Press the [Menu] key to bring up the onscreen GUI). This is the
supported means of changing the preferred camera resolution on Android.
Enhacements:
- The runtime ARToolKit for Unity classes have been renamed for clarity. ARToolKit
class becomes ARController, Marker becomes ARMarker, and TrackedCamera becomes
ARCamera. See http://www.artoolworks.com/support/library/ARToolKit_for_Unity_-
_Upgrading_to_the_latest_version for instructions on how to update existing
projects.
Bug fixes
- A bug affecting calls to StopAR() followed by StartAR() has been corrected.
- This release corrects in-Editor display of marker gizmos for multimarker sets.
- Added preliminary support for optical see-through display.
- Adds support for ARToolKit multi-marker sets. At present, barcode (matrix) and
pattern-based (template) multi-marker sets are supported, with the exception of
Android, where pattern-based markers are not currently supported. The multimarker
config. file and any dependent pattern files should be placed in the
"StreamingAssets" folder, and the path to the multimarker config. file entered into
the "Marker" script object. The appropriate tracking mode must be manually
(template vs matrix) must be selected in the "ARToolKit" script object. The in-
editor display of the position and size of the marker is not currently operational
but will be corrected in a subsequent release.
- Source for the Android UnityARPlayer class is now included in the "extras"
directory. See also
http://www.artoolworks.com/support/library/ARToolKit_for_Unity_on_Android#Using_ART
oolKit_for_Unity_in_a_larger_Android_project.
Includes ARToolKit Professional v5.0.7, with one Unity-relevant fix for the default
Windows video module (WinDS). This module should now re-open correctly after
multiple runs in the Unity Editor.
- Separated the call to capture a frame and the call to update AR tracking to
improve timing in some cases.
- Fixes an issue which could lead to frame stutter in some heavily patterned visual
environments.
- Adds a user-visible error dialog in case where camera cannot be found or
initialised.
- Improved shuto
- Fix for memory leaks on shutdown (observed when repeatedly starting/stopping AR
or running inside the Unity Editor).
- Improved handling of buffer clearing.
- This is an update which corrects an issue in ARToolKit for Unity v5.0.5 UPDATE1
affecting NFT dataset generation.
- mscvp71.dll or msvcr71.dll have been removed from the "redist" folder as they no
longer need to be included with apps which use ARToolKit for Unity.
N.B. This is an update which corrects an issue in ARToolKit for Unity v5.0.5
affecting NFT tracking.
--
EOF