TASEmulators / TASEmulators/BizHawk
The Input_Display.lua script provided with Bizhawk 2.9.1 does not work on N64 and doesn't acknowledge any controllers being connected
Open
Nobody has claimed this yet.
Meta
re: Lua API/scripting
Request: Feature/Enhancement
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
Summary
The Input_Display.lua script provided with Bizhawk 2.9.1 does not work with N64 and doesn't acknowledge any controllers being connected
Repro
- first step run perfect dark PAL N64 with either ARES or mupen core
- second step perform inputs
- third step run the Input_Display.lua Script
Output
ARES core:
N64
Player 1: Unconnected!
Player 2: Unconnected!
Player 3: Unconnected!
Player 4: Unconnected!
Reminder: Enable Capure OSD when Dumping!
Mupen core:
N64
Player 1: Unconnected!
Player 2: Unconnected!
Player 3: Unconnected!
Player 4: Unconnected!
Reminder: Enable Capure OSD when Dumping!
NLua.Exceptions.LuaScriptException: [string "main"]:111: attempt to perform arithmetic on a nil value (field '?')
NLua.Exceptions.LuaScriptException: [string "main"]:111: attempt to perform arithmetic on a nil value (field '?')
NLua.Exceptions.LuaScriptException: [string "main"]:111: attempt to perform arithmetic on a nil value (field '?')
Host env.
- BizHawk 2.9.1 Windows 11 System SKU LENOVO_MT_82JW_BU_idea_FM_Legion 5 15ACH6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the provided Input_Display.lua script, especially the arithmetic failure reported at line 111, and inspect its output in the Lua Console while running the N64 repro with the ARES and Mupen cores. Done means the script acknowledges connected controllers for the tested setup and no longer reports the nil-value exception during inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- game-dev, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100