I asked this in the last Q&A and got a couple of breadcrumbs and spent a few mins exploring this today. @Charlie Malmqvist suggested adding a '-mwindows' flag to the compiler. This works when you launch the program through VSCode but unfortunately doesn't when you run the exe from a file explorer or the desktop for example. I asked the AI and used the GoogleFu and I think I came to the conclusion that because oogabooga is by default a console app and not a windows gui app the -mwindows flag doesn't work. I tried adding a manifest file to the compiler as well as a bunch of other flags to no avail (I could be doing this wrong lol). I think basically you just need to make the exe a windows gui app by running WinMain() instead of main(). I didn't spend the time to work out how to change this in the oogabooga files but did come across a hack. Add something like this to your code - It's Windows specific so be aware of that. HANDLE hConsole = GetConsoleWindow(); if (hConsole != NULL) { ShowWindow(hConsole, SW_HIDE); } The console window will spawn but will quickly be minimized and then disappear. I believe if the program was using WinMain() you could use the -mwindows flag on your release build and -mconsole on your debug build and things would be sweet but I am not really sure. There might be other reasons to not use WinMain() that I have no idea about. If anyone has any better solutions. Please let me know! Cheers Bell

made my Ui a little better and made the slime's attacks have some weight. iv been struggling with some burnout on the project lately but im still proud of how far Iv gotten, further then I thought i would anyway.

I just wrote up a little post for y'all on substack: https://randysworkshop.substack.com/p/how-i-make-banger-sfx-with-no-cost I'll try format it better as a post directly on Skool next time I write one. p.s - we're doing a game jam for the private community soon, send me a DM if you're interested in joining

not sure if its an issue with oogabooga or me but, hjelp?

I was following the "Development environment setup" but at step 8. VSC threw out bunch of stuff I do not understand. Could it be because I installed "LLVM-19.1.0-win64.exe"? The error: * Executing task in folder Cavedman: D:\Programming\C\Cavedman\build In file included from ../build.c:32: In file included from ../oogabooga/oogabooga.c:148: In file included from C:/Programs_C/mingw64/lib/clang/18/include/immintrin.h:704: C:/Programs_C/mingw64/lib/clang/18/include/amxintrin.h:328:15: error: always_inline function '_tile_loadd_internal' requires target feature 'amx-int8', but would be inlined into function '__tile_loadd' that is compiled without support for 'amx-int8' 328 | dst->tile = _tile_loadd_internal(dst->row, dst->col, base, stride); | ^ In file included from ../build.c:32: In file included from ../oogabooga/oogabooga.c:356: ../oogabooga/os_impl_windows.c:204:10: warning: label followed by a declaration is a C23 extension [-Wc23-extensions] 204 | bool is_repeat = (lparam & 0x40000000) != 0; | ^ ../oogabooga/os_impl_windows.c:424:7: error: call to undeclared function 'SetProcessDpiAwarenessContext'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration] 424 | ok = SetProcessDpiAwarenessContext(DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE_V2); | ^ ../oogabooga/os_impl_windows.c:426:8: error: call to undeclared function 'SetProcessDpiAwareness'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration] 426 | hr = SetProcessDpiAwareness(PROCESS_PER_MONITOR_DPI_AWARE); | ^ ../oogabooga/os_impl_windows.c:426:8: note: did you mean 'SetProcessDPIAware'? C:/Programs_C/mingw64/x86_64-w64-mingw32/include/winuser.h:6099:29: note: 'SetProcessDPIAware' declared here 6099 | WINUSERAPI WINBOOL WINAPI SetProcessDPIAware (VOID); | ^ In file included from ../build.c:32: In file included from ../oogabooga/oogabooga.c:356: