> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/releases/2020/2020.3.11.0-october-14th-2020.md). # 2020.3.11.0 - October 14th, 2020 Environments `Preview`, `Admin-FTS` ### ### Player * **Desktop to Mobile AR** has been added to the out-of-the-box player. We now give users the ability to jump into AR mode from desktop using QR codes. Best of all, you don’t have to turn on anything, it just works. ### Virtual Photographer * **Granular Tag and Layer Filtering** has been added to the New Render screen allowing you to easily test render new Parts and Materials and get as specific as rendering individual Layers. * **Filter for Moiré Effect** in the 2D player displays pinstripes or dots correctly on fabrics and other material regardless of your screen resolution. ### WebGL * **Video Overlay Shader** uses MP4 videos as overlays that can be played during different steps of the configuration process to give Shoppers an engaging customer experience. * **Outline/Toon Outliner** adds a shaded, sketch, or outline effect in real time with controls over line color, thickness, and opacity. ### Exporter * **STEP** Export is now part of the growing list of file types Threekit can export. STEP is a common format used for CAD used for manufacturing and architecture. Learn more about STEP [here](https://www.threekit.com/blog/should-you-use-the-step-file-format). ### Bugs * Rendering with Vray Displacement is broken --- # 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://community.threekit.com/releases/2020/2020.3.11.0-october-14th-2020.md?ask=&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.