There is a good debugging advice related to this story: "if your code is the same but suddenly starts behaving differently, check for hidden state."
It's more like code than state, isn't it? The thing that changed is the implementation of a circuit for computing the result of some calculation, i.e. a function.
Pilotwings demos act differently depending on when the cartridge was made
81–90 of 143 posts
Re: Pilotwings demos act differently depending on when the cartridge was made
#82Earlier quoted context omitted.
Your comment would IMHO be a lot better without the first paragraph speculating about other commenters.
The comments would be a lot better without seeing 6-7 completely reasonable posts being mass-downvoted and greyed out with a bunch of people complaining and seeing their comments solidly in the black. So no, I disagree with your premise, hence why I posted it in the first place.
Re: Pilotwings demos act differently depending on when the cartridge was made
#83Re: Pilotwings demos act differently depending on when the cartridge was made
#84I enjoyed this but I hate twitter as the delivery method for things of this length. Its a terrible way to digest the content.
Came here to say the same. Someone needs to tell these people that Twitter is not a blogging service...
Re: Pilotwings demos act differently depending on when the cartridge was made
#85You know, I think the crashing demo is more compeling game design wise. I watch it and have an itch to pull up a bit the nose and give a bit more throttle. That itch is the demo pulling me in, causing me to want to play. The perfect landing is meh, clearly the computer can do it, why would I bother picking up the controls? Interesting that the developers disagreed enough to roll a new chip, at what I guess was a cons…
(Spoiler) My understanding was that the "perfect" landing was first, using the old version of the chip. Then the new chip changed the physics calculations and the demo replay became a crash landing. So the "crash landing" cartridges are the newer revisions and I'd guess the motivation to change the ship was a simple "update this dependency to the newest version".
Re: Pilotwings demos act differently depending on when the cartridge was made
#86Tell me more !! How? Do a YouTube video on this ! Hell, Netflix will pay for a ten episode series on hardware hacking easy!
Re: Pilotwings demos act differently depending on when the cartridge was made
#87> you carefully dump acid on them, and you visually extract the ROM data. Super interested in how that works. Do they literally map out the chip at a transistor/gate level?
Re: Pilotwings demos act differently depending on when the cartridge was made
#88I've recommended @foone's feed on here before, but I'll do it again now. I don't even know who this guy is or how I started following him, but his feed is full of interesting fun threads like this, often looking at older tech like this. I think most people on here would really enjoy following him.
Re: Pilotwings demos act differently depending on when the cartridge was made
#89Earlier quoted context omitted.
Or you should be a little more sensitive and read about the OP and why he doesn't use a blog (severe ADHD).
Source?
Re: Pilotwings demos act differently depending on when the cartridge was made
#90I've recommended @foone's feed on here before, but I'll do it again now. I don't even know who this guy is or how I started following him, but his feed is full of interesting fun threads like this, often looking at older tech like this. I think most people on here would really enjoy following him.
His Twitter is Patreon funded which he literally never advertises, so I will do it for him. https://www.patreon.com/foone