Difference between revisions of "CSpect:known bugs"

From SpecNext official Wiki
Jump to: navigation, search
(removing mention of $A3 register, as it got removed completely :))
(V2.12.24 refresh)
Line 1: Line 1:
CSpect V2.12.22
+
CSpect V2.12.24
 +
* (new in V2.12.24) * may crash when idling in debugger view
 
* sprites: the collision bit is not implemented (intentionally for emulator performance reasons)
 
* sprites: the collision bit is not implemented (intentionally for emulator performance reasons)
 
* 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) (mostly intentionally for emulator performance reasons)
 
* 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) (mostly intentionally for emulator performance reasons)
Line 13: Line 14:
 
* sprites rendering is not one-scanline-buffer delayed and all changes in sprites affect current scanline
 
* sprites rendering is not one-scanline-buffer delayed and all changes in sprites affect current scanline
 
* sprites rendering is unlimited (real HW drops further sprites after exhausting allocated pixel throughput for current line) (reported by David B.)
 
* sprites rendering is unlimited (real HW drops further sprites after exhausting allocated pixel throughput for current line) (reported by David B.)
* border color and Enhanced ULA on/off states sometimes produce incorrect results, sometimes the bottom area of border has different color
+
* border color and Enhanced ULA on/off states sometimes produce incorrect results
 
* direct loading of NEX file doesn't init the machine in the same way as NEXLOAD from NextZXOS (memory stays filled with FF, etc)
 
* direct loading of NEX file doesn't init the machine in the same way as NEXLOAD from NextZXOS (memory stays filled with FF, etc)
 
* direct loading of NEX files does not support all combinations of loading-screen type and palette on/off (but V2.12.9 does load more files than V2.12.5) (the unofficial V1.3 NEX file is partially supported)
 
* direct loading of NEX files does not support all combinations of loading-screen type and palette on/off (but V2.12.9 does load more files than V2.12.5) (the unofficial V1.3 NEX file is partially supported)
 
* when running without the full NextZXOS card image, the esxdos services are provided by the emulator itself, the implementation is very limited and crude (most of the returned values are incorrect/etc, but loading files works)
 
* when running without the full NextZXOS card image, the esxdos services are provided by the emulator itself, the implementation is very limited and crude (most of the returned values are incorrect/etc, but loading files works)
  
not verified in V2.12.22 (but known bugs of V2.12.5):
+
not verified in V2.12.24 (but known bugs of V2.12.5):
 
* screen saver of NextZXOS will "crash" the emulated machine (not emulator itself)
 
* screen saver of NextZXOS will "crash" the emulated machine (not emulator itself)
 
* blending modes: the new core3.1.3 blending (with extra ULA slice) is not supported
 
* blending modes: the new core3.1.3 blending (with extra ULA slice) is not supported
 
* sprites: the default clipping is wrong (rather set clip window explicitly)
 
* sprites: the default clipping is wrong (rather set clip window explicitly)

Revision as of 06:16, 12 May 2020

CSpect V2.12.24

  • (new in V2.12.24) * may crash when idling in debugger view
  • sprites: the collision bit is not implemented (intentionally for emulator performance reasons)
  • 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) (mostly intentionally for emulator performance reasons)
  • some NextRegs read as zero until they are written into first (quick-boot mode without full NextZXOS image) (for example regs $03, $08, $12, $13, $14, $42, $4A, $4B, $4C, $6E, $6F)
  • NextRegs $09, $34, $41, $8E reads wrong values (the more "esoteric" ones like expansion bus related are not part of this test/list)
  • NextRegs $6E and $6F don't read the top two bits as zeroes, but return the written value
  • DMA: Zilog mode is not implemented (port 0x0B), reading DMA registers is not supported, burst mode has incorrect speed
  • Layer2 mode 640x256x4bpp is not implemented
  • Layer2 port $123B - the new feature "bank offset" when writing with bit4=1 is not working correctly
  • layers clipping - it is often +-1px off showing/hiding one extra pixel
  • blending modes: there's sometimes wrong half-pixel at end of paper area
  • sprites: mostly work except the "big sprites" having wrong compound transformations
  • sprites rendering is not one-scanline-buffer delayed and all changes in sprites affect current scanline
  • sprites rendering is unlimited (real HW drops further sprites after exhausting allocated pixel throughput for current line) (reported by David B.)
  • border color and Enhanced ULA on/off states sometimes produce incorrect results
  • direct loading of NEX file doesn't init the machine in the same way as NEXLOAD from NextZXOS (memory stays filled with FF, etc)
  • direct loading of NEX files does not support all combinations of loading-screen type and palette on/off (but V2.12.9 does load more files than V2.12.5) (the unofficial V1.3 NEX file is partially supported)
  • when running without the full NextZXOS card image, the esxdos services are provided by the emulator itself, the implementation is very limited and crude (most of the returned values are incorrect/etc, but loading files works)

not verified in V2.12.24 (but known bugs of V2.12.5):

  • screen saver of NextZXOS will "crash" the emulated machine (not emulator itself)
  • blending modes: the new core3.1.3 blending (with extra ULA slice) is not supported
  • sprites: the default clipping is wrong (rather set clip window explicitly)