Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Bryce

  1. @Bellum I've just realized that these issues could actually be due to the WOW BTT profile I made for you last month. Are these issues mainly occurring while you use that preset in BTT? We will be doing an update to the Z Mac firmware soon. So I'm thinking of including a new simpler BTT setup which will avoid the possible tilt issue I mentioned above, or perhaps a keyboard based gaming profile which doesn't need BTT at all.
  2. @csum17 The starter profiles can be reloaded into the driver at any time by selecting "Import Mappings From a File" in the main driver menu (The three horizontal lines at the top left of the driver window) then selecting the "Starter Mappings.spcf" file which will be in the default directory. Or if you want to wipe all of your current profiles and return to the defaults you can also select "Clear and Reset Settings in Driver and Mouse" from the same menu, then chose to load the starter mappings.
  3. @HalcJ5 Currently the only way to get this input back (without manually editing your config file) is to use the "-REMOVE" button near the bottom of the window, then add a new set of blank inputs for the trigger with the "+ADD" button that will appear. A better solution which doesn't require you to clear the other buttons outputs will be added in an upcoming driver update.
  4. @Bellum Just to clarify, when you say that all trigger buttons stop working, are you just referring to the left and right trigger push and pull buttons on the top of the Z? Or do you mean all of the buttons (other than the standard left, right, middle, and thumb buttons) stop working? If the latter, the first things that comes to mind is that for any mappings you've setup in BTT to work, BTT must be running, and you need to be in the Map All profile. Another possible cause for your mappings to not work correctly is if your Zs tilt angles and out of calibration. Since the Map All profile has separate outputs for most buttons while your Z is tilted in either direction. To correct this you would just need to pull the right trigger on your Z and then let it sit flat on your mouse mat for a few seconds. The OLED screen will update through the process, and then the Z will vibrate when it is complete.
  5. @latexyankee I'm glad I could help, and many thanks for the feedback. One problem I've found with the two profile system is the possibility of getting out of sync. For example if you are put into a vehicle by a cut-scene you will be in the wrong profile, and trying to change back will exit the vehicle. There are ways around this but the other setup avoids this problem entirely, which is why I generally recommend it in games where it is possible.
  6. @RegularZ This behavior is due to the filtering the Z does on tilt-inputs to prevent accidental activation. Since any rapid movement of the mouse will effect the gyroscope readings. Without this filtering low angle tilt outputs could trigger from any quick mouse movements. It may be possible to tweak this system further to allow tilts to function at higher mouse movements speeds. But it would be a challenge to do so without causing problems with accidental activation.
  7. @Andrew T. It is not currently possible to adjust the Z's polling rate, but a polling rate setting will be added in the next driver update. In the meantime you can disable the "Show window contents while dragging" option in Windows to avoid this kind of lag, as shown below.
  8. @latexyankee How you correct this will depend on what it causing the tilts to trigger. If you are actually leaning your Z, the only way to stop it from triggering would be to raise the tilt angle even higher. However if your tilts are getting stuck down even while your mouse is flat, this may be a issue with the auto calibration system. In which case disabling the "Tilt Auto Zero" option I mentioned, then manually re-zeroing your tilt angles when you start a game should provide more stable tilt performance. The Noise Level value is subtracted from the Angle value to determine when the tilts return output will trigger. For example the default 1.2° inputs have a noise value of 0.5°, which means that the output will trigger when you tilt to 1.2°, but only release once you have moved back to 0.7°.  So adjusting the noise value won't help with inadvertent activation of tilts, but it can be used to adjust the angle they will de-activate. Setting up separate on foot and vehicle controls for these two games will require different approaches. For GTA if you want analog control while driving/flying the most practical option would be to swap profiles when you enter/exit a vehicle. (You could partially automate this by putting a profile swap output on the same button as your enter/exit vehicle key) However in Battlefield an example of what I mentioned above would look like this. As you can see the Z will be outputting both a joystick button, and an analog joystick axis when you tilt in either direction. This would be a problem in GTA, as there is no way to prevent the "Analog Left / Right" output from steering your character while you are on foot. This is not a problem in Battlefield though, as you can simply remove the joystick buttons from your vehicle controls in-game, and remove the analog joystick axis from your on-foot controls in-game. So when you are on foot, only the button outputs will have an affect, and the opposite while you are in a vehicle. I realize now that the Gaming Gesture and Analog profiles do not have both the "Analog Left / Right" and separate left and right tilt inputs by default, which likely caused some extra confusion. So to use the setup above you would need to add these back in. To do this click the "-REMOVE" button at the bottom of the tilt mappings pane, then the "+ADD" button to restore all of the base tilt inputs. For analog control you need to use a Joystick axis or slider as the output. These outputs are only available for analog inputs such as "Analog Left / Right". The Z's Joystick outputs will only be recognized in games that support DirectInput joysticks. So for games like GTA which do not support DirectInput you'll need to use a tool like x360ce to convert the Zs analog joystick outputs to XInput. You can find a brief guide on how this works in the link below. https://community.swiftpoint.com/topic/7-how-to-use-the-z-in-games-that-do-not-support-directinput/ Config mode is just a few mappings in the Global profile under tilt right 25°. You can delete this if you want, but it is useful for switching profiles, OLED display etc. without opening the driver. So another option would be to increase its activation angle so that you do not trigger it accidentally.
  9. Hi @latexyankee, Your questions touch on a lot of different topics, but I'll try to address them briefly below. Pivots inputs can be created on any profile, and you can find an overview of how to set these up from the link below: https://community.swiftpoint.com/topic/18-swiftpoint-driver-overview/?do=findComment&comment=378 Using Parent and sub profiles can sometimes make things simpler if you have a number of profiles which are mostly the same, with a few minor changes for each. But you can also just make a copy of a profile and modify that instead if it's easier. To use pivot as free look the "right trigger push" mapping in "Gaming Analog" would be all you need on the Z. But this will only work in games that support free look via a controller output, such as Arma. If your tilt outputs are not working consistently try disabling the "Tilt Auto Zero" option from the Profile settings screen (Immediately below the Global Defaults profile name). Then pull the right trigger with your mouse flat on your mouse mat to re-zero your tilt angles manually. Doing this re-zero manually once a day can keep your tilt angles stable for longer than relying on the auto zero option. The separate left and right tilt inputs can be used at the same time as the analog tilt if you ever need to. Though in most cases you this would probably not be desired and you would just choose one or the other. If you want to use the Z "in the air" all you would need to do is increase your tilt angles to match the extra range of movement you have access to. The difference between the two starting gaming profiles is just that the "Analog" profile incorporates analog joystick outputs for tilt and pivot. Whereas Gestures instead uses non-analog button presses on tilt and pivot. So which one you would use depends on if the game supports analog control and if you think it would be useful. To set the gaming analog profile up so you can drive with analog control, but use your mouse normally while on foot would just involve unbinding the joystick outputs from your on foot controls in Battlefield. So that tilt only has an effect while you are in a vehicle. If you want tilt to do something else while you are on foot, you could assign new outputs to the separate tilt left/right inputs. Just make sure that the buttons you assign to these tilts have no are not bound to any "in vehicle" controls in Battlefield. The Gaming Analog and Gaming Gestures profiles can be a good starting point for games that support joystick outputs (Like Battlefield), but you do not need to use either as parents profiles if you would prefer to start from scratch, or they are not suitable. For example games like DOS2, that do not support Directinput Joysticks, the profile below which uses only keyboard keys would be a better starting point. https://community.swiftpoint.com/files/file/14-general-gaming-numpad-version/ More in-depth videos are something we need to work on. But I hope this helps somewhat in the meantime..
  10. @Oleg Girko If you (or anyone else) are still interested in creating Linux software for the Z, please find the specification for the Z's raw sensor events below. This should give you all the info you need to enable the raw outputs for all of the Z's inputs (they are disabled by default), and show you how to interpret that output. If you have any questions on the specifics they're likely to go over my head. But I can try to pass a few on to our devs if necessary. Z Raw Sensor Events Specification.pdf
  11. @Carl Edman I'm glad to hear that worked. Eventually we do plan to make the "Game Controller Type" setting work in a similar way to disabling it in device manager. Currently it disables the individual controller outputs, but not the whole controller interface. Which unfortunately isn't enough to prevent this issue on its own.
  12. With the approach I mentioned you won't need to unplug your mouse, and your Z will still function normally; other than its joystick outputs being disabled. So unless there is something I'm missing, it should work,
  13. @doebro2010 Gaming Analog should have been added automatically when you first started the driver. But if it's not there you can add it again by opening the main menu (at the top left of the driver window) and selecting "Import Mappings from a File". Then select the "Starter Mappings.spcf" file which should be to only one visible. Use the checkboxes to select the profiles you want. If you have not made any changes to the global profile I would recommend importing all of them and selecting "Clear Current, and Import". (You can find details on what all of these profiles do here) The Tilt mappings for a profile can be viewed by clicking the buttons directly below the image of the Z, on the left side of the driver window. By "right trigger will enable pivot for Main Stick rotation" I mean that while you are in the "Gaming Analog" profile holding down the right trigger button and pivoting your mouse will work in the same way as pivoting/rotating a physical joystick. Just as tilting the mouse left/right or forward/back will work like pushing a joystick in those directions.
  14. @JohannHo I've covered a quite few extra steps here which aren't strictly necessary, but they should help you get more consistent performance from your tilt mappings. Select your R6: Siege profile. Click "Tilt left / right" button near the bottom left of the driver window to access the tilt mappings for this profile. (+ADD mappings to override Global if they do not exist). Click Tilt Left 1.2° then increase Angle to 1.7° and Noise Level to 1.2°. This will help to ensure you only lean when you really want to, and prevent you from dropping out of your lean while you are aiming. Click "Do Nothing" to the right of "Tilt Left 1.7°" Click "RECORD keystrokes". Tap the keyboard key you will use for leaning left. I would recommend using a key you would not normally use while playing, as this will free up Q on your keyboard for something else. Click the mouse left button anywhere to stop recording. Select "When mouse input is released" on the dialog that appears, so that lean will remain active while you are tilting the mouse. Perform steps 4-9 again but with "Tilt right 1.2°". Click on your Siege profile's settings and disable "Tilt Auto-Zeroing". This will help prevent problems with tilt getting out of calibration while you play. Select the right trigger button in the driver and add mappings to override global if required. Click "Right Trigger Pull" and select Delete. This will allow the default right trigger pull function from the global profile to work in your Siege profile. This can be used to re-zero your tilt angles, and we recommend you do this once a day before you start playing to make sure your tilt functions work correctly. If you did not use Q and E for your lean mappings, set your key-binds in Siege to match what you set on your Z.
  15. @doebro2010 A good starting point for this would be the default Gaming Analog profile. This assigns all of the Z's extra buttons to joystick buttons, tilt (left/right and forward/back) to the main joystick axes, and holding the right trigger will enable pivot for Main Stick rotation. You can switch to this profile either within the driver, or by picking up the Z and pointing its OLED screen up at you to enter config mode. Then pressing the edge buttons to cycle between profiles until "Gaming Analog" is displayed. Once you are in this profile you should just need to setup your binds in FSX as you would with your flightstick.
  16. That's not exactly how the "Tilt Auto Zeroing" feature on the Z works. But if you find that your tilt angles are quickly getting out of calibration disabling this as CodeBerry suggested should help.
  17. @Carl Edman If the Z's controller outputs are causing problems you can disable them from device manager with the steps below. Open device manager by pressing "Windows Key + X", to open the windows tool menu. Then press 'M' for Device Manager", or select it from the menu. In Device Manager expand the "Human Interface Devices" category, then right click the "HID-compliant game controller" and select "Disable device". It can then be enabled again in the same way when needed.
  18. @xtracaf Check out the thread below for a few examples of tilt mappings. They are centered around lean in PUBG, but the same system will work for strafe, you'd just need to change the keys to A and D. https://community.swiftpoint.com/topic/66-tilt-control-in-game/ Since you also mention tilt working on one side but not the other you may need to calibrate, or re-zero your tilt angles. Calibration can be done from the main driver menu, and it's recommended you do this at least once. Re-zeroing it is available by default on "right trigger pull", but can also be setup on any other button by adding it as an output under "Set Profile / Reset Angles".
  19. @Spook54 Caps lock is not available in the current driver however it will be added in the next update; which is now available as an open Beta. You can find details on this in the thread below. https://community.swiftpoint.com/topic/254-z-driver-update-open-beta-test/
  20. @Bellum Unfortunately these profiles can only be imported by the Swiftpoint Driver on Windows for now. When our complete configuration tool for mac is released it will be compatible with these files, but for now I've created a similar profile for BTT which you can find attached. It is setup as follows: Input Output Top Thumb Alt+1 Bottom Thumb Alt+2 Left Trigger Push Alt+3 Right Trigger Push Alt+4 Left Fingertip Alt+5 Right Fingertip Alt+6 Rear Edge Alt+7 Front Edge Alt+8 Left Trigger Pull Alt+9 Left Fingertip Deep Click 50% Alt+- Right Fingertip Deep Click 50% Alt+= Another option if you have access to Windows, is to save custom profiles to your Z's internal memory so they will still be available when you plug your Z back into your Mac. NOTE: Due to the modifier keys used in the Map All profile on the Z this setup will not work consistently and is no longer recommended.
  21. @XxTSDTxX The best output to use for this kind of setup is probably a slider set to 50% range as below. You can use the rotation axis of the Main Stick for the other deep click, since it works similarly to a slider (it can be left at 100% though)
  22. @Nemachaser It sounds like one of your mappings might be holding the Control key down and not releasing it. Normally that shouldn't be possible, but just check if you have any Ctrl press outputs without a release. If you can't find what could be causing this just upload your mappings file and I'll take a look.
  23. @skypickle I'm not familiar with Insurgency myself but can't see anything in your profiles which looks like it could cause this. Is the "mouse pointer" that is drifting one that can only be controlled by your mouse, or could it also be moved with a controller input? If it can be moved with a controller, are you able to remove this keybind in-game so that controller outputs will not effect the mouse pointer? If the mouse pointer can be moved by a controller, but the keybind for this cannot be disabled in-game. Please try temporarily disabling your Zs joystick output completely to ensure this is not sending any outputs your game could be reading. This can be done within Device Manager. Which can be accessed via control panel, or by right clicking the Start Menu. Within device manager expand the "Human Interface Devices" section, then find the "HID-compliant game controller". Right click it and select "Disable Device". This will prevent any of your games from recognizing the Z as a joystick until you re-enable this device in Device Manager.
  24. @skypickle If I'm understanding correctly the setup in the screenshot below should do what you're after. The main things about it to note are the "Wait....." settings on the OLED Flash outputs, this setting prevents the next output from triggering until the flash duration is complete. With these set to "Continue" the next output will be triggered immediately. Which is useful when you want a macro to run while you are displaying something on the OLED screen. But wont work for a sequence of OLED outputs, since the next output will overwrite the one before it almost immediately. Also in your setup the "OLED \ Show \ Current DPI" output is overwriting the "Current Profile" setting on "OLED Mode". Since it triggers last and an OLED "Show" output will remain until something else changes it. Instead you should set the OLED mode to the final setting you want it to be on, then just use flashes for the OLED sequence on profile switch.
  25. @skypickle Input combinations can be created in the Swiftpoint Driver using almost any Z input with any other. Though keyboard inputs are not currently supported in these combinations A profile switching setup like you mentioned is actually setup by default global profile under "Tilt Right 25°", along with other mappings for changing the OLED display, and DPI. If you want to create your own custom version of this, just select the input you want to use for the first part of the combination (you mentioned mouse button 4 so we'll use that in this example). Hover your cursor over its name in the input/output list and an "+ADD" button will appear next to it. Click this to create a new input which will only be active while the bottom thumb button is held down. Use the dialog box that appears to chose the input type, then the specific input you want to add. In your example we'll want to add the front and rear edge buttons, so add one of these then open the dialog again to add the other. You should then have the setup below, from which you can start adding outputs to the two button combinations. Or if you like you can even add more layers of inputs for more complex input combinations.
  • Create New...