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

Uncaught exception on line 274 #497

Open
BriggsW opened this issue Jul 8, 2023 · 8 comments
Open

Uncaught exception on line 274 #497

BriggsW opened this issue Jul 8, 2023 · 8 comments

Comments

@BriggsW
Copy link

BriggsW commented Jul 8, 2023

Whether I select Remap, Macro, Map to Keyboard, or any other option and press add, I get the following exception

Traceback (most recent call last):
File "gremlin\ui\device_tab.py", line 274, in redraw
File "container_plugins\basic_init_.py", line 35, in init
super().init(profile_data, parent)
File "gremlin\ui\input_item.py", line 635, in init
File "gremlin\ui\input_item.py", line 654, in create_action_tab
File "container_plugins\basic_init
.py", line 49, in create_action_ui
widget.redraw()
File "gremlin\ui\input_item.py", line 383, in redraw
File "C:\Program Files (x86)\H2ik\Joystick Gremlin\action_plugins\remap_init
.py", line 60, in init
super().init(action_data, parent=parent)
File "gremlin\ui\input_item.py", line 822, in init
File "C:\Program Files (x86)\H2ik\Joystick Gremlin\action_plugins\remap_init_.py", line 130, in _populate_ui
input_name = self.type_to_name_map[input_type].lower()
KeyError: None

If I then unselect and then select the button, axis, or hat I tried to add to, I get this error

2023-07-08 00:10:33 ERROR Uncaught exception:
Traceback (most recent call last):
File "gremlin\ui\device_tab.py", line 393, in input_item_selected_cb
File "gremlin\ui\device_tab.py", line 61, in init
File "gremlin\ui\device_tab.py", line 274, in redraw
File "container_plugins\basic_init_.py", line 35, in init
super().init(profile_data, parent)
File "gremlin\ui\input_item.py", line 635, in init
File "gremlin\ui\input_item.py", line 654, in create_action_tab
File "container_plugins\basic_init
.py", line 49, in create_action_ui
widget.redraw()
File "gremlin\ui\input_item.py", line 383, in redraw
File "C:\Program Files (x86)\H2ik\Joystick Gremlin\action_plugins\remap_init
.py", line 60, in init
super().init(action_data, parent=parent)
File "gremlin\ui\input_item.py", line 822, in init
File "C:\Program Files (x86)\H2ik\Joystick Gremlin\action_plugins\remap_init_.py", line 130, in _populate_ui
input_name = self.type_to_name_map[input_type].lower()
KeyError: None

I've installed and uninstalled vJoy and Joystick Gemlin multiple times using the msi and zip file to no affect and will happen regardless of the vJoy config. I've repaired and reinstalled the x86 versions of vc2010 and vc2013 and have been unable to break this pattern

@WhiteMagic
Copy link
Owner

Which version of Gremlin are you using, and what does the vJoy configuration look like? The error you're getting should not be possible as that particular failure mode is guarded against in the code.

@GregShiner
Copy link

Im getting the exact same error on version 13.3

@WhiteMagic
Copy link
Owner

Are you using 13.3 or 13.3 Debug? The latter is the one with code addressing that kind of issue.

@GregShiner
Copy link

13.3. I guess that would do it lol

@jfjago
Copy link

jfjago commented Jun 4, 2024

Well I have this error too. Have anyone found a solution ?

@atledreier
Copy link

It seems for me it's a special character in the device name that is causing it (Moza wheelbase with character 144 somewhere in there).
Haven't found a solution. The 13.3 debug just fails to run, with no errors.

@WhiteMagic
Copy link
Owner

If the issue truly is the name of the device the registry trick to change the device name outlined in #369 might work.

@atledreier
Copy link

Yes, that trick worked, with no sideeffects that I have found so far.

For reference this was a Moza R9 Base, and the name looked ok in the registry. I deleted the full string to get rid of any hidden characters, typed in Moza R9 Base again, saved and it worked.
All the Moza software seems to work as intended after the change, so looking good so far.

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

5 participants