It’s been the default since 2015 when Windows 10 launched, although there was an obvious button to opt out during first-time setup back then which was then respected permanently. It’s got gradually less prominent over time, and maybe the article’s just doing a really bad job of explaining that it’s no longer something where your initial preference is permanent and it’ll change back to the default every so often.

It’s a silly flag to use as it only works when running 32-bit Windows applications on 64-bit Windows, and if you’re compiling from source, you should also have the option to just build a 64-bit binary in the first place. It made a degree of sense years ago when people actually used 32-bit Windows sometimes (which was usually just down to OEMs installing the wrong version on prebuilt PCs could have supported 64-bit) if you really wanted to only have one binary or you consumed a precompiled third party library and had to match its architecture.

That’s what I remember, so I’m not convinced the other commenter posted correct numbers.

No, that’s the cyborgs.

It doesn’t necessarily work that way, though. If tests tell you you broke something immediately, you don’t have time to forget how anything works, so identifying the problem and fixing it is much faster. For the kind of minor bug that’s potentially acceptable to launch a game with, if it’s something tests detect, it’s probably easier to fix than it is to determine whether it’s viable to just ignore it. If it’s something tests don’t detect, it’s just as easy to ignore whether it’s because there are no tests or because despite there being tests, none of them cover this situation.

The games industry is rife with managers doing things that mean developers have a worse time and have the opposite effect to their stated goals. A good example is crunch. It obviously helps to do extra hours right before a launch when there’s the promise of a holiday after the launch to recuperate, but it’s now common for games studios to be in crunch for months and years at a time, despite the evidence being that after a couple of weeks, everyone’s so tired from crunch that they’re less productive than if they worked normal hours.

Games are complicated, and building something complicated in a mad rush because of an imposed deadline is less effective than taking the time to think things through, and typically ends up failing or taking longer anyway.

You can lose trademarks, but this is a copyright issue. You don’t have to defend copyright to keep it.

I’m thinking more for the scale of something like OpenMW, as we’ve got more frequently asked questions than we could hope to put on an FAQ page. In the olden days, stuff showed up from our forums when people googled it, and now it doesn’t, so we get loads of questions through Discord, and very rarely one from Matrix.

If past support questions showed up in searches, then more users would be able to help themselves and would never need to ask for support, so it wouldn’t matter as much what platform it happened on.

Personally, I think it would be good if support discords were all bridged to matrix spaces (currently doable, but matrix needs locking down more than discord to stop spam as the tools to prevent and remove it are worse) and the matrix history was archived somewhere search engines could index it like mailing list archives are (currently not doable). That approach would let users use what they want without forcing anyone else to, and keeps self help as easy as it was in the days of forums.

It’s a 250W+ part running at around 1V, so it’s going to draw a lot of current. Power is supplied via many pins on the back of the CPU, and they’re connected to many traces, so it’s not putting all that current through just one. It still puts out a lot of heat anyway, which is why modern motherboards have large heat sinks, sometimes with fans, on their VRMs.

I just left a game where someone was using the Spear to great effect, although they were finding it a bit of a pain to lock. That’s pretty different to completely broken.

This kind of mod is always a DLL of some kind, and typically, they’ll have you install the DLL to a location that the script extender will load DLLs from automatically (but sometimes they instead use the same name as a Windows DLL and go in the same directory as the game’s executable, as when the game tries to load the Windows DLL, it’ll try ones in its own directory before System32 and similar folders, then as long as the mod DLL in turn loads the real DLL, everything will still work). When the DLL’s loading, it’ll either overwrite bits of memory corresponding to functions with its own code, or if it needs to replace the whole function, will swap out the first few instructions with instructions to jump to a mod function instead.

If all they do is add more Creation Club content, all that happens is the functions people are hooking end up the same, but at different addresses. After the first few Creation Club updates, tools were made to automate mapping old addresses to new ones, and most script-extender-based mods could be made to work with just an Address Library update, which said which new addresses to use.

This is not that kind of update. The compiler version and settings used have changed, so functions, even ones that do the same thing, end up with different machine code at different addresses. This means a lot of mods will need making from scratch, and a lot of mods will need lots of work tracking down which functions need hooking now and how to do it even if there’s still stuff that’s salvageable.

There’s a pretty extensive API, capable of more than most games that advertise modding support, but it can’t do literally everything anyone could think of, so people reverse engineer the game engine to make it possible to do even more things (hence it being called a script extender rather than the modding API). It’s the mod reliant on reverse engineering the executable that break, not the ones using the modding API.

Fixing the script extender itself won’t take that long as it doesn’t need to hook that many functions (although depending on how much free time people have and whether there are any surprises, it could still take longer than most people expect). Fixing all the mods that depend on it will take much longer, as between them, they hook lots more functions than the script extender itself, and with this update, it’s not just a case of most functions being the same, but at a slightly different address (as was typical with creation club updates, which tools could help with), but instead lots of functions have changed slightly due to using an updated compiler, and lots of functions have been inlined differently (so instead of just existing once, they get copied into every function that uses them, and then optimised differently in each place based on the surrounding code).

It’s super quick to swap it on Windows once you know the problem exists and know where to look. You just click the audio icon in the system tray and change the output device in the dropdown from the headset version of the device to the headphones one, and it enables all the higher-bandwidth modes. I’m not sure there’s user-accessible control over which specific codec gets used, though.

Some Bluetooth controllers can’t handle the bandwidth required for sound input and output at the same time unless it’s at very low quality, and if Windows suspects such a device is in use, it defaults to the low quality mode as users are more likely to be able to tolerate it than tolerate their headphones not working at all. It’s overly cautious, though, and uses the low quality mode far more than it has to.

Federation ships explicitly have warp drives in the movie, allowing FTL travel.

Purdy Purdy Prisoner is both gay and a rapist, and the two aspects aren’t presented as orthogonal.

I never said I preferred Outlook to Thunderbird, but both are generally horrible.

It affects Windows 10, too.