Watertoon

I think engine design starts with a problem space, where available technology should be considered in how and who it enables to navigate those problems. Which I think ends up glossed over and the motivations mired a bit here. The runtime is like coloring a painting at the end.

Some good jumping off points here. My main criticism (more a reader be wary) is the tutorial selects it's technology to tutorialize the process of creating an engine runtime.

I recently saw a JP codebase use result codes named like "LoadOK" and "AllocSizeNG". I often use head-initial "failed" or "bad", etc, but I think I like head-final "NG" as an expression enough to start using it. "OutOfRange" vs "RangeNG", etc.

And people's decisions often end up acting as their group's.

I do value other people attempting to lead cooperative lives of discovery and self-improvement. Some don't, but I don't think I respect that very much.

This is my concern I tell others when considering GenAI, or outsourcing in general (just using an appliance sometimes). Ideally someone roughly understands what they are doing, as outsourcing something one is not familiar enough with is gambling away one's agency and intent.

Proposal link for more info on the extension: docs.vulkan.org/features/lat...

Love to see VK_EXT_descriptor_heap make it in to Vulkan. My ideal descriptor binding model was already roughly the "heap with indirect index" and "indirect address" mappings, but emulated on top of VK_EXT_descriptor_buffer. So this will greatly simplify my descriptor management, with no api changes.

Gameplay mainly wants to hit a throughput target to avoid loading being the cause of an interruption. Where more recent modern compression standards like zstd have been able to increase overall HDD throughput in a way that may reduce the need to duplicate game data to reduce poor HDD seek times.

Helldivers 2 is specifically a PS5 game, it's good they already did assume an SSD there. I more meant they likely inherited tech and adages from their past titles like Helldivers 1, which would have targeted PS3 HDD/Bluray, maintained today for PC players who still use an HDD.

I'd presume they inherited part of that decision from over a decade ago with the first game where compression standards like zstd weren't widely adopted, and a PS3 game loaded directly off a Blueray.

If the cardboard model also brings the Switch 1 VR headset titles forward to the Switch 2 then I'm decently happy with that option.

Not all cheats are accessibility options but almost all accessibility options are cheats, so I think a distinction is worthwhile. Unless one argues Big Head mode is necessary for clowns with low-blood comedy, a cheat doesn't have to be more than a meme. Accessibility I think has more expectaction.

Party rockers in the hou

My problem is Donkey Kong does not prove his faith in banana through his deeds, but instead by proving his religion was the correct one.

For 2d, depending on my requirements, I'd look for an as conceptually simple to use framework as I could.

I have ideas on how I want to implement my game designs, and Godot doesn't fit my conceptions well, and doesn't seem particularly more worthwhile for it's differences. For 3d I'd default to Unreal or look into Bevy for an open option, if I didn't have a unique reason to kitbash my own engine.

A nebulous statistic called "ambient comedy score" which goes up or down on most behaviors to rank how funny a playthrough is. Defacto Funny%.

The kind of reverse engineering communities I think they are from I'm not too surprised at the armchair attitude, possibly from some sort of odd relationship of wishing Nintendo's game code was more straightforward to work with. I think it's probably not intentional, just a bit of a shame.

I appreciate them trying to tell a story from that routine, but it mostly devolves to their headcanons and the ultimate conclusion is a resounding "lol".

My impression is that game has many small quality issues, but as far as mildly funny and easy to explain examples go that vid is a poor cherrypick. They could stand to be a bit more respectful to the limitations of that era instead of comedically speculating on it. I saw some poor takeaways.

Bluesky's structure seems to promote an OP based timeline of threads, which are then shared out of context through discover. Idk, cult of personality with stuff leaking out to true randoms feels bad for real discussion (it feels wrong for me to write 3 post replies, skill issue? Not sure).

Shouldn't ideally outside dunk to op be a relevant interaction to the original community? And discouraged by the other community? Reality is kind of more an abstract war of abstract nations of limited resource. Here if it's just noise, then uh, annoying and sucks, but at least not much of a threat.

I think I see. I was modelling it as in site/thread dunks on OP, not considering out of community dunks on another site/thread's OP? I'm not strong with wider relations. Not very sure on ideal ways to protect a local community from wider contexts and incentivise wider improvement.

It's good work! Why public wikis can be so great. Having a basis for discussion should imply an amount of seriousness with respect to the basis, and that can be a tree from a site's goal to it's thread's. I think it's often not easy to structure or navigate this.

I think the ideal is to trim the noise of discussion from a topic, and have easy access to forwarding that info. Make the relevant info an expectation for participation (which reduces accessibilty, but imo more deservedly as complexity increases), then the followup should be used to refine the info.

I think people like this often want to improve a community's signal to noise ratio on a topic. But don't really understand their want or how to improve it, while taking their knowledge for granted. Noise will happen, harassment and clowning is probably not how to cut it short.

The former, my impression is EPD doesn't like to generate more visual frames than physics frames. Physics is interleaved with actor processing in this engine, where increasing the framerate would mean using a smaller physics step rate, which would produce different physics results between consoles.

The compressed binary size grew by ~8 MB this update. It's a little impressive.

I think subtlety is a menace in a global context. An api is typically born from somewhere's local cultural context. My favorite api's tend to be explicit, ergonomic, and respectful of motivations. Though hard to generalize the latter 2 because they can have an element of opinion.

Api design is a personal concern of mine I've been trying to articulate. Using an api is like going to a friend's house and having to respect their rules, which can be lax, strict, subtle, subvertible, etc. The standouts make me reevaluate my home life.