-
Notifications
You must be signed in to change notification settings - Fork 185
/
ARToolKit for Unity Readme.txt
executable file
·180 lines (107 loc) · 11.7 KB
/
ARToolKit for Unity Readme.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
Read me for ARToolKit for Unity.
================================
Contents.
---------
About this archive.
System requirements.
Release notes.
About this archive.
-------------------
This archive contains the ARToolKit for Unity project, plugins, utilities and examples, version 5.2.
ARToolKit for Unity version 5.2 is released under the GNU Lesser General Public License version 3, with some additional permissions. Example code is generally released under a more permissive disclaimer; please read the file LICENSE.txt for more information.
ARToolKit for Unity is designed to build on Windows, Macintosh OS X, iOS and Android platforms.
This archive was assembled by:
Philip Lamb
http://www.artoolkit.org
2015-05-13
Copyright 2015 DAQRI LLC
Copyright 2011-2015 ARToolworks, Inc.
System requirements:
--------------------
In addition to any base requirements for Unity, the ARToolKit for Unity plugin(s) have the following requirements:
* ARToolKit for Unity 5.2 requires Unity Pro v4.5.5f1 or later.
* If targeting Android, Unity Android Pro is required. Android v2.3 and later is supported.
* If targeting iOS, Unity iOS Pro is required. Xcode tools v5.0.1 or later is required. iOS v5.1.1 and later is supported.
Release notes:
--------------
== ARToolKit for Unity v5.2 ==
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.
== ARToolKit for Unity v5.1.7 ==
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.
== ARToolKit for Unity v5.1.6 ==
Bug fixes:
- Corrects an issue when using the new Windows Media Foundation video module under Unity on Windows 8.
== ARToolKit for Unity v5.1.5 ==
Enhancements:
- Brings ARToolKits support for stereo video sources and stereo tracking to ARToolKit for Unity.
- When using a single video source with a stereo display, the video background now renders in both eyes.
- A new video module is available on Windows. It uses the Microsoft Media Foundation framework, and is supported on Windows 7 or later. This module provides better support for built-in cameras on tablet devices running Windows 8. to use this new module, use a video configuration string of "-device=WinMF -format=BGRA". See http://www.artoolworks.com/support/library/Configuring_video_capture_in_ARToolKit_Professional#AR_VIDEO_DEVICE_WINDOWS_MEDIA_FOUNDATION for more information on format and frame size options.
Bug fixes:
- Corrects an issue introduced in version 5.1.3R2 which affected AOT compilation on non-Android platforms.
== ARToolKit for Unity v5.1.4 ==
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.
== ARToolKit for Unity v5.1.3R3 ==
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.
== ARToolKit for Unity v5.1.3R2 ==
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.
== ARToolKit for Unity v5.1.2 ==
Includes ARToolKit Professional v5.1.2.
- This release corrects in-Editor display of marker gizmos for multimarker sets.
- Added preliminary support for optical see-through display.
== ARToolKit for Unity v5.1.1 ==
Android: ARToolKit 5.1 introduces a significant new feature on Android, fetching of camera calibration data from an ARToolworks-provided server. On request, ARToolworks provides developers access to an on-device version of calib_camera which submits calibration data to ARToolworks' server, making it available to all users of that device. For ARToolKit for Unity on Android, the underlying changes to support this are incorporated into the native plugin. Your app will link against libARWrapper.so and its additional dependencies libcurl.so, libssl.so and libcrypto.so. Please see http://www.artoolworks.com/support/library/Using_automatic_online_camera_calibration_retrieval for details on this feature.
Android: this release also corrects some inconsistencies in the example AndroidManifest.xml (screen size, uses-feature). Added requirement for android.hardware.camera.any and made android.hardware.camera.autofocus and android.hardware.camera optional. This should fix reported issues with Android market not making apps available to devices with only a front camera or to devices without an autofocus camera.
iOS: An error whereby the correct camera parameters were not being selected for most recent iOS devices when using a video configuration of "-preset=high" has been corrected
== ARToolKit for Unity v5.0.8 ==
Includes ARToolKit Professional v5.0.8.
- 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_ARToolKit_for_Unity_in_a_larger_Android_project.
== ARToolKit for Unity v5.0.7 ==
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.
== ARToolKit for Unity v5.0.6 ==
- 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.
== ARToolKit for Unity v5.0.5 UPDATE2 ==
- 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.
== ARToolKit for Unity v5.0.5 UPDATE1 ==
N.B. This is an update which corrects an issue in ARToolKit for Unity v5.0.5 affecting NFT tracking.
This release incorporates ARToolKit Professional v5.0.5. The numbering of ARToolKit for Unity releases has been changed to match the version of ARToolKit for desktop and mobile platforms.
ARToolKit version 5.0 introduces a new (non-backwards compatible) improved NFT dataset format. While most of the APIs and tools for NFT tracking remain identical, performance has been improved and dataset sizes have been dramatically reduced, typically by more than 90%. As an example, the gibraltar sample NFT dataset (high-resolution A4 size) included with ARToolKit for Unity v2.1.x has shrunk from a total of 1.7B to 229KB. An A5-size dataset at lower resolution can be shrunk to under 100KB. This change comes with the same level of tracking performance. We believe this will make both local storage and over-the-air transmission of NFT datasets far more comfortable for developers.
--
EOF