openframeworks / openframeworks/openFrameworks
ofMesh draw wireframe with indices on IOS
Open
Nobody has claimed this yet.
bug
core
section-3D
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
test code:
ofEnableAlphaBlending();
ofMesh temp;
temp.setMode(OF_PRIMITIVE_TRIANGLES);
temp.addVertex( ofPoint(200,500));
temp.addVertex( ofPoint(300,500));
temp.addVertex( ofPoint(250,550));
temp.addVertex( ofPoint(300,550));
temp.addVertex( ofPoint(250,600));
temp.addIndex(0);
temp.addIndex(1);
temp.addIndex(2);
temp.addIndex(1);
temp.addIndex(2);
temp.addIndex(3);
temp.addIndex(2);
temp.addIndex(3);
temp.addIndex(4);
ofSetColor(255,255,255, 60);
temp.draw();
ofSetColor(255,0,0);
temp.drawWireframe();
produces odd output on IOS
vs desktop
I've seen glitchier things w/ mesh.drawWireframe() on ios when the mesh has indices, this is just a simple test to show that something's not totally right.
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 the provided indexed ofMesh reproduction, especially addIndex(), draw(), and drawWireframe(), and compare the iOS rendering path with the desktop result. Confirm the behavior using the same triangle and index data; done means indexed wireframe rendering on iOS matches the expected desktop output without the shown glitches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, ios
- Domain
- computer-graphics, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100