Resonite: update for the splittening #137
Reference in New Issue
Block a user
Delete Branch "resonite-splittening"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Update Resonite documentation for the splittening - mainly just removing some out of date information.
this have been fixed https://github.com/Yellow-Dog-Man/Resonite-Issues/issues/5303
there should no need to be forced
Currently OpenComposite crashes Resonite https://github.com/Yellow-Dog-Man/Resonite-Issues/issues/5152
we should not recommend using it so if there's issues, as it'll be worst
is this a Linux only issues? I remember having it on window, maybe just cuz of bad machine, it just appear to be when doing some form of assets processing when assets isnt comming from Cloud (and after a few second is fine).
other than for the case of assets not yet cloud processed (which I can replicate on Window), I can not really replicated this issue
Resonite is now not typically CPU bound anymore, most of the time it will be GPU.
the comment about lowering rez for gpu bound still apply, but there could be precision about the ingame's graphics settings (in particular VRAM settings)
see my comment about opencomposite earlier anyway
I havent had any engine freeze, but we should had something about how the Renderer tend to crash more often than on window,
and also have something about this https://github.com/Yellow-Dog-Man/Resonite-Issues/issues/5246
you should add something about Viseme being broken https://github.com/Yellow-Dog-Man/Resonite-Issues/issues/5151
and this mod to fix it: https://github.com/KyuubiYoru/VisemesAtHome
added a certains number of change I feel are needed
There are a certain number of person having troubles with it,
but just yeeting and reinstalling game + prefix seems to fix it most of time. (also important too are the cache/data files https://wiki.resonite.com/Resonite_Data_Folders , I'll update the page with common paths on Linux)
only case that is really a problem is https://github.com/Yellow-Dog-Man/Resonite-Issues/issues/5335
from what I have seen.
also maybe a note about how first launch may be long as it'll download the runtime
Oh right I forgot
https://github.com/Yellow-Dog-Man/Resonite-Issues/issues/5217
On Nvidia and Intel, the game will always default to very low textures size in graphical settings, add a note about it too
mentioned in commit bredo228/lvra.gitlab.io@a77aa3f14f
changed this line in version 2 of the diff
changed this file in version 2 of the diff
added 1 commit
a77aa3f1- Resonite: remove mention about needing to force ProtonCompare with previous version
Thanks, wasn't aware of that.
changed this line in version 3 of the diff
added 1 commit
9474ce77- Resonite: Mention OpenComposite crashingCompare with previous version
added 1 commit
8cde6c33- Resonite: Add section about viseme analysis on LinuxCompare with previous version
Yeah, the textures stuff is a bit vague, generic, potentially hardware-dependent, and may not even be an issue anymore. Remove imo
At the very least remove the OC mention.
Eh, might as well gut most of this. We don't have the scaling stuff doc'd anywhere yet, so it's a bit awkward.
left review comments
mentioned in commit bredo228/lvra.gitlab.io@7f24920de4
changed this line in version 5 of the diff
added 1 commit
7f24920d- Resonite: remove mention of texture bugsCompare with previous version
Have changed this now.
changed this line in version 6 of the diff
added 1 commit
dd5a19ac- Apply 1 suggestion(s) to 1 file(s)Compare with previous version
changed this line in version 7 of the diff
added 1 commit
0badd456- Resonite: Mention issues with renderer on LinuxCompare with previous version
I've made some changes in https://gitlab.com/lvra/lvra.gitlab.io/-/merge_requests/132/diffs?commit_id=0badd456b422b2d9eea859e6b20ffb353d17be55 - how does this look now?
LGTM
resolved all threads
approved this merge request
LMK when ready
Ready!
resolved all threads
mentioned in commit
83245d2acf