your-land/bugtracker
your-land/bugtracker
40
21
Issues 3.6k Projects 4 Wiki

The dirt roads (feldwege) somehow don't look right ... #8254

New Issue
Open
opened 2025-03-18 17:09:59 +01:00 by Boot · 4 comments
Boot commented 2025-03-18 17:09:59 +01:00
Member
Copy Link

... especially with the new shaders. In the screenshot you can see the saw teeth and the difference to normal dirt.

screenshot_20250315_224649.jpg

... especially with the new shaders. In the screenshot you can see the saw teeth and the difference to normal dirt. ![screenshot_20250315_224649.jpg](/attachments/21d4b43e-9619-43a8-84eb-c389779671f8)
screenshot_20250315_224649.jpg
170 KiB
AliasAlreadyTaken was assigned by Boot 2025-03-18 17:10:07 +01:00
Boot changed title from The dirt roads (feldwege)somehow don't look right ... to The dirt roads (feldwege) somehow don't look right ... 2025-03-18 17:10:53 +01:00
Sokomine commented 2025-03-22 00:29:06 +01:00
Member
Copy Link

No idea. I don't know enough about shaders and that. The feldweg nodes have to be models - not full nodes. That may lead to some diffrent way of drawing them. Other than that I have no idea.

No idea. I don't know enough about shaders and that. The feldweg nodes have to be models - not full nodes. That may lead to some diffrent way of drawing them. Other than that I have no idea.
AliasAlreadyTaken added the
1. kind/bug
4. step/help wanted
 labels 2025-03-22 00:30:30 +01:00
AliasAlreadyTaken commented 2025-03-22 00:35:02 +01:00
Owner
Copy Link

There may be some setting we need to take. Experimentation needed.

There may be some setting we need to take. Experimentation needed.
whosit commented 2025-03-22 14:13:44 +01:00
Member
Copy Link

This is caused by shadow shaders (disable shadows and roads look exactly same as full nodes).

The first problem that I see on my machine looks like shadow acne (other description) - the stripes/banding you can see.

The blocks being darker as a whole (and even shadowing adjacent block edges) looks like a similar self-shadowing issue, maybe caused by somehow scaling them differently during shadow map pass (like the mesh being slightly larger when shadow map is rendered, then, during rendering, each pixel of the mesh surface ends up being shadowed)...

[I also examined the mesh, there's no doubled surfaces or wrong normals there.]

In short: engine/shaders issue.

This is caused by shadow shaders (disable shadows and roads look exactly same as full nodes). The first problem that I see on my machine looks like [shadow acne](https://computergraphics.stackexchange.com/questions/2192/cause-of-shadow-acne) ([other description](https://digitalrune.github.io/DigitalRune-Documentation/html/3f4d959e-9c98-4a97-8d85-7a73c26145d7.htm)) - the stripes/banding you can see. The blocks being darker as a whole (and even shadowing adjacent block edges) looks like a similar *self-shadowing* issue, maybe caused by somehow scaling them differently during shadow map pass (like the mesh being slightly larger when shadow map is rendered, then, during rendering, each pixel of the mesh surface ends up being shadowed)... [I also examined the mesh, there's no doubled surfaces or wrong normals there.] In short: engine/shaders issue.
AliasAlreadyTaken added
3. source/client
 and removed
4. step/help wanted
 labels 2025-03-22 15:01:55 +01:00
Boot commented 2025-04-01 15:39:12 +02:00
Author
Member
Copy Link

I only use the shaders of the original game. So I don't see this as a problem of my client only. But something is missing from Sokomine's mod so that it can be displayed attractively with the latest versions of Luanti. I suspect the problem will also occur with other mods of other coders and therefore it could be an issue from Luanti (client).

I only use the shaders of the original game. So I don't see this as a problem of my client only. But something is missing from Sokomine's mod so that it can be displayed attractively with the latest versions of Luanti. I suspect the problem will also occur with other mods of other coders and therefore it could be an issue from Luanti (client).
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/petz

yet another petz bugz.

  
3. source/testserver

Originates on the testserver, no effect on main yet

  
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/QA main

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

  
4. step/QA NOK

Fix didn't yield the expected results

  
4. step/QA OK

tested

  
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.

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/petz
3. source/testserver
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/QA main
4. step/QA NOK
4. step/QA OK
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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
AliasAlreadyTaken
4 Participants
Notifications
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#8254
No description provided.
Delete Branch "%!s()"

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?