ZILtoid1991

No real issue with comments, but my posts only show up on this server, and not on the remote one. This is so bad that I was thinking on getting a Lemmy account for posting there.

kbin sounds a lot like kabin, or かびん／花瓶, which means vase in Japanese.

Vocals by: wink wink

Lyrics by: Kazuyuki Yama

Music by: Ryota Kozuka

Note: It is unknown if the singer has more work or not (if wink wink isn't a band name), and I likely suspect this was used as a one-off pseudonym for the project, which is standard among Japanese (?) singers.

Added code of conduct, branding guidelines, also fixed issues with off-screen popups.

If you're a #gamedev working with #pixelart artstyle, and looking for an engine to use, maybe after all the #unity debacle? Then I can suggest my own.

• Written in D (quite similar to C#, save for the underlying framework).
• Pixel-perfect graphics, no "pixel misalignment" due to mismatched assets. - Retro-inspired GUI.
• Unicode text rendering from real bitmap fonts.
• Built-in palette-swap effects, real-time color lookup.
• Relatively low overhead and footprint (3-5MB executable files).
• Software synthesizers for audio, one even has some feline-looking sine wave.
• No per-install monetization BS, instead you can support me via either Patreon (https://patreon.com/ShapeshiftingLizard) or Ko-Fi (https://ko-fi.com/shapeshiftinglizard)
• Fully #opensource, you can both check what's under the hood, or even completely modify the code for your own liking.

After a software update, VS2022 stopped working correctly. When I hit a break point, I don't get any local variables and their values, instead I get a "wait..." label that looks like a button, and also VS is growing in memory size until it crashes my Windows, or I either stop the debugging or VS itself.

So far I get the best results by using x64dbg, but it has it's own issues, namely that almost all guides only discuss its reverse engineering capabilities, and I need a development tool, so I don't have to rely on printing to the console as debugging, which has a lot of issues (leaving in the print commands, etc). I'm programming in D, but it should work with any other debugger made for C, and up until recently I used VS for that purpose.

I use a bit weird development setup. Since VisualD, the official plugin for VS adding D language support, does not have dub support (which D's official package manager, and without it a lot of things get very hard to do, like dependency management), I have to use VSCode as my main code editor, build my code in command line, then load it in an empty VS project set up for C++ development.

However, since the latest update, VS2022 broke completely. I previously had issues with the option to break on every D exceptions disappearing, now I don't even have that. When it hits a breakpoint or an exception, the debugger does not show the local variables, instead it has a "wait..." sign that looks like a button (but is unclickable), and the executable of VS grows until either crashes my Windows, or I stop either the debugging or VS. Probably would still work if I used it normally, but then I have to stop using dub as a build tool, and manage dependencies manually, which is a nightmare with bigger projects and dependencies having their own dependencies.

Currently I have some luck with x64dbg, but so far it's not the most ideal solution. Almost all tutorials for it is about reverse engineering software without any available source code, and I need it as a development tool instead. It seems to load my symbol file and show call stack, but not local variables or source code. D should be able to work with most debuggers developed for C.

I want to get into writing (primarily political), and while I've written some to those, I want to get as far away from centralized social media as I can.

https://github.com/ZILtoid1991/iota/blob/7299074d7013ab5664415ed9c9b9fc02bd29cfc9/source/iota/controls/polling.d#L80
https://github.com/ZILtoid1991/iota/blob/7299074d7013ab5664415ed9c9b9fc02bd29cfc9/source/iota/window/oswindow.d#L323

I have this very non-standard event loop for an input-output library. It has issues with processing and receiving certain messages. I'm only getting input language change messages by doing certain tricks (usually by changing the input method on the taskbar, then moving the window), but even then it often makes my app hanging. I also don't get any device handles from raw input messages (always null, even with devices that supposed to have all time). It's like if some other function calls, that would make things work as should, aren't mentioned in the MS documentation, and is just assumed it's common knowledge. Similar thing happened to me with SDL, when I was pulling my hair for not being able to get audio working, I even wrote my alternative library, then someone told me it's common knowledge that you should call yet another function before starting the audio stream, except none of the few existing tutorials mentioned it (most just recommended you to use existing sound playback libraries instead of doing your own thing), and the documentation wasn't clear on it (by not clear, it did not mention explicitly, other than being named prepareAudioStream or something).