Signs Become Empty On Older Servers #3137

New Issue

Ghost · 2022-12-15T12:49:07+01:00

Ghost commented

2022-12-15 12:49:07 +01:00

No idea why, but on older servers, signs seem to just turn empty for no reason and placing any new signs to write things on won't work either.

The only solution to this that I have found is to create a new world entirely, then the signs work on that world, but they still don't work on the old world.

The signs eventually stop working on the newer world as well, forcing you to once again create a new world.

No idea why, but on older servers, signs seem to just turn empty for no reason and placing any new signs to write things on won't work either. The only solution to this that I have found is to create a new world entirely, then the signs work on that world, but they still don't work on the old world. The signs eventually stop working on the newer world as well, forcing you to once again create a new world.

ancientmarinerdev commented

2022-12-15 12:52:54 +01:00

By placing new signs, do you mean digging up and placing again? Or making a new one from scratch?

Michieal added the

needs more information

label 2022-12-15 14:26:04 +01:00

Michieal commented

2022-12-15 14:27:03 +01:00

error logs?
version numbers of the MCL of the server?
etc.

I need to know what to look for.

error logs? version numbers of the MCL of the server? etc. I need to know what to look for.

Ghost commented

2022-12-15 15:15:00 +01:00

By placing new signs, do you mean digging up and placing again? Or making a new one from scratch?

I just placed a new one from the creative inventory.

error logs?
version numbers of the MCL of the server?
etc.

I need to know what to look for.

This had been a problem for a while now. It has been a problem for months. It is only now that I had decided to open an issue for it, after remembering the problem. Version probably doesn't matter here.

As for error logs, what do you mean by this? I got no errors in the chat when placing signs.

>By placing new signs, do you mean digging up and placing again? Or making a new one from scratch? I just placed a new one from the creative inventory. >error logs? version numbers of the MCL of the server? etc. >I need to know what to look for. This had been a problem for a while now. It has been a problem for months. It is only now that I had decided to open an issue for it, after remembering the problem. Version probably doesn't matter here. As for error logs, what do you mean by this? I got no errors in the chat when placing signs.

Michieal commented

2022-12-15 16:19:08 +01:00

I mean that if the signs fail, it states an error.
Depending though, minetest can report an error as a warning, and it doesn't show up in the chat log.

Debug.txt from the minetest directory.

Do you know when it started happening?

And the reason I asked you about the server's Mineclone version that it was, is because it will tell me needed information about the signs that were there.

So yeah, it does matter, thanks :)

I mean that if the signs fail, it states an error. Depending though, minetest can report an error as a warning, and it doesn't show up in the chat log. Debug.txt from the minetest directory. Do you know when it started happening? And the reason I asked you about the server's Mineclone version that it was, is because it will tell me needed information about the signs that were there. So yeah, it does matter, thanks :)

Ghost commented

2022-12-15 16:31:58 +01:00

Debug.txt from the minetest directory.

I read the debug.txt, and it only mentions me placing the signs. It doesn't even mention any issues.

Do you know when it started happening?

It started happening since a couple of months ago. I don't remember very well.

And the reason I asked you about the server's Mineclone version that it was, is because it will tell me needed information about the signs that were there.

As for the version, it's difficult to say, since I am using a custom branch that I use to mess around with certain fixes. I'd still say that it's about one version before the mcl_hoppers fixes.

>Debug.txt from the minetest directory. I read the debug.txt, and it only mentions me placing the signs. It doesn't even mention any issues. >Do you know when it started happening? It started happening since a couple of months ago. I don't remember very well. >And the reason I asked you about the server's Mineclone version that it was, is because it will tell me needed information about the signs that were there. As for the version, it's difficult to say, since I am using a custom branch that I use to mess around with certain fixes. I'd still say that it's about one version before the mcl_hoppers fixes.

Michieal commented

2022-12-16 02:18:18 +01:00

@FossFanatic so, are you using the Master-InDev? or is it a release branch?

The reason that it's important to know, is that I need to be able to grab the version that the signs were made in, and then upgrade that to the version that is being used, minus mods and minus different tweaks that you have made. That way, I can test it, and see what's going on.

Also, it would be helpful to know if it is wall signs, standing signs, or both that are affected. Another piece of data that I need to be able to see -- does a restart of the server / single player game fix it? or do they regenerate after a couple of minutes? do they stop working after a specified amount of time?

The way that the signs work has been upgraded and we did test it with version 0.78 and 0.79 being upgraded.

@FossFanatic so, are you using the Master-InDev? or is it a release branch? The reason that it's important to know, is that I need to be able to grab the version that the signs were made in, and then upgrade that to the version that is being used, minus mods and minus different tweaks that you have made. That way, I can test it, and see what's going on. Also, it would be helpful to know if it is wall signs, standing signs, or both that are affected. Another piece of data that I need to be able to see -- does a restart of the server / single player game fix it? or do they regenerate after a couple of minutes? do they stop working after a specified amount of time? The way that the signs work has been upgraded and we did test it with version 0.78 and 0.79 being upgraded.

Ghost commented

2022-12-16 09:17:29 +01:00

Also, it would be helpful to know if it is wall signs, standing signs, or both that are affected.

Both. Both are affected.

Another piece of data that I need to be able to see -- does a restart of the server / single player game fix it?

No.

or do they regenerate after a couple of minutes?

No.

do they stop working after a specified amount of time?

Yes.

The way that the signs work has been upgraded and we did test it with version 0.78 and 0.79 being upgraded.

Which is coincidentally when the problems began. I had this problem since 0.79.

