[REQUEST] The implemented Angle support for Windows is not usable
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- cpp
- Domain
- computer-graphics, operating-systems
Research direction
Start by reading pull request 942 and the Windows Angle implementation it introduced, then compare the requested GLES 3.0 requirement with the Direct3D 11 support described in this issue. Done means projectM can render through Angle with Direct3D 11 on Windows without requiring GLES 3.2; the payload names no specific tests or files.
Written by the indexing model from the issue text.
Description
Please confirm the following points:
- This question is NOT about the Android apps in the Play Store
- I have searched the project page to check if the question was already asked elsewhere
Topic
General Request
Your Request
We started on Kodi to update our addon https://github.com/xbmc/visualization.projectm to use newest version from here.
Unfortunately, there was a significant, tricky error in the Windows implementation for Angle via DirectX and unfortunately Kodi uses Direct3D 11 on Windows and not GL or Vulkan.
It was added with this request here https://github.com/projectM-visualizer/projectm/pull/942 (also wrote a small note in it).
Thank you very much for the implementation, from testing it works fine in terms of code processing and implementation in Kodi is very good, just no GLES rendering via Angle under Windows!
Angle only allows GLES version 3.0 with DirectX and the 3.2 specified for Angle in projectM cannot be used (Angle with OpenGL directly under Windows supports GLES 3.2, only then would we not need Angle).
Here is the support list defined at https://github.com/google/angle:
| Direct3D 9 | Direct3D 11 | Desktop GL | GL ES | Vulkan | Metal | |
|---|---|---|---|---|---|---|
| OpenGL ES 2.0 | complete | complete | complete | complete | complete | complete |
| OpenGL ES 3.0 | complete | complete | complete | complete | complete | |
| OpenGL ES 3.1 | complete | complete | complete | |||
| OpenGL ES 3.2 | in progress | in progress | complete |
If it were somehow possible to reduce the minimum GLES version in projectM to 3.0 it would be good, as support for higher versions will not be available under Angle in the foreseeable future.
- Dominant language
- C++
- Stars
- 4.5k
- Forks
- 485
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 5
Contributor guide
No contributing guide indexed for this repository
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.
More from projectM-visualizer/projectm
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
projectM-visualizer/projectm#1028 · 2 comments ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
projectM-visualizer/projectm#1024 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
projectM-visualizer/projectm#1004 · 1 comment · 1 reaction ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
projectM-visualizer/projectm#1000 · 6 comments ·
-
question
Difficulty 5/5 Over a week Newbie friendliness 30/100
projectM-visualizer/projectm#999 · 3 comments ·
All issues in projectM-visualizer/projectm
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·