UE optimizer earns praise

Unreal Engine projects often slow down for boring reasons, not dramatic ones: a mesh ships with no level of detail model, a texture uses the wrong size, or a sound asset is missing the settings that keep dozens of copies from playing at once. Epic’s own optimization guides point developers toward checks like level of detail setup, texture streaming, lighting, and profiling because those small misses add up fast. (dev.epicgames.com) James Rowbotham built a tool called Project Optimise to run those checks across an entire Unreal Engine project instead of making a developer inspect assets one by one. On the Epic Developer Community forum, he describes it as a lightweight Unreal Editor Utility Widget that scans projects for optimization opportunities, bugs, and naming problems. (forums.unrealengine.com) The key detail is that it reads assets but does not edit them. Rowbotham says the tool only generates logs of possible issues, which fits how Unreal work usually goes: one project may treat “no collision” as a bug, while another may do it on purpose for a decorative prop. (forums.unrealengine.com) That “report first, don’t auto-fix” approach is why tools like this get attention from working teams. On its current itch.io page, Project Optimise says it searches for 24 kinds of optimization issues across 8 asset types, plus 10 bug categories across 7 asset types, and it also checks naming conventions that teams use to keep large content libraries searchable. (cbgamedev.itch.io) The examples are very specific. The tool can flag static meshes with no level of detail models, meshes with many material slots, textures that are not power-of-two sizes, blueprints with replication enabled, sounds with no concurrency settings, and foliage that still casts shadows when that may be too expensive. (cbgamedev.itch.io) It also looks for plain bugs that are easy to miss in a content-heavy project. Rowbotham’s documentation lists checks for missing materials, missing physics assets on skeletal meshes, missing sound class assets, project redirectors, and foliage entries with missing meshes. (cbgamedev.itch.io) The workflow is built for triage, not theory. In Rowbotham’s how-to post, each button runs a search, shows a total count, and lets the user jump straight to the flagged asset in the Content Browser, which turns “something is wrong somewhere” into a short list an artist or technical designer can actually clear. (cbgamedev.com) This matters more as Unreal projects get larger because performance regressions rarely arrive as one giant mistake. Rowbotham describes the problem as “death by 1000 cuts,” with lots of small content issues gradually hurting frame rate or creating player-facing glitches as a game grows. (cbgamedev.itch.io) The recent burst of praise is landing after the tool moved from a free early-access style release into Epic’s newer Fab marketplace, where Rowbotham said he spent 2024 hardening the product with outside feedback before selling it there. He wrote that the free itch.io version had effectively become an early test bed, and that user feedback over that year helped make the Fab release more solid. (cbgamedev.com) It is also still being maintained against new engine versions, which is the difference between a clever utility and a dependable workflow tool. In a November 15, 2025 update, Rowbotham said Project Optimise had been updated for Unreal Engine 5.7 with engine-specific changes required to keep it working after the version moved out of preview. (cbgamedev.com) So the acclaim is not really about a flashy feature. It is about a tool that turns a giant Unreal content library into a checklist, catches the kinds of mistakes that usually survive until late testing, and leaves the final call to the developer instead of pretending every flagged asset should be changed. (forums.unrealengine.com)