>Also, it would be helpful to know if it is wall signs, standing signs, or both that are affected. Both. Both are affected. >Another piece of data that I need to be able to see -- does a restart of the server / single player game fix it? No. >or do they regenerate after a couple of minutes? No. >do they stop working after a specified amount of time? Yes. >The way that the signs work has been upgraded and we did test it with version 0.78 and 0.79 being upgraded. Which is coincidentally when the problems began. I had this problem since 0.79.

Michieal commented

2022-12-16 19:41:13 +01:00

Well, 0.81 is when the new signs code went into play. It was merged into 0.81-indev about 1/3 of the way to 0.82-indev.

The current version that was released in 0.81 (and, even more so now as it has the checker for clearblocks) actually goes through and regenerates the signs every minute or two.

The only things that would prevent that, is if 1) the sign was placed without anything written on it. 2) the map file became corrupted. 3) it was converted from MCL5 -> MCL2. (That last one specifically states "YMMV")

Well, 0.81 is when the new signs code went into play. It was merged into 0.81-indev about 1/3 of the way to 0.82-indev. The current version that was released in 0.81 (and, even more so now as it has the checker for clearblocks) actually goes through and regenerates the signs every minute or two. The only things that would prevent that, is if 1) the sign was placed without anything written on it. 2) the map file became corrupted. 3) it was converted from MCL5 -> MCL2. (That last one specifically states "YMMV")

Ghost commented

2022-12-16 19:52:58 +01:00

I might have to play the latest stable release then, until I encounter this problem again and can confirm that the problem still exists.

❤️ 1

Michieal commented

2022-12-16 19:57:59 +01:00

I would. that or try it with the last signs commit.

Ghost commented

2022-12-27 16:59:33 +01:00

I have found another lead. That lead is that the sign letters disappear when shaders are turned off?

This is more apparent on multiplayer servers.

I have found another lead. That lead is that the sign letters disappear when shaders are turned off? This is more apparent on multiplayer servers.

👍 1

Michieal commented

2022-12-28 05:04:22 +01:00

I have found another lead. That lead is that the sign letters disappear when shaders are turned off?

This is more apparent on multiplayer servers.

Thank you for this.

This is why I said that entities need shaders turned on. What clued me in was the item frame maps where the maps didn't display. (Mind you that maps are their own can of worms.) Smooth lighting requires shaders.

Entities (the sign's lettering) are very ... finicky and can break really easily. And, almost every time, it's not our code. it's either the user's hardware, or the engine.

I do have hopes that we can get to the bottom of this, and then state what is required in the requirements.

If you have ideas on how to fix this, I am very open to hearing them, and will help in any way I can to fix it.

> I have found another lead. That lead is that the sign letters disappear when shaders are turned off? > > This is more apparent on multiplayer servers. Thank you for this. This is why I said that entities need shaders turned on. What clued me in was the item frame maps where the maps didn't display. (Mind you that maps are their own can of worms.) Smooth lighting requires shaders. Entities (the sign's lettering) are very ... finicky and can break really easily. And, almost every time, it's not our code. it's either the user's hardware, or the engine. I do have hopes that we can get to the bottom of this, and then state what is required in the requirements. If you have ideas on how to fix this, I am very open to hearing them, and will help in any way I can to fix it.

👍 1

Michieal commented

2023-02-04 11:26:09 +01:00

Broken signs have a built in fix. Punching them updates the sign's writing. I just re-reviewed the code for it, and it was something that was built in, in the original sign code. After testing it for the rewrite, I left it in as a manual way to fix the sign. I had assumed that it was because of not having an automated /clearobjects fix. But, it could have been because they somehow lose their entity. Another fix is to move far enough away for the nodes to be unloaded, allow them to unload, and then come back so that they are loaded back up.

The latter fix will restart the nodetimer on the signs so that they regenerate the sign entity every X seconds (like 35 or 40 seconds).

If, it is a shaders issue, though, they will probably stay blank. So, we need to ascertain if that is what is happening, or if the node timer failed. So, can you try punching it and see if that fixes the affected signs? (as this will answer the questions.)

Broken signs have a built in fix. Punching them updates the sign's writing. I just re-reviewed the code for it, and it was something that was built in, in the original sign code. After testing it for the rewrite, I left it in as a manual way to fix the sign. I had assumed that it was because of not having an automated `/clearobjects` fix. But, it could have been because they somehow lose their entity. Another fix is to move far enough away for the nodes to be unloaded, allow them to unload, and then come back so that they are loaded back up. The latter fix will restart the nodetimer on the signs so that they regenerate the sign entity every X seconds (like 35 or 40 seconds). If, it is a shaders issue, though, they will probably stay blank. So, we need to ascertain if that is what is happening, or if the node timer failed. So, can you try punching it and see if that fixes the affected signs? (as this will answer the questions.)

Ghost commented

2023-02-04 12:09:36 +01:00

I punched the signs with shaders turned off, and the letters don't come back.

This is likely an issue with disabling shaders. The same also happens to paintings and maps.

Minetest will likely force shaders to be used in the future (as it should, since shaders are required if one wants to get anywhere graphically), so this problem won't really be encountered anymore.

I punched the signs with shaders turned off, and the letters don't come back. This is likely an issue with disabling shaders. The same also happens to paintings and maps. Minetest will likely force shaders to be used in the future (as it should, since shaders are required if one wants to get anywhere graphically), so this problem won't really be encountered anymore.

❤️ 1

ancientmarinerdev added the

nodes

label 2023-02-04 15:29:32 +01:00

ancientmarinerdev commented

2023-03-27 20:00:15 +02:00

erlehmann suggested that https://github.com/minetest/minetest/pull/12906 may fix this, so I'm thinking we can retest this after 5.7.

👍 1

ancientmarinerdev added the

Testing / Retest

label 2023-03-27 20:00:52 +02:00

ancientmarinerdev added the