openframeworks / openframeworks/openFrameworks
Strange drawing behaviors from 0.84 and 0.9.3 (RPI)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
I am seeing some weird glitches in 0.9.3 that didn't exist in 0.8.4
This is the app I am running. First in 0.84 and then 0.9.3
The app captures the camera into a texture using my addon and applies a shader. In 0.9.3, when the shader is deactivated it is like there is a pool of buffers that is slowly being drained. You can see the shader effects every few frames even though it is not active. It seems to be more apparently the longer period that the shader is applied
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 with example-shaders/src/ofApp.cpp and compare the reported behavior between versions 0.8.4 and 0.9.3 on the Raspberry Pi. Reproduce the camera-texture and shader sequence, then trace what remains active after the shader is deactivated. Done means shader effects no longer appear in later frames after deactivation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, raspberry-pi
- Domain
- computer-graphics, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100