bengreenier / bengreenier/webrtc-unity-plugin
texture data is not written directly to device context
- Dominant language
- C#
- Stars
- 117
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
This tracks an optimization that we have added in the past for https://github.com/3DStreamingToolkit/3DStreamingToolkit - wherein we store the device context and write to the device directly, rather than marshalling data up into a unity texture.
https://github.com/3DStreamingToolkit/3DStreamingToolkit/blob/master/Plugins/UnityServerPlugin/StreamingUnityServerPlugin.cpp#L339
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the issue's linked StreamingUnityServerPlugin.cpp reference around line 339 and then locate the corresponding texture-handling entry point in this repository. Compare the existing Unity texture path with the referenced direct device-context approach; done means texture data is written directly to the device context without marshalling through a Unity texture.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, csharp, unity
- Domain
- computer-graphics, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100