[Bug] wires not updating #1862
Labels
Comments
|
I can investigate but have a few questions:
|
|
The copy of the world was attached to report. And yes i am sure it is not
just render issue since no components reacted. If it was just render issue
the f3+t should fix it but it didn't. Only way to solve it was completely
reloading the game instance, not just world.
…On Tue, May 28, 2024, 23:18 MrTJP ***@***.***> wrote:
I can investigate but have a few questions:
1. Can you load back into your world with *only* ProjectRed installed
and see if it still happens? A copy of that world would be useful.
2. Do you know if its just a rendering issue with the wires themselves
or are blocks actually not responding to signal changes?
—
Reply to this email directly, view it on GitHub
<#1862 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJE66QL75Q26M5WRXPLFXT3ZETYCXAVCNFSM6AAAAABILWSQWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZWGEZDQMZUGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Forgot to add... yes it was doing it even if i had only project red
installed.
…On Tue, May 28, 2024, 23:32 Stano Chytrý ***@***.***> wrote:
The copy of the world was attached to report. And yes i am sure it is not
just render issue since no components reacted. If it was just render issue
the f3+t should fix it but it didn't. Only way to solve it was completely
reloading the game instance, not just world.
On Tue, May 28, 2024, 23:18 MrTJP ***@***.***> wrote:
> I can investigate but have a few questions:
>
> 1. Can you load back into your world with *only* ProjectRed installed
> and see if it still happens? A copy of that world would be useful.
> 2. Do you know if its just a rendering issue with the wires
> themselves or are blocks actually not responding to signal changes?
>
> —
> Reply to this email directly, view it on GitHub
> <#1862 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AJE66QL75Q26M5WRXPLFXT3ZETYCXAVCNFSM6AAAAABILWSQWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZWGEZDQMZUGA>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
I have run into this issue several times myself in a singleplayer world. Today, I got it to occur on a multiplayer server while experimenting with friends which produced a stacktrace. I am not sure what we specifically did to trigger it, but I think it might have been breaking or placing a wire, bundle, or microblock. It was also definitely not just a rendering glitch as wires and cells globally stopped responding to signal changes from levers and other redstone sources. As a specific example, if I placed an illumar lamp, placed a lever on it directly, and flicked the lever, it worked. If I then separately placed a lever and illumar lamp a few blocks apart, connected them with red alloy wire, and flicked the lever, nothing happened. Versions:
No ComputerCraft computers or chunk loaders were present anywhere in the world when the issue started. Stacktrace: |
|
Interesting stack trace. It occurred when you tried to break a Framed bundled cable part. Its definitely a bug, though not sure if related to this issue. Either way, if you can find a way to do it reliably, this would be an easy fix. |
|
Same issue occurred on my client:
The bug occurred after I entered the map WITHOUT doing anything( breaking or placing any block), its mechanism is still unknown... |
|
Have you moved or copied any ProjectRed blocks around in your world with WorldEdit? Would love to get my hands on a save that causes this issue to occur repeatedly. |
|
Yes I did. I tested just now that simply move/paste PR blocks does not cause this problem (reliably). |
|
I managed to find something which causes this consistently on 1.20.1, though I've no idea how it got to this point. On flicking the lever attached to the red wire (beneath the small tower of sponges, you should be right in front of it when you spawn in) on and then off, you get the following error, quite similar to the last part of some of the other errors: Error message
It seems as if the top wire over the AND cells is mistakenly stuck high while everything else attached to it is low. When you attempt to unpower it it seems to break. Curiously, the lever also doesn't make a sound when you flick it off for the first time (that is, when it causes the error) but then works normally after that. I should note that I had a number of other mods installed when this issue cropped up, which I've listed below, but the save produces the error just as well with just the project red mods installed and nothing else (which is how the save I've linked is set up). Mod List
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Minecraft version
1.19.x
CodeChickenLib version
4.3.2.490
CBMultipart version
3.2.0.139
ProjectRed version
4.18.0-beta +4
What happened?
During my creative play-trough I stumbled upon strange bug where levers don't update wire signals. It seems to happen out of nowhere and affects wires globally. Like if the updating system stopped working. It does not produce any errors nor warnings in the logs, therefore i am not including them. And there was no crash log so i am including whatever i have.
Crash log
How do you make it happen again?
copy of my world: computation heaven.zip
Haven't figured out how to reliably recreate it but it happens at least once every play-season mainly when it lasts longer time. But time probably doesn't pay any role. In my opinion it might be optimization issue.
The text was updated successfully, but these errors were encountered: