It creates a label through the same system that the FPS and other stuff uses.
It seems it's only the 1.11.4 and December part that's out of date.
Capture OSD off | Capture OSD on | |
| Saving AVI/GIF | Game screen only | Game screen
+ game padding
+ client padding
+ all text rendered by lua (except gui.text) or the client |
| Saving Screenshot | Game screen
+ game padding | Game screen
+ game padding
+ client padding
+ all text rendered by lua (including gui.text) or the client |
What if you don't pause? For other cores it worked for me.
************** Ausnahmetext ************** System.Exception: 0, 255, 0 ist kein gültiger Wert für Int32. ---> System.FormatException: Die Eingabezeichenfolge hat das falsche Format. bei System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) bei System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) bei System.ComponentModel.Int32Converter.FromString(String value, NumberFormatInfo formatInfo) bei System.ComponentModel.BaseNumberConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value) --- Ende der internen Ausnahmestapelüberwachung --- bei System.ComponentModel.BaseNumberConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value) bei System.Drawing.ColorConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value) bei BizHawk.Client.EmuHawk.ToolManager.InstallCustomConfig(IToolForm tool, Dictionary`2 data) bei BizHawk.Client.EmuHawk.ToolManager.Load[T](String toolPath, Boolean focus) bei BizHawk.Client.EmuHawk.MainForm.GBGPUViewerMenuItem_Click(Object sender, EventArgs e) bei System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) bei System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e) bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) bei System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) bei System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) bei System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) bei System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) bei System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea) bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) bei System.Windows.Forms.Control.WndProc(Message& m) bei System.Windows.Forms.ScrollableControl.WndProc(Message& m) bei System.Windows.Forms.ToolStrip.WndProc(Message& m) bei System.Windows.Forms.ToolStripDropDown.WndProc(Message& m) bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
System.InvalidOperationException: Lua surface is already locked: emu at
BizHawk.Client.EmuHawk.DisplayManager.LockLuaSurface(String name) at
BizHawk.Client.EmuHawk.GuiLuaLibrary.DrawNew(String name)so it should be possible to make a run that doesn't use the BIOS at all. Is using the BIOS to change the clock during the run required to not get an unfair advantage compared to consoles when timing the run?
My script for it works, but I can't pause or do anything until after the frame ends. I can read the memory addresses following $02001E90.
During frame 14001, $02001E90 gets written to which fires my function that reads the upcoming addresses. The reads all yielded 0. At the end of that frame, all those addresses have been written to (as you can see in the memory viewer).
I don't know if the game performs any check if nothing has gone awry during that crucial frame, but I haven't seen anything that indicates that yet.
Maybe I will investigate this some more and if I see the chance of a very quick theoretical TAS, I will make it.
Edit: I think there is a checksum protection after all. I've seen it delete my custom save upon reset sometimes. Also, I think savegame abuse is not possible. The room ID gets written in one piece and that's the only lead I had.Language: Lua--mlsstestVBA.lua function NumToHex(IN) local B,K,OUT,I,D=16,"0123456789ABCDEF","",0 while IN>0 do I=I+1 IN,D=math.floor(IN/B),math.mod(IN,B)+1 OUT=string.sub(K,D,D)..OUT end return OUT end write_1E90 = function() emu.pause() print(emu.framecount()..": Write to $02001E90 occured.") print("$02001E90 now reads ".. NumToHex(memory.readwordsigned(0x02001E90))) print("Next memory addresses read:") counter=0 for k, v in pairs( memory.readbyterange(0x02001E92,10) ) do print(NumToHex(0x02001E92+counter) ..": ".. v) counter=counter+1 end print("---") end memory.registerwrite(0x02001E90,write_1E90) while true do emu.frameadvance() end
string memory.readbyterange(int addr, int length)
When writing to 0x001E90, it should do the print but it doesn't. What gives? Looking for a way to do subframe resets or at least get close to it. Is it possible for GBA games?Language: Luamemory.usememorydomain("EWRAM") write_1E90 = function() client.pause() print(emu.framecount()..": Write occured.") end read_1E90 = function() client.pause() print(emu.framecount()..": Read occured.") end exec_1E90 = function() client.pause() print(emu.framecount()..": Exec occured.") end event.onmemorywrite(write_1E90,0x1E90) event.onmemoryread(read_1E90,0x1E90) event.onmemoryexecute(exec_1E90,0x1E90) while true do emu.frameadvance() end
$ca1c (1 byte) health
$ca10 (1 byte) timer minutes
$ca11 (1 byte) timer seconds
now :18091 white out after stage 3 boss
1px saved :18092 "
2px saved :18089 "
3px saved :18089 "
- Autofire pausing causes a temporary minor graphical bug with the screen not updating correctly. Doesn't lead to out of bounds or inside of walls glitches.
- When using musical note item just after getting hit, you can get hit again very soon. Basicly, your invincibility period is nullified. Edit: There indeed seems to be a bug with it. After using musical note, the invincibility span counter stops and you are vulnerable again right away. In fact, the next time you get hit, it will count down from the value where it stopped.
- Walls seem interesting
Edit:
Lua http://pastebin.com/iVuCBTcJ
shows position, your invincibility period, your suitcase hitpoints, your hp, boss hp
Edit:
My run http://tasvideos.org/5094S.html