๐–’๐–†๐–‹

๐–’๐–†๐–‹

@mrogalski.eu

Working towards a virtual workbench for your cybernetic contraptions. Check it out at https://automat.org/ (or Steam - link below !!WISHLIST!!) Feel free to come and hang out with me at https://twitch.tv/maf_pl or https://www.youtube.com/@MarekRogalski !

773 followers208 following163 posts

Pinned

๐–’๐–†๐–‹ reposted

So here is the new mouse trace chunking algorithm. Notice that mouse traces are now split into meaningful windows now and zooming no longer causes chaos. Also new bugs. Powered by segment trees. #gamedev #wip #ui #design

Here is a fun trick: signal handlers can perform surgery on the stack & registers for the interrupted thread. It can be used to inject fake function calls or steer the execution arbitrarily. It's almost like a built-in programmatic debugger that can be triggered with a "signal()" call.

๐–’๐–†๐–‹ reposted

that was *such* a good demo session. 3 mind bending futuristic tech demos techs from @mrogalski.eu , @pomdtr.me and I. Links in the vid. It went so well! I love that meetup.

Ivy Reese@spiralganglion.com

Every month we do an FoC "virtual meetup", and this most recent one was bananas!! Three (and a half) killer presentations/demos, across a pretty wide spectrum of the computing space. www.youtube.com/watch?v=In_B...

Automat can now farm alchemy ingredients in Skyrim! It scans the shopkeeper's inventory, buying every "Giant's Toe" & "Creep Cluster". When done, performs inventory reset glitch & starts over. Another step towards fully automated alchemy grinding. #TheElderScrolls #skyrim

An interesting performance tip I learned while making sense of x86 addressing system is that your arrays elements should ideally have 1, 2, 4 or 8 bytes. Only for those sizes x86 instructions can access array elements directly (so no extra multiplication is needed to get an address).

Here is a tiny but useful function. Given radius of a circle and length of a leg of an embedded triangle, it finds the length of the other leg. It may seem silly but it really makes it easier to think about geometric problems. It's like LERP for geometry.

Some of notes made while making sense of x86 conditions. The worst part for me are the JB & JNB conditions which have dual use. They are used for comparing numbers and for "unsigned overflow" checking. This makes it hard to find a reasonable visual metaphor as it also has to exhibit this duality.

Do you know what's the difference between JA (jump above) and JG (jump if greater)? Conditional instructions in x86 come in 16 variants with a bunch of interesting symmetries between them. Here is a visual language that attempts to exploit those symmetries to make their meaning more intuitive.