> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/web/changelogs/webviewer-bim/wvbim-changelog-2023.md).

# WebViewer BIM 2023 Changelog

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

### 1.5.0 - February 17th, 2023

## New

## Issue Hotspots

* Issue hotspots allow you to visually see where the created issues reside on the 3D asset.
* By clicking a hotspot, you change the current view to the selected issue.
* Hovering over a hotspot displays the respective issue on the issue's panel.

## Section Planes

* `Section Planes` allow you to temporarily cut through a 3D asset along a designated axis, enabling easy viewing of the interior of assets.
* Users can now add section planes to the X, Y, and Z axes.
* Active `Section Planes` are saved within an "Issue" when created.
* Users can reset all "Section Planes" in the current view.

## Camera Modes

* Support for an orthographic camera has been added.
* The camera mode can now be toggled from the viewport.

## File Formats

* Added support for .RVT, .OBJ, and .STL 3d file formats.

## Issue Improvements

* Hidden elements, section planes, and camera mode are now preserved in the 'Issue'. These elements are applied when entering an 'Issue'.

## New APIs

* Ground shadows can now be toggled on or off.
* APIs for customizing the properties panel.
* APIs for customizing the first-person camera mode.

## Fixes

* Improved performance of the 'Model Tree' when hiding/unhiding elements.
* Fixed an issue where panel menus did not close properly.
* Fixed an issue where the 'WCS' widget was blocking the 'UI'.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apryse.com/web/changelogs/webviewer-bim/wvbim-changelog-2023.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.