hedge-dev / hedge-dev/UnleashedRecomp

Enhancement option to increase number of Fur Shells

Open
#566 0 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement video option
Dominant language
C++
Stars
5.1k
Forks
421
PR merge metrics
No merged PRs in 30d

Description

At higher render resolutions, the fur rendering method breaks down on the Werehog and you can see the individual shells pretty easily. This was a problem even on console, but the lower render resolution at least made it look decent most of the time.
Increasing the number of shells should help mitigate this if possible, although it would be a major performance hit so it should be an option like the enhanced motion blur.

I think it should be a slider, since different people will be rendering at different resolutions or maybe would want to have an absurd number of shells. There is a point of diminishing returns even at absurd render resolutions, because of the distance of each shell from the original mesh, so the max count shouldn't need to go higher then ~80?

From what I remember, it's just the Werehog and Chip who have shell fur. I believe the games default is around 11 shells for the Werehog? Chip is a smaller model and probably doesn't need to have this available.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No files or tests are named. Start by locating the Werehog and Chip shell-fur rendering path and the existing enhanced motion blur option; determine where a configurable shell-count slider belongs, then verify it changes the shell count while remaining optional.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-graphics, game-dev, performance
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.