hap
hap
mame ti99_4a moonpatr works fine here, or is it another TI99 system or another Moon Patrol game? If you played it a few weeks ago and it suddenly doesn't work...
I'd assume something simpler like the last thing you mentioned: nonlinear resistor array for r/g/b. I'd even say possibly 'gamma proms' like Namco System 22 are more likely than it...
It does not crash here, but I see this driver (nintendo/vsnes.cpp) does not officially support savestates, which means some variables are not saved and unexpected things can happen when a...
And those drivers compile fine if you don't include asio.h? Which would be strange, since the errors you posted look like GCC 11.2 bugs or the version is outdated.
@cuavas is it still in a state where you'd revert it if someone else merged it?
@SailorSat to properly initialize (zerofill) device class variables, we don't do it in the .h file, but in the .cpp file. Either in the constructor or at device_start. So, a...
Anyone else have feedback? If no, let's merge it 24hrs from now.
@SailorSat BTW could you update your 1st post? Mention ASIO? It'll be the commit msg (whatsnew.txt) Also, I'll make sure to ask: is everything working as you expect it to...
You forgot to initialize m_baud. If the CPU manual says it's unmodified at reset, do m_baud = 0 at device_start. Also, the new variables each need a save_item.
Same thing in the driver by the way: If you want savestates to work, add a save_item to machine_start for keyscan and lcd mode. Also, MAME drivers add m_ prefix...