patent.fyi
Applications  /  US 2026/0355634
United States Patent Application Publication

US 2026/0355634 A1

Published
Nov 12, 2026
Filed
Apr 15, 2026
Earliest date on the face
May 12, 2025
Classification
A63F 13/63
First published here
Nov 19, 2026

Generated automatically. Not reviewed by a person. Not legal advice or an opinion.

Section 1 · machine-generated

What if?

Questions about how individual parts of claim 1 might be changed. A question may describe something different from what the claim language recites, or a version of it; no view is offered on which.

1.1Profile editing outside gameplay

What ifWhat if players set character appearance in a companion profile editor while the game is closed?
Claim language“in a first scene”

A standalone editor presents part thumbnails and writes the selected mesh identifiers, color values, and visibility flags to a profile file. The game reads the file when it starts and applies those values when it creates the character.

1.2Scheduled appearance parameter updates

What ifWhat if an internal clock triggers part appearance changes automatically?
Claim language“based on an operation input”

An appearance controller compares the elapsed time since scene entry with a table of scheduled updates. At each scheduled time it writes the listed material identifiers and color values into the corresponding part records.

1.3Visible neutral part variants

What ifWhat if selecting a neutral variant replaces a decorated part with a plain mesh of the same type?
Claim language“a non-display state in which the part is hidden”

The editor stores one mesh identifier per part type and includes a plain mesh among the available selections. The renderer draws the selected mesh for every part type, including the plain mesh.

1.4Prebuilt accessory selection

What ifWhat if players place a prebuilt accessory from a catalog?
Claim language“generated in response to a part generation instruction”

The installed asset bundle contains accessory meshes with fixed asset identifiers. Selecting an accessory and an attachment point records the asset identifier and a local transform on the character.

1.8Output profile accessory placement

What ifWhat if the third character receives an accessory selected from its own generation profile?
Claim language“based on the additional part placed”

The generator reads an accessory asset identifier and attachment point identifier from the output profile. It resolves the attachment point on the third character's rig and places the accessory using the profile's local transform.

Section 2 · machine-generated

Variations

Further arrangements of the same subject matter, described here as of the publication date at the foot of this page.

Other field of use

Digital mannequins for garment fitting

A garment-fitting application stores clothing and accessory slots on each digital mannequin, with a style record and a visibility flag per slot. An operator edits the styles and flags and draws a patch on a texture canvas, then anchors the patch to a garment region using local surface coordinates. When the application combines two mannequins, the first mannequin controls slot visibility and each visible slot takes its style from the source selected by the operator. The application transfers the first mannequin’s patch to the corresponding garment region using the stored surface coordinates.

Component substitution

Weighted blending of shape parameters

A weighted linear interpolation algorithm replaces whole-part selection for visible parts with matching mesh topology. For each part type, the editor stores a coefficient vector for a shared set of mesh deformation targets and a separate visibility flag. When the first character’s part is visible, the generator multiplies its coefficients by a slider value from 0 to 1 and the second character’s corresponding coefficients by one minus that value, then adds the vectors and applies the result to the shared mesh. The generator retains the first character’s visibility flag and copies its user-created attachment and local transform to the corresponding anchor.

Parameter or scale variation

Batch generation with sixty four slots

Each character record contains 64 indexed part slots and supports up to 16 user-created attachments, each stored with a resource identifier, an anchor index and a local transform. The editor stores slot visibility in a 64-bit mask and stores appearance parameters in an array indexed by slot. A batch job generates 128 characters from 128 source pairs by copying the first source’s mask in each pair and reading a separate 64-bit selection mask to choose the source appearance for each visible slot. The job copies the first source’s attachment records into the generated character and resolves their anchors by index.

Combination with existing systems

Character generation in a replay system

A game replay system stores character editing events and generation events in an ordered simulation log. Editing events record the slot index and updated appearance or visibility value, while attachment events record the generated asset identifier and local placement. A generation event records immutable revision identifiers for both source characters and a random seed, and the generator uses those revisions and the seed to select appearances for slots visible in the first character. During playback, the replay system reconstructs the source revisions from the log and regenerates the output with the first source’s visibility flags and attachment placements.

Automated or data-driven variant

Automatic selection by color matching

The appearance editor stores an average color for each part asset, calculated from its opaque texture pixels in a perceptual color space. During generation, the software takes a target color from a user-selected region of the first character’s custom attachment. For each slot visible on the first character, the software compares the two source assets by Euclidean distance to the target color and selects the closer asset, using the first source for ties. The output retains the first character’s hidden slots and places its custom attachment at the matching anchor.

Surface fitting for transferred attachments

At placement time, the editor records three surface anchors on the first character, each with a triangle identifier, barycentric coordinates and a normal offset. The source and output meshes share triangle indexing in the attachment area, and the generator carries the first character’s visibility flags while selecting appearances for visible slots from the two source records. On the output mesh, the software evaluates the three anchors on the deformed triangles and applies the stored offsets along the resulting surface normals. The software fits a translation, rotation and uniform scale to map the attachment’s three reference points onto the evaluated anchors in a least-squares sense.

Specific version of a part

Template assigned part appearance

The generator uses the first character's visibility flag to determine whether the output part is visible. For a visible part, it uses the part type to look up a mesh identifier and material values in the selected output template.

Per part color sliders

The editor displays red, green, and blue sliders for the selected part type. Moving a slider writes a normalized channel value to that part's material parameters and updates the rendered character.

User drawn mesh attachment

The player draws a closed outline and selects a depth, and the editor triangulates and extrudes the outline to create an accessory mesh. A placement input stores the mesh identifier, attachment point, and local transform in the character record.

Paired character generation screen

A dedicated generation screen loads two selected character records into a preview scene. A generate input passes both records to the character generator, which creates a third record and displays the resulting character.

Per type visibility bitmask

Each part type maps to one bit in a character visibility mask, with zero indicating a hidden part. When the bit for the first character's part type is zero, the generator clears the corresponding bit for the third character, and the renderer skips that part.

Cite aspatent.fyi, US 2026/0355634 A1, claim 1, first published 2026-11-19T13:37:15-05:00, https://patent.fyi/US20260355634/, SHA-256 73566fc82b4ac1a52f6adfb17fac21ce181a6de4ed64229eb7a28167fdb8ec9b
First published
Permanent addresshttps://patent.fyi/US20260355634/
Content fingerprint (SHA-256)73566fc82b4ac1a52f6adfb17fac21ce181a6de4ed64229eb7a28167fdb8ec9b
Methodv2026-11-18.2 · automated, not reviewed by a person
Correctionscorrections@patent.fyi