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

Incompatibile paths for shader #214

Open
LKAMinco opened this issue Jun 25, 2024 · 1 comment
Open

Incompatibile paths for shader #214

LKAMinco opened this issue Jun 25, 2024 · 1 comment
Labels
enhancement A suggestion for updating existing functionality Similar issue exists This issue is similar to an already existing issue, but doesn't add enough value to be standalone.

Comments

@LKAMinco
Copy link
Contributor

Maybe would be nice to have some tool, that updates all sources from user fs data path to current user fs data path.
-> now every shader has to be manually updated when one user send to another working file and they have different paths for data folder. Main focus on shader, textures can be packed into blendfile.

@LKAMinco LKAMinco added bug Something isn't working Needs Auditing Issues that should be audited by a dev before being considered labels Jun 25, 2024
@StjerneIdioten
Copy link
Owner

StjerneIdioten commented Jun 25, 2024

This is more or less the same as #179 although I guess you are suggesting a tool instead. There is actually around 4-5 issues regarding shaders and I am currently (finally) reworking a prior pull request (#182) by @NMC-TBone. In any case handling this is the next feature coming up. I am not doing a tool, but rather a way to define "shader libraries" which are essentially just search paths to find shaders. The defaults that 99% of people are going to use is just the built-in shader library from the FS folder. The idea being that instead of having your shaders reset/not work, when sharing your blend file, you just have to tell the plugin where you keep your shaders. I've implemented most of my ideas for it at this point and it is backwards compatible with the existing files and will setup everything when the file is loaded.

@StjerneIdioten StjerneIdioten added Similar issue exists This issue is similar to an already existing issue, but doesn't add enough value to be standalone. enhancement A suggestion for updating existing functionality and removed Needs Auditing Issues that should be audited by a dev before being considered bug Something isn't working labels Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement A suggestion for updating existing functionality Similar issue exists This issue is similar to an already existing issue, but doesn't add enough value to be standalone.
Projects
None yet
Development

No branches or pull requests

2 participants