It doesn't vary with lbpp on RO3.5+ - look carefully where you found that code, it's conditionally assembled if 'Arthur' is set, however if 'VIDC20' is set, it assembles the non lbpp specific code which I posted above.JonAbbott wrote:I implemented CursorFudgeFactor in ADFFS...the point I'm making is that RO changes the value based on lbpp, which may explain why Caverns is out slightly.
Sorry, it's up now - the 'vidc_abort' file.JonAbbott wrote:You didn't upload your DCTL source code for me to look at...so I started again from scratch as I couldn't sleep
Looks good, never considered SWIs during Data Aborts - I guess they'll be fine unless they cause another...JonAbbott wrote:I avoided poking around in ZP for values, as it's not forward compatible and went for legal calls to get the VRAM size.
Although we're patching ZP for the CursorFudgeFactor, so can't escape the incompatibility problem.
I've not done that. I thought VRAM was externally driven, and as you say - RO doesn't set those bits. So programming to '00' I guess must count...JonAbbott wrote: I think the only code I've got to add is to calculate VRAM[1:0] based on VRAM speed/pixel clock, which may fix it.