Beating the limitations of the TurboGrafx-16/PC Engine | White_Pointer Gaming

[@braveinsanity6843]

I loved the Turbo Graphics 16. I had it for like a week when I was younger, but my brother stole it and sold it for drugs.

[@WhitePointerGaming]

Oh dang, sorry to hear that.

[@RemoWilliams1227]

Dude I'm so sorry to hear that. In like 90 he did? Dang I somehow lost mine over the years before I got back into games (and had turbo CD and an express 😢). Hope your life is good these days brother.

[@Fry09294]

What ever happened to your brother if you don’t mind me asking

[@braveinsanity6843]

@@Fry09294 He ended up doing a 3 year stint in prison and completely changed his life when he got out. He now has a wife, 2 kids, motorcycle, nice car, nice house with a pool, and is a journeymen plumber that only has to take the test to become a master. He makes very good money. We weren't close during childhood, he was pretty abusive, but after prison, completely different person. The system was technically his as well so I can't be too mad, but damn was I excited when he brought that home. I let him play my SNES and Genesis and I thought he was returning the favor.

[@MaxOakland]

Noooo that’s horrible!

[@ChannelCortez33]

Excellent video describing the tricks developers used to make magic with the Turbo Grafx 16/PC Engine. And the fact that the console had an 8 bit CPU only impresses me more to what Hudson had created and reaffirms the dedication of what developers to push the hardware to the limit! In retrospect, it somehow manages to be my favorite console of both the 3rd and 4th generation.

[@noop9k]

SNES CPU is only 16-bit internally, from outside it is also a 8-bit 6502 drop-in replacement, just faster and can address more memory. That CPU IIRC was created as an upgrade for the 6502 in Apple II, used in Apple IIgs, which was used as the dev system for SNES. SNES audio (SPC700) was also probably inspired by Apple IIgs, even if not an exact clone, has somewhat similar capabilities.

[@salvatronprime9882]

PC-Engine will always be my favorite childhood console ^__^ It had a style and ecosystem entirely unique that will always be special.

[@fattomandeibu]

The animated tiles thing was used on several C64 games at the end of the '80s, which is even more crazy when you consider the 1MHz CPU and limited RAM(the 64kb was shared between the graphics and CPU program space, you couldn't just bank switch or load in more tiles when the game is stored on cassette tape as most C64 games were, new data could only be loaded between stages and in a linear fashion) available.

[@noop9k]

Quite a few NES/FC or GB games did this as well to simulate parallax scrolling. The same method, called preshifting, was used is multiple technically advanced games on the PCs that had no smooth scrolling whatsoever, like Atari ST or ZX Spectrum (See Cobra, for example) Or, IIRC, in some MSX1 games. R-Type on ZX Spectrum did not do preshifting, but used incremental pixel scroll for some areas of the screen and tile-based animations with the rest.

[@Bofner]

I've done some hobby work programming for the Sega Master System and Game Boy in assembly. Getting those parallax effects or a HUD that doesn't scroll vertically OR horizontally is a really fun and interesting challenge, with many different ways to go about handling it. These are some really fascinating examples! I always wondered how the TG-16 got away with some of its more impressive effects with just one layer, thanks for sharing!

[@kwkfortythree39]

Did you achieve that in the Master System?

[@Bofner]

@@kwkfortythree39 I've got one video on my channel of a little parallax scrolling demo I made for the SMS, and I've taken a look behind the code as to how the SMS version of Y's has its static HUD while the screen scrolls 4 ways. I plan on making a video about it actually, and have a script written, but it stil needs a lot of work to convey the complexities of assembly programming in a way that anyone can understand

[@WhitePointerGaming]

The Game Boy at least had a window layer, similar to the Mega Drive's window plane, which allowed it to create stuff like static HUDs and text boxes without much trouble. Of course, you would know this, I'm just saying this for the benefit of others that might read this :)

[@Bofner]

@@WhitePointerGaming Yeah! Thanks for pointing it out! The window box is also used in some really clever out-of-the-box ways, such as many bosses in Operation C, and Prehistorik Man.

[@PeranMe]

I have to admit I always just assumed the PC Engine HAD multiple background layers, so this was an eye opener for sure! Thanks a lot for this video!

[@TS-yz3ud]

Them developers did a pretty good job with whatever games you were playing/watching to convice you. I'm pretty sure it happened a lot. What games gave you that impression?

[@ajsingh4545]

What gave it away for me was the inconsistency of this effect. For example some games had it and some didn't. Most games that had scrolling also had it for select stages/areas only. Also some had it very choppy (ys 3 and ninja gaiden). So I knew something is up.

[@TS-yz3ud]

@@ajsingh4545 I mean, I personally haven't seen a game with the same parallax as the likes of Pitfall: the Mayan Adventure, or the 16 bit versions of Earthworm Jim, The Lion King, Jungle Book and Aladdin. That's interesting.🤔

[@noop9k]

Its sprite power is actually roughly similar to both of its 16-bit competitors, but with more color palettes to choose from, and SuperGrafx doubles that, giving extra BG and sprite layer.

[@MaxOakland]

