person that posted the sheet deleted unfortunately but here is the new one: https://docs.google.com/spreadsheets/d/1G_ZW6YUKg0DX1Gfs54GXm_2akicjb_3I9JYCV_VhEog/edit?usp=sharing
person that posted this deleted but here is the sheet: https://docs.google.com/spreadsheets/d/1IPZcQoWmnF9SzQDw6JqGB1oZu3ekBtAz8griXO466-0/edit?usp=sharing
i would defintely be in support of using IGT. I just tested Duckstation and its got even much slower loads than epsxe which was already slower than console. I have some runs done here on my youtube channel https://www.youtube.com/channel/UCpGwxony_BjYIB3loN0caJw
(if you want me to just add the runs to the sheet myself just shoot me a message and ill give you my email)
this also may just be down to ePSXe's general inaccuracy, tbh it was just the first thing I got working so I was using it.
in my rough testing of my ePSXe run vs Ricky's console run, it seems that ePSXe was losing roughly 2 minutes of time in loads compared to console (about 6 seconds per loading screen.) Seems like console is significantly faster as far as I can tell. just putting this info here in case anyone ever cares enough to optimize this.
very helpful. I think Digo might be the way to go possibly.
