Razer Ornata V2 not recognized

[dima0git]

Good afternoon!

I have a Razer Ornata V2.

I installed Visual Studio 2019 Community Edition and cloned the repo (master).
OpenRazer64.dll and the example project builds successfully.

If I run OpenRazerExampleDLL.exe, what should I see?
Should I see that the keyboard is recognized? It just shows "Press Enter to load DLL". And than nothing.

If I copy the OpenRazer64.dll to OpenRGB it does not recognizer the keyboard as well.

[avengerx]

this exampledll is broken to me... it quits saying nothing but if you add a check you'll see it doesn't load anything...
I couldn't figure out what's wrong with it

[avengerx]

This open razer port is actually superceded in the OpenRGB project by a new Razer driver written from scratch. But it is merged with the OpenRGB project. You may be interested in taking a look at it if you just want your RGB hardware controlled outside synapse.

[dima0git]

I tried to build the DLL myself, because OpenRGB does not support my keyboard (Razer Ornata v2).
To support for this keyboard was added in OpenRazer a couple of weeks ago. It is on the master branch, but still not in OpenRazer-Win32 nor in OpenRGB.

[avengerx]

I went the same path when I reached #6. OpenRGB is staging out OpenRazer driver in favor of their own implementation. So get back to OpenRGB master branch and delve into Controllers/RazerControllers for a much better experience... that is, if your controller isn't already supported by that driver. :)

[dima0git]

So OpenRGB will get rid of the OpenRazer dependencies?

My device is aleady listed in the new controller source code.

Maybe I just need to grad the newest build...

[dima0git]

It is on the master branch.
But the last relase is about one month old.
Now I have to find out how to build OpenRGB myself.

[avengerx]

noo you don't need to build it if you are not looking for that
just grab the latest build off its "pipeline"

[avengerx]

Look for pipelines for the master branch in the repo.
CI / CD => Pipelines

Each pipeline is based in a branch, and will have builds for every supported platform. So you can just grab the latest.

Notwithstanding, building it yourself is cool, I think you should try it, as you can then contribute with new features for your own hardware -- or support it if it is not already so. Usually with the new razer driver, it's just a matter of registering its hardware IDs, and maybe the light zones based on a similar device!.. Should be fun!