Ed Mello

@TECHNOuchi Are you telling us that Konami was working on a sequel for Space Manbow back then? I had never heard that before! 😳 Were you involved? Space Manbow is one of my favorite shmup ever, I absolutely love the game, and the soundtrack is probably my favorite SCC soundtrack ever.

スペースマンボウも新録とHDリマスターアレンジでCD出したかったなあ…。というか今の技術でリマスターされて発売されないかなあ。幻のスペースマンボウ２もあわせて。

３６年前ですが…スペースマンボウのサントラを作るときSCCの開発用マザーボード使ってSCCアレンジなるものを作りました。関戸先輩によるステージ１BGMをペーペーの新卒社員だった僕が右も左も分からないまま頑張って作ったものです。（左） それを先日改めて耳コピしてREアレンジしました。

@baNesaka @kumokosi Hi. I am a publisher for the Atari 7800 platform. Would you be open to port Metal Cancer for the 7800? It uses the same CPU, and in same cases it is more capable, mainly offering more colors to choose from and more objects per scanline.

そういえば昨日久々にBOOTHログインしたので、メタルキャンサー体験版のDL数を確認したら300超えてました！ 説明書差し替え前と合わせて450以上！皆さんありがとうございます🙏 #nesdev

WIP of #slayin on the #atari7800. #retrogames #pixelart youtu.be/IGPFa-gfiG4

Doing some #Atari7800 work and thought I would translate #Slayin. I'm particularly happy with how cute the Knight turned out. ^_^

@PortIsland1987 @klaxmsx Konami was my favorite game company in the 80s, and I loved all the games it was putting out for the MSX. Which makes you one of my favorite game artists ever. Your work is nothing short of stellar. Thank you for helping create such amazing games.

ネオ・コウベ・シティの夜景は88版で描いていたが、SDスナッチャー はMSX2、色数が使え発色も良かったので雰囲気を変えた。奥のビル群は赤系、手前は青系でそれぞれ作画。その2枚を重ねて多重スクロールさせ奥行きと動きを出した。

@yazioh @MijuBaku2k2 Is this being made for the MSX? It looks amazing!

@MijuBaku2k2 This image is based on the limitations of the MSX SCREEN2, so it should be possible to display it on a single screen on the ColecoVision. Whether D.C. can port it as a game is something we won't know until we ask a cross-porting expert like @Ed_Opcode .

（２色制限がない）スプライトなら描けそうな体力だったので、デビルクラッシュ #MSX IF に追記 SCREEN 4化しても２枚重ねしないなら結局スケスケスプライトなので、ほぼこんな画面になるんだよね　きっと

More progress on the title screen idea for our #Colecovision game. Would you want to press start? #MSX #pixelart

Started sketching a title screen for our #Colecovision game within the usual limitations. Lots of work is being done so stay tuned for new footage soon. #MSX #pixelart #indiegame

Some sketches of the main player in our #Colecovision game. #MSX #conceptart

Doing a bunch of sketching of our game's main character. He is going to explore wild jungles and crumbling ruins. Whatcha think? #IndieGameDev #conceptart

Our game running on an ACTUAL #Colecovision !! Sorry if we keep showing the same section, but lots of basics are still being worked out. #MSX #pixelart #IndieGameDev

@GijselDries @pixellicker This is a ColecoVision, so everything must be custom made in Z80 assembly.

@pixellicker With what engine did you make this?

Added enemies and climbing to our #Colecovision game. Also we decided that our main character needed a refresh. Who wants plain old Indy style explorers when you can have a... wolf?! #MSX #pixelart #IndieGameDev

@BananaBytesBr @pixellicker I’m more inclined to flicker sprites evenly since it produces the best results by allowing more sprites to rotate. Goonies for the MSX is a good example of why prioritizing sprite flickering isn’t ideal—the enemies flicker badly with only two sprites to rotate.

@pixellicker About sprite flicker, that was something anyone who had an MSX was very used to. Some devs tried to avoid it as much as it could (Konami had some insane success doing it) The trick, I think, is to smartly decide which sprites should flicker :)

More progress with container objects that spawn treasure. Scanline flicker isn’t too bad either. #Colecovision #MSX #IndieGameDev

Early build of our #Colecovision game with some basic collisions and the main player doing his thing! Super excited to see it running on hardware. #MSX #pixelart #IndieGameDev

Updating the player sprite to be a little more scanline friendly. Also added a couple enemy ideas. #screenshotsaturday #colecovision #MSX #pixelart

@nishikazuhiko Will the built-in IO devices be enabled this time? R800 had DMA controller, interrupt controller, better memory mapper (16MB), and more, but was all disabled by the TurboR. I never understood why. Were those functions meant only for the planned MSX3?

次世代R800CPUについて ずいぶん迷いましたが、R800の次のもっと早いCPUを作ることにしました どういうものになるのかは考え中ですが、とりあえず名前だけは決めました R900です R800の数倍早い奴に仕上げたいと思っています 細かい方針は決まってるけど、正式にはイタリアのDEVCONの後に決めたいです 任天堂の社長であった故　岩田聡　氏の作られたHALNOTEやその兄弟でアスキーが改造したMSXVIEWがこの早いCPUでちゃんと動くようになります 幸いHAL研から私どもにHALNOTEの使用許諾もいただきましたし、生前にご本人はあと数倍R800が早かったならなあと言っておられたと聞きましたので、高速R800で日本の生んだ最高傑作ソフトがよみがえり、世界のMSXユーザーに再評価してもらうことは岩田さんへのオマージュであり、今の日本を元気にするために必要なことだと思うのです MSXDIYのMSXturboR+で動きます

@RCAVictorCo Ok, please disregard my previous message, the V9958 INT pin is open drain, that is the V9938 data sheet. 😅 Do you have any idea how INT is implemented in the TMS9918? It clearly is not open drain...

This is the most interesting cell inside the R800 CPU... An 8-bit odd parity generator with individual bit enable/high drive power! You can control each bit input individually, but all enable signals are tied externally in the R800 CPU. Why does this CPU need parity?

@RCAVictorCo Hi. I have been trying to contact you regarding the INT pin in the V9958 chip. Trying to figure out how that output is implemented. Not the logic, but the port signal itself. Is it totem pole, open collector, does it uses an attenuation resistor, etc. Thanks!!