AnyPS5/docs/dev/debt/libSceNpTus.md

libSceNpTus technical debt

Unknown function info

• sceNpTusCreateNpTitleCtx - throws through NotImplemented_nid_no_patch; behaviour and the PS5 prototypes are unmeasured. The only source of the parameter lists is shadPS4's PS4-derived prototypes (GPLv2, used as a reference only), with no second reference; structure pointers are void* because no layout is known.
• TUS variable outputs (libSceNpTus) - the layouts of the variable arrays of the sceNpTusGetMultiSlotVariable* calls and of outVariable in sceNpTusAddAndGetVariableAAsync are not verified, so the output is never written and variableArraySize / outVariableSize are not checked; shadPS4, and RPCS3 in its PS3 sceNpTusGetMultiSlotVariable* and sceNpTusAddAndGetVariable* calls, return INVALID_ALIGNMENT unless the size is arrayLen variables of the call's type, or one variable for outVariable. The signatures and the community error codes follow shadPS4, which fpPS4 agrees with for the context and request calls; no console measurement.
• Multi-slot variable calls (libSceNpTus) - the argument checks of the multi-slot get, set and delete calls are not measured on a console; they follow shadPS4, where they differ between functions: arrayLen < 1 is INSUFFICIENT_ARGUMENT in the NpId and virtual-user delete calls and in sceNpTusGetMultiSlotVariableVUserAsync, and INVALID_ARGUMENT in the others; a null NpId is accepted except in delete; an empty virtual user ID is INVALID_ARGUMENT. RPCS3's PS3 module has only the NpId and virtual-user calls; it returns INVALID_ARGUMENT for an empty array in all of them, rejects a null target in get and set and does not check for an empty virtual user ID.
• Variable, data, data status and TSS requests (libSceNpTus) - the argument checks of the 82 add-and-get, try-and-set, data, data status, multi-user, friends and sceNpTssGetSmallStorage calls are not measured on a console; their signatures, checks and order follow shadPS4, including its differences between forms: the NpId try-and-set calls return INVALID_ARGUMENT for an operation type outside 1-6 where the others return INVALID_TYPE, and the NpId and virtual-user multi-slot data status calls return TOO_MANY_NPID for more than 64 slots. As for the calls above, the output and structure sizes are not checked, and every request finishes with SCE_NP_ERROR_SIGNED_OUT
• sceNpTusSetThreadParam (libSceNpTus) - unknown signature
• sceNpTusCreateTitleCtx (libSceNpTus) - unknown signature
• sceNpTusSetTimeout (libSceNpTus) - unknown signature
• sceNpTusChangeModeForOtherSaveDataOwners (libSceNpTus) - unknown signature
• sceNpTusDeleteMultiSlotDataVUser (libSceNpTus) - unknown signature
• sceNpTusDeleteMultiSlotDataVUserAsync (libSceNpTus) - unknown signature
• sceNpTssGetStorage (libSceNpTus) - unknown signature
• sceNpTssGetStorageAsync (libSceNpTus) - unknown signature
• sceNpTssGetDataAsync (libSceNpTus) - unknown signature
• sceNpTusGetDataForCrossSaveVUser (libSceNpTus) - unknown signature
• sceNpTusGetDataForCrossSaveVUserAsync (libSceNpTus) - unknown signature
• sceNpTusGetFriendsVariableA (libSceNpTus) - unknown signature
• sceNpTusGetFriendsVariableAAsync (libSceNpTus) - unknown signature
• sceNpTusGetFriendsVariableForCrossSave (libSceNpTus) - unknown signature
• sceNpTusGetFriendsVariableForCrossSaveAsync (libSceNpTus) - unknown signature
• sceNpTusGetFriendsDataStatusA (libSceNpTus) - unknown signature
• sceNpTusGetFriendsDataStatusAAsync (libSceNpTus) - unknown signature
• sceNpTusGetFriendsDataStatusForCrossSave (libSceNpTus) - unknown signature
• sceNpTusGetFriendsDataStatusForCrossSaveAsync (libSceNpTus) - unknown signature
• sceNpTusDeleteNpTitleCtx (libSceNpTus) - the PS5 signature, error codes and child-request lifetime have not been measured on a console. Deletion invalidates the context and all its requests, following shadPS4.

Functional

• sceNpTusCreateNpTitleCtxA (libSceNpTus) - creates a title context without checking sign-in, up to 32 contexts (TOO_MANY_OBJECTS beyond); shadPS4 returns the sceNpGetNpId error instead. Requests are limited to 256, and the limits are not measured on a console.
• sceNpTssCreateNpTitleCtx and sceNpTssCreateNpTitleCtxA (libSceNpTus) - that TSS title contexts share the TUS context table and its 32-context limit is inferred from shadPS4, which redirects both to the TUS creators, and from TSS requests coming from sceNpTusCreateRequest; nothing is measured on a console. The A form is sceNpTusCreateNpTitleCtxA. The NpId form returns INSUFFICIENT_ARGUMENT for a null npId and INVALID_ARGUMENT for service label 0xFFFFFFFF before the limit, as shadPS4's sceNpTusCreateNpTitleCtx does; the signatures are shadPS4's and fpPS4's, and Orbital's for the A form.
• sceNpTusPollAsync, sceNpTusWaitAsync (libSceNpTus) - there is no PSN, so every implemented *Async call whose arguments pass the checks starts a request that finishes at once with SCE_NP_ERROR_SIGNED_OUT, which poll and wait report and the blocking calls return; shadPS4 returns SIGNED_OUT from the *Async call itself when no shadNet client is signed in, and RPCS3 returns INVALID_ONLINE_ID while offline, marked there as probable behaviour. An abort stays set, so every later operation on the request, blocking ones included, finishes with ABORTED; in shadPS4 an abort only ends the operation in progress. Until an operation has started, poll returns 1 and wait returns INVALID_ARGUMENT as in shadPS4; RPCS3 blocks until a result is set.
• sceNpTusGetData, sceNpTusGetDataVUser, sceNpTusGetMultiSlotVariable, sceNpTusGetMultiSlotVariableVUser, sceNpTusGetMultiUserVariableForCrossSave, sceNpTusSetData, sceNpTusSetDataVUser, sceNpTusSetMultiSlotVariable and sceNpTusSetMultiSlotVariableVUser (libSceNpTus) - block on their *Async forms with the same parameters, as shadPS4 does, so they inherit those forms' unmeasured checks and the offline SIGNED_OUT result