Post - Forum - Plus/4 World



	Home Search Games Tapes Covers Cheats Maps Software New Stuff Hall Of Fame HVTC Game Endings Solutions Remakes Publications Magazines Effects Top List Members Groups Features Plus/4 Encyclopedia Hardware Tools Options Forum Home Search Games Tapes Covers Cheats Maps Software New Stuff Hall Of Fame HVTC Game Endings Solutions Remakes Publications Magazines Effects Top List Members Groups Features Plus/4 Encyclopedia Hardware Tools Options Forum	Login

Forum Help

Post Your Message

Previous Messages

Posted By

Gaia
on 2011-08-01
01:50:27

Re: $FF0C/$FF0D autosetting?

Well, there it was set to $FF/$FF (that is: $03FF, since only 10 bits are used) as well, but Bubis opened up the lower border, so the character position (row 25, column 23) corresponding to the value 1023 - that is normally not shown -, became actually visible revealing the cursor's "hideout". AFAIR he did write to $FF1F each frame to prevent it from flashing, but he still sometimes catches it in the wrong phase and it gets locked in the "ON" flash phase. The easiest fix would be to switch to RVS OFF mode ($FF07 bit #7 -> 1) but I am not sure whether it screws up the gfx or not, so it may get a bit trickier than that.

Posted By

Luca
on 2011-07-31
19:08:24

Re: $FF0C/$FF0D autosetting?

I wonder what happened in Heartfixer 95%, then...

Posted By

Csabo
on 2011-07-31
19:04:58

Re: $FF0C/$FF0D autosetting?

If you're program starts with RUN, it's the default behavior. It should be the ROM at $D914.

Posted By

Luca
on 2011-07-31
18:41:59

$FF0C/$FF0D autosetting?

I checked some codes, where I didn't set the cursor's position by changing $FF0C/$FF0D, and they are magically set to #$FF beyond my intervention. What does let it happen?