XIM Community

Does 20160918 include the NAV trigger deadzone fix?  (Read 9381 times)

Offline Mark8010

  • Member
  • *
  • Posts: 93
    • View Profile
Re: Does 20160918 include the NAV trigger deadzone fix?
« Reply #30 on: 05:25 AM - 11/05/16 »
We have some other device support fixes we want to do. I'll make the change, but honestly though, I can't see how this is going to make a substantial difference to gameplay.

The large deadzone equates to a delay in ADS time - it feels laggy relative to even a normal controller trigger, let alone a hair trigger.

Also, because the range of motion needed to activate the trigger (it honestly has a feel like you have to press it 80% to it's maximum) it's easier (especially when been playing for a while) to unintentionally come out of ADS.

The way the Nav trigger works at the moment is the opposite end of the spectrum to a hair trigger and of course hair triggers are seen as the best style of trigger for many.

Being able to use the FragFX wand would be beneficial to Sony Nav style users too as this is superior to the Sony Nav IMO.
« Last Edit: 05:33 AM - 11/05/16 by Mark8010 »

Offline piiwii

  • MVP
  • *
  • Posts: 1625
    • View Profile
Re: Does 20160918 include the NAV trigger deadzone fix?
« Reply #31 on: 11:31 PM - 11/07/16 »
I don't claim to have any technical expertise but I'd like to think there must be a better way to handle firmware updates. Often something is ready for release, but gets delayed because so many other things are being squeezed in. For example the XB1 S controller support was ready but if I recall correctly, it was then delayed a few days or a week or something due to some other fixes / enhancements.

Couldn't the process be streamlined so that you could have two separate streams, whereby low risk, low effort changes are pushed out first while higher risk changes and fixes are deployed after? An example of this is how the release of ST's are separate from firmware updates. Perhaps hardware compatibility releases could be separated out from bug / enhancement releases too? I really love this device but the only thing that really frustrates me sometimes is how every release needs to be so BIG. I mean the last gold firmware was nearly 2 years in the cooker! I don't think I've ever seen a release that hasn't been delayed because "we want to fix a few more things and add more hardware compat at the same time". I totally understand that this is a small company and I'm not criticising, I'm just wondering if there's a better way to approach this.
« Last Edit: 01:54 AM - 11/08/16 by piiwii »
Setup: XIM4, Titan Two, Sony Nav, Logitech G502, SteelSeries 4HD mousepad, DXRacer armrest, LucidSound LS30 headphones, Netduma router, Ubiquiti UniFi AP LR wireless access point

My setup: http://xim4.com/community/index.php?topic=39334.msg495390#msg495390

My Sony Nav mount: http://xim4.com/community/index.php?topic=39138.0

My DXRacer armrest and Razer mouse bungee: http://xim4.com/community/index.php?topic=39334.msg582636#msg582636

My RAINBOW SIX SIEGE Titan Two Mega Script: https://youtu.be/x-9NtxyySVM

My FOR HONOR Titan Two Combat Pack Script: https://youtu.be/ED66yjFNEb8

Offline Mark8010

  • Member
  • *
  • Posts: 93
    • View Profile
Re: Does 20160918 include the NAV trigger deadzone fix?
« Reply #32 on: 01:48 AM - 11/08/16 »
I can understand the need to work efficiently and include multiple 'fixes' in the same update.

But having to wait this long (as well as experience multiple delays) for a fix that Nav users have stated will be a material improvement is frustrating.

It comes down to Obsiv treating it as a low priority fix versus other fixes (when for use Nav users it's a material update). Would be nice to have clearer expectations as to when the fix would be implemented though rather than experiencing multiple delays.

Going forward,  if we can't have the full range of motion/inputs on triggers then being able to set the deadzone ourselves should really be an option IMO. You can achieve both on a Titan One for example.



Offline piiwii

  • MVP
  • *
  • Posts: 1625
    • View Profile
Re: Does 20160918 include the NAV trigger deadzone fix?
« Reply #33 on: 01:57 AM - 11/08/16 »
I agree and disagree.

Yes it's being treated as a lower priority, and in all fairness it probably is.

But I don't think that's the main reason. As I said I think it has to do with the development / release model.

There have been some high priority updates such as the XB1 S controller but this was slightly delayed to make room for a few other inclusions.

As I suggested, I think the model whereby each release needs to be big, big, BIG and packed with improvements needs a rethink. I don't think there's anything wrong with small updates.

Again I'm not a technical guy, but I'd like to think that support for a new brand of mouse for example or adjusting a config (Nav trigger) must be much less risky and time consuming than say a bug fix or new feature.
« Last Edit: 02:05 AM - 11/08/16 by piiwii »
Setup: XIM4, Titan Two, Sony Nav, Logitech G502, SteelSeries 4HD mousepad, DXRacer armrest, LucidSound LS30 headphones, Netduma router, Ubiquiti UniFi AP LR wireless access point

My setup: http://xim4.com/community/index.php?topic=39334.msg495390#msg495390

My Sony Nav mount: http://xim4.com/community/index.php?topic=39138.0

My DXRacer armrest and Razer mouse bungee: http://xim4.com/community/index.php?topic=39334.msg582636#msg582636

My RAINBOW SIX SIEGE Titan Two Mega Script: https://youtu.be/x-9NtxyySVM

My FOR HONOR Titan Two Combat Pack Script: https://youtu.be/ED66yjFNEb8

Offline nene

  • Member
  • *
  • Posts: 186
    • View Profile
  • Gamertag: king killer cj
Re: Does 20160918 include the NAV trigger deadzone fix?
« Reply #34 on: 12:35 PM - 12/17/16 »
Any updates I'm surprise this has not been brought up more often I'm a gamer so I own the the crosshair and venom and as soon as I press them nav triggers I can ads with xim there's a dead zone delay I have to push  the botton all the way down and its just a mushie feeling can we at least get a beta

Offline Edawsiwel

  • Member
  • *
  • Posts: 265
    • View Profile
Re: Does 20160918 include the NAV trigger deadzone fix?
« Reply #35 on: 02:15 AM - 12/18/16 »
I took a little piece of rubber just the right thickness and glued it on the trigger (l2) and the dead zone doesn't exist anymore

Offline OBsIV

  • Administrator
  • MVP
  • *
  • Posts: 29884
  • It's obsessive.
    • View Profile
    • OBsIV's Blog
Re: Does 20160918 include the NAV trigger deadzone fix?
« Reply #36 on: 11:45 AM - 12/18/16 »
Any updates I'm surprise this has not been brought up more often I'm a gamer so I own the the crosshair and venom and as soon as I press them nav triggers I can ads with xim there's a dead zone delay I have to push  the botton all the way down and its just a mushie feeling can we at least get a beta

Sorry, this turned out to be a much bigger fix than I originally anticipated so it was delayed. We are driving toward another release to make Slim/Pro compatibility firmware our new "gold" and then after that we can revisit.
Get the most out of your XIM4, read the XIM4 Support FAQ.

Offline matthewk85

  • Member
  • *
  • Posts: 119
    • View Profile
  • Gamertag: o MattyAu o
Re: Does 20160918 include the NAV trigger deadzone fix?
« Reply #37 on: 12:46 AM - 06/27/17 »
Any updates I'm surprise this has not been brought up more often I'm a gamer so I own the the crosshair and venom and as soon as I press them nav triggers I can ads with xim there's a dead zone delay I have to push  the botton all the way down and its just a mushie feeling can we at least get a beta

Sorry, this turned out to be a much bigger fix than I originally anticipated so it was delayed. We are driving toward another release to make Slim/Pro compatibility firmware our new "gold" and then after that we can revisit.

I'm assuming the revisit hasn't happened yet?

Offline OBsIV

  • Administrator
  • MVP
  • *
  • Posts: 29884
  • It's obsessive.
    • View Profile
    • OBsIV's Blog
Re: Does 20160918 include the NAV trigger deadzone fix?
« Reply #38 on: 10:01 AM - 06/27/17 »
Sorry, it hasn't.
Get the most out of your XIM4, read the XIM4 Support FAQ.