I'm just confused why this has annoyed users just NOW since the button has always existed. It was just a down-pointing chevron before it got changed to a new icon so it's not like it suddenly popped up and took space away
TimeWalker
joined 1 year ago
Just a reminder that Boox does not release the kernel source code and is thus violating GPL2
Mark Stevenson, lead artist of DK64, has already said in an interview with Nintendo Life that the use of the Expansion Pak to fix a bug was just a myth. This kind of bug did exist but was fully outside of the context of the Expanion Pak:
That story has become more-or-less accepted fact, although Stevenson believes the truth is more complicated. "This one’s a myth. The decision to use the Expansion Pak happened a long time before the game shipped, in fact we were called in by management and told that we were going to use the Expansion Pak and that we needed to do find ways to do stuff in the game that justified its use and made it a selling point. I think the bug story somehow got amalgamated into the Expansion Pak use and became urban myth."
"There was a game-breaking bug right at the end of development that we were struggling with," he clarifies, "but the Expansion Pak wasn’t introduced to deal with this and wasn’t the solution to the problem. My memory is that, like all consoles, the hardware is constantly revised over its lifetime to take advantage of ongoing improvements in technology and manufacture methods to essentially make the manufacture more cost effective and eventually profitable. I think there we’re something like 3 different revisions of the internal hardware by this point and the bug was unique to only one of these versions. We did eventually find it and fix it, but very late in the day."
Source: Nintendo Life - Feature: Donkey Kong 64 Devs On Bugs, Boxing And 20 Years Of The DK Rap
Stevenson later in an Games Radar Interview explained that the Expansion Pak was used for having bigger maps as well as being able to do more advanced lightning techniques:
Artist Mark Stevenson remembers it being beneficial in terms of standard things like level size in Donkey Kong 64, but there were also more creative uses. “One thing I remember that we did use it for was that we had a lot of dynamic lighting in there, which was hard to do and expensive,” he recalls. “One of the engineers wrote a system whereby you’d go into a cave area, and there’d be a swinging light - the first swing of that light, it’d record all of the colour changes on all of the vertices in that area, and then save it as data and just play it back as an animation rather than going on to calculate the lighting constantly. You’d get a little bit of slowdown when you went in, but after that, it was nice and smooth.”
Source: Retro Gamer - How the N64 "confidently signposted our way into the 3D future"
They incorrectly assumed that when Fairphone was working on the A14 feature update that they halted any and all security updates for existing versions which is not true.
European here and I still find it distasteful and unnecessary for a release announcement post. Since you've mentioned you'd like to mod [email protected], I hope you won't be considered to mod this community.
Just in case somebody only reads the title and wants to ready their pitchforks:
And to reiterate a couple important points we’ve communicated in our previous updates published in March and May:
- The webRequest API is not on a deprecation path in Firefox
- Mozilla has no plans to deprecate MV2
Are you sure you were logging into TradeOgre? Your screenshot is showing "traderogre.com" with an extra r in your URL
Agreed! On a Lenovo Yoga Slim 7 X, I also had a big, big boost of battery life. It's really great how far it came in comparison to a few months ago!
That's the solution if you immediately tried to login and it didn't work.
Twitch login has in general very misleading error messages. The exact same message with unsupported browser also appears if you take too long to login
view more: next ›
To be fair, they supported two different git backends, one of them being go-git which was the one corrupting repositories. However, it was never enabled by default, you specifically had to build Forgejo with a specific tag to instead use that as the backend. If you just built normally or pulled ready-made containers or bins then it was always the default git backend.