TASEmulators/BizHawk

[wish] Consider a new release ?

Opened this issue · 7 comments

It's been a year since last release, is there any plan for a new one ?
I'm very excited about the new features and bug fixes, and want to give them a try.
but I don't have necessary knowledge to build this project myself.

Don't hold your breath.

In the meantime, you can try out new features by downloading a dev build—you don't have to build it yourself, though if you wanted to, there are instructions here.

In support of a new release, a potential DK64 TAS is waiting on support for Ares core which has significantly more accurate framebuffer emulation which is key for creating a proof-of-concept for an exploit.

We're well past due a release candidate, so now that some important PRs have been merged, we've agreed on Discord that this weekend is as good a time as any for RC1.
If any devs have a questionable change ready to go, now's the time to make the call on whether to get it in and field-tested or to wait until after release.

The next release will be 2.10 per our odd convention, since Encore (Citra) and ChannelFHawk are now fully-functional. We also have 2 new WIP cores, PUAE and Stella, as well as rewrites of Genplus-gx and QuickNes and regular updates for several others.
As for regression testing, we're of course focused on TAStudio, but also host rendering/graphics. Hopefully a reasonably popular RC will help us (and by us I mean @CasualPokePlayer) fix any driver incompatibilities before release.

Can we have an option to prevent changing window size after loading a new type of ROM file?
Each time I load a new ROM file of another core, the window size will be changed, but if I load another ROM of the same core, it will not happen;

The two actions are somewhat inconsistent. I'd like scale the window size up to meet my preference, the the size will reset after changing cores, it makes me feel disturbed.

See #3410; you can set a fixed resolution in Config > Display, or from 2.10, use a new "freeze size" checkbox added by #4011.
Please keep this thread on-topic.

Thank you