ZEsarUX:known bugs

You may want also to check the official ZEsarUX FAQ to see if you have a known issue which has solution (ZX Next is "TBBlue" type of machine).

Github "master" branch at 2020-11-26 23:00CEST (commit e8346c7601bd92, version 9.1 final):

• both 4B/5B sprite types are now implemented, but only partially with lot of bugs and incorrect on-screen results
• 4bpp sprites are somewhat supported (wrong transparency, wrong relative sprites, etc.. but the most trivial cases somewhat resemble what is drawn on real Next)
• sprites rendering is not one-scanline-buffer delayed and all changes in sprites affect current scanline
• Layer 2 displays shadow variant (NextReg $13) when the "shadow" mapping is enabled
• Layer 2 extra memory mapping controlled by Layer 2 Access Port ($123B / 4667) works only in core2.x way.
• Layer 2 does not support "priority" bit in L2 colors
• NextRegs $09 reads wrong values
• missing Nextreg $64 "video line offset" (core 3.1.5)
• tilemode gfx/map address read (NextReg $6E + $6F) does return original value without top bits reset to zero
• DMA: too many differences to list, but most crucial: slow "burst" functionality is missing, CONTINUE is not supported, legacy Z80 mode is not implemented, all transfers are "instant"
• blending modes are not implemented
• ULA scroll is not at new NextReg $26, $27 (but still shared with LoRes offset registers)
• ULA+tilemode does not support stencil mode
• audio has "clicks" and noise on many platforms, although YMMV
• tilemode doesn't wrap in memory the same way as HW (when gfx/map address is toward end of Bank 5)
• direct loading of NEX file doesn't init the machine in the same way as NEXLOAD from NextZXOS (it's close, but few things are different)
• modifications to NextRegs done in copper propagate to rendering usually only once per scanline, usually retroactively for full scanline when triggered in h-blank area (palette changes, X/Y offsets, etc)
• when running without the full NextZXOS card image, the esxdos services are provided by the emulator itself, which does not implement all of them, and they don't always return the state described by the NextZXOS documentation
• missing all(?) features/changes of cores after version 3.1.5 (the emulator itself reports as core 3.1.9, but I haven't find any functionality related to the changes in real cores)

Other Issues (not a bug):

• 28MHz mode requires quite powerful PC to emulate it smoothly, "lagging" emulator menu/etc is likely to happen in 28MHz mode and unfit for many development purposes.
• don't use "--enable-esxdos-handler" option together with running NextZXOS from full MMC card image - it will clash with the MMC functionality