did water_life crocs get into neon paint or something? (linux) #5778

New Issue

Closed

opened 2023-12-21 23:45:58 +00:00 by rewired_X · 26 comments

rewired_X commented 2023-12-21 23:45:58 +00:00

Copy Link

I say linux because I am using MT 5.8.0-1 on arch linux.
No, I did not photoshop this. This appeared exactly the way it did.
Windows does not display this discrepancy.

I say linux because I am using MT 5.8.0-1 on arch linux. No, I did not photoshop this. This appeared exactly the way it did. Windows does not display this discrepancy. 

Screenshot_20231221_184303.png

370 KiB

flux added the

1. kind/bug

3. source/unknown

labels 2023-12-22 01:51:48 +00:00

flux added the

4. step/question

label 2023-12-22 01:54:27 +00:00

flux commented 2023-12-22 01:55:06 +00:00

Member

Copy Link

can you give us more info about the linux build, e.g. version of irrlichtmt, graphics settings, etc.? seems fine for me:

can you give us more info about the linux build, e.g. version of irrlichtmt, graphics settings, etc.? seems fine for me: 

image.png

124 KiB

rewired_X commented 2023-12-22 22:42:00 +00:00

Author

Copy Link

I think the issue was I didn't also update minetest-common to 5.8.0-1 as well.
Croc's are fixed for me now, closing.

I think the issue was I didn't also update minetest-common to 5.8.0-1 as well. Croc's are fixed for me now, closing.

Screenshot_20231222_173950.png

2.3 MiB

rewired_X closed this issue 2023-12-22 22:42:01 +00:00

rewired_X commented 2023-12-22 22:44:10 +00:00

Author

Copy Link

apparently NOT fixed.
it went neon during nighttime.

apparently NOT fixed. it went neon during nighttime.

Screenshot_20231222_174341.png

1.4 MiB

rewired_X reopened this issue 2023-12-22 22:44:10 +00:00

rewired_X commented 2023-12-22 22:48:27 +00:00

Author

Copy Link

after relogging onto windows NOWWWWWWWWW it wants to look normal again...grrrrrrr
I don't have the slightest clue as to how to find arch linux version.
MT version is 5.8.0-1 (Irrlicht should be the same......?)
Only graphics setting that's different is I have trilinear filtering on.

after relogging onto windows NOWWWWWWWWW it wants to look normal again...grrrrrrr I don't have the slightest clue as to how to find arch linux version. MT version is 5.8.0-1 (Irrlicht should be the same......?) Only graphics setting that's different is I have trilinear filtering on.

Screenshot (1168).png

1.7 MiB

rewired_X commented 2023-12-29 00:17:49 +00:00

Author

Copy Link

I've taken this to the people who might know something about this
Upstream issue: https://github.com/minetest/minetest/issues/14174

I've taken this to the people who might know something about this Upstream issue: https://github.com/minetest/minetest/issues/14174

flux commented 2023-12-29 00:29:05 +00:00

Member

Copy Link

I've taken this to the people who might know something about this
Upstream issue: https://github.com/minetest/minetest/issues/14174

hope that turns up something. sorry this dropped off my radar, but i wasn't able to replicate it (even on arch).

> I've taken this to the people who might know something about this > Upstream issue: https://github.com/minetest/minetest/issues/14174 hope that turns up something. sorry this dropped off my radar, but i wasn't able to replicate it (even on arch).

rewired_X commented 2023-12-29 00:33:37 +00:00

Author

Copy Link

