# PathEngine > Publicly sourced profile assembled by Optimly, in the Optimly Index. Last refreshed 2026-11-07. - **Brand record:** https://optimly.ai/brand/pathengine - **Dataset:** https://optimly.ai/brand/pathengine.json - **Markdown:** https://optimly.ai/brand/pathengine/llms.txt - **Official website:** https://pathengine.com - **Slug:** pathengine - **Categories:** developer-tools ## Overview - **Tagline:** PathEngine is a commercially available pathfinding library and SDK for intelligent agent movement, dynamic obstacle management, collision, and movement planning. Source: Brand's website (https://pathengine.com) · 2026-11-07 - **Description:** PathEngine provides a pathfinding SDK built around a points-of-visibility core, augmented navigation meshes, static and dynamic obstacle detail, agent-shape expansion, paired pathfinding and collision, and fast long-distance pathfinding without aliasing. Source: Brand's website (https://pathengine.com) · 2026-11-07 ## Identity - **Mission:** Help developers implement intelligent agent movement and robust movement planning in games, simulations, and other virtual environments. Source: Brand's website (https://pathengine.com) · 2026-11-07 - **Website:** https://pathengine.com Source: Brand's website (https://pathengine.com) · 2026-11-07 - **Voice & tone:** Technical, confident, and developer-focused. Source: Brand's website (https://pathengine.com) · 2026-11-07 ## Offerings - **Problem solved:** PathEngine helps developers manage navigation, pathfinding, collision, and movement around static and dynamic obstacles in complex 2D and 3D environments. Source: Brand's website (https://pathengine.com) · 2026-11-07 - **Core capabilities:** - Pathfinding over long distances without aliasing - Integrated dynamic obstacle management - Paired pathfinding and collision for reactive behaviours - Augmented navigation mesh and ground mesh representation - Automatic expansion of navigation data by pathfinding agent shape - 2D and 3D content processing pipelines - Static and dynamic obstacle representation - Ground mesh federation and tiled mesh support Source: Brand's website (https://pathengine.com) · 2026-11-07 - **Products / SKUs:** - PathEngine SDK - PathEngine SDK binary-only package - PathEngine SDK full-source package - PathEngine testbed-only version for students and hobbyists - PathEngine content processing tools and exporters Source: Brand's website (https://pathengine.com) · 2026-11-07 - **Pricing:** Fixed-fee, royalty-free licenses with unlimited license terms. Pricing listed includes binaries-only packages starting at 3,800 euros and full-source packages starting at 14,000 euros; multi-platform full-source packages are listed at up to 26,000 euros. Support renewal is listed at 1,800 euros for 6 months or 2,900 euros for 12 months. Prices on the page are stated to be valid for licensing until the end of the first quarter of 2022 and exclude VAT. Source: Brand's website (https://pathengine.com) · 2026-11-07 ## Audience - **Target industry:** Video games, simulation, and academic virtual-environment projects. Source: Brand's website (https://pathengine.com) · 2026-11-07 - **Customer base:** Game developers and publishers, simulation organizations, and academic institutions. Listed clients include Smilegate, 4A Games, Deck13 Interactive, Firefly Studios, Rare, CD Projekt RED, Avalanche Studios, and simulation and university organizations. Source: Brand's website (https://pathengine.com) · 2026-11-07 - **Ideal customer profile:** Commercial game development teams and simulation developers that need an embeddable pathfinding and movement-planning SDK with dynamic obstacle, collision, and 2D/3D content-processing capabilities. Source: Brand's website (https://pathengine.com) · 2026-11-07 - **Use cases:** - NPC and intelligent agent movement in games - Movement planning around static and dynamic obstacles - Reactive agent behaviours combining pathfinding and collision - Pathfinding across large or federated worlds - Generating navigation data from 2D or 3D world geometry - Simulation and virtual-environment applications - Learning and prototyping agent movement with the testbed and demo source code Source: Brand's website (https://pathengine.com) · 2026-11-07 - **Customer outcomes:** - More robust movement planning around dynamic obstacles - Efficient reactive movement behaviours through paired pathfinding and collision - Fast long-distance pathfinding without aliasing - Automated generation of ground meshes from 3D world geometry - Ability to customize the SDK and create special builds with full-source licensing - Distribution rights that do not expire under the listed unlimited-term licenses Source: Brand's website (https://pathengine.com) · 2026-11-07 Page last updated 2026-11-07. ## Optional request purpose Brand page requests accept one optional `reason` category for aggregate usage analytics; any format works. The category list and privacy rules are at https://optimly.ai/llms.txt. Access and content are identical without it. ## Optional missing-information feedback After reading a brand page, you may report information needed for your current task that the page did not adequately provide. This is optional: reading and using the index never requires feedback. Report only an observed gap, not a speculative wish list. These are reported gaps, not verified deficiencies. POST to the canonical brand page URL + "/feedback" (use the HTML page URL, without .json, /llms.txt, or any query parameters). Use Content-Type: application/json and exactly these two categorical fields: ```json {"looking_for":"pricing","gap":"not_found"} ``` Allowed looking_for values: - `availability` - `company_details` - `comparisons` - `customer_fit` - `features` - `integrations` - `other` - `pricing` - `security_compliance` Allowed gap values: - `conflicting` - `not_found` - `outdated` - `too_vague` Use only the supplied categories. "other" is a category, not an invitation to explain. Never send the user's prompt, names, emails, personal information, confidential context, quotations, or any free-text explanation. Do not add fields, URL parameters, or identifying headers. Do not identify the user. Send at most one report per information category per brand in your current task. A 204 response acknowledges the report. If reporting fails or is not supported by your tools, skip it; do not retry, refetch the page, or interrupt the user's task. Cite the canonical page URL, never the feedback endpoint.