Are you sure that game has no sub-pixels?
As feos mentioned, you forgot to add subpixels in to the calculations.
It would be a good idea to share at least the name of the game you are talking about. There are many reasons while a specific value doesn't changes each frame.
state = savestate.create()
gui.register( function ()
havocVX= memory.readlongsigned(0xFFDBCC) -- Havocs velocity (x)
camX = memory.readlongunsigned(0xFFF6D0) -- Camera Position (x)
havocXonScr = memory.readlongunsigned(0xFFDBB0) -- Havocs Position relative to the camera (x)
havocX = camX + havocXonScr -- Havocs Position (x)
cpuPC = memory.getregister ("pc") -- program counter
savestate.save(state)
gens.emulateframeinvisible()
effectiveVxonScr = (memory.readlongunsigned(0xFFF6D0)+memory.readlongunsigned(0xFFDBB0)) - havocX
cpuPC2 = memory.getregister ("pc")
savestate.load(state)
message = string.format("PC: %X, %X", cpuPC,cpuPC2)
gui.text(10, 42, message, "#FFFF00FF", "black")
message = string.format("vel: %10d", havocVX)
gui.text(10, 58, message, "#FFFF00FF", "black")
message = string.format("real vel: %10d", effectiveVxonScr)
gui.text(10, 66, message, "#FFFF00FF", "black")
message = string.format("pos: %10d", havocX)
gui.text(10, 74, message, "#FFFF00FF", "black")
end)move.l (0xFFF6D0).l, d0
add.l (0xFFDBB0).l, d0
move.l (0xFFF6D8).l, d1
add.l (0xFFDBB4).l, d1
move.l d0, (0xFFDBB8).l
move.l d1, (0xFFDBBC).l((0xFFF6D0) + (0xFFDBB0)) of next frame
-((0xFFF6D0) + (0xFFDBB0)) of current frame
|
|
(0xFFF6D0) + (0xFFDBB0) --+ |
| |
(0xFFDBCC) --+ | |
| | |
Frame PC vX posX real vX
850 457C 0 19398656 0
851 B3E6 0 19398656 0
852 457C 8192 19406848 16384
853 4676 16384 19423232 24576
854 63C4 24576 19447808 32768
855 4678 32768 19480576 0
856 6226 40960 19480576 90112
857 B1DC 49152 19570688 57344
858 45BC 57344 19628032 65536
859 B1B6 65536 19693568 73728
860 4580 73728 19767296 81920
861 456A 81920 19849216 0
862 5930 90112 19849216 188416
863 4580 98304 20037632 106496Frame: X-Value
1 1
2 2
3 2
4 4
5 5
6 5
7 7Is it normal for Nicovideo to have lots of text (mostly gibberish) stream over the screen at all times? It's rather annoying.
You mash the Start button to skip the score tallies. Mistake there. You should check to see what's the first possible frame in which skipping is possible. For instance, imagine you press Start on frames ..., 31, 33, 35, 37, ..., and the first possible instance to skip is on the 32th frame. You only press Start on the 33th, missing one frame. Worst case scenario, all these add up, so... 12 (13? does the final count?) levels, times all the things you skip (level intro, score tally for every score), which is like 4, gives 48 lost frames. (Calculations may be a bit off, but my point still stands)Huh... Looks like you only mash the Start button on the first level.
After the first hit on Bernardo, you do a quick up-and-down dance. I think that distracts too much; you should only dance on long, monotonous sections.
I guess you could add a small extra bit of entertainment in Burning Hamlet 1. Like try to collect as many jewels as possible along the way, or none at all. Sure beats holding right for the majority of the level. Also, when you're on the platform with the huge blaze very close to you, are you as close to the blaze as possible?
I think few high jumps are better than several short jumps when climbing hills in Mt. Chester.
When you take the huge shortcut in Mt. Chester 2, I think you should have jumped to fall on the gap faster. http://tasvideos.org/GameResources/CommonTricks.html#JumpingOffLedges
You wait to collect the boots on Mt. Bernardo. I'm sure you have an explanation for that. Put it on the submission's comments.
A bit after the start of Mt. Bernardo 2, you stand on a platform waiting for it to collapse. You duck, but you can only actually go right when there's enough space to fit Havoc while standing up, so that's why you don't go right even though there's some space. But the thing is, wouldn't it be fast to start moving already by doing a roll? I don't think so, but it's worth a check, no?
For starters don't slip off platforms rather jump down to them and manipulate the air to fall to the next one below
you could take more damage to save time. From what I see you do somewhat but very rare.
Try not to bump into walls, when jumping to the edge of the top.
There is points where you suddenly wait for no reason.
------ Build started: Project: gens, Configuration: Debug Win32 ------
Linking...
LINK : fatal error LNK1104: cannot open file 'release\mem_M68K.obj'------ Build started: Project: gens, Configuration: Release Win32 ------
Assembling z80.asm
The System can not find the file specified.
Project : error PRJ0019: A tool returned an error code from "Assembling z80.asm"on the 3rd special stage, the mistake is that you bump on that ball.