A Moogle  🏳️‍🌈 💻 🎮 🎶 🇸🇪

Ahoy @StuffIBuild, just saw the video where you tried to fire up Blender 1.0 in MAME's SGI Indy driver! As the dude who wrote the majority of the driver in conjunction with another dev, the slowness is mainly down to MAME lacking a recompiler/JIT for the new MIPS core just yet.

While MAME's older MIPS core does have a JIT, it also has a handful of edge-case bugs that don't seem to affect arcade games, but which do affect workstations, so I had to punt on it and use P-Mack's newer, more accurate core, at the cost of speed.

That said, he's gradually working towards getting the CPU emulation to be more performant. FWIW, running MAME with -aviwrite -snapsize 1280x1024 would have made it run slower (due to scribbling out a 1280x1024 uncompressed AVI), but the video would play back at full speed. :)

While it was slow, it was certainly usable! So glad it existed, b/c I don't think I would have been able to experience B1.0 without it. Neat AVI recording trick!

Cheers, I just wish I knew what was going on with the "blenderbuttons" thing. Did you ever get it sorted out, or did it end up being a dead-end? The allocator warnings are also alarming, but I could envision a direct exit potentially causing issues.

WHOA! I just noticed Part 2, seems like you did! BRB, watching.

Oh yea, I got it working and did a lot with it. I think there's like 5 parts haha. Enjoy

Jumping around a bit - when you moved the ImageView window around 24:55 in the second part, I'm reasonably sure you might have uncovered a MAME bug. I'll see if I can repro it in isolation. I'm 100% sure there are edge cases in the XL8/XL24 board that aren't yet handled.