ReSkate custom-map textures and HUD troubleshooting

First identify which symptom you have

Issue #309 describes rainbow, corrupt, dark or black textures on custom maps, with Mammoth Mountain and Timber Ridge Snake Run as examples. Issue #311 instead describes a UI texture mod that works in the city but reverts to stock UI on custom maps such as SLS Hangar and PLYWORKS. Keep these cases separate from a game crash, a map that never loads or an invisible character.

Compare a minimal, reversible setup

The aim is to identify which change reproduces the symptom. Keep the supported game build and current separate-folder setup constant. Back up your current mod profile or note its enabled items before changing it. A comparison that narrows the issue is useful evidence even if it does not fix the map.

1. Record the launcher/runtime version, Steam game build, affected map package and package version before making changes.
2. Use the launcher’s MY MODS controls to disable unrelated mods, keep the map and its declared dependencies, then relaunch. Note the exact profile you tested.
3. Compare the city with one affected custom map. For a HUD problem, compare the same map with and without the UI texture mod; change one variable at a time.
4. Capture whether the symptom persists and restore your original profile when finished. A disappearing symptom narrows the trigger; it does not prove the map or another mod is faulty.

Collect evidence that can be compared

A clear report should describe where the problem starts and which comparison changes it. Include screenshots of the same UI or surface in the city and affected map where possible. ReSkate 2.1.1 adds extra diagnostics after a GPU stops responding, but that release change is not a texture-repair guarantee.

• ReSkate launcher/runtime version, game build, operating system, GPU and driver; for Proton, also record its version.
• Original map and UI-mod package links, exact versions, enabled mod list and reproducible steps from a fresh launch.
• City-versus-map results, UI-mod on/off results, screenshots and the relevant log/error. Remove account details and private file paths before sharing publicly.

Follow the matching report and keep fixes provisional

At this review both reports remained open without a confirmed general fix. In #311 the reporter suspects that custom maps carry HUD resource chunks that are not merged forward like EBX/Lua changes, but explicitly has not built or tested the proposed fix. Treat that as a lead for maintainers, not a repair to apply blindly. Check the matching issue for later maintainer replies or a linked release before describing the problem as solved.

October 21: missing cosmetics and long-loading reports

A new Discord report combines missing textures or cosmetics, a long black screen and falling through the map. Other users describe similar symptoms, but no maintainer-confirmed general fix was observed. Disabling mods is a comparison suggested by participants, not proof of one cause. An older Studio PNG fix and a forum Fixed tag do not establish that every current case is solved.