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

Support for the Viper Ultimate Wireless #23

Closed
angelus2014 opened this issue Jul 14, 2020 · 14 comments
Closed

Support for the Viper Ultimate Wireless #23

angelus2014 opened this issue Jul 14, 2020 · 14 comments

Comments

@angelus2014
Copy link

Hello,

First off, thank you for your efforts to bring Razer support to macOS! I have the Viper Ultimate Wireless and only the 'static' color option works. Choosing 'wave' crashes the application. Will there also be support for the Viper docking station? :)


With regards,

Angelo Machils

@1kc
Copy link
Owner

1kc commented Jul 15, 2020

Hi Angelo,

I'm glad you've found it useful. I have just uploaded a new version of the 'Razer macOS-0.1.9.dmg' that should fix the mentioned issues.
The priority of the project is to support keyboard and mouse first, since I think the most number of people would benefit.
Additionally, I do not own any Razer devices other than the keyboard and mouse, so it is very difficult for me to add support for other devices as I need to test them. You are always welcome to contribute of course.

Cheers

@angelus2014
Copy link
Author

Hello,

Thank you for the reply and the new release, I will try it out later. I mentioned the dock as it is a part of the wireless version, it's the charging dock and it has some (independent) lighting at the base. I'm not sure how I can contribute (my last coding experience was Cobol ;) ), but I'm always willing to test.


Regards,

Angelo

@angelus2014
Copy link
Author

Hello,

The 'wave' option doesn't do anything on the Viper, but it doesn't crash anymore either :)


Regards,

Angelo

@sammy1881
Copy link

I tested the latest version of the app with Basilisk Ultimate Wireless with dock and it doesn't even get recognized, not even in wired mode.

@sammy1881
Copy link

Nevermind, I see a pull request open to adding device support to openrazer. openrazer/openrazer#1152

How often do you port Linux drivers once new PRs are merged? I would like to help to make this an automated process.

Thanks!

@angelus2014
Copy link
Author

Hello,

The new version (0.2) adds more support to my Viper Ultimate Wireless which work fine as far as I can tell. The dock however it not 'seen' as a configurable device.


Regards,

Angelo

@1kc
Copy link
Owner

1kc commented Jul 28, 2020 via email

@1kc
Copy link
Owner

1kc commented Jul 28, 2020

@sammy1881
Hi Sachin,
Porting over code from Openrazer actually requires manual some code changes. Which makes automating this difficult. You can compare the driver files to see what the modifications are. If you can find a way to automate efficiently please let us know!

@bournejc
Copy link
Contributor

Hello,

The new version (0.2) adds more support to my Viper Ultimate Wireless which work fine as far as I can tell. The dock however it not 'seen' as a configurable device.

Regards,

Angelo

Angelo, I will add the dock as a new device in an upcoming release.

@angelus2014
Copy link
Author

Hello,

Angelo, I will add the dock as a new device in an upcoming release.

Thank you. Has the battery indicator been incorporated in the latest (0.2.2) release? Because I can't see any indicator for my Viper wireless.


Regards,

Angelo

@bournejc
Copy link
Contributor

The battery seems to only show when you plug the cable directly into your viper mouse and then Refresh Device List.

@angelus2014
Copy link
Author

Hello,

Thank you for support for the Viper wireless dock. There is an issue though, if I choose a custom colour, save this and then choose to use that custom colour for the dock, it doesn't work; it goes to yellow. This option does work for the mouse itself, just not for the dock.


With regards,

Angelo Machils

@bournejc
Copy link
Contributor

Angelo, this is fixed in the latest 2.4 release.

@angelus2014
Copy link
Author

Hello,

Angelo, this is fixed in the latest 2.4 release.

Yes, it is working correctly now. Thank you!


Regards,

Angelo

@1kc 1kc closed this as completed Aug 23, 2020
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

4 participants