I like how you chalked up the advanced techniques to witchcraft 😆

[@blufudgecrispyrice8528]

I think the 16-bit era was the best for console wars. Thanks for your work, love learning about this.

[@darrenmontjar7168]

That port of Street Fighter 2 to the TurboGrafx16 is pure witchcraft. Incredible port.

[@DandyDNA]

10:00 this is insane, the trick to getting the healthbar there is extremely clever-if you pause on a frame where Ken goes above the healthbar (10:49), you can see that the healthbar creates some sort of wormhole that makes Ken taller because it doesn't actually overlap with the background! If you weren't pausing to look though, you'd never notice, so this technique is truly brilliant. Luv the PCE, luv this video. Subbed!

[@WhitePointerGaming]

There's some coding voodoo going on there for sure lol.

[@Michirin9801]

I LOVE this stuff! This is what fascinates me about the PCE's hardware! (Well, that and its awesome soundchip) I also actually really like the GBC in particular for very similar reasons!

[@LeonmitchelliGalette]

HudsonSoft are very experienced famicom devs. So when they made own hardware platform - they made true Famicom 2.0 in every aspect. Also with expansion in mind and CD-ROM as true media for it.

[@develin]

Really love these techy videos that explain console dev tricks. Reminds me of GameHut! I am thanking the KZbin algorithm that I found your channel. Wish you a lot of success in the future.

[@WhitePointerGaming]

Thanks for the kind words, I'll do my best :)

[@DoinThatRag]

Game devs were so clever during this time period. Limited hardware really made them have to think and come up with crazy solutions. What game was that at the very end flying around and shooting dragons and such?

[@WhitePointerGaming]

The game at the end is Lords of Thunder. Awesome shoot 'em up that also takes advantage of the CD format for a rocking soundtrack.

[@waylonoconner9121]

Having drawn tile graphics on a couple of Homebrew releases a d designed graphics for a couple of unfinished titles, the way these guys worked around the limitations is just amazing

[@Johnnygrafx]

Awesome explanation of a rather complex topic! I still don't fully understand it, but I definitely understand it better than I did before watching this video! 🙂

[@loganjorgensen]

The 482 on screen color count of the TurboGrafx-16 is a bit of a misnomer when you consider the 9-bit RGB system palette as a whole not having a tremendous amount of color gradient range beyond what a 4bpp graphic can display individually. Yes it is much easier using 16-tile palettes and 16-sprite palettes than the measly 2+2 the Genesis offered just in asset management alone, but a 9-bit RGB system palette of 512 colors is a lot smaller than the SNES 15-bit RGB system palette of 32,768 possible colors. As a result it was a color system of diminishing returns collectively in the long run Ie. more individual palettes per bitmap but the contrast gradient range being equal to Genesis but less than SNES per individual graphic element. This is evident in live action or CGI based graphics on the TG-16 where it never looks rich enough in gradient quality to do the aesthetic justice and layering more colors together doesn't yield much improvement. Same sort of pitfall Sega CD FMV had with color count stacking creating only a moderate boost in gradient fidelity until the 32X. Even the Shadow & Highlight option on Genesis can only blend 4bpp-maximum graphics together rather than making 5bpp or higher quality because 512 colors only stretches so far. So collectively you're more likely to use the same colors and or shading values across more palettes than ever to use 482 individual colors at the same time, as there isn't enough color gradient contrast present in the system palette to do that effectively. Realistically you'll do graphics in the 256 color range seen on SNES or DOS-VGA which is a pretty good standard to match.🙂

[@acem7749]

I always love videos like this and wish for more. I'd like to see a long play of games that us a lot of trick broken down.

[@connorkiss2614]

Been binging your videos, they’re so so good!

[@gurujoe75]

very educational, thanks.

[@Laserdreamz]

Very interesting, thanks for the video. PCE is my main system but for sure a number of games do look quite flat where these techniques aren't used.

[@Phredreeke]

3:35 worth keeping in mind that while the SNES had 256 color registers it also had color math (add, subtract or average two layers), so the potential number of on screen colors would still be way higher,

[@WhitePointerGaming]

Technically, the colour maths was applied between the main screen and the sub screen, not between two layers. I cover how the transparency effects worked in this video: kzbin.info/www/bejne/gWKnhIh-e6mgoaM

[@Phredreeke]

@@WhitePointerGaming correct, still it allowed for many more colors than the normally stated 256.

[@TurboXray]

@@Phredreeke but it was never used as direct color. That's the point. Because direct color (sub palettes) is how art and details are derived.

[@Phredreeke]

@@TurboXrayI think we have different understandings as to what "direct color" means. The way it is used in regard to the SNES is a mode that bypasses looking up the palette in the color registers and instead mapping bytes directly to RGB values. I don't know of any game actually using it though

[@TurboXray]

@@Phredreeke Ohh.. I was talking about the direct "use of color" as in number of colors available impact art - not the 3:3:2 "direct color" mode on the snes. That mode is completely useless IMO because its basically a fixed 256 color palette rather than 256 colors out of 32000 colors (which is a better mode). Act Raiser does use "direct color" mode paired with mode 7 though. All other games that use mode 7 (which is 8bit color) use the indirect 8bit palette mode. But yeah, SNES is already starved for VRAM (and sprites very much so too), and it makes both "8bit" color modes mostly impractical (both vram and rom space).

