> For the complete documentation index, see [llms.txt](https://docs.forge3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.forge3d.com/force-field/changelog.md).

# Changelog

The latest Force Field Update 2.4 is loaded with features that will enhance your experience in various ways. We’ve improved the overall Shield system, allowing you to make it easier to apply to a complex surface, such as Ships meshes cluttered with the details by utilizing the built-in Unity’s UV1 unwrapping.&#x20;

We’ve changed the example scenes with a brand-new PBR Reactor and Hangar Example along with the new Wasp Interdictor model to demonstrate how you can get back to the MeshCollider and the Rigidbody pipeline.&#x20;

We’ve also added new shader variations including the Edge Fade and Vertex Animation already seen in our Planets what makes Force Field even better in exciting ways.

### **\[Version 2.4 changes]**

* PBR Space Ship model with docking animation
* PBR “Reactor & Hangar” scene
* Edge Fading and Vertex Animation shader
* UV1 shader to use with an automatic lightmap unwrapping which helps fitting shield texture on a complex mesh
* RigidBody and MeshCollider should be fixed now! Check the new example scene
* The FORGE3D menu in the Unity Editor includes several new links and categories


---

# 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.forge3d.com/force-field/changelog.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.
