ManO'War and Ornata Chroma SDK Support?

Discussion in 'General Discussion' started by Predator5, Nov 5, 2016.

Thread Status:
Not open for further replies.
  1. Predator5

    Predator5 Well-Known Member

    Basically the title. Is there going to be Chroma SDK support for the ManO'War & the Ornata Chroma?
    They're not listed in the compatible device list.

    The SDK page is pretty outdated. Don't get me wrong, it provides heaps of useful information, but looking at the SDK Changelog, it hasn't been updated in a year.

    But when looking at the changelog here, there is stuff about the ManO'War.
    Also, I though Chroma SDK was in version 4.8???

    This is confusing me :confused_::confused_::confused_:

    pls explain someone
    okonietoperza likes this.
  2. Vaypron

    Vaypron Well-Known Member

    @njbmartin Are you able to help? Or do we need some official staff? :)
  3. Predator5

    Predator5 Well-Known Member

    Ummm any response?
  4. njbmartin

    njbmartin Well-Known Member


    The changelog is now kept here:

    As per the changelog:

    Version 1.8.11

    • Fixed ManOWar Chroma effects not displaying correctly

    Version 1.8.8

    • Added support for the the following products
      • Blade Stealth 2
      • Ornata Chroma
    • Fixed cannot create effect on Blackwidow X Chroma keyboard.
    • Fixed QueryDevice on Naga Chroma failed even when it is connected.
    Note about the ManOWar, we have been made aware that there was a firmware issue discovered with the first batch of ManOWars, but later versions have been fixed. If you purchased the ManOWar soon after they were released, they may have this issue and Razer Support should be able to assist you with upgrading the firmware.
    Predator5 and Vaypron like this.
  5. Predator5

    Predator5 Well-Known Member

    What problems would have been caused by the old firmware?
    Also, why wasn't the first changelog that I listed in my OP updated in like 1 year?
    Why do I hear the SDK being in 4.8 version when you're talking about 1.811 here?
  6. njbmartin

    njbmartin Well-Known Member

    Razer likes to be confusing. 4.8 is in fact 1.4.8, and they don't follow the semver approach very well either.

    Regarding the MoW issue, I'm not sure exactly but I'd imagine it has something to do with it not reading Chroma signals correctly.

    Forgot to mention your other question. I've informed them that the changelog on the main page is out of date.
    Last edited by a moderator: Nov 6, 2016
    Predator5 and Vaypron like this.
  7. okonietoperza

    okonietoperza Active Member

    Hey @njbmartin, do you know if there are any more updates on the ManO'War SDK support? I've sent a request through Chroma SDK official contact channels 2 weeks ago but it's been dead so far. I can't seem to get the SDK support working properly (fw upgraded). Static and other simple effects work but for the love of all things Chroma I can't get Custom to work. And I really want to and ManO'War exposes both sides as different zones!
  8. njbmartin

    njbmartin Well-Known Member

    I'll raise this again in my next call with the team.
    okonietoperza likes this.
  9. okonietoperza

    okonietoperza Active Member

    Bump! Any updates? :)
  10. njbmartin

    njbmartin Well-Known Member

    I previously raised this with the team to look into during CES. Their developer was at CES so wasn't able to respond. Since then I've not had a response on the progress. I will keep chasing.

    Just as an FYI, due to the way the headset was designed it's limited to a single zone.

    There is definitely inconsistencies between how the numerous headsets handle each effect.
  11. okonietoperza

    okonietoperza Active Member


    That conflicts with all the information I've gathered so far. See my comment on github.

    Since it looks like custom SDK effects never worked for ManO'War since its release, I doubt anyone actually managed to test custom effects with it
  12. okonietoperza

    okonietoperza Active Member

    @njbmartin just updating that Chroma SDK Core 1.13.3 is out, ManO'War support is still broken
  13. njbmartin

    njbmartin Well-Known Member

    I've raised this with Razer. It's on the todo list!
    Predator5 likes this.
  14. Predator5

    Predator5 Well-Known Member

    njbmartin likes this.
  15. okonietoperza

    okonietoperza Active Member

    Hey @njbmartin, sorry to bother you again, but it's still broken as of 1.14.7 SDK update. Would you be able to follow up with someone from the Chroma team? If you have any contacts I can hit up about that, that'd be great as well :)

    Also seems like mods closed my thread, #19123 without bothering to answer. How nice
  16. njbmartin

    njbmartin Well-Known Member

    Threads are automatically closed after a certain time, so may not have been closed by a mod.

    Here's the sad news:
    Kraken 7.1 v1 and Man'OWar does not support custom effects. We did try to work around it but after a review, a collaborated decision was to leave it as it is.
  17. okonietoperza

    okonietoperza Active Member

    That's utterly and totally BS considering all the promotional materials and SDK documentation created for the ManO'War.

    Same as with Mamba Chroma not having a firmware upgrade in over a year and crappy antenna design, stuttery cursor and laggy efffects. This is getting on my nerves. Razer creates damn unfinished products and then abandons them after 2 weeks unless the stink is big enough to fix it up. Disgraceful bait and switch. One of the reasons I got the ManO'War was that it was supposed to have full 2-channel RGB SDK support, which I based on SDK docs.

    Thanks for the update anyway, now I'm gonna go complain on reddit
    Last edited: Apr 21, 2017
  18. Predator5

    Predator5 Well-Known Member

    I don't understand why ManO'War does not support custom effects. I doubt that it can't, is Razer just to lazy to provide us with the SDK or something? Also, what @okonietoperza said, there was the promotional material and SDK documentation, that should mean that Razer obliged to provide us the SDK.
Thread Status:
Not open for further replies.