[@pixelsrnautded9286]

Would love to hear you talk about the Neo geo MVS or AES hardware techniques.

[@WhitePointerGaming]

Definitely considering it!

[@WhitePointerGaming]

Your wish has been granted :) kzbin.info/www/bejne/gpmaaH6BqNhnfs0

[@TurboXray]

Mesen 2 pce emulator is your friend. The status bar in SF2, while yes is a scroll reposition for the bar (background).. it also turns off sprites for that section and then turns them back on at the bottom of it. This forces the sprites to "appear" underneath bar. The PCE can turn on/off the background and/or sprites on a scanline basis. It can change a lot of video register values on a scanline basis.

[@James-fo8rf]

Good video thanks. I remember the pc engines had many arcade ports. A great machine.

[@soraaoixxthebluesky]

Back in the day when frame buffer doesn’t exist. Impressed how creative developers can be especially when they did a pseudo-3D games using a sprite only to create a 3D illusion like racing games or flight games.

[@ArneChristianRosenfeldt]

Amiga1000 was available in 1985, and Amiga 500 was affordable in 1987. But the blitter could only draw wireframes or letters. Is still useful for wide flat shaded polygons.

[@joshuaspringer5589]

Love this kind of content! Keep it up!

[@BenjaminSpencer-m1k]

Remember my cousin getting one of these and a important copy of Rondo Of Blood. The guy who had it imported spent alot of $$ getting it to the US.

[@loganjorgensen]

I kind of thought it would be a bit like the NES in terms of effects setup given one background layer only. Certainly had your work cut out for you on the TG-16 but at least everything was possible with the stock hardware. Certainly with NES and SNES flash carts it was a giant pain in the butt having to support all those helper-chips in the aftermath.

[@IdentityCrisis1581]

I always liked tg16 because it was already dead in the mid 90s when i began collecting. So it felt obscure and unique. And no one else had one. So i got to introduce games to my friends that they had never seen. My only letdown was that it never truly upgraded. All the add-ons used the same hardware other than a memory upgrade. So going from chip games to the CDs never felt like a major difference. It wasn't like the difference between NES and SNES. The biggest improvement was the game music and voice-overs. I always wondered why they never upgraded the processor. Even the supergrafx wasn't a huge leap. When they made the Duo, they should have used the supergrafx chipset, instead of just combining the older tg16 hardware into one unit. But history played out that Nec and Sega tanked themselves with expensive add ons that didn't add much to the graphics or gameplay. Its still my favorite retro system though. I would love to see the homebrew community fully make use of every trick and exploit to squeeze every last bit of juice out of the system and see what it could really do when pushed to the limit. I feel the same way about the Jaguar. That system is the definition of unrealized potential. It was a powerhouse on paper but none of the games used its full capability, and that made it a pass up system. Before KB toys went out of business they were selling the jaguar for 20$, and the cd add on for 40$. I remember that because i was about to buy one just because they were so cheap. But the games were so lack luster that i passed.

[@RolandoMarreroPR]

So many great examples of parallax scrolling on the PCE! I wonder what happened to Ninja Gaiden?!

[@WhitePointerGaming]

I think Ninja Gaiden tried to be a bit too tricky for its own good.

[@ridiculous_gaming]

The TG16, which was created to challenge the NES, was a magical piece of hardware that unfortunately was overlooked by most North Americans.

[@Gorette66]

Nintendo of America's stranglehold on the 80s & 90s video games industry made it almost impossible for competitors (such as Sega & NEC) to achieve success.

[@DancesRainyStreets]

Nice video! Have to watch it again soon to understand everything better, too much noise around here now. With three of the main 16-bit consoles covered, there's only one left. Some consider it more of an arcade machine, but it was competing with the others in the magazines back then, with ads and reviews. Any plans for covering that one?

[@WhitePointerGaming]

Thanks for the comment! As for the Neo Geo... maybe!

[@WhitePointerGaming]

You might like my latest video! kzbin.info/www/bejne/gpmaaH6BqNhnfs0

[@theevilmuppet]

One could argue that the SNES didn't have a proper 16-bit CPU either based on the bus width, or that the Mega Drive (thank you, fellow Australian for not using that silly American name for the console) featured a 32-bit CPU given the register width. Not remotely a criticism of your awesome work - please keep going!

[@rustymixer2886]

Great video

[@mekman4]

Great Stuff!

[@mekman4]

Thank you for the like!

[@WhitePointerGaming]

Thanks for the comment! These videos take a lot of work so it's nice to know people enjoy them :)

[@AltimaNEO]

Sounds very similar to how the Neo Geo did a lot of it's effects. It doesn't have a lot of fancy capabilities, just a lot of sprites and brute force,

[@WhitePointerGaming]

Definitely considering taking a look at the Neo Geo sometime in the future.

[@AltimaNEO]

