seastalker wrote:I am also wondering how you make a MINI PC-Engine as it is already the tiniest thing! Any smaller and it might be mistaken as a Triscuit!
According to this the Mister core is very innacruate at every test level, should we be concerned about this?
normal19 wrote:According to this the Mister core is very innacruate at every test level, should we be concerned about this?
seastalker wrote:That actually surprises me. I have a TG16, a PCE and haven't noticed any problems yet with the core. I'll have to pay more attention now. I still think the core is already EXTREMELY good.
dshadoff wrote:3) Every timing test at every level shows a gentle slope leftward as the tests progress down the screen. About 1 pixel per line, which equates to about 2 cycles per test. This does not imply a problem with the opcodes involved with the test, but rather something which occurs once per test. I suspect it's the update to the 6260 palette generator, which seems too fast (~2 cycles as I mentioned). I would suggest writing a new test for this (or, given time, I will do so).
GreyRogue wrote:The slope is caused by the Video Encoder using a slightly off number:
https://github.com/MiSTer-devel/TurboGr ... 60.vhd#L68
This number is a multiple of all 3 horizontal display resolution modes. The actual hardware should be 2730 https://github.com/mamedev/mame/blob/ma ... 60.cpp#L11, not 2736. If this is changed, it will need to be done in a way that doesn't break the scalar/scan doubler.
Users browsing this forum: witchmaster and 9 guests