Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Try to fix Bathypelagic Background #5766

Closed
wants to merge 2 commits into from

Conversation

HexapodPhilosopher
Copy link
Contributor

Brief Description of What This PR Does

I was not able to replicate the issue with a horizontal line appearing on the bathypelagic patch background, but I noticed that the only patch backgrounds not set to detect_3d/compress_to=1 were for Bathypelagic and Vents. Hopefully this fixes the issue.
(I also checked the texture and found no issues with it.)

Related Issues

Hopefully closes #1265

Progress Checklist

Note: before starting this checklist the PR should be marked as non-draft.

  • PR author has checked that this PR works as intended and doesn't
    break existing features:
    https://wiki.revolutionarygamesstudio.com/wiki/Testing_Checklist
    (this is important as to not waste the time of Thrive team
    members reviewing this PR)
  • Initial code review passed (this and further items should not be checked by the PR author)
  • Functionality is confirmed working by another person (see above checklist link)
  • Final code review is passed and code conforms to the
    styleguide.

Before merging all CI jobs should finish on this PR without errors, if
there are automatically detected style issues they should be fixed by
the PR author. Merging must follow our
styleguide.

@revolutionary-bot
Copy link

We are currently in feature freeze until the next release.
If your PR is not just a simple fix, then it may take until the release to get reviewed and merged.

@hhyyrylainen hhyyrylainen added this to the Release 0.8.0 milestone Dec 19, 2024
@hhyyrylainen
Copy link
Member

That shouldn't really have an effect as the detect option only triggers in the godot editor when you use the texture in a way that warrants different options, it will auto-apply those. And once detected it turns off the autodetection, which is probably why the other backgrounds have the property unset.

@HexapodPhilosopher
Copy link
Contributor Author

All the other ones have the property on. These are the only ones that didn't.

@hhyyrylainen
Copy link
Member

hhyyrylainen commented Dec 19, 2024

Probably what happened is that for these backgrounds they were used in the godot editor to try something which triggered the 3D detection, messing up their import settings and turning the detection off. Then when that was noticed the import settings were fixed but 3D detection was not put on because that's going to do totally the wrong thing with these backgrounds as these are meant for a 2D effect kind of thing.

At least that's my understanding that these "detect 3D" options don't impact anything outside the Godot editor whatsoever, so these changes shouldn't be able to do anything, other than set up a landmine for if someone accidentally does something in the Godot editor that triggers the detection and causes the import settings to change to unsuitable ones.

Edit: here's the documentation from Godot:

kuva

So yeah, this PR shouldn't be able to affect anything...

@hhyyrylainen hhyyrylainen removed this from the Release 0.8.0 milestone Dec 20, 2024
@hhyyrylainen
Copy link
Member

I'll close this PR for now as I don't think this should affect anything. If I'm wrong absolutely reopen this and let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Fix bathypelagic background image artifact (horizontal line)
3 participants