@@WhitePointerGaming From another video I watched on the subject, it can handle a TON of sprites and like one background layer or something like that. The backgrounds in most games are nothing but sprites. Its insane.

[@ParanoiaDragon]

That might be similar to what's happening here in @TurboXrays Bonk parallax demo. It goes over my head but I believe it's all using sprites for the foreground layer kzbin.info/www/bejne/Z5rUaaGHZ6eXbpIsi=lEUpfJj_wS4PN3Jy

[@WhitePointerGaming]

New video on the Neo Geo! kzbin.info/www/bejne/gpmaaH6BqNhnfs0

[@JoeSim8s]

Great stuff, thnx!

[@AltimaNEO]

Doesnt the Super CD card add additional RAM as well?

[@darrendavenport3094]

Yes it does and the Arcade card adds even more making neo geo ports quite good

[@inceptional]

As primarily a SNES fan who's interested in development there, I like seeing how stuff like this was done on both PC Engine and Genesis too, as the methods employed are almost always available to be used on SNES as standard as well. And, doubly interestingly in particular here imo, is that because the PC Engine's particular sprites per scanline limit and sprite pixels per scanline limit both fall a bit below SNES (16 and 256 on PC Engine vs 32 and 272 on SNES), you can actually do basically everything with sprites on SNES similar to how you see it being done with sprites on PC Engine (and even more in some cases), just with the potential for a little more flicker in some specific use cases if you were to similarly do it all just with sprites on SNES due to how priorities work on each system, which of course usually wouldn't be necessary on SNES anyway as you have up to four times as many background layers to work with there. What it means for SNES is that you can combine these methods you see for faking background layers and elements and such on both PC Engine and Genesis alongside the capabilities that are unique to SNES for some really cool results. Imagine using all of these tricks seen above on top of the four fully-overlapping full-screen background layers available in Mode 0 on SNES alongside the standard transparency effects and such there too for example. . . . Good stuff going into the various details and explaining how much of it works. It's very useful for people to understand this kind of thing imo, both the capabilities and the limitations, especially for potential developers on any of these beloved fourth generation consoles. PS. One little detail with the colours on-screen there: You've listed both the Genesis and SNES numbers including the transparent colours in each palette but the PC Engine minus the transparent colours in each palette. So, keeping them all the same, I think it should read 512 on-screen colours for PC Engine, 64 for Genesis and 256 for SNES, or I think 480 [+1 backdrop colour and 1 border colour] for PC Engine, 60 [+1 backdrop colour] for Genesis and 255 [+1 backdrop colour] for SNES. I'd probably just go with the full numbers including transparent palette colours for each for simplicity. PPS. I just subscribed. :)

[@WhitePointerGaming]

Glad you liked it, thanks for the subscription and the comment :) I'm actually not entirely sure whether the SNES could handle all of those things you speak about all at once, that would tax it quite a bit and would likely cause a lot of slowdown I imagine.

[@inceptional]

​@@WhitePointerGaming A game like Donkey Kong Country 2 running on the stock SNES actually shows a bunch of the effects going on at the same time, so I think it definitely could, but only if the programmer had/has the skills to pull it off: kzbin.info/www/bejne/iIfdm3moa8yjqMk There's full screen, full colour, three overlapping background layers, row/line scrolling for faux perspective and even pseudo 3D on both the water surface and separate floor levels in the background, tile priority switching, transparency effects, dynamic sprite tile loading in/out on the players and enemies, etc, all going on at once there while maintaining 60fps. I'm pretty sure some dynamic background tile animations to fake extra parallax and using some sprites as background elements could be added into the mix there too. Again though, only if the programmer has a good grasp of the system and knows how to optimize things fully. Edit: I should also mentioned that quite a few of the examples on my own KZbin channel use lots of these effects and tricks at the same time too. And a couple of those have been coded up [by some helpful SNES programmers] and run just fine on SNES.

[@WhitePointerGaming]

Yeah but even DKC2 struggles with slowdown at times, and DKC3 is even worse, there's actually quite a bit of slowdown in that game.

[@inceptional]

