Feature: Emulate Infinity Base

[deReeperJosh]

Description

This PR introduces the ability to emulate the Infinity Base within Dolphin, another Wii peripheral device that can be a hassle to set up, and is currently unavailable for use on MacOS (without sudo) or Android. Where the Skylanders portal was a port from RPCS3, the Infinity code was written from scratch based on reverse engineering done with an Infinity 1.0 Base, and other pieces of research found online. Here's a video of the functionality in action

Tasks

Currently Working:

• Responding to the challenge sent by the game
• Reading from .bin files from the UI
• Ensuring order for reads/write commands
• Play Sets/Power Discs in Hexagon slot
• Players in either of the Circular slots
• Circular "Ability" discs that sit underneath the Character figures
• The ability to create blank Figures in the UI

Nice to Haves:
Proper Color structures - similar to the Skylander Portal. Requires investigation.

Hopefully this might inspire a developer to look in to seeing how we can optimise Infinity within Dolphin 😄

[deReeperJosh]

Looked like bit shifting on Windows wasn't trusted, changed all the instances of unsigned long to u32/u64 depending on their length

[deReeperJosh]

Unsure if the creation will be possible without a bunch of hardcoded "checksums".
The checksums are known now, just needed some brute-force to figure out the CRC32 polynomial :)

For a blank infinity figure file to be able to be used in game, it needs the 7 byte UID (which is known for most figures) and block 1 of the 20 block file (where each block is 16 bytes). This UID can be randomly generated and still work, so the CreateFigure method I have created uses a 7 byte random number when creating blanks.

In the 1st block of the file, there is key information about the figure that the game caches and stores so that it is known what Infinity figure/power disc/play set is in each slot, and this block is read only, so is never written to.

An example of what a block 1 (decrypted) looks like can be seen below:

00 0F 42 4C 10 0C 1E 00 00 01 D1 1F A7 3F 78 60

This block represents Barbosa from the Pirates of the Caribbean, and the byte breakdown is as follows:

The first 2 bytes (00 0F) are the same for every character in the game as far as I can tell. The 3rd and 4th byte (42 4C) is the Id of the character itself, so every Barbosa will be 42 4C etc. The 3rd and 4th bytes are the only ones that need to be included in the list, as a u16.

The next 4 bytes (10 0C 1E 00) appear to be sort of consistent This set of 4 bytes is actually the toy's manufacture date, written YY/MM/DD.

The next 4 bytes (00 01 D1 1F) are consistent across every figure type in the same series, so play sets, power discs, characters and toy box customisations all have this sequence for infinity 1.0. Noting here that this probably stands for 1.0 Disney Infinity or something similar. Series 2 toys are 00 02 D1 1F, and Series 3 are 00 03 D1 1F.

The last 4 bytes are a crc32 checksum of the prior 12 bytes.

[mandar1jn]

The second to last commit says Skylanders

[deReeperJosh]

@mandar1jn oops just a typo, should say Infinity Figures

[JMC47]

@dolphin-emu-bot rebuild

[dolphin-emu-bot]

FifoCI detected that this change impacts graphical rendering. Here are the behavior differences detected by the system:

• xenoblade-menu on uberogl-lin-radeon: diff

_{^{automated-fifoci-reporter}}

[lioncash]

Should this not be given a parent, like:

Suggested change

	m_infinity_window = new InfinityBaseWindow;
	m_infinity_window = new InfinityBaseWindow(this);

otherwise this could leak

[deReeperJosh]

I copied this from the FIFO Window - which also is not given a parent. Should it also have this referenced? (The Skylander Portal Window has this missing as well)

[leoetlino]

Qt will automatically reparent widgets in some cases (when you add a widget to a layout for instance). In this case (and for the Skylander window too), you're just creating a window and I don't think there's any automatic reparenting being done here so you should probably give it a parent

[deReeperJosh]

When I specify (this) as the parent, the window looks like this (on Mac at least):

Is it appropriate to specify the parent as being null?

[deReeperJosh]

Changes made as above - I should note that some of the changes here may also apply to the Skylanders Qt Window, like QStringLiterals, would like to keep it consistent and map that across in a future PR.

[deReeperJosh]

A little bit more research has meant that there is no need for the 2 structs that I had defined in the header file, just a u32 for the figure number (found here). The bytes that I thought were figure specific were just the manufacture date of the toy, so I have set this to the date Disney Infinity 1.0 was released.

[JMC47]

Is there anything left blocking this? Would like to have it in for the progress report.

[deReeperJosh]

Nothing from an implementation standpoint - @leoetlino @AdmiralCurtiss any other review comments?

[leoetlino]

Sorry for the delay, I'll give this another review asap (tonight or tomorrow)

[deReeperJosh]

@leoetlino thanks heaps - hopefully that is everything. Have also slightly modified the Host.cpp file to reflect latest changes with the EmulationKernel(). Fingers crossed I haven't missed anything there!

[AdmiralCurtiss]

Yeah go ahead and push the lint fixes.

[deReeperJosh]

Just restored a Qt change with the filepath after testing it and remembering why I had included the change in the first place - still ready for build and test

[AdmiralCurtiss]

Untested and I don't know whether the actual algorithms are correct, but this looks fine to me now.