Unigine Profiler

What Unigine Profiler is

Unigine Profiler displays per-frame performance data on a timeline to help development teams locate application bottlenecks and compare performance before and after changes. Its modes include Generic, Rendering, Memory, Physics, World Management, and Thread profiling. Timings can cover rendering visible nodes, updating node states, executing game logic, and calculating physics. Profiling statistics can be enabled at runtime with the show_profiler 1 console command and disabled with show_profiler 0.

Microprofile gathers CPU and GPU performance data for frame-by-frame inspection through a local web server, with results saveable as HTML. It can profile up to 1,000 frames and is available only in Development engine builds. C++ developers can instrument code regions with Profiler::begin() and Profiler::end(). For offline work, Profiler Reader interprets binary profiler dumps, exposes system and engine configuration, and summarizes average metric values. The tools are part of UNIGINE’s SDK for teams building interactive 3D applications, including C++ and C# programmers and 3D artists. Supported platforms are Windows and Linux. The Community Free SDK is available to eligible users; paid plans include Entertainment at $9,995 per year and Academic Research at $15,595 per year.

Who it suits

Unigine Profiler suits development teams building interactive 3D applications, including C++ and C# programmers and 3D artists. It is useful when a team needs frame-level CPU, GPU, memory, or other performance analysis on Windows or Linux.

Limits

Microprofile can profile up to 1,000 frames and is available only in Development engine builds. The free Community SDK is for hobbyists, small indie teams, and students whose revenue and/or funding was below $200,000 in the preceding 12 months, and excludes defense, energy, mining, and gambling. The Academic Research SDK is for non-commercial university research; projects with commercial or defense funding above 30% of budget require a Sim license.

Getting started

1. Open the UNIGINE Profiler documentation website.
2. Choose the Community Free SDK if your team meets its eligibility rules, or select a paid SDK plan.
3. Use the SDK on Windows or Linux.
4. Enable profiler statistics at runtime with show_profiler 1.
5. Instrument C++ regions with Profiler::begin() and Profiler::end() if needed.
6. Use Profiler Reader to interpret binary dumps for offline analysis.

Verdict

Choose Unigine Profiler if your team builds interactive 3D applications and needs timeline based bottleneck analysis, multiple profiling modes, or offline dump review. The Community SDK is limited by its eligibility rules, while paid SDK plans carry substantial annual costs; Microprofile also has a 1,000-frame limit and requires Development engine builds.