​@@WhitePointerGaming I don't personally see any noticeable slowdown there in that scene in DK2 that I linked. So, I guess that's a matter of how we each interpret the meaning of "a lot of slowdown". Is it what you are seeing with your eyes or viewing it via some kind of technical frame measuring tool or something? Either way, I personally think it's entirely possible to do something with many of the effects combined at a solid frame rate on SNES. That was just one example with lots of cool effects going on at once that immediately came to mind. But, if you're interested in some other examples, I'd say the likes of Super Aleste and Rendering Ranger R2, which both run at solid frame rates even while stuck in SlowROM at 70% of the SNES' full CPU speed, are great showcases for the potential there: kzbin.info/www/bejne/en6cc2Zsj9t7ba8si=kJCHXEmTkvc9YjWU&t=223 There's three full-screen fully-overlapping background layers, proper transparency effects, full line-scrolling, loads of sprites on-screen, sprites faking background elements, solid frame rate, etc, there. kzbin.info/www/bejne/ip2adWVrfpusesUsi=AagAt3hDuk-461lV&t=783 kzbin.info/www/bejne/ip2adWVrfpusesUsi=DEl0jJjwZ1254VoF&t=1180 kzbin.info/www/bejne/ip2adWVrfpusesUsi=VNpoyVSvrFj_wUeS&t=1372 kzbin.info/www/bejne/ip2adWVrfpusesUsi=5-S5_3chkp4XcFyZ&t=2833 There's often three fully-overlapping full-screen background layers, sprites faking additional background elements, row/line scrolling, transparency effects, loads of sprites on-screen, solid frame rate, etc, there. And, just to emphasize again, these games are both running in SlowROM. So, even if there are a couple of frames of slowdown during the most busy/hectic moments there, they could certainly be removed simply by switching to FastROM and, if necessary, also optimizing the code even further as well. And, if you want another in-progress example, you can check out the upcoming Rex Nobilis too: kzbin.info/www/bejne/Z3KqfniQq7pkasksi=upei2C538M2Eg3Gn&t=1535 That game has levels running in the SNES' 512x448i mode with two full-screen fully-overlapping background layers, an additional third semi-transparent background layer using the colour windows plus HDMA, loads of sprites on-screen, all at a solid frame rate, etc So, yeah, I still think the SNES is capable of doing basically all the aforementioned more traditional tricks alongside the stuff that's more specific to it at the same time, if the programmer knows what they are doing.

[@WhitePointerGaming]

I'm not saying there was slowdown in that specific scene, just that the game does have slowdown in places.

[@CharlesHepburn2]

The CPU was actually pretty beefy. A 65c02 at 7Mhz is no slow poke, whereas it was very efficient in clock cycles per instruction. Having only 1 background layer was its main technical limitation. Its sound abilities weren’t as advanced as FM or PCM of Genesis and SNES. NEC was also seen as nickel and diming consumers due to no RCA composite out or 2nd controller port unless you bought add on devices. It was also more expensive than Genesis by a little bit. NEC should have just released the SuperGraphx instead. With extra ram and another background layer, along with a slightly cheaper price $149, two controller ports, a composite video out and Ghost & Goblins as a pack in, it could have done well.

[@Sinn0100]

You talked about some of the systems specs in comparison to the Genesis and Snes but that isn't the entire picture. The TG-16 held its own for the same reason the Genesis did.... both machines were far more than their VDP/GPU's. For example, both consoles ran with a multiprocessor setup and are faster than an Snes. Sega just flat setup their 16-bit machine like an arcade cab with as little bottlenecks as possible. This gave Sega the ability to punch well above what they should have been doing. For example 99.9% of all Genesis games run in a higher resolution than the Snes. You sure wouldn't have guessed that just looking at their video output specs but it happened. Now, look at what indy developers are doing with the Genesis today. We are finally seeing what one is truly capable of, and it's amazing. I believe if indy developers decided to go crazy with the TG-16, we would see similar results.

[@AltimaNEO]

A lot of cross console ports almost always resulted in the SNES version being cropped compared to the Genesis!

[@Sinn0100]

@@AltimaNEO Very true!

[@WhitePointerGaming]

I talk about this kind of stuff in my Mega Drive/Genesis video here: kzbin.info/www/bejne/iKjHmJR4o8lsi5I

[@randomhajile]

didnt sf2ce on pc-engine have an enhancement chip by way of it being a memory-mapper-chip on the bulker rom-card

[@WhitePointerGaming]

Yeah I think it did, but that was due to it using a non-standard size for the Hucard - 20 megabits, or 2.5 megabytes. It needed the memory mapper because the console only had 2 megabytes of address space. Most other games capped out at 8 megabits, or 1 megabyte in size.

[@rhinox3474]

I miss my tg 16. My brother took mine to college without asking. Had around 20 games. It magically vanished probably for beer money.

[@WhitePointerGaming]

Dang, someone else here in another comment said their brother took theirs as well. That sucks, man.

[@alexisread5325]

Nice overview of the game tricks! The PCE was a lot more powerful than first thought- it can chuck around sprites more similar to a NeoGeo, so it's possible to create an entire background layer with large sprites on top: kzbin.info/www/bejne/oYaanqyLrcqgkMk Interestingly, the soundchip can be better than the Megadrive and Snes in that it has cleaner pcm playback. Another sprite capability is rotation and some scaling: kzbin.info/www/bejne/d4HQhniYfqpjaqM Colour is the main strength of the VDP though: kzbin.info/www/bejne/gH6sdX17q7l7brM The cpu is actually quite powerful though, and could do comparable 3D: kzbin.info/www/bejne/iaHCo2ZsbpJslZY

[@WhitePointerGaming]

The TG-16/PCE could not do sprite rotation and scaling, not even the stock SNES could do that. That video you linked to is running on the SuperGrafx, an attempted upgraded follow-up to the PCE that was backwards compatible, but was its own thing (with only around 6 games ever made specifically for it). Despite that it's still not a proper hardware rotation, they have just been animated to rotate, similar to how Sonic 1's bonus stages were done. Same story with the 3D demo you show, that's once again running on the SuperGrafx. So don't confuse the SuperGrafx with the original PCE/TG-16.

[@alexisread5325]

