Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Unity - Loading Assets/Audio Clips etc.

Open
#44 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp, grpc, unity
Domain
game-dev

Research direction

Start with the README's asset-downloading statement and the UnityWebRequest and UnityWebRequestMultimedia approaches named in the issue. Determine whether supported audio loading is intended; done would require a documented example or a clearly stated limitation.

Written by the indexing model from the issue text.

Description

Hi, I've been able to get the library working in a project and can talk with GRPC and download strings and png just fine.

But curious if it can also be used to load Audio Clips or other formats not necessarily asset bundles or addressables.

The readme says:
It can also be used for asset downloading via HTTP/2, providing more functionality to your projects.

Are there examples of doing this, with UnityWebRequest or UnityWebRequestMultimedia etc we can load AudioClip from a URL with an Ogg, Wav, Mp3.

I'm not seeing a way to easily load AudioClip from other formats, whilst using System.Net.Http.HttpClient with this handler and just wondered if there was something I'm missing.

I could cobble something together but wondering if someone knows how to use the built-in internal ways with Unity rather than use third-party decoder/libs such as https://github.com/gindemit/unity-wrapper-vorbis or https://github.com/NVorbis/NVorbis

Dominant language
C#
Stars
512
Forks
46
Avg merge
17h 26m
Merged PRs (30d)
6

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Cysharp/YetAnotherHttpHandler

All issues in Cysharp/YetAnotherHttpHandler

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.