SHP(TD) LCW Decoder limitation

Open
#10,609 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
game-dev

Research direction

Compare the existing SHP (TD) decoder with the VQA decoder's higher-resolution LCW handling, focusing on the null-byte switch to relative offsets. Done means SHP decoding supports the extended format beyond the current 64 KB basic encoding limit; no encoder change is requested.

Written by the indexing model from the issue text.

Description

Feature

I would humbly request this limitation be uplifted by porting the higher resolution algorithm support from VQA decoder also for SHP as SHP currently only support the 64kb at max basic encoding decode which is switched to the other LCW algorithm that uses relative offsets instead of absolute by null byte marker.
If null byte is encountered, switch to the other LCW decoder method just like VQA decoder does already in OpenRA.

Else SHP (TD) format is resolution limited somewhere above 256x256 at best :/ and what exceeds this, will also look ingame like the picture. Not asking for encoder here, just extended format read support.

tdencoding

Dominant language
C#
Stars
17.4k
Forks
3k
Avg merge
1d 12h
Merged PRs (30d)
14

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenRA/OpenRA

All issues in OpenRA/OpenRA

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.