@@WhitePointerGaming I didn't say hardware rotation and scaling. It's likely that this technique is similar to the Sonic1 bonus stages, so the fact that's It's shown on the supergrafx doesn't mean it can't be done on the PC engine. Similarly for polygons which are typically cpu bound- the supergrafx has the same cpu so polygons should perform identically? The supergrafx can do some clever effects with the two vdps that the pc engine can't, like transparency kzbin.info/www/bejne/bWaslXqFZq5kpZYsi=bqhwt1F8Rex32-LL

[@orlandoturbo6431]

Thank you for explaining all the tricks they use to make games for the PC Engine(TurboGrafx16). I wonder what Sega games could NEC made for the system. Could there been a Sonic the hedgehog for the PC engine. I wish they have made more fighting games for the TurboGrafx16; but somebody thought Americans was tired of fighting games. 😂😂😂

[@WhitePointerGaming]

There were actually some Sega games on the PC Engine, oddly enough, such as Outrun.

[@orlandoturbo6431]

@@WhitePointerGaming What would Enternal Champions look like on the PC Engine. Probably have more colors on screen and brighter.

[@kwkfortythree39]

Would not be the Master System or Mark III the first console to have the scanline counter?

[@TurboXray]

It would. It does have a built-in scanline interrupt system.. but you can't change the Y scroll on the master system.. which makes it more limiting. Even the NES, with external interrupts (and without) could change the Y scroll position. The SMS also struggles with handling lots of scanline IRQs, where as the PCE high clock speed is pretty much made for that sort of thing (even more efficient than 68k doing scanline interrupts.. which is why Sega opt'd for a VDP scroll memory implementation.. and hDMA for snes).

[@kwkfortythree39]

@@TurboXray can you please elaborate that last part of MD's and SNES' approaches? Thanks!

[@WhitePointerGaming]

Yes, I say that the TG-16 was ONE of the first ;) I acknowledge the SMS to be the first one in this video: kzbin.info/www/bejne/hqHHo5ifjcSIfK8

[@TurboXray]

@@kwkfortythree39 Mostly that lots of interrupts means lot of overhead for context switching in a frame. This is very true for the 68k cpu, because the call takes longer than most processors and more registers need to be saved, etc. So it makes more sense to put things into tables which the device (VDP) can just read out and apply on whatever basis (scanline, 8 pixel block, etc). The SNES cpu is a fast context switching design for interrupts, unlike the 68k, but the lower clock speed means it's relatively more taxing. Plus, the SNES has a lot more registers it needs to update per scanline for effects compred to either the MD or PCE, so the hDMA is a really fast way to get data to those registers quickly (timing matters too). Don't get me wrong, the MD and SNES have the option to do scanline interrupts too - it's just rarely used because there are much faster/better methods (VDP tables or hDMA tables). On the MD, a couple of things can only be done via scanline interrupts (color changes, or changing the v scroll table mid screen, etc). On the SNES, it's sometimes faster to use scanline interrupts than hDMA if you're not using that many - but this rare. And like the MD, there are a few super rare effects that can only be done via scanline interrupts (but these are for demoscene type FX). But in general, both the MD and SNES were designed with a newer approach/design-philosophy than simply using scanline interrupts via the cpu.

[@thezood]

This fixation with the number of bits in the processor architecture has been plaguing us since the 80s. It wasn't long ago I was yelled at because our company used 32-bit office, the guy claimed 64-bit was "much better" (and he didn't even use big spreadsheets or anything). I think Sega and Nintendo started that nonsense.

[@Poco-tr9xw]

Of topic sorry. The world map every one uses is incorrect. It make the the northern lands look much much bigger than they really are.

[@Troll_Ha]

The snes was also not a true 16-bit console, could you make a video about that?

[@ajsingh4545]

Blasphemy 😮

[@bluedistortions]

What, due to the 8-bit bus?

[@Adibal_Gamer]

Pc engine was officialy distributed in France by Sodipeng man....

[@WhitePointerGaming]

NEC didn't technically officially release it in France and Sodipeng never had an official arrangement with them. What Sodipeng actually did was grey import Japanese PC Engine models and distribute them with French instructions and appropriate AV cables to play on French TVs. The only European countries the console was officially released in were the UK, Spain and Portugal.

[@charliekahn4205]

Was this console designed with an MMU as a gimmick?

[@DmSayr]

No-one in my capital city carried any TG-16 games and I was stuck with Kieth Courage until emulation creeped into my life...e-m-u-l-a-t-i-o-n...aaaaaagggghh...

[@Jolly-Green-Steve]

2:45 This was stupid the console was called TurboGrafx16 not TurboCPU16. It's not false advertising because the Grafx I mean graphics were 16-bit. Having only an 8-bit cpu has zero effect on the visuals. The only thing it might limit is frame-rate and objects on screen.

[@orlandoturbo6431]

PC Engine Golden Axe and Strider could have been better if they use the full potential of the CD. Was it the ram that cause the games to look terrible.

[@SuperNofriendo-HAHA]

The snes was also not true 16-bit, you should make a video about that.

[@joshfacio9379]

