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

Exploding Macro Screws Up "OverFX" order #2329

Open
phillycheese007 opened this issue Oct 14, 2018 · 2 comments
Open

Exploding Macro Screws Up "OverFX" order #2329

phillycheese007 opened this issue Oct 14, 2018 · 2 comments
Labels

Comments

@phillycheese007
Copy link

phillycheese007 commented Oct 14, 2018

Issue Summary

Exploding Macro Screws Up "OverFX" order

Screenshot or Video Reference

schemprob_1
notice in the video the "hairmidfront" passthrough is somewhwere near the middle of the macro...when exploded it is at the bottom

Steps to Reproduce

Create a Macro that includes an "overfx" with multiple items plugged in (not sure amount needed to replicate)...note the order of the items plugged into overfx...now explode the macro. the order no longer reflects the order when macro was created

Expected Results

The order should stay the same.

Actual Results

It seems to always revert back to the following order (source1, source2, source10-18, source3-9) I suppose that pattern would repeat the more u add though i have not tested.

System Information

  • OpenToonz Version: nightly from sept early
  • Operating System: windows 10
  • CPU:
  • Memory:
  • Graphics Card:
  • Graphics Tablet:
@phillycheese007
Copy link
Author

wow.....Just opened up a project.... had a bunch of lines going into an overFX.......They are all out of order...Same thing as my post above but this time ....no Macro involved...scene was saved with lines going into overfx. The order of the sources the same as above too (1-2, 10-19, and 3-9)

@RodneyBaker
Copy link
Collaborator

RodneyBaker commented Dec 12, 2018

Those who have tested the recent Schematic improvements can weigh in on this but I suspect much of this has been resolved. At least we can hope.

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

No branches or pull requests

2 participants