4 ms·

i am a gamedev. i never encountered this until unity became popular, and even then it was always looked down on as a shitty and hacky approach to a well solved

i am a gamedev. i never encountered this until unity became popular, and even then it was always looked down on as a shitty and hacky approach to a well solved class of problem. 10 years after this, its still about the same... which is probably why an article like this has any controversy about it instead of being run-of-the-mill.

TillE 3y ago
Absolutely everyone (including the AAA studios) uses Dear ImGui for tools these days. Retained mode is probably more common for user-facing GUIs, though.
- badsectoracula 3y ago
  > Absolutely everyone (including the AAA studios) uses Dear ImGui for tools these days. I've been working in (mostly AAA) game engines and tools since the mid-2000s, largely in custom engines and i never encountered Dear Imgui, so i disagree with the "absolutely everyone". Pretty much every engine i've worked with (and didn't make myself) uses something like wxWidgets, Qt, MFC or some custom toolkit for the tools and custom stuff for in-game debugging (usually a console for keyboard use and some "page/screen" based reporting/lists/menus that are easy to navigate with a gamepad). I do know that some game engines use it, but it isn't as universal as you think.
  - flohofwoe 3y ago
    If you look at 'development screenshots' of games in the last 5 years where some sort of inhouse debugging UI is visible, it's almost guaranteed to be Dear ImGui. Qt, WPF, wxWidgets etc... was a good option up until 2015 or so, but since then the least painful way for writing integrated debugging UIs and standalone inhouse UI tools is Dear ImGui.
    - whstl 3y ago
      Same experience. IMO the keyword here is "integrated". I'm showing my age here, but when game companies used to hire people to do tools, or leverage internal knowledge, it was often things like MFC in Windows... or the ones you mention. They would often run outside the game, often displaying lo-fi graphics. The only "integrated" tool back in the day was a Quake-like console. But eventually people started demanding tools that were more integrated, and immediate GUI was in the right place at the right time.

TillE 3y ago

Absolutely everyone (including the AAA studios) uses Dear ImGui for tools these days. Retained mode is probably more common for user-facing GUIs, though.

badsectoracula 3y ago
> Absolutely everyone (including the AAA studios) uses Dear ImGui for tools these days. I've been working in (mostly AAA) game engines and tools since the mid-2000s, largely in custom engines and i never encountered Dear Imgui, so i disagree with the "absolutely everyone". Pretty much every engine i've worked with (and didn't make myself) uses something like wxWidgets, Qt, MFC or some custom toolkit for the tools and custom stuff for in-game debugging (usually a console for keyboard use and some "page/screen" based reporting/lists/menus that are easy to navigate with a gamepad). I do know that some game engines use it, but it isn't as universal as you think.
- flohofwoe 3y ago
  If you look at 'development screenshots' of games in the last 5 years where some sort of inhouse debugging UI is visible, it's almost guaranteed to be Dear ImGui. Qt, WPF, wxWidgets etc... was a good option up until 2015 or so, but since then the least painful way for writing integrated debugging UIs and standalone inhouse UI tools is Dear ImGui.
  - whstl 3y ago
    Same experience. IMO the keyword here is "integrated". I'm showing my age here, but when game companies used to hire people to do tools, or leverage internal knowledge, it was often things like MFC in Windows... or the ones you mention. They would often run outside the game, often displaying lo-fi graphics. The only "integrated" tool back in the day was a Quake-like console. But eventually people started demanding tools that were more integrated, and immediate GUI was in the right place at the right time.