How so? Ive heard that once before years ago but knowledgable people would get into the conversation and verify that it was 16bit. Either way id love to hear more about it!

[@104d_3rr0r_vince]

Actually it was an 8bit machine as you said. But SNES is 8bit too. The databus is 8bit. With that in mind, if snes is a 16bit machine cause its cpu is 16bit internally, then the megadrive is 32bit...

[@ArneChristianRosenfeldt]

68k has a 24 bit address bus. I think it is shocking that Motorola did not offer a 68EC10 by 1984. So does the 68k need two cycles to put a register on the address bus? Or do the 8 address registers actually sit on a 24bit bus? Also MUL is so bad on 68k. At least after the first 3d games on AtariSt, Motorola should have improved fixed.point math .

[@104d_3rr0r_vince]

@@ArneChristianRosenfeldt 24bit address is correct, but it is for the amount of RAM that the system can see. Actually is 23bit with the last bit acting as even/odd but yes, 16MB of RAM. As for the EC version, I think it is pointless as the MMU unit on the 010 was external. 2 cycles indeed.

[@ArneChristianRosenfeldt]

@@104d_3rr0r_vincea special case would be to write a single byte. Then somehow the 24 bits need to be routed out of the address register to to the (25) pins. Even N64 games and Quake on PC ignored the MMU. I just think it is so weird how Intel included so many queues in their 8086 and 8088, but 68k has fixed timing like 8-bits or RISC. Patents? Queues are needed to really saturate memory and ALU.

[@TurboXray]

The data bus has nothing to do with it. If any of these machines had a super hi-speed 1bit data bus.. it wouldn't make them 1bit systems. That's ridiculous. What makes the PCE "8bit" is that the CPU registers are.. 8bit. The SNES is 16bit because the processor registers ARE 16bit. And yes, the 68k feels NO different than if the ALU was 32bit.. because all the registers are 32bit and support full 32bit operations! I have no idea why people keep focusing on the data bus. Clearly don't have an understanding of what actually matters.

[@104d_3rr0r_vince]

@@TurboXray So can it send 16bit chunks at a time? If it just sends 2x8 then this is the definition of bottleneck. The exact thing happens to the 68000. If you are doing 32bit calculations, you need 12 cycles instead of 4.

[@cash5627]

Instead of it being a weak "16bit" machine, I've always thought of the TG16 as the beefiest 8bit game console ever!

[@KarnovJr]

Im simple. Someone posts Turbo content i click sub.

[@WhitePointerGaming]

Thanks for the sub! :)

[@iwanttocomplain]

It's so funny. The PCE had a 7.16Mhz 6502 based cpu, designed by Hudson. Which is extremely fast for a 6502 style cpu. The SNES has the same 6502 base, but only 2.56Mhz. It has a 16bit ALU! But limited 16bit instructions, maybe 4, for multiplying, moving a decimal point, stuff like that. All completely pointless because the bus was 8bits. They pulled the same trick with the N64. The bus is memory speed and running games needs lots of it and for it to be fast.

[@WhitePointerGaming]

SNES usually ran at 3.58MHz, but could slow down to 2.68MHz. There are other differences in the architecture, too, even though it's based on similar tech.

[@iwanttocomplain]

@@WhitePointerGaming opposite.

[@iwanttocomplain]

@@WhitePointerGaming I'm working on a complete knowledge of the system. I would be the only person with this knowledge.

[@iwanttocomplain]

@@WhitePointerGaming if it makes you feel better alot of the potential of the snes library was affected by politics, affecting quality.

[@TurboXray]

"But limited 16bit instructions, maybe 4, for multiplying, moving a decimal point, stuff like that. All completely pointless because the bus was 8bits." I swear, where do people come up with this stuff. That is 100% not correct at all. And the N64 has nothing in common with the SNES.

[@jimedd2561]

Seeing this makes me see how Nintendo and Sega did little to nothing to improve over the PC engine 😮

[@apollosungod2819]