its alright, at least complaining to the higher ups might get me somewhere (and hopefully I don't get shut down D:)

its alright, at least complaining to the higher ups might get me somewhere (and hopefully I don't get shut down D:)

rewired_X commented 2024-01-04 00:06:01 +00:00

Author

Copy Link

After reinstalling minetest twice, this is now fixed. Apparently something got borked during updating the client.

After reinstalling minetest twice, this is now fixed. Apparently something got borked during updating the client.

rewired_X closed this issue 2024-01-04 00:06:01 +00:00

flux commented 2024-01-04 01:30:50 +00:00

Member

Copy Link

After reinstalling minetest twice, this is now fixed. Apparently something got borked during updating the client.

oh, i bet one of minetest's shaders was from an incompatible version, i've encountered something vaguely similar in the very early days of me using minetest. the effects were much less subtle, though.

> After reinstalling minetest twice, this is now fixed. Apparently something got borked during updating the client. oh, i bet one of minetest's shaders was from an incompatible version, i've encountered something vaguely similar in the very early days of me using minetest. the effects were much less subtle, though.

AliasAlreadyTaken removed the

4. step/question

label 2024-01-04 12:29:26 +00:00

AliasAlreadyTaken commented 2024-01-04 12:30:34 +00:00

Owner

Copy Link

Fixed by ... ?

I just wonder the result we should put. Divine intervention is no reasonable result category ;D

Fixed by ... ? I just wonder the result we should put. Divine intervention is no reasonable result category ;D

flux commented 2024-01-04 17:56:01 +00:00

Member

Copy Link

Fixed by ... ?

i'd say "can't reproduce" - the player's client was in an invalid state that shouldn't have been possible, and can't be "fixed".

> Fixed by ... ? i'd say "can't reproduce" - the player's client was in an invalid state that shouldn't have been possible, and can't be "fixed".

rewired_X commented 2024-01-04 21:04:03 +00:00

Author

Copy Link

im sure i can get mt to be in the invalid state again, the first reinstall made it impossible to join YL

im sure i can get mt to be in the invalid state again, the first reinstall made it impossible to join YL

AliasAlreadyTaken commented 2024-01-04 22:21:16 +00:00

Owner

Copy Link

If rewired_X can demonstrate a repro, we should probably tell upstream. If not, rsult/cannot reproduce

If rewired_X can demonstrate a repro, we should probably tell upstream. If not, rsult/cannot reproduce

rewired_X commented 2024-01-04 22:23:04 +00:00

Author

Copy Link

id say tag it as cannot reproduce, if i ever get the instance of neon crocs again ill post here

id say tag it as cannot reproduce, if i ever get the instance of neon crocs again ill post here

👍 1

flux added the

5. result/cannot reproduce

label 2024-01-04 22:43:02 +00:00

rewired_X commented 2024-01-05 01:09:51 +00:00

Author

Copy Link

safe to say despite multiple different attempts to repro it I can't seem to get it to trigger again, im sure though a new visual glitch will worm its way to me come next release

safe to say despite multiple different attempts to repro it I can't seem to get it to trigger again, im sure though a new visual glitch will worm its way to me come next release

👍 1

flux commented 2024-01-05 04:23:29 +00:00

Member

Copy Link

@rewired_X if you're really concerned about this, try using a 5.8 client with 5.7 (or possibly earlier) shaders. but even if that triggers the issue, it's not a your-land thing in the least. even upstream can't be blamed if you're using old shader code that's no longer compatible.

@rewired_X if you're really concerned about this, try using a 5.8 client with 5.7 (or possibly earlier) shaders. but even if that triggers the issue, it's not a your-land thing in the least. even upstream can't be blamed if you're using old shader code that's no longer compatible.

whosit commented 2024-01-13 03:13:31 +00:00

Member

Copy Link

This is on windows 11, MT 5.8.0.

So, first, they are neon only at night.
Second, if I tick "enable shaders" in the menu (even without enabling any actual stuff like shadows/bloom/waving) then crocs become normal.
If I disable shaders completely (enable_shaders = false), they become neon.

Same running instance of MT, after I toggled shaders on (there's a croc somewhere there, I think):

Night version of the shaderless croc's limbs just does not have any darkening effect applied to it, but the body is darkened as it should:

I tested this on 5.7.0 and 5.9.0-dev-345e93d19 (on linux) - crocs become neon-looking if shaders are disabled.

 This is on windows 11, MT `5.8.0`.  So, first, they are neon only at night. Second, if I tick "enable shaders" in the menu (even without enabling any actual stuff like shadows/bloom/waving) then crocs become normal. If I *disable* shaders completely (`enable_shaders = false`), they become neon. Same running instance of MT, after I toggled shaders on (there's a croc somewhere there, I think):  Night version of the shaderless croc's limbs just does not have any darkening effect applied to it, but the body is darkened as it should:  I tested this on `5.7.0` and `5.9.0-dev-345e93d19` (on linux) - crocs become neon-looking if shaders are disabled.

neon_croc.png

183 KiB

neon_croc_day.png

250 KiB

Screenshot 2024-01-13 062431.png

155 KiB

daynight.png

106 KiB

👍 1

whosit reopened this issue 2024-01-13 04:40:51 +00:00

flux commented 2024-01-13 04:57:37 +00:00

Member

Copy Link

verified this happens on linux too

verified this happens on linux too 

image.png

167 KiB

flux commented 2024-01-13 05:01:32 +00:00

Member

Copy Link

i've poked upstream, but probably we need to figure out whether this is a problem w/ the engine or with how water_life does things

i've poked upstream, but probably we need to figure out whether this is a problem w/ the engine or with how water_life does things

AliasAlreadyTaken commented 2024-01-13 17:57:16 +00:00

Owner

Copy Link

I asked Apercy on discord for his opinion, he did the models for the crocs. Maybe we have an old version or something wrong.

I asked Apercy on discord for his opinion, he did the models for the crocs. Maybe we have an old version or something wrong.

AliasAlreadyTaken commented 2024-01-13 19:22:27 +00:00

Owner

Copy Link

Fixed upstream, rewired_X took a look and found them ok

Fixed upstream, rewired_X took a look and found them ok

AliasAlreadyTaken added

4. step/ready to QA test

ugh/QA OK

3. source/mod upstream

and removed

5. result/cannot reproduce

3. source/unknown

labels 2024-01-13 19:22:53 +00:00

AliasAlreadyTaken added this to the 1.1.123 milestone 2024-01-13 19:22:56 +00:00

flux commented 2024-01-13 22:22:39 +00:00

Member

Copy Link

not an engine issue - the fix related to texture/model mismatch in #5699 fixes this.

not an engine issue - the fix related to texture/model mismatch in #5699 fixes this.

flux commented 2024-01-13 22:23:08 +00:00

Member

Copy Link

oh hah i should have read the comments first

oh hah i should have read the comments first

rewired_X commented 2024-01-13 22:34:29 +00:00

Author

Copy Link

windows 10, 5.8.0, enable_shaders = false

windows 10, 5.8.0, enable_shaders = false 

Screenshot (1421).png

1.7 MiB

👍 1

rewired_X commented 2024-01-13 22:41:45 +00:00

Author

Copy Link

arch linux, 5.8.0-1, enable_shaders = false

arch linux, 5.8.0-1, enable_shaders = false 

Screenshot_20240113_174105.png

1.6 MiB

👍 1

flux added

5. result/fixed

and removed

4. step/ready to QA test

labels 2024-03-28 19:41:56 +00:00

flux commented 2024-03-28 19:42:02 +00:00

Member

Copy Link

this is live

this is live

flux closed this issue 2024-03-28 19:42:02 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

Labels

Clear labels   

1. kind/balancing

Depends on balancing

  

1. kind/breaking

something that alters or disables an existing game mechanic

  

1. kind/bug

Something is not working

  

1. kind/construction

A build needs fixing

  

1. kind/documentation

Needs proper documentation

  

1. kind/enhancement

New feature

  

1. kind/griefing

players despoiling builds or nature

  

1. kind/invalid

Not a valid report, e.g. created by mistake with no content.

  

1. kind/meme

issue is mostly a joke

  

1. kind/node limit

something which works for or against the node limit

  

1. kind/other

Something not within the other kinds

  

1. kind/protocol

something concerning how staff should react to player requests, or how players should treat each other

  

2. prio/controversial

not likely to happen w/out a lot of discussion

  

2. prio/critical

Very important

  

2. prio/elevated

something players are eager to have fixed

  

2. prio/good first issue

the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem

  

2. prio/interesting

one of us has real interest in getting this implemented or fixed. however, more research might be needed.

  

2. prio/low

Not so important

  

3. source/art

art needs to be created or found for this to exist. includes sound, 3d modelling, and in-game building.

  

3. source/client

Issue is with the minetest client, or with player client configuration or the technical details of their setup

  

3. source/engine

Issue is due to a bug or feature of the minetest engine

  

3. source/ingame

Problem and solution exist in-game, e.g. builds or player moderation

  

3. source/integration

Two or more nonbuggy mechanics conflict, or our attempts to rectify conflicting mechanics have created a new bug

  

3. source/lag

A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues

  

3. source/license

A licensing problem is involved

  

3. source/mod upstream

Problem is upstream (not engine/client)

  

3. source/unknown

  

3. source/website

Affects the website

  

4. step/approved

Alias has approved this feature, someone should implement it

  

4. step/at work

Being worked on

  

4. step/blocked

we plan to do this, but other work has to be finished first

  

4. step/discussion

issue is under discussion, a solution has not been dictated or agreed upon

  

4. step/help wanted

Need some help

  

4. step/needs confirmation

  

4. step/partially fixed

this is mitigated or partially solved, but more work needs to be done

  

4. step/question

More information is needed

  

4. step/ready to deploy

has been QA tested by another person. has no outstanding issues. might be installed on prod, but needs final testing

  

4. step/ready to QA test

the code is supposedly fixed, but needs to be tested.

  

4. step/want approval

Someone can quickly implement this if Alias approves the change/feature

  

5. result/cannot reproduce

  

5. result/duplicate

This issue or pull request already exists

  

5. result/fixed

problem is fixed

  

5. result/maybe

not planned currently, but maybe some day

  

5. result/wontfix

the reported issue won't be changed, whether it's intentional or not.

  

ugh/petz

yet another petz bugz.

  

ugh/QA main

That's something we can only wait and see whether it hapens again: On the main server

  

ugh/QA NOK

Fix didn't yield the expected results

  

ugh/QA OK

tested

No Label

1. kind/balancing

1. kind/breaking

1. kind/bug

1. kind/construction

1. kind/documentation

1. kind/enhancement

1. kind/griefing

1. kind/invalid

1. kind/meme

1. kind/node limit

1. kind/other

1. kind/protocol

2. prio/controversial

2. prio/critical

2. prio/elevated

2. prio/good first issue

2. prio/interesting

2. prio/low

3. source/art

3. source/client

3. source/engine

3. source/ingame

3. source/integration

3. source/lag

3. source/license

3. source/mod upstream

3. source/unknown

3. source/website

4. step/approved

4. step/at work

4. step/blocked

4. step/discussion

4. step/help wanted

4. step/needs confirmation

4. step/partially fixed

4. step/question

4. step/ready to deploy

4. step/ready to QA test

4. step/want approval

5. result/cannot reproduce

5. result/duplicate

5. result/fixed

5. result/maybe

5. result/wontfix

ugh/petz

ugh/QA main

ugh/QA NOK

ugh/QA OK

Milestone

Clear milestone

No items

No Milestone

1.1.123

Projects

Clear projects

No project

Assignees

Clear assignees

No Assignees

4 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#5778

No description provided.