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

[BUG] Saber modifiers with the same name causes target exception. #134

Open
AlexxSeven opened this issue Jun 17, 2022 · 1 comment
Open

Comments

@AlexxSeven
Copy link
Contributor

SF Version: 2.5.1
Game Version: 1.22.1

Steps to reproduce:

  • Use saber with a visibility and transform modifier which are named the same.
  • Attempt to change size or anything.
  • Attempt to exit SF settings and get target exception error.

Console output:
Console Output

This also inherently stops SF from exiting even if a different saber is chosen after the fact. It could be alleviated in the unity project side of things by having the exporter warn if two modifiers have the same name? Since this was with a saber I was working on, I was able to test the modifiers with different names to ensure that names were exactly what was causing it.

@manel-graca
Copy link

If it was me, first thing I would do was checking all my references to sabers and check if they are the same type.
If they are the same, check all calls to sabers to make sure you are always calling it by the same type.

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

No branches or pull requests

2 participants