Hey some huge spoilers for you because you don't seem to know... basically the TRUE reason why the NEC Turbo GraFX 16 failed in North America is because Hudson Soft and NEC headquarters in Japan entrusted the subsidiary branch (a subsidiary branch is NOT the headquarters of a company and can never be... this is harsh lesson to Sega Genesis fanboys) to launch the NEC PC-Engine in North America by 1988 however the subsidiary branch management decided that the name "PC-Engine" needed to be changed and that the plastic shell design also needed to be changed which by all accounts required an entire YEAR wasted doing that... then what sealed the doom of the NEC Turbo GraFX 16 was the fact and ONLY fact that will make sense in that again the subsidiary branch were apparently looking at the sales numbers they could potentially estimate for the U.S.A. (btw there is a problem of subsidiary branches back then minus Nintendo of America of completely ignoring Mexico and barely making a presence in Canada and French Quebec so when you take those two regions where middle class wealthy people existed and were technology literate and if the marketing and distribution was very subpar then that will translate to major problems later) which means the fifty states of the Union and could also use the additional territories but back then being that NEC Turbo GraFX 16 was new and that NEC America had to overcome themselves instead of doing proper research, apparently they felt too confident that they could reach a particular sales number of units sold in a year's time frame and they just decided to order something like 700,000 TG16s for the launch in 1989 which apparently makes it clear that the NEC America management staff were convinced that they were actually going to sell that many units at $200 dollars a pop.. eh ... just because? Therefore a clueless American public and quite possibly snubbed Canada and Mexico... nevermind that even in 1989 it was not easy for all fifty states and towns within to have retail stores to buy a Nintendo NES even though Nintendo had the advantage of building distribution relations earlier on. Therefore we can look back and confirm that many of the shipped TG16 units simply sat in stores while some indeed sold but the proportion of units sold to the 700k number was disproportionate during the first couple of months which means that when these TG16s were just sitting there in store shelves during 1990 year that they were becoming a loss to the retail shops who were convinced to order them so when new shipments were available for more units to order, most of those retail stores opted not to order more TG16s. Then combine that with the then rising EGM magazine article with data that was alleged to have been supplied by then Sega of America's management staff who later made a special contract deal with the EGM publisher to make an additional official Sega quarterly publication (Sega Force) and the then rising hardcore gamers who were teenagers rising into young adult gamers and the remaining arcade and Atari gamers who had been gaming since the early 1980s and were still amazed by and interested in arcade and the newer tech from Sega and NEC and Nintendo and as such an image that somehow the TG16 marketing was lying became a thing... however that is a minor issue.. the real problem was the NEC America management being too over confident in how many units to order and ship which is also the SAME problem faced by Michael Katz who was the new manager hired by Sega headquarters in Japan to be the main manager of Sega of America (a subsidiary branch) and according to some old numbers it was said that Michael Katz's marketing team were confident that they could sell between probably 700k and one million Sega Genesis systems and note that the big Sega Genesis package in 1989 included two gamepads, Altered Beast ROM Cartridge and the Sega Genesis system (the Sega MegaDrive because again Sega of America's management had some weird ideas even though they failed to market the Sega Master System and decided they did not like the MegaDrive name so they went through several name changes until they settled on Genesis and most likely also WASTED almost an entire year where a North American MegaDrive launch could have happened by December 1988 to even say February 1989... but more important is that back then the Japanese 1988 launch MegaDrive shipped with one gamepad and no game for roughly $210 USD equivalent in 1988 and by 1989 SoA was selling the Sega Genesis with an additional gamepad and a free game for $190 USD which tells us that they were losing money giving a free game and gamepad so if a certain number of units were not reached then they could not expect a percentage of one million buyers to buy additional game software which is a huge problem with the truest reasons why Sega of America's management led Sega as a brand and company down to bankrupcy.

[@ParanoiaDragon]

Another problem that multiple people close to the situation(namely, people I knew at TTI, TZD, Icom, & WD) all said the same thing, that trying to get games from Japan was basically like pulling teeth. NEC of Japan shut down tons of games NEC of America wanted and then later Hudson Soft of Japan shot down TTI's game list. Whatever truth there is in the whole Mortal Kombat for TurboGrafx-CD debacle is some evidence of that, the Japanese branch shooting down the idea of Americans wanting fighting games. Plus, Electronic Arts giving NEC America the finger I think didn't help because I think sports games at least in North America were big time. Very few sports games came out for the tg16, and none other than maybe Champions forever boxing and Andre Panza kickboxing had real people in them. It was always made up teams and players of the few games that did come out. Supposedly when presenting the TG to various companies, a representative of Electronic Arts got upset when a representative of NEC said something along the lines of "Are you up to the challenge" if making games for the TG. Very bizarre, I can't imagine any sea was trying to be a jerk, but EA allegedly took it as such. However I did recently uncover that EA did have a deal to release tons of games in Japan for the PCE in a joint venture with Victor Musical Industries. However, only one game(Ferrari Formula One) was named specifically and it was pushed back and eventually canceled. I haven't yet figured out what happened between that joint venture. In one of the articles I found, it mentioned some ridiculous number of games they wanted to port over mainly from the Amiga, something like 150 games. Which obviously never happened. John Madden did eventually come out but that was a completely separate thing done by Hudson Soft, not Victor Musical. Possibly one game that does have a connection is Shadow of the Beast which was released for some consoles by Electronic Arts but then the PCE version in Japan was released by Victor Musical. But I can only speculate.

[@avjaarsveldt]

I loved, no LOVE Splatterhouse and Jacky Chan on the PC-Engine. Really remarkable games as well.

[@ArneChristianRosenfeldt]

Boycott of 50 Hz flicker is the only right way. PcEngine can output RGB on the expansion port without modifications inside. So no need to call that NTSC .

[@TurboXray]

The RGB output is NTSC spec though. It has no option for 50hz frame timings.

[@ArneChristianRosenfeldt]

@@TurboXray and this okay as I have learned that many TV in PAL land accept 60Hz RGB ( RGB only , no composite ). Vertical deflection is controlled by software

[@mark6302]

wow I always thought tg and genesis were like neck and neck hardware wise

[@curtisnewton895]

wtf is a white pointer ?

[@WhitePointerGaming]

It's a shark. Another name for the great white shark.