![Exordium](https://media.forgecdn.net/avatars/thumbnails/614/437/256/256/637998093760381250.png)
Sign text not rendering
DarkAndBlue opened this issue ยท 21 comments
Note: this is more of a temporary release, since it's basically a straight port of the 1.19.4 version. Adds known issues with mods like Enhanced Block Entities. Tested with ImmediatelyFast.
Note: this is more of a temporary release, since it's basically a straight port of the 1.19.4 version. Adds known issues with mods like Enhanced Block Entities. Tested with ImmediatelyFast.
What does that mean? Is the issue already known or do you think im using Enhanced Block Entities or ImmediatelyFast? Or do you want me to use Enhanced Block Entities or ImmediatelyFast?
Or do you want me to not report this bug as it is marked as "temporary release"?
I mean with that, I know that this release is not perfect/has issues, especially with other mods. I don't have the time right now to make it proper, but people kept asking for "Exordium 1.20 when?". I know it works with just Sodium(at least it was tested with Sodium and ImmediatelyFast), so I assume you have something else in there causing issues. Either way, you can just turn off Sign buffering in the settings to fix it.
Yes I wanted to write that too with disabling sign buffering to temporarily disable fix the bug.
And Im only using the mods I listed above.
Also please don't feel stressed or pressured by this issue.
I only wanted to create this issue as I noticed it today and the version was new released and I thought you might need feedback/issues.
Hm, in that case, it could be interesting if adding ImmediatelyFast fixes it? Cause I had people test with Sodium before, without any issues.
Hm, in that case, it could be interesting if adding ImmediatelyFast fixes it? Cause I had people test with Sodium before, without any issues.
I encountered this issue some days ago, and tested with following circumstances iirc:
- With Sodium, Enhanced Block Entities, Exordium, ImmediatelyFast, EntityCulling, MoreCulling = Yes
- With Sodium, Enhanced Block Entities, Exordium, ImmediatelyFast, EntityCulling = Yes
- With Sodium, Enhanced Block Entities, Exordium, ImmediatelyFast = Yes
- With Sodium, Exordium, ImmediatelyFast = Yes
- With Sodium, ImmediatelyFast = No
ImmediatelyFast and Sodium was never disabled.
I mean, right now it crashes with Enhanced Block Entities, unless you turn off the buffering?
The "blank sign" issue is still present with the only the following mods on a single Minecraft 1.20.1 fabric instance:
- Sodium
- Exordium
- Fabric API
Just re-tested with only Fabric API 0.86.1+1.20.1
, Enhanced Block Entities 0.9+1.20
and Exordium 1.1.3.1-mc1.20.1
, and sign text renders with no issues. The game did not crash. Newest hotfix seems to block sign buffering if Enhanced Block Entities installed.
OS: KUbuntu 23.04
GPU: AMD core graphics card
Resource Packs: None
exordium.json
:
{
"configVersion": 2,
"enableSignBuffering": true,
"targetFPSNameTags": 60,
"enableNametagScreenBuffering": false,
"chatSettings": {
"enabled": true,
"maxFps": 20,
"forceBlend": false,
"forceUpdates": false
},
...
}
No, like I said, this is not a proper release, and these issues won't be worked on for now. Also, the nametag stuff might probably get removed instead of fixed.
Im also running into a similar issue with "Enable Nametags Buffering", it makes nametags invisible, should I open a seperate issue?
it could be the same cause as this one.
isn't this a duplicate of #27
No. This is just about 1.20 and since the release is not a "done" 1.20 release, its buggy. But for both the fix is the same, just turn off the buffering.
No, like I said, this is not a proper release, and these issues won't be worked on for now. Also, the nametag stuff might probably get removed instead of fixed.
It would be epic to have nametag buffering back, can you imagine if Exordium will give even better fps boost? Maybe also buffering hand/item? Everybody has text and hand on their screen almost all the time.
This issue doesn't happen when there is text on both sides on the sign, which is a 1.20 feature. I assume Exordium doesn't properly handle 1.20 signs and thus causes it to fail rendering entirely. For now you will have to put text on the other side of the sign.
I tested with text on both sides, worst case some check messes up and cancels rendering when there is text Only on one side.
This issue doesn't happen when there is text on both sides on the sign, which is a 1.20 feature. I assume Exordium doesn't properly handle 1.20 signs and thus causes it to fail rendering entirely. For now you will have to put text on the other side of the sign.
100 points to you:
It skipped everything when either side is empty. Also, an internal cache was not filled(probably causing a re-render each frame, which defeats the entire point). As said in the release notes, this 1.20 version is a "Better than nothing" WIP release, just don't have the irl time to test/debug/implement all the things right now.