Jump to content

Tuudi

Members
  • Content Count

    85
  • Joined

  • Last visited

  • Days Won

    14

Posts posted by Tuudi


  1. 18 hours ago, mxstern18 said:

    Yes most of what you explain I understand and my stop are loops were in there because I was looping left click then forgot to take out the stop all loops. I still don’t quite understand the nesting though. If I nest a left click within the right trigger push will the driver carry out the right trigger release if I use block further output on the left click release or does it only block left click outputs? When right trigger push is released I want my left click to release if I am not holding down left click, but if left click is held down, then I want a release then press action to be carried out. I feel like you guys have a way to resemble If Else statements but I can’t quite figure out how. 

    In this case it would block outputs from both buttons untill right trigger push is physically released, as after triggering 'Block Further Outputs' any output from the nested buttons and the parent are blocked untill the parent is released physically. Though pressing any other button while the right trigger push is still held when output blocking is active doesn't prevent them from functioning.

    As a little example how this works, we'll add a third button to your configuration, bottom thumb button nested into the nested left click:

    So let's skip straight to the point where 'Block Further Outputs' has been triggered, at this point you won't be able to output anything(presses or releases) from any of the buttons in the nesting sequence, so no more output from right trigger push, left button or bottom thumb button. But I said in the sequence since while your still holding the right trigger push you'll be able to output from bottom thumb bbutton what ever it has bind to it by default, not the nested output, but when you also press left click down and hold it the bottom thumb button won't output anything anymore, sincce it would suppoused to output the nested bind but since it's blocked that won't happen. Only after you stop holding the right trigger push will the output blocking deactivate for it and any nested inputs.

    Hopefully that's clear enough explanation.


  2. Well for starters nested inputs can only be used while the parent input is hold and nesting the parent input to its self just triggers both inputs as it was one input, unless it's behind an other input like in your first screenshot, but in that case as soon you press left button it also triggers the third input of right trigger push. Also it's pointless to nest the same button as first child input instead of using the parent input to configure the button, for the reason I just explained.

    Also 'Stop Further Outputs' will prevent out putting any more outputs from the button and any nested ones(in order ofcourse) in it while it's held down and to be able to input again from those buttons you'll need to release the parent button. 'Stop All Loops' just terminates any repeats you have on, it won't stop any macros from running through the sequence, but it can skip any waits there might be in the macro.

    As it goes for macro outputing, if you initiate more than one macro to be run simultaneously they will do that literally interfering with each other.

    Hopefully this helps you figure out how to get your setup to work, although if you do hit the brickwall again let me know.


  3. Well I don't personally use the analog output, so can't say that I have any experience with it, but I think it's actually meant to be used with tilt and not deep click so that might be the issue.

    Here's a link to the @Bryce post on Z guides section which explains it: 

    Although I guess you could always post in the Z request/feedback section about the analog outputs compatibility with deep clicking.


  4. selective_output1.thumb.png.673f3d66b6ede73ba043feaf9ee551f0.png

    So here's a simple example with two outpts, so if you just tap the button, so it doesn't reach the 50% force treshold for the deep click, it will output number 1 and when deep clicked it will output number 2 and skip number 1 on button release. Also worth a notice that there won't be any other outputs until you release the physical button, that is how the stop further outputs works.

    How the release looks, notice the checkbox to stop further outputs:

    selective_output2.thumb.png.1c4e8b6d57fff432209bcd8f61fe1056.png

    And here's a screenshot with four outputs with increasing vibration force to tell yooou which output your getting(you could also add or replace the vibration with led screen output to tell you at which output you are at):

    selective_output3.thumb.png.e9212b2a1ad4d63a36b8cda7dd118b24.png


  5. That is exactly how it's meant to work, even tilt, one way to have multi output do single select output button is to use button releases instead of presses.

    You could also add vibration to the press of the output to know which output you are giving, not nessesary for the regular tap but for the deep clicks. Also you'll need to block further outputs when doing this so you don't output the other outputs also, not nessesary to add this to the regular tap, again.

    Hope that's clear enough, though if not let me know and I can take some screenshot to clarify it.


  6. If you want to bypass lower angles you could put the outputs into the return of the tilt instead of the activation point and having stop further outputs checked on the return of the angles past the first one to prevent activation of outputs of lower angles when returnign the mouse to zero angle.

    Also putting different vibrations to activation points would propably help detrimine on which tilt angle you are at.


  7. You're able to configure the press and release of a button independently, so if you have a loop on the press you can add stop looping command to the release of a button.

    This would make it so on press the loop keeps looping and on release it will stop.

    • Thanks 1

  8. If you mean a physical button, you need to have a press output instead of tap.

    If you mean tapping a physical button and the mouse holding the bound button/key to it then there a couple of ways to go about it:

    1. You need to disable the mouses feature to auto release pressed buttons when there is no interaction between the mouse and the user, then you simply set a button with press of a button/key without release output. You should have a button to also for release any buttons/keys that that you've set up without release or you might not be able to use them.

    2. You can make infinte repeat of button/key press, you will also need a button for breaking the loop. With this method you don't need to disable the auto button release feature of the mouse.


  9. 1 hour ago, Damir said:

    I need the "Wait" to break the whole cycle IF the Tilt is over 1.5 degrees.

    Oh, well sadly that isn't possible at current state(don't know if that could be added to the driver though). Only way to cut the side scrollin would be by adding an other tilt degree over the 1.5 degree with the delay and loop breaking in it.


  10. From another thread reguearding the same issue from issues and bug reports section:

    On 8/1/2018 at 8:49 AM, Bryce said:

    The Z's USB update rate is 1000Hz, and its optical sensor is also capable of a consistent 1ms response time. However, unlike most other mice there is a lot more going on in the Z’s firmware than just optical sensor reporting and handling of a few button inputs. So the overall report rate will depend on what else the Z’s firmware is processing. For example OLED display modes like “Tilt Angles” and “Deep Click Forces” which are updated dynamically will have an effect on the report rate (noticeable to a rate checking tool, though probably not to most users). Firmware updates since the Z’s initial release have also affected the Z's report rate. With some updates having a performance cost, and others including optimizations to counteract this.

    We are aware that the Z’s report rate can be lower than 1000Hz, and keeping it as close to 1000Hz as possible is important to us. Though, currently our top priorities are adding long requested features. If the community disagrees we can re-evaluate this, and move further optimizations above other planned feature updates and fixes.


    This is obviously not a solution to the above, but as the question was raised by @gasknr, a polling rate cap option will be available in an upcoming driver/firmware release. Not the next one (expected to be out within the fortnight), but the one after that.
     

     

    • Thanks 1

  11. What your after is propably something like this:

    fnb1.thumb.png.75542f4135ae60f8c9ba2705285c5fdc.png

    On the screen shot above you would switch to the Building mode and keep tapping the lmb indefinetely. You might want to add some Waits there before tapping and before repeat if needed. Also I guess note worthy is this is on the mouse button press.

    fnb2.thumb.png.8eec2875151deb1778aa67f60badfd60.png

    On this screenshot you will break the loop from the press of the button in the release of the button as well as switching back to your weapon.

×
×
  • Create New...