orbiternassp / orbiternassp/NASSP
Lunar Rover Instruments Don't Work When Using Hardware Rendering
Open
Nobody has claimed this yet.
bug
- Dominant language
- C++
- Stars
- 213
- Forks
- 74
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 6
Description
Due to the fact that the LRV uses the function MeshgroupTransform in order to move the instruments, when using D3D9Client, where the function is not supported, none of the instruments work and hence are static. This issue is not seen when using software rendering.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Lunar Rover instrument movement through MeshgroupTransform and compare its behavior under D3D9Client hardware rendering and software rendering. The issue is done when the instruments move correctly with hardware rendering without regressing software rendering; no file or test is named in the report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100