> For the complete documentation index, see [llms.txt](https://docs.blippar.com/webar-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blippar.com/webar-sdk/v2.0.5/whats-new.md).

# What's New?

## WebAR SDK v2.0.5 Updates

We are excited to announce the release of WebAR SDK v2.0.5. This update brings significant enhancements to improve the user experience. Below are the key features and improvements included in this version.

### Instant Tracking

No hand movements or surface scanning required.

* AR appears as soon as the scene opens or the camera starts.
* Simply tap, and AR will appear instantly.

### Tap Anywhere

Place AR objects anywhere with a simple tap.

### Improved Ground Plane Alignment

* Improved ground plane alignment for better AR object placement.
* Enhanced surface detection for a more accurate experience.

### Speed Optimzations

Performance improvements for higher FPS and smoother experiences.

### Smooth Fade-In

The camera now opens with a slow fade-in effect, offering a seamless transition into the AR experience.

### Face Tracking Enhancements (A-Frame)

* New Attributes
  1. `webar-face-landmark="point: 151;"`: Attach a 3D model to a face landmark point.
  2. `webar-facemesh-shadow`: Create an additional face-mesh layer to display only shadows.
* Inbuilt Material Attributes
  1. `webar-facemat-occluder`
  2. `webar-facemat-normal`
  3. `webar-facemesh-shadow`
* Issues Fixed
  1. Replaced orthographic camera with a perspective camera for face tracking.
  2. Fixed shadow rendering issues.

**Note:**

* `webar-facemesh` and `webar-facemesh-shadow` are two different layers acting as a face mask. The `webar-facemesh-shadow` is positioned above the webar-facemesh layer.
* webar-video-plane should be placed at a negative z-distance as shown below:

  `<a-plane id="webar-video-plane" color="white" visible="true" position="0 0 -200"></a-plane>`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.blippar.com/webar-sdk/v2.0.5/whats-new.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.