"I wanna fly sky hiiiiigh!"
"Let's gooo together!"
Instantly had Sky High from Daytona USA in my mind after seeing this.
https://youtu.be/q0phmMlyIcQ?is=L2ECr3qVMmHNDC2V
As I'm sure many of you are already aware, Did You Know Gaming (who have been doing some really great investigative work lately) recently put out a video on canceled Sonic games. The whole thing's worth a watch, but I have to bring it up here specifically because they talk about the plans for Sonic Chronicles 2 with a LOT of new info directly from the lead designer.
The section on how the story of Sonic Chronicles 2 would have went starts at 9:45. It's very interesting! He outlines the whole plot, including the fact that they were going to end with ANOTHER obvious plot hook for a sequel in the hopes that they or some other studio could keep the Sonic Chronicles series going indefinitely. Sonic Team even claimed they were interested in using Chronicles characters like Shade in other games. It's crazy to imagine a timeline where this might have become a pillar of the franchise.
I refuse to mourn the loss of the sequel, though, because y'all saw me stream the original. It was miserable. And with the original game selling and reviewing decently well, they would have had little reason to go back to the drawing board and overhaul that game's bizarrely hateful design.
Of course, DYKG also had to talk about the reason why the game was canceled. I was dreading this because of how often people tend to get the basic facts of the Penders cases wrong or downplay the obvious Archie Knuckles inspiration in Chronicles. But no, they did their homework! And they got the details right in part because, well... they asked Penders for comment directly. And he sent them back a MASSIVE wall of text about the whole ordeal, including some fascinating details that I don't believe I've heard before!
You can go to 15:19 in the video and scrub through to read the many, MANY screencaps of their emails from Ken, but here are the most interesting and/or hilarious tidbits to me:
#1: Perjury!
As we already knew, Ken claimed that the incomplete, photocopied contract Archie presented in court was a forgery, and that he had never signed a work for hire contract.
The judge obviously knew that one side had to be lying here, and thus was more than willing to present the case to a jury to let them decide the truth... and send whoever was deemed the liar to jail for perjury. (The judge apparently looked Ken directly in the eye when he said this, which... well, make of that what you will.)
Archie's lawyers knew that they didn't have a completely airtight case and obviously did not want to go to jail. So they decided to settle instead of going to trial in front of a jury.
(I will reiterate that Archie's arguments not working out is overall a GOOD thing, because we really do not want to set a legal precedent where corporations can "lose" a contract for a creator, make up a story about what was on the contract, and then have that hold up in court. They gotta get that shit in writing. And they didn't. They fucked up!)
#2: Sega was threatening to revoke the Sonic license!
As we knew, Sega wanted nothing to do with the comic copyright lawsuit. To them, it was Archie's job as licensee to deal with their freelancers. (Y'all watch Succession? You know how Logan loves lackeys who will eat shit for him without him having to even hear about the problem? Yeah.) And, in fact, according to Ken, Sega gave Archie an ultimatum: if they wanted their license to make Sonic comics renewed, they were gonna have to deal with Ken on their own, and cover all the costs.
Yeah, uh, this kinda makes me think that Sega being pissed about the ongoing Scott Fulop copyright case in 2016 may have been a bigger factor in Archie Sonic's cancellation than I previously thought. There was a lot going on at the time that could have contributed, but, y'know.
Anyway, Archie sued Ken for "damaging their business" largely because Sega was threatening to take away the Sonic IP. But because Archie couldn't ask Sega for help and they couldn't produce an original contract, they had to settle.
There's another detail I find funny here, though. Ken WANTED Sega to get involved in the comic copyright case, thinking that Sega would strongarm Archie into paying him the millions of dollars he wanted for "using his work without permission" so that they could be done with it. I mean, sure. I guess Sega wouldn't have cared about Archie's finances, but still. I'm not so sure that would've worked out for him.
#3: Shade!
Yes, Penders still claims he legally owns Shade, and under advice from his lawyer still intends to put out an NFT of her to put his claim to the test. Yes, it's incredible that he still hasn't put out the damn NFT. It only needs to be one image, which he already drew! The market has collapsed!
Anyway, building an argument off the legal concept of estoppel, he says that if Sega continues to not do anything about his claims that he owns Shade then, in the eyes of the court, they'll be forfeiting their claims to Shade altogether. But they aren't going to do anything because they never wanted any part in the copyright battles in the first place, and to them Chronicles is a long dead asset not worth fighting over. Why bother trying to use Shade again and giving Ken a reason to take them back to court when they can just move on? It's not like this franchise is short on characters. And so Ken can say that Shade and Julie-Su are literally the same character, and if he owns Julie-Su then therefore he also owns Shade.
Our copyright system is, indeed, a nightmare. Chronicles should have been halfway to the public domain by now.
#4: Sega's oversight on the Archie comics!
Ken says that in his first year on the series Sega only requested some dialogue changes here and there through the editor. They never requested huge script changes, and also never spoke to Ken directly. After that first year, they stopped asking for dialogue changes altogether, and Ken "had a free hand to do pretty much whatever he wanted." Yeah, no surprise there.
He does, however, say that Archie's original deal with Sega stated that they weren't allowed to create ANY new Sonic characters without informing Sega. They would've needed to make a contract every single time to get Sega's approval and make it absolutely crystal clear that Sega owned the whole cast. And then Archie just... didn't do that! And didn't tell any of the freelance creatives not to come up with new characters! Had Archie followed this rule, the trajectory of the comics would have been completely different, but there also never would've been a copyright battle in the first place.
Spring and summer seem to be convention season. I need to do another one of these. Not so much redo this one, as character personalities may have changed *cough*Lisa*cough*, but have another interpretation.
I love how Nidorina and Nidorino are still the most attractive people there without trying. Needles is still adorable.
Click on the artwork to be taken to the source page. You can read my original description for this in the Others micro-gallery!
Do you think were any kind of specific aspects of the culture, industry, economy, etc that made making cartoons in 90s / 2000s better or worse than trying to make them today?
They're literally different worlds.
As a 22 year old neurodivergent, I was able to pitch show ideas directly to executives. Part of that was because TV Animation wasn't a glamorous profession (quite yet), so the higher-ups were genuinely passionate about the medium. I earned good money for the time and was generally trusted to run my show and tend to the crew. I would periodically be handed portfolios, which I would personally review and pass on to other show runners. For the networks it was always corporate, cutthroat, and ultimately about the money, but as an artist you could still have a voice and make art while being paid a living wage.
The pay for a freelance storyboard in 2005 is almost exactly what it is today, but now you're likely to have less time and be required to do an animatic on top of it. Portfolios are online, and (beyond metrics) you'll probably never know if anyone looks at it or not.
Animation got big. Too big. The executives got "glamorous", then the talent got "glamorous". By then you probably wouldn't get a pitch meeting unless you were a celebrity or knew one willing to be connected to your project. Animation eventually got so big that it popped. And that's where we are now.
Most of the people I know from Kid's TV Animation are currently unemployed. I have been off Jellystone for over a year, and I'm starting to get genuinely worried. Like, "move away to save money" worried. Most of the employed artists I do know are on long-running legacy series, and they're concerned about their futures when/if those series end. Right now is not a fantastic time for "animation as a money-making profession". The "glamorous" part popped years ago.
That being said, there are still opportunities out there. If you're just starting out, apparently there's a planned surge in adult and pre-school animation. It's also a great time (as long as YouTube remains sane) to be crafting your own content. But I think that the time of Big Studio Patronage is over for most of the industry. It's up to the individual artist now more than ever, not only to make but to promote their own content.
Back at the height of Billy & Mandy, we mostly pulled fours and fives in the Neilsen ratings, but we occasionally got a seven. For reference, E.R. consistently got eights. It's difficult to say exactly how many people that actually was due to how those ratings work, but it was a big deal for the time. Millions. Enough people that if I had a dollar for each person that just watched that one episode, I would have been set for life. Now, nobody gets a seven. A four is huge. Back then there were maybe fifteen or twenty channels of programmed content as opposed to the streaming smorgasbord we were all just enjoying (and which now also seems to have popped). Point being, even though I wasn't paid-per-view, I was able to use those views as justification for an eventual raise. In modern times, streaming numbers are seemingly deliberately kept secret. You'll never really know how well your show was doing until it's over. Or maybe never.
In modern times, a million views on YouTube is enough to get you noticed online. It's a lower bar for entry in a way, but you've got to get there all by yourself. Once you're there (hello Hazbin) a network may indeed come and scoop you up. Even if they don't, you can probably make a decent living with numbers like that if you're savvy and willing to take the time.
I feel like I could go on all day, shaking my fist at the sky, gray-ass beard blowing in the wind. Was it better or easier making cartoons in the past? It seemed that way to me, but that was a world I knew. There was no AI to sell you out to, and the media was more of a "Wild West" than it is today. I do think that AI is going to continue to displace artists (and soon others), making it even more difficult to get anyone's eyes on anything at all.
Culturally, we lack the common touchpoints that bonded our society in the 20th Century. I suspect that the media landscape will continue to become more "bubbly" and disjointed unless some powerful force swoops in to mandate a common viewpoint. Those are two very divergent, uniquely tiring futures, each presenting a different challenge for an artist's survival.
Outside of whatever our modern world is, animation was made for a century by photographing drawings. If Émile Cohl could do it in 1908, you can do it now. It's a lot of labor, but maybe that's part of what makes it special.
Probably not the final post in relation to the N64 emulator on Switch, but we did get a bunch of new information thanks to a new leak of iQue emails not too long ago. Somehow the gigaleak continued, it seems.
There's a ton of emails in relation to game localization of first party Switch games, but I won't talk about those, there's also tons of stuff in relation to Wii U VC and the Pokémon 3DS GB rereleases, instead I'm gonna focus about the early development of emulators on Switch.
GameCube Emulation for Wii U?
I don't know where to put this, I found this in the leak, but I'm sure some people would have been interested to know: iQue was working on a GameCube emulator for Wii U in 2013. I have no reason to believe this work was used by NERD later, I believe they fully did their own thing later.
For explanation: CAT actually means Wii U here. CAT-DEV is the name of one of Wii U development kit. For context the same emulator framework would use CTR (3DS) and PC (well… Windows PC).
It absolutely did not work like Nintendont, I saw evidence of JIT code recompilation. It would join the unreleased GBA emulator for 3DS by the same developers.
(For those who might ask: No, Nintendo did not use a GBA emulator for the 10 GBA games that came out on 3DS, it relies on the 3DS's GBA backward compatibility mode. Yep, they did that on the hardware level and somehow they still wanted to make an emulator for it.)
Switch Virtual Console (Clipper)
Yes, Switch Virtual Console was originally a thing!
It was codenamed "Clipper", development seems to have started around 2015, and continued from there. It was seemingly a collaboration between iQue and M2, possibly others like NERD but they get barely mentioned so I can't be certain.
Do you guys actually remember the original announcement of Nintendo Switch Online's retro game service? It used to say this:
Subscribers will get to download and play a Nintendo Entertainment System™ (NES) or Super Nintendo Entertainment System™ (Super NES) game (with newly-added online play) for free for a month.
This, for me, is the relic of what it used to be. I believe the original plan, was basically Virtual Console, but with one free monthly game for those who pay for NSO. It was confirmed it was paid games after that, at least by the press.
iQue took their NES emulator from the 3DS, which was okay, it wasn't bad, and N64 would continue from Wii U N64 VC, which already had terrible reputation.
If you started a game on Switch VC in CRT mode, you would see an animation where a CRT TV would be turned on, complete with TV noise, and even caring enough to record the sound of the power button for both the Famicom and NES seperately. Nintendo cared to have a very descriptive animation.
There was actual testing for NES Switch VC, listing tons of the usual first party game and also third party games such as: Final Fantasy 1 & 3, Mega Man 2 to 6, Ganbare Goemon! Karakuri dōchū, Star Luster…
I don't know whether it was going to be part of the final product, but they seemed to test games with different game speeds (Slow, Normal, Fast), and they do report bugs in relation to that so I don't know.
Also they did make it important to have online netplay in it, with different ideas for implementation. One of the ideas that was given as a fun mode was a way to automatically shuffle controllers between up to 4 players every 30 seconds, with a countdown until it says "SHUFFLE!", as well as premade messages (such as emojis and "thx", "sry", "plz", "cya").
For SNES, I saw a mention of "Street Fighter ZERO 2". I don't have the full context but it sounds like M2 was responsible for SNES Switch VC initially? M2 was very involved at the very least.
I did see a bunch for N64, but a lot of focus were on Wii U VC, specifically for games like Banjo-Kazooie (yep), Blast Corps and Ogre Battle 64.
A bit of off-topic in regards to Ogre Battle 64: It seems they tried to fix a bug that also happened on original hardware, which also happens to lock up the entire system. Unfortunately fixing such bugs isn't easy.
And then around May 2017, I don't seem to see too much about Clipper. And that would make sense, because in June 2017, Nintendo announced a change about how they would deal with classic games on Nintendo Switch Online, with what was originally called "Classic Game Selection."
Nintendo Switch Online (L-Classics)
This is where the project that we know about, codenamed "L-Classics", would come to be. There's a lot of back and forth between iQue and NERD, where NERD explained why Clipper was cancelled in favor of L-Classics:
Previously, when shipping Virtual Console titles on new platform, Nintendo relied on extensive testing for each emulator (NES, SNES, N64) on each new platform (3DS, Wii, WiiU). This approach is no longer possible, it is just too costly. Besides, players were annoyed that previous Virtual Console titles were not available at lunch on the next platform, and they were angry that they had to buy again the Virtual Console titles they bought on the previous platform.
This and other factor lead to the cancelling the Virtual Console single-title approach, and the new L-Classics multi-title project. Now, the goal is to:
- ship many titles (30+) on short schedule
- maintain all the titles in the “long-run” while still adding features
- ship everything very quickly and for a very low cost on the next hardware
There were a lot of talks about code recompilation, as NERD was very busy on doing that for their GameCube emulator, while iQue was also doing this for their N64 emulator.
The NES emulator would be replaced with the one used on the NES Classic Mini developed by NERD in 2016, which was after development of the Switch Virtual Console started, or at least was concurrent with each other, frankly I don't understand why Nintendo has like 3 NES emulators for Switch now. Clearly, during 2016, after the development of DS Virtual Console emulator, NERD started to have some real influence on emulation within Nintendo, to the point of having NES, SNES, GB, GBA, DS and GameCube emulation today… and maybe more? For real though, NERD seriously cooked there, like, I feel like they did almost everything at the same time.
The initial idea was to have a version of retro NSO to contain NES, SNES and N64 in one app, so the approach that I quoted about was very serious on having easy to maintain but also future proof emulators for long term development. Obviously though, this did not happen in the end, probably for similar reasons of cost, as it could just be easier to develop and test when it's seperate.
One of the key things that NERD made a point on was to automate testing with controller replays to make sure nothing has regressed in testing after updates. I don't think this is a bad idea, actually.
(In retrospect, seeing SNES Mouse replay feature in the latest SNES NSO update from September 2024 is actually pretty positive because it means it is considered as a serious feature now.)
NERD also makes it very clear that L-Classics is absolutely long term and really insists on this aspect:
Finally, and this is the most critical issue.
We must make sure the whole L-Classics application, with all the emulators, can be supported and maintained for the many years to come. We want to be able to quickly add new features, new games, new emulators. We should make sure that all emulators are well integrated. For example, we should avoid duplicating code as much as possible. And when possible, we should refactor each emulator to have similar behavior.
We understand that it may require a lot of work on your side. But, it is NERD opinion that this initial time investment will have a very positive impact on the future of this project.
So if there's anyone worried about the future of the retro games on Nintendo Switch Online, this really seems like a project that Nintendo takes very seriously. This is kind of reassuring that finally, everyone is on the same page, and not just doing their own thing, there's a lot of back and forth between teams.
I'd like to do the reminder that Nintendo had literally THREE DIFFERENT NES emulators running on Switch:
iQue's NES emulator which almost happened for Switch VC
NERD's NES emulator from the NES Mini and powering NES NSO
Intelligent Systems' Wii U NES VC emulator powering the english translation of Fire Emblem NES and even Luigi Bros. in Super Mario 3D World on Switch.
Can I comment how very poorly planned this was?
I even suspect the NES emulator on the new Mario & Zelda Game & Watch is a different one again, though, that one is a lot more understandable in terms of hardware and optimization required. It's only since the planning for the NSO that we know that they finally started to stop making a mess (though Fire Emblem NES… ugh).
The development of Nintendo 64 emulation on Switch
Considering that all we have is only iQue's side of things, Nintendo 64 emulation is basically all we can talk about, more or less.
Maybe I need more context on top, but I'll be frank, I'm not gonna be on the side of the developers here. I tried not to be that way, but seeing these leaks, with discussions with other people on the matter…
I really think N64 emulation should have been managed by people with more experience. I am really sorry if I become seriously harsh on this section.
To make their Nintendo 64 emulator from Wii U to work on Switch, there were several issues that stemmed from the Switch, here's the most important ones:
The CPU JIT recompilation performs worse on Switch due to security reasons. (Small explanation: JIT basically means real time recompilation as you play, "Just In Time")
The graphics rendering needed to support another graphics API as on Wii U, it used another unique one. So they looked into Vulkan API, which was the brand new one that could work everywhere.
To sum up the CPU JIT topic, there was a lot of back and forth between iQue and NERD about the specific topic of basically recompiling the game in advance and rely less on real time recompilation for performance.
That's something NERD has done to GameCube emulation and was honestly pretty easy to do in advance because the overall GC architecture made this easy to automate. You can't really do this on N64, so iQue opted to basically "record" recompiled parts and put them alongside the game, doing real time recompilation for stuff that they didn't precompile. There's not much else to say about it, it's really not the part I'm going too wild about.
To me, the biggest failure of N64 emulation is not that it is unaccurate in general, to me I think full accuracy is kind of unnecessary. I don't really like MVG's focus on timing emulation on his latest video about N64 emulation, I think it's not the main issue. However, I believe graphics can be emulated a whole lot better, and that's the real failure for me. It was really obvious in the launch of N64 NSO, but to me, it's still that way now.
A lot of the problems were already there on Wii U Virtual Console. You can speak to Zelda Ocarina of Time speedrunners about that. But instead iQue chose that they should port their renderer to Vulkan. And that's not me saying it, here's iQue's N64 emulation schedule development from March 7th, 2017 outright saying it.
Translation: Vulkan port (provisional, expected work time 2 months)
N64 emulation currently, unofficially speaking, owes a whole lot to Vulkan. We wouldn't have a performant highly accurate renderer that is parallel-rdp without Vulkan. It was literally impossible without it. RT64's hackless approach to graphics rendering also wouldn't exist without DirectX 12 and Vulkan.
And considering how at N64 NSO launch, the bugs were still there, or, should I rather say it, even worse, to me it shows that they just ported their work and did not do anything to make advantage of Vulkan's specifics to make N64 emulation even better from here.
In a later description of how they handle graphics, from September 2017, I see this part:
This seemed to have been emulated correctly even on Wii U, so I'm not gonna be picky about this. But I will still be because sure, dealing with stuff that is more of a result of a bug is annoying when you're an emulator developer. Well the thing is: This happens a lot. This is pretty much part of your job to deal with the mess of old game devs. This isn't unique to N64, and at least, if I deal with something like this, well, you can complain all you want, but what you do is perform specific tests on the actual system to understand how it works.
When people talk about "Nintendo has all the documentation but they can't figure out N64 emulation" to me they don't know what they're talking about. The amount of times when official documentation can outright be lying to the developer, the times where you deal with a highly specific bug that could happen to the hardware and isn't explained at all, one of the things that I think is that you should NOT trust the documentation, you should trust what the original hardware is actually doing. And many emudevs I know stick to this adage.
Remember Sloop? The leaked GBA emulator demo build that we got years before the GBA NSO launch? Well I remember writing two posts about it especially when I talk about how it shows the use of a GBA flashcart where they can go back and forth with real hardware save states and a homebrew to test the screen output, as well as a ROM that performs tests.
Well that's the proof of actual dedication to the craft. They're paying attention to real hardware tests. They might even write some of their own tests.
Well that's what I hoped for when NERD received a N64 flashcart in 2017. A few people may remember that I said this around February 2017 in some places. I hoped NERD developed a N64 emulator alongside the rest which showed a lot of promise. And then it seemed like they didn't make one… or did they?
Introducing "Mushi"! It seems NERD has worked on an emulator which I am not fully certain it is N64 to be perfectly honest, but I don't believe it is GameCube, which is called "Hagi", and within the context of it, I believe "Mushi" is NERD's N64 emulator. It uses software (CPU) rendering for graphics, on which iQue's developer noted for its accuracy (this is not really evidence that it is accurate though). That's all the info I have about it, unfortunately.
Anyway, from there, iQue's goal was clear: Make all of the Wii U VC games work on Switch (including unreleased ones like Smash Bros., Banjo-Kazooie and Blast Corps, yep), and look into other games later. They also looked into rollback… and an Android and iOS port?
Yep. I don't know where the idea of iOS and Android port came from.
When it comes to rollback, I think considering the way N64 emulation works in general across everything including unofficial emulation, it's pretty hard to do, and could just fill your RAM extremely fast + save state processing time could prevent things to work as well as they want.
There's also talk about Nintendo wanting to put N64 emulator development to Panasonic Vietnam for September 2019..? That is honestly curious and apparently has put some iQue employees wondering about why this was put into consideration. NERD was also talked about as having high technical skills and capable, but "not good at mass production process". That last part may seem confusing, but I believe they're talking about more like the process of putting the work required for software for public hands.
Personally though, I don't believe N64 emulation was ever given to Panasonic Vietnam in the end, I still have reasonable belief that iQue is still around for it, for reasons that I cannot invoke. Or, if Panasonic Vietnam is involved, I think they're mostly just a support team helping across all of NSO emulators, one of which is confirmed to be GBA.
And now?
And that's about it, really. All info ends at around March 2018, so anything that happened past that is still very much a secret.
I'm sorry that I'm still giving iQue developers not a pretty good look from me. I expect that we're still missing a lot of context, I would have certainly loved to look at the internal discussions that happened after the disasterous launch of N64 NSO. To me I still believe that Nintendo hasn't done a good job about N64 emulation, especially when the emulator was truly in constant development for 10+ years. But as much as I'm not an expert on Nintendo 64 hardware, I still have some understanding of it as a modder and as a 64DD emulation developer.
If Nintendo truly wants to do something long term, then having emulation that does good enough accuracy (aka not what's in N64 NSO) with legit performance tradeoffs should be their goal. The goal is to respect the legacy of their games. The least they could have done is at least good graphics emulation. I'm not even asking for super accuracy, this is not possible on Switch, but at least to actually use the technology at their disposal to do it well, and I consider that they did absolutely not.
When it comes to Switch Virtual Console, I know a lot of people would have wanted that instead, but on a personal level, I never liked Virtual Console since the Wii. And what I've been seeing about Switch VC was none other than a continuation of it but with online play added to it, well… I'm not interested. I believe that playing retro games shouldn't be a niche thing, and I'm sure Nintendo would think so.
But it sure is interesting to have a glimpse of how it was like with some details here and there. I like development details like this, and I hope this was an interesting read.
vaporwave
titsay
gummygunk
yousharknotpass
dededos
izzy806
tangentwithtanner
prguitarman
blakekathryn
dailybridgerton
