Read access violation - address at settings_ptr accessed too early for values to be set

[marinesciencedude]

Validation

• [X] I've read the FAQ.
• [X] The Xenia build used is from the master branch (not MLBS/AlexVS/Canary/pull requests, etc.)
• [X] This issue isn't for tech support (help with Xenia).
• [X] If this issue occurs in a specific game, I've done analysis to locate the faulty subsystem of the emulator and a potential reason in it.
• [X] I've checked if this issue hasn't already been reported.
• [X] My device meets the minimum requirements: https://github.com/xenia-project/xenia/wiki/Quickstart#system-requirements
• [X] (If building) I have read the building doc: https://github.com/xenia-project/xenia/blob/master/docs/building.md

Describe what's going wrong

game_addrs.settings_addr for November 2007 Release, 0x83088228 (or 0x183088228 as per TranslateVirtual), points to zero value causing settings_ptr to be set to an address pointing to null value

Seems later canary versions have shifted around some of the loaded memory, not sure how much Cheat Engine can help

Describe what should happen

settings_addr should point to a non-zero value usable for settings_ptr

If applicable, provide a callstack here, especially for crashes

xenia_canary.zip

If applicable, upload a logfile and link it here

xenia.log

[marinesciencedude]

0x183088228 seems to show up values in Cheat Engine with mainline build of xenia canary, no problem there

Instead it seems code fixed during #1 in WinKeyInputDriver::GetState is being executed too early, clearly emulator->is_title_open() as a condition doesn't give a chance for 0x183088228 to be written to