Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

owo-ui-error; No ui model with id:config #61

Open
notIkibo opened this issue Oct 17, 2022 · 13 comments
Open

owo-ui-error; No ui model with id:config #61

notIkibo opened this issue Oct 17, 2022 · 13 comments
Labels
priority: low this issue only has minor effects - adressing it is not immediately required status: confirmed this issue is reproducible or otherwise confirmed to exist status: investigating this issue is not easily reproducible or fixable, the cause is being investigated type: compatibility this issue is caused by a compatibility problem

Comments

@notIkibo
Copy link

I guess everything works fine (?)
Though every time I open my MC modpack, I see this. Really every time. I couldn't find anything in the logs.
image
latest.log

Now some probably unnecessary information or fun facts:
It looks like this for the majority of the Mojang loading screen and the error is only visible for like a couple frames
image

Anyway, thank you for reading and hopefully finding the problem isn't that though? I unfortunately have no clue on how to find the problem, but probably anyone else can find it

@Noaaan
Copy link
Member

Noaaan commented Oct 17, 2022

Font errors like that are usually a sign of DashLoader having issues. Have you tried running your game with it disabled?

@gliscowo
Copy link
Member

In fact, this is just what the text renderer does during a resource reload - it's missing every single glyph and thus always draws the empty box. I wouldn't be concerned about that, the actual owo error is significantly more strange, especially given the time at which it appears. The only way I could explain this is if someone is trying to initialize a config screen way too early, but we'll need to do some investigation - thanks for reporting
Cheers

@notIkibo
Copy link
Author

Font errors like that are usually a sign of DashLoader having issues. Have you tried running your game with it disabled?

I just did and next to taking a minute longer to load, nothing changed

@notIkibo
Copy link
Author

In fact, this is just what the text renderer does during a resource reload - it's missing every single glyph and thus always draws the empty box. I wouldn't be concerned about that, the actual owo error is significantly more strange, especially given the time at which it appears. The only way I could explain this is if someone is trying to initialize a config screen way too early, but we'll need to do some investigation - thanks for reporting Cheers

Wow, thanks mate. That is really good to hear. I do give out my issues, if I encounter any though most devs don't really care or don't trust it's their fault.
It surely is my mistake though then I need some basic understanding of modding and I don't know where to find that knowledge (except maybe a dozen of youtube videos)

@Firrae95
Copy link

Has this issue been resolved? I have a minecraft server running and a few of the players on the server are reporting this same issue, already tried relogging into minecraft launcher and repairing profile in curseforge.

@notIkibo
Copy link
Author

No, unfortunately not. There hasn't been an update since I said that

@gliscowo gliscowo added priority: low this issue only has minor effects - adressing it is not immediately required status: confirmed this issue is reproducible or otherwise confirmed to exist status: investigating this issue is not easily reproducible or fixable, the cause is being investigated type: compatibility this issue is caused by a compatibility problem labels Jan 29, 2023
@DontAtTheNex
Copy link

I got something you can try, rollback to owo-lib-0.8.1+1.19.jar and if you have Fabric Waystones you may need to rollback that to wraith-waystones-3.0.3+mc1.19.2.jar and it should boot up without any owo error.

This is just something I discovered when making my pack for MC 1.19.2 Fabric v0.14.19
Of course it maybe different depending on the mods you have but its worth a shot.

@splatchoot
Copy link

splatchoot commented Jun 4, 2023

i'm having this problem too, i know saying it won't fix your issue, but it might change the priority of this issue
it's also taking a looooooooooong time to load

@gliscowo
Copy link
Member

gliscowo commented Jun 4, 2023

The reason why this hasn't been resolved yet isn't so much a lack of priority as it is simply the fact that nobody has been able to consistently reproduce it. Thus, if we can't reproduce the problem in a reliable manner, we can't try to figure out why it happens

If you think you can provide us with steps required in order to finally get it replicated reliably, please do let us know
Cheers

@notIkibo
Copy link
Author

notIkibo commented Jun 4, 2023

Ngl, I don't have it anymore. It suddenly stopped occuring and I don't know when. Im on 1.19.2 on the latest update and latest Fabric Loader, but I think I already noticed it being gone in 19

@splatchoot
Copy link

If you think you can provide us with steps required in order to finally get it replicated reliably, please do let us know

It's a modpack I made with polymc, is there any way I can send you all the files of this modpack maybe?

@LevelsCraft7
Copy link

Hello, I've also had this problem for some time, but for no real reason.
I have identified this bug when Betterend mods and Macaws mods are active. I've deactivated everything that could be linked to UI in their configs, but to no avail. Has anyone found a solution?
Thanks

@OrdinaiCo
Copy link

Hello, I may have the ability to reproduce it consistently on every launch via the modpack I am in development of, however from a chunk of trial and error I have not been able to resolve the issue, and the error is persistent. Is there an effective way I could try and help out with this issue being solved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low this issue only has minor effects - adressing it is not immediately required status: confirmed this issue is reproducible or otherwise confirmed to exist status: investigating this issue is not easily reproducible or fixable, the cause is being investigated type: compatibility this issue is caused by a compatibility problem
Projects
None yet
Development

No branches or pull requests

8 participants