At least ChatGPT has good suggestions how to block it. I knew it would be some registry entry but we’ll see for how long Win11 respects those settings.

#Microsoft ‘s forced Win11 online account at random boot sessions is the best invention since Internet Explorer </sarcasm>

@sinbad is it nerdy of me that I also wanted initially an espresso machine with pressure gauge? I settled for a touch screen one, though.

@aras yes, it matches my own results - approved 👌

@aras another well documented blog post! I almost mistook the battle ship for the USS NC, which is the only ship I’ve seen here so far, but they look very similar, probably not a coincidence - but what do I know :D

My biggest pet peeve in computer software is popups. Of any possible kind! Not just ads, really anything that changes the top level window while you’re typing in your password or search request. Anything that steels your attention of what you were doing right now. Is that an ADHD thing or do more people share this sentiment?

@wumpf iirc VS uses Ctrl+Shift+Comma/Period. Ctrl+Plus/Minus sounds more reasonable, but mouse wheel? C’mon :p

@SonnyBonds haha, that’s true 😆 There are some questionable shortcuts that trigger the zoom-in and then no one knows how to zoom back out.

First thing I do on a new #VisualStudio installation: replace zooming via mouse wheel by “Mouse Fast Scroll” extension. Who seriously needs to zoom the text on a daily basis? Isn’t that something you’d want configured once and never touch it again?

@Ronflaix @zeux I/O streams? :p

@aeva I’m also a bit torn between APIs like D3D that are sometimes vague when “NumElements” can refer to bytes or texels and then you have Vulkan where the documentation is so overwhelming that you forgot half the conditions before you reached the end of the page.

@aeva it looked like a bug to me; some read access violation and nothing in RenderDoc nor the D3D11 debug layer showed any sign of wrong inputs. Nor did extra bounds checks and debug info in the DXBC shader avoid the crash. Debug symbols showed it crashed inside some compute shader execution that WARP emulates.

It appears to me that D3D’s WARP renderer can’t handle ByteAddressBuffer of size 4. After a long session of debugging I just clamped its size to 16 and that worked, but the debug validation did not help in this case.

@demofox The JS I get in touch with when using Emscripten is enough for me. It did teach me a lesson, though, that unaligned memory is not only slower but also potentially incompatible with the JS glue.

@ErikUden Thanks for sharing, this gave me a bit of relief of this real-life horror story 😳

@sinbad I submitted a fix for 5.6. Might take a while until it shows up on GitHub.

@sinbad I presume this was added to fix a specific issue at the time, not to keep the const version internal. This change goes back to 2015 btw.

@slembcke It’s obviously for multiplayer. Man In The Middle, The Game

For those interested: This happeend because some bones were transformed by keyframes that wouldn’t change, so it was a zero time range (to.time - from.time = 0) and that caused a lot of NANs in the vertex transformations because of invalid interpolation.

@mondanzo I love taking screenshots of my own bugs and those I find in AAA games. Oh and the Utah Teapot of course.