Symbol Database v2 Method

Creating an OOVPA

See here.

The OOVPA method itself has not changed.

Maintenance

Once an OOVPA has been added, replaced, or removed, the library's database v2 needs to be updated.

This is a requirement in order to compile properly.

• Any time an OOVPA has been lowered, the OOVPA itself must be moved into a specific revision database file.
• If a new OOVPA is replaced with a better OOVPA, please comment the whole obsolete OOVPA section for preservation purposes with a comment stating "replaced with _version_".
• Whenever you find a specific OOVPA is causing 100% false detection please comment it out, and create a correct OOVPA signature for it.
• There are high chances of ability to make generic OOVPAs. When you discover a preexisting OOVPA or OOVPA you made is indeed generic and does match correctly the highest XDK version which is 5849, please add a comment stating "Generic OOVPA as of _XDK_version_ and newer". Also check with lower XDK titles to be sure if it's possible to add at starting point of the XDK version.

Method for Symbol Database v2 library

REGISTER_OOVPAS(/*Name of OOVPA*/, /*XDK versions*/, ...),

Register new OOVPA

Once you are done with creating an OOVPA, manually add or update it's existing register in respective v2 database.

For example:

REGISTER_OOVPAS(XAudioCalculatePitch, XREF, 3911, 4039),

If you do not understand how REGISTER_OOVPAS work, please use the search bar then choose the "code" tab to understand how it works.

Recommendation

• Keep notes on what hasn't been verified in the library's database file.
• Use specific version title if you are able to discover almost to full compiled library. (Doing this way does speed up add all missing OOVPAs detection.)
• Please do add library version and title's name to the note to keep track of known title might or does contain almost to full library compiled.