Skip to content
New issue

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

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

Already on GitHub? # to your account

Unable to validate information for weapon ID#70 #510

Open
7 of 8 tasks
farsdewibs0n opened this issue Mar 3, 2024 · 1 comment
Open
7 of 8 tasks

Unable to validate information for weapon ID#70 #510

farsdewibs0n opened this issue Mar 3, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@farsdewibs0n
Copy link

Current Behavior

Inventory Kamera can't scan "Ultimate's Overlord Mega Magic Sword"

Expected Behavior

The scanner continues to scan

Reproducing a Behavior

Own "Ultimate's Overlord Mega Magic Sword"
Let Inventory Kamera scan for weapons

Device OS

Windows 10

Genshin Impact Version

4.4

Inventory Kamera Version

1.3.14

Screen resolution, screen mode, and UI scale

1920x1080p borderless

Additional notes and remarks

log.txt
weapon.json

Evidence

card

Preflight Checklist

  • I have checked for similar issues in the issue page, and I have not found any similar to mine.
  • I am using the latest version of the scanner.
  • I tried setting the scanning delay to maximum, and it still doesn't work.
  • I have attached the video recording to the bug report.
  • I have attached the error log to the bug report.
  • I am available to later explains the issue.
  • I have disabled (or documented) all screen filtering software, plugins, and enhancements while scanning.
  • I use default in-game keybindings or have configured keybindings for the scanner.
@farsdewibs0n farsdewibs0n added the bug Something isn't working label Mar 3, 2024
@Moisesg08
Copy link

Moisesg08 commented Mar 14, 2024

I had the same issue in the same Inventory kamera version. In my case it also sometimes crashes somewhere after the mega magic sword, although I'm not sure it is related to this or if it is a separate issue altogether. I found issue #497 which seems to be the same problem but it was on version 1.3.12 and it was labeled as complete. I'm not sure if it means that the team is currently fixing it or if they think it should be fixed but it isn't. I din't find the issue mentioned on any of the "What's Fixed" sections of the newest versions so they might still be trying to fix it.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants