Lyra should be put on Github

General Feedback & Requests
1

Given that Lyra is intended to be kept up to date and developed alongside the UE5 process, Lyra should also be put on Github.

This gives users a few things that are incredibly nice to have:

  1. We can fork Lyra to add our own features to it
  2. We can merge Epic’s upstream changes down into our own forks of Lyra, keeping us up to date easier with best practices and fixing bugs.
  3. We can submit pull requests against Lyra to improve it as well, improving the developer ecosystem
  4. we can possibly file bugs using the github tracker, if Epic wants to support that.

The advantages to putting Lyra on github are immense, and the entire development community would benefit from it.

2

I agree! That would work out to further enhance access to the code.

5 Likes
3

I agree. This would be really helpful!

4

Definitely!

5

Yes! I fixed already two little bugs with Lyra, and it would be much easier to share PR in a single place rather than spread them around in forum posts.

2 Likes
6

Agreed 100%, at least the cpp core.

7

Hey folks!

We’re in the process of looking into this. We will update everyone once we have some news :slight_smile:

Thanks, and happy developing! <3

19 Likes
8

Agreed.

9

It cant happen soon enough.

10

Great news! Let’s hope this happens soon :slight_smile:

11

good to hear! I hope it happens soon!

12

Awesome, thank you! I was just about to ask for this myself! :slightly_smiling_face:

13

Any update on this @SkyeEden ?

I’ve found and fixed several Lyra bugs so far, with several more pending.

At the moment there is no way for me to share these bug fixes with Epic or with other devs trying to use Lyra other than to b/vlog and hope people google the exact keywords that will lead them to the solution.

If Github won’t be used for some reason, then please do give us some other way to submit bug reports and bug fixes.

Please and thank you! :smile:

14

If its not too much trouble, out of curiosity, what were the bugs you found?

I know someone else online has mentioned the potential unchecked RPC for dash that could be expoited. (no server side checks for dash cooldown issued by the client)

15

At the moment the bug lists include several unarmed animation bugs, and some “OnReady” type events firing too many times.

And of course the vast majority of the Lyra C++ code base does not seem to be exported and/or lists required data as private without giving any C++ getter/setter. meta=(AllowPrivateAccess=true) is garbage and not a viable solution for extensible code.

Nothing disastrous, pretty easy fixes in fact, but still the kinds of things that would be great to be able to submit back to the official distribution so other people don’t have to find/fix them as well.

2 Likes
16

I’ve noticed Lyra has received an update recently, since there is no repo, do you guys know of anything like release notes?

17

it’s really crazy that they decided to release Lyra as a framework and then deploy multiple updates to it without so much as a changelog. I don’t think i’ve ever had a prompt to update something without a changelog in all my years of using a ■■■■ computer.

18

Yes, see this thread New Lyra Update - Release Notes? - #4 by iZtrahd . a good case and point for a github repo.

I will literally be making one in a few weeks if epic doesn’t. Kind of holding out atm.

1 Like
19

I considered pushing my version of Lyra up to Github. I’ve made about 20 changes to it including a few bug fixes and mostly exporting C++ classes.

The 5.0.2 update didn’t touch much code at all, it was mainly just some useless uasset updates so it was easy to merge.

My concern with posting this myself on Github is that technically Epic owns the code and I’m not sure what their policy is for other people “publishing” it, which is effectively what a public Github repo would do.

Epic, PLEASE PUSH LYRA TO GITHUB. Or give us some guidance on how we can.

Please and thanks.

7 Likes
20

Upload it and see what happens, someone has to do it