Jump to content

Bryce

Administrators
  • Content Count

    412
  • Joined

  • Last visited

  • Days Won

    46

Everything posted by Bryce

  1. 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..
  2. @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
  3. @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.
  4. @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.
  5. @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.
  6. 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.
  7. @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".
  8. @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/
  9. @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.
  10. @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)
  11. @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.
  12. @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.
  13. @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.
  14. @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.
  15. @bodyboarder2528 To use the Z's analog tilt controls for Flight in Arma 3 you can start with the "Gaming Analog" profile, which has tilts on both axes set to joystick outputs; or you can add these outputs to your own profile as below. With this setup, you should just need to go into Arma's keybinds, find the flight controls for each axis and tilt the Z in the appropriate direction. Pivot can also be setup for Yaw on button press as in the example below.
  16. @tomharto Currently a small workaround is required to enable mappings like that which leave an output held down after you release a button. The next driver update will render this workaround obsolete, but for now just refer to the thread below for how to setup and enable toggle outputs. https://community.swiftpoint.com/topic/10-enabling-toggle-outputs/?tab=comments#comment-11
  17. Here's the summary of what's new in the PC Driver Release August 10, 2018 Keyboard Input recorder Instead of manually selecting every keyboard output using several drop-down list you can now record outputs directly from your keyboard using the new record button on the output list screen. While recording press and release outputs will be added to the output list as you type for all standard keyboard keys and media controls like volume, play/pause etc. Tap outputs will be created automatically if a press output is immediately followed by its own release. So if you want just a press or just a release either start the recording with a key already held down (to only record the release), or stop the recording before you release a key ) to only record the press). You will also be given the option of adding the release output to the release input when you are just mapping a single key with the recorder. Option to disable or enable "Tilt Auto-Zeroing" "Tilt Auto-Zeroing" is a firmware feature of the Z which works to prevent the gyroscope's tilt readings from drifting over time. In general it does its job well; but in some use cases it can cause more problems than it solves. So if you find that you are frequently needing to re-calibrate your tilt angles for your tilt functions to work correctly, try disabling this feature from the profile settings screen. Just note that since disabling "Tilt Auto-Zeroing" will mean that your Z is not trying to auto-correct for the natural drift in the gyroscope, your tilt values will drift over time. But this drift will be slow, so doing a manual re-zero (with the default right trigger pull function on the global profile, or your own custom mapping) should mean you don't have any problems with tilt for even an extended gaming/work session. Auto-Release Inputs Toggle By default there is a fail-safe enabled in the Zs firmware which prevents keys from being left held down if the Z is not currently processing any user input. So a press command will automatically release if the Z is not tilted, no buttons are physically held down, and no macros are running. This means that if you accidentally forget to add a release for one of your press outputs, the key wont be stuck down permanently, which is generally a good thing. However it is a problem if you actually want a key to be left held down after you release a button. For example, the mapping below which starts holding down 'W' when you first press the Left Fingertip button, then releases it when you press it again will not work correctly with the Auto-Release fail-safe enabled. So if you want to make use of these kinds of functions in any of your profiles. Just disable the new "Auto-Release Inputs" setting from the profile settings screen. If you do just make sure that all of your press outputs have releases, or they will remain stuck down until you change profiles, or unplug the mouse. New Ouptuts Added Caps Lock and Application/Menu key under the "Modifiers and Actions" category. These will also work with the new keyboard recorder. UI Changes/ Bug Fixes Added Spanish translation. "Stop Further Outputs" flags are now correctly maintained on the global profile when it is exported and imported. The "Output ID#" setting on "Repeat From" functions now updates correctly when outputs are re-arranged, and also displays the correct number of options on the profile settings screen. The correct side of the slider is now highlighted when modifying analog toggle inputs. Removed '{0}' text from the DPI output label. Resolved issue where '+ADD' button would sometimes be displayed on analog inputs which are set to an analog output (e.g. deep click analog range). Which allowed the creation of invalid mappings. Firmware Changes Updates to scroll-wheel ‘de-bounce logic’ which will resolve the issue of ‘reverse scrolling’ that a few users are experiencing.
  18. Hi @Tonester, The grip pads in the Z are replaceable and we do have some in spares stock. So please just send an email through to support (support@swiftpoint.com) and we can sort some out for you.
  19. Hi @windtwo, We have an SDK for iOS developers looking to add GT support to their apps, but at this time we have not made it publicly available. If you would like access to it, please just send us an email at support@swiftpoint.com with some details regarding your app for us to evaluate.
  20. Version 1.0.1

    456 downloads

    This is a simple profile for WoW (or other MMOs) which can be used to quickly assign a full Action Bar worth of skills to the Z. It uses an Alt modifier with the numbers keys from 1 to =/+, so should not interfere with any default keybinds, and by combining your mouse buttons with Ctrl and Shift modifiers, three full action bars worth of skills can quickly be accessed without moving a finger off WASD (Or four if you're comfortable holding Shift and Ctrl together). Also included is a version with tilt to assigned to Ctrl and Shift modifiers, if you want to have access to three full actions bars directly from the Z. Input World of Warcraft World of Warcraft + Tilt Bottom Thumb Alt+1 Alt+1 Top Thumb Alt+2 Alt+2 Left Trigger Push Alt+3 Alt+3 Right Trigger Push Alt+4 Alt+4 Left Fingertip Alt+5 Alt+5 Right Fingertip Alt+6 Alt+6 Rear Edge Alt+7 Alt+7 Front Edge Alt+8 Alt+8 Left Trigger Pull Alt+9 Alt+9 Right Trigger Pull Alt+0 Alt+0 Left Fingertip Deep Click 50% Alt+- Alt+- Right Fingertip Deep Click 50% Alt+= Alt+= Tilt Left Ctrl Tilt Right Shift Middle Mouse + Right Trigger Pull Re-zero Tilt Angles
  21. Getting that approach to work well could be a challenge, but using those contact points it would be possible.
  22. Hi @Glamor, sorry for the slow response. Currently the Swiftpoint Driver on Mac is just a tool for updating the Z's firmware, and adding a profile which can be used in conjunction with Better Touch Tools. So it does not actually install anything, you just run it once then use BTT. This being the case it will not be preventing the Z from connecting to the Windows Driver on your VM. However for this to work you will need to "attach" the Z to your VM so that all five of its USB interfaces are forwarded through to the VM where the Windows driver can detect them. While your Z is attached to the VM in this manner it will be disabled on your Mac. So once you have made changes using the Windows Driver, save them to your Z's internal flash memory so they will be available when you detach the Z from your VM. The Windows Swiftpoint Driver is compatible with Windows 7 and up, so your Z should definitely be working with it on a native Windows installation. If you are connecting via any kind of hub, please try plugging your Z directly into your laptops USB port. If this doesn't help, is your Z just unable to connect to the driver on all of these systems, or is it not even working as a normal mouse too?
  23. @treb42 I just had another look at this and you're right that unplugging the Z doesn't seem to resolve it anymore (if it ever did). But resetting the slider by binding it to a pivot input the re-zeroing the Yaw is still working. If you want to test that you have it setup correct just go to the website below which displays the Z's controller outputs in real time. http://html5gamepad.com/ On this page you'll likely see that "Axis 6" is set to -1, while other axes up to 8 are approximately 0. With the setup above pushing the left fingertip button should set this axis back to ~0 (you may need to press it more than once). If it doesn't work, just make sure that you are resetting Pivot (Yaw) not Tilt, and that your slider output has a range from 0-50%. Also be sure not to pivot your mouse when you press the button or the slider will move off 0 again. I hope this helps. But if you have any further trouble with this feel free to upload your profile and I'll take a look at it.
  24. @SilentMan While it's possible we could branch out into other peripherals at some point in the future. For now we are focused on providing updates to the Z's software/firmware and the upcoming ProPoint.
  25. I should have linked to it here, but since my post we have made an announcement with details on the first of the upcoming driver updates, which you can read in the thread below. https://community.swiftpoint.com/topic/198-swiftpoint-driver-development-update/ Work is under way on this, with the first release coming this month if all goes well.
×
×
  • Create New...