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

280: Remove Composite Textures feature #528

Closed
3 tasks done
tngreene opened this issue Jan 17, 2020 · 2 comments
Closed
3 tasks done

280: Remove Composite Textures feature #528

tngreene opened this issue Jan 17, 2020 · 2 comments

Comments

@tngreene
Copy link
Contributor

tngreene commented Jan 17, 2020

Composite Textures should be removed because

  • Substance Painter and EEVEE make it obsolete, the feature can't match

  • It isn't useful for PBR (I think)

  • I haven't seen much reports of people using it (any well used feature usually has some bugs or feature requests)

  • You can accomplish the same thing quickly in Photoshop or GIMP, the process doesn't use any special Blender properties aside from auto detect figuring out what textures to use (which we've removed anyway)

  • While cleaning unit tests, I've disabled basically everything that uses the feature

  • See if anybody responds to this bug request saying its an essential part of their workflow

  • Remove code from xplane_header.py

  • Delete xplane_image_composer.py (a file so little used, I had completely forgotten of its existence - and its in the top directory)

@tngreene
Copy link
Contributor Author

tngreene commented Mar 8, 2020

If, after the next RC, I make a poll of developers and no one says they'll miss this - we'll remove it

@tngreene tngreene added good first issue Bugs in one or two easy plces that can be fixed quickly help wanted priority normal and removed in review labels Jun 5, 2020
@tngreene
Copy link
Contributor Author

tngreene commented Jun 5, 2020

d84881d nearly solves this. We need to replace the build number in updater to be the actual build number and such for when we really get close to beta.3 when this is planned for

  • Replace build number before actual release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant