This demo requires a flash or development cartridge with
■ 8 Megabytes capacity
■ Support for the SSF2 mapper
e.g.: TiTANDEV-MD, Mega Everdrive, ToToTek MD-Pro 64M
Due to extensive usage of a previously largely undocumented
hardware register, it will not run properly on all MD systems.
Our tests have shown that around 30% of Model I and 5% of
Model II systems experience issues. This is due to a change
in the manufacturing process of the video chip.
More detailed information will follow in the tech docs that
we'll be releasing in the coming weeks.
This demo will only run on PAL / 50 Hz systems.
At the moment, this demo will not run on ANY emulator.
Emulator developers can expect full support from us in order
to fix this (Please contact us!)
This post has been edited by Oerg866: 16 April 2017 - 01:00 PM
Can you describe the testing process if this doesn't work in emulator? Was it a case of writing code and then flashing the ROM over and over in flash carts? Sounds painful.
I've created my own USB based development cartridge. It costs less than 25 euros in parts and allows you to upload code at around 5.8 MiB/s, then the cartridge initiates a hard reset and runs it. Very comfortable!
This post has been edited by Oerg866: 16 April 2017 - 01:25 PM
Project:Sekrit stuff and Sega Virtua Processor research
This demo uses an "undocumented" register that NO emulators support. While this register is actually partially documented as of now, there's still more info that will be released sometime in the future.
This post has been edited by Ralakimus: 17 April 2017 - 10:23 PM
I am indeed. The latest nightly of BlastEm (look for one dated 19-Apr-2017 or later, they are not in date order unfortunately) runs most of the demo correctly. The biggest remaining issues are in the "Titancade" portion (handling of V30 mode bit is incorrect and doesn't play nicely with the vertical border extension trick) and the rotating cube/rectangular prism(s) (suspected to be a timing issue, but I haven't investigated it yet). The horizontal border extension stuff isn't supported yet either, but that's a bit less jarring; especially since horizontal borders are not displayed with the default overscan setting. The V30 switching issue should be fixed within a day or so. The issue with the cube could be quick or painful depending on what the actual problem is.