XIM Community

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - CEOrko

Pages: [1]
1
Xbox / Interesting release from Bannco...
« on: 04:19 PM - 03/08/10 »
...Or at least that's how I feel about it to some degree.

(Posting this here because it seems off-topic everywhere else, save for the board of the same name, and because I am not trying to stir up any arguments with others by posting it on a board that would imply I was comparing the two options in a competitive manner.)

(Again, I'm not trying to be an @#$%. I'm merely highlighting the fact that people now have a choice of adapter besides the XIM that at least seems to hold more potential than the XFPS, regardless of however obsolete it may be once the XIM3 releases.)


It seems the producers of the FRAGnStein have made a Xbox 360 variant called SCORCH. I've no idea of how well it works that isn't based off of the performance of the FRAGnStein, but if it holds to that level, at least people who don't take the XIM course for whatever reason will have a better solution than what XCM have been trying to peddle for the last four years. It might also be worth finding a way to run a XIM through one if there is less input lag than through the current adapters used (yeah, I have been away for a bit too long), but... There's a good chance that the XIM3 will nullify any need. Anyway, at least there's even more choice given back to the consumer with this release, hopefully without their being susceptible to detection and disconnection.

Sorry if this is old, though I did check to see if it was mentioned already, without success.

2
Configurations and Requests / Left 4 Dead - 1800 DPI
« on: 08:20 PM - 02/23/09 »
InputUpdateFrequency=60
AutoAnalogDisconnect=True
DeadZone=8700
DeadZoneType=Square
YXRatio=.8
TranslationExponent=.47
SensitivityPrimary=2300
SensitivitySecondary=1400
DiagonalDampen=0.2
Smoothness=0

The secondary sensitivity here is set to its own button on the mouse and is used for long range sniping or very precise shooting over distance. You shouldn't need to use it except in the very few situations where you are able to get headshots at your leisure. In-game vertical and horizontal sensitivity are maxed.

    Attributes of these configurations worth noting:
    • I typically match a 180-degree turn to what is a little under a full wrist motion for me, so most of my configs might not be agreeable with anyone who likes twitch gameplay.
    • Though I start with what seems closest to the correct YX ratio when making a config, they are often changed to match my preferred patterns of diagonal movement. Usually this means the YX ratio ends up being lower than what is needed to achieve equal movement along both axes.
    • The deadzone used in these configs may be lower than what is normally used by the game in order to combat any jumpy behavior that was originally present. It should not create problems due to it being balanced out with sensitivity.
    • The diagonal dampen setting is geared towards making the distance traveled diagonally equal to that traveled horizontally or vertically with similar mouse strokes, not to matching the position of both distances if were they combined.
    • All of these configs were run on a G9 with the SetPoint pointer speed setting at five and mouse acceleration disabled through SetPoint, the control panel, and the system registry. Windows' pointer speed is also at the default "five" setting.

    3
    InputUpdateFrequency=60
    AutoAnalogDisconnect=True
    DeadZone=11500
    DeadZoneType=Circular
    YXRatio=2
    TranslationExponent=.5
    SensitivityPrimary=2000
    SensitivitySecondary=3000
    DiagonalDampen=.1
    Smoothness=0

    Secondary sensitivity is mapped to the same key as sprint to counteract the lower look sensitivity when running. The maximum in-game setting for look sensitivity was used with this config. I may have used the incorrect dead zone type to counter abnormal vertical movement, but I have not noticed any ill-effects from that setting change. This is mostly because AutoAnalogDisconnect needed to be left on due to the need of the controller to accurately control JDAMs.

      Attributes of these configurations worth noting:
      • I typically match a 180-degree turn to what is a little under a full wrist motion for me, so most of my configs might not be agreeable with anyone who likes twitch gameplay.
      • Though I start with what seems closest to the correct YX ratio when making a config, they are often changed to match my preferred patterns of diagonal movement. Usually this means the YX ratio ends up being lower than what is needed to achieve equal movement along both axes.
      • The deadzone used in these configs may be lower than what is normally used by the game in order to combat any jumpy behavior that was originally present. It should not create problems due to it being balanced out with sensitivity.
      • The diagonal dampen setting is geared towards making the distance traveled diagonally equal to that traveled horizontally or vertically with similar mouse strokes, not to matching the position of both distances if were they combined.
      • All of these configs were run on a G9 with the SetPoint pointer speed setting at five and mouse acceleration disabled through SetPoint, the control panel, and the system registry. Windows' pointer speed is also at the default "five" setting.

      4
      Because this is a config for the demo it may not work as well with the final product.

      InputUpdateFrequency=60
      AutoAnalogDisconnect=True
      DeadZone=6400
      DeadZoneType=Square
      YXRatio=1.25
      TranslationExponent=.65
      SensitivityPrimary=2400
      SensitivitySecondary=3000
      DiagonalDampen=.2
      Smoothness=.1

      Secondary sensitivity was used for aiming and the setting for in-game look sensitivity was the maximum allowed.

        Attributes of these configurations worth noting:
        • I typically match a 180-degree turn to what is a little under a full wrist motion for me, so most of my configs might not be agreeable with anyone who likes twitch gameplay.
        • Though I start with what seems closest to the correct YX ratio when making a config, they are often changed to match my preferred patterns of diagonal movement. Usually this means the YX ratio ends up being lower than what is needed to achieve equal movement along both axes.
        • The deadzone used in these configs may be lower than what is normally used by the game in order to combat any jumpy behavior that was originally present. It should not create problems due to it being balanced out with sensitivity.
        • The diagonal dampen setting is geared towards making the distance traveled diagonally equal to that traveled horizontally or vertically with similar mouse strokes, not to matching the position of both distances if were they combined.
        • All of these configs were run on a G9 with the SetPoint pointer speed setting at five and mouse acceleration disabled through SetPoint, the control panel, and the system registry. Windows' pointer speed is also at the default "five" setting.

        5
        Configurations and Requests / Bioshock (demo) - 1800 DPI
        « on: 02:01 PM - 02/23/09 »
        Because this is a config for the demo it may not work as well with the final product.

        InputUpdateFrequency=60
        AutoAnalogDisconnect=True
        DeadZone=6400
        DeadZoneType=Square
        YXRatio=1.5
        TranslationExponent=0.65
        SensitivityPrimary=2400
        SensitivitySecondary=2400
        DiagonalDampen=.3
        Smoothness=.2

        Secondary sensitivity was not used and in-game controller sensitivity was set to 100.

          Attributes of these configurations worth noting:
          • I typically match a 180-degree turn to what is a little under a full wrist motion for me, so most of my configs might not be agreeable with anyone who likes twitch gameplay.
          • Though I start with what seems closest to the correct YX ratio when making a config, they are often changed to match my preferred patterns of diagonal movement. Usually this means the YX ratio ends up being lower than what is needed to achieve equal movement along both axes.
          • The deadzone used in these configs may be lower than what is normally used by the game in order to combat any jumpy behavior that was originally present. It should not create problems due to it being balanced out with sensitivity.
          • The diagonal dampen setting is geared towards making the distance traveled diagonally equal to that traveled horizontally or vertically with similar mouse strokes, not to matching the position of both distances if were they combined.
          • All of these configs were run on a G9 with the SetPoint pointer speed setting at five and mouse acceleration disabled through SetPoint, the control panel, and the system registry. Windows' pointer speed is also at the default "five" setting.

          6
          Configurations and Requests / Dead Space (demo) - 1800 DPI
          « on: 01:54 PM - 02/23/09 »
          Because this is a config for the demo it may not work as well with the final product.

          InputUpdateFrequency=55
          AutoAnalogDisconnect=False
          DeadZone=17500
          DeadZoneType=Circular
          YXRatio=1.4
          TranslationExponent=0.65
          SensitivityPrimary=3100
          SensitivitySecondary=2200
          DiagonalDampen=.18
          Smoothness=.1

          Like in Resident Evil 5, Dead Space uses a smaller dead zone for aiming than it does when normally looking around. I countered this by increasing the primary sensitivity and mapping the secondary setting to the same button that aim is mapped to. Your mileage with a mouse in this game is going to vary if the full version is as limited (there is no option to change look sensitivity) as the demo.

            Attributes of these configurations worth noting:
            • I typically match a 180-degree turn to what is a little under a full wrist motion for me, so most of my configs might not be agreeable with anyone who likes twitch gameplay.
            • Though I start with what seems closest to the correct YX ratio when making a config, they are often changed to match my preferred patterns of diagonal movement. Usually this means the YX ratio ends up being lower than what is needed to achieve equal movement along both axes.
            • The deadzone used in these configs may be lower than what is normally used by the game in order to combat any jumpy behavior that was originally present. It should not create problems due to it being balanced out with sensitivity.
            • The diagonal dampen setting is geared towards making the distance traveled diagonally equal to that traveled horizontally or vertically with similar mouse strokes, not to matching the position of both distances if were they combined.
            • All of these configs were run on a G9 with the SetPoint pointer speed setting at five and mouse acceleration disabled through SetPoint, the control panel, and the system registry. Windows' pointer speed is also at the default "five" setting.

            7
            Configurations and Requests / F.E.A.R. 2 (demo) - 1800 DPI
            « on: 01:47 PM - 02/23/09 »
            Because this is a config for the demo it may not work as well with the final product.

            InputUpdateFrequency=55
            AutoAnalogDisconnect=True
            DeadZone=8700
            DeadZoneType=Square
            YXRatio=1.25
            TranslationExponent=0.65
            SensitivityPrimary=1000
            SensitivitySecondary=1000
            DiagonalDampen=0.1
            Smoothness=0.15

            Secondary sensitivity was not used or tested with any of the weapons available (it didn't really feel like it was needed with this game), in-game aim sensitivity was set to the maximum allowed.

              Attributes of these configurations worth noting:
              • I typically match a 180-degree turn to what is a little under a full wrist motion for me, so most of my configs might not be agreeable with anyone who likes twitch gameplay.
              • Though I start with what seems closest to the correct YX ratio when making a config, they are often changed to match my preferred patterns of diagonal movement. Usually this means the YX ratio ends up being lower than what is needed to achieve equal movement along both axes.
              • The deadzone used in these configs may be lower than what is normally used by the game in order to combat any jumpy behavior that was originally present. It should not create problems due to it being balanced out with sensitivity.
              • The diagonal dampen setting is geared towards making the distance traveled diagonally equal to that traveled horizontally or vertically with similar mouse strokes, not to matching the position of both distances if were they combined.
              • All of these configs were run on a G9 with the SetPoint pointer speed setting at five and mouse acceleration disabled through SetPoint, the control panel, and the system registry. Windows' pointer speed is also at the default "five" setting.

              8
              Configurations and Requests / Gears of War 2 - 1800 DPI
              « on: 01:42 PM - 02/23/09 »
              InputUpdateFrequency=60
              AutoAnalogDisconnect=True
              DeadZone=9800
              DeadZoneType=Square
              YXRatio=1.0
              TranslationExponent=.45
              SensitivityPrimary=3600
              SensitivitySecondary=2400
              DiagonalDampen=0.1
              Smoothness=0.1

              Secondary sensitivity is used for aiming, in-game look, target, and zoom sensitivity are all set to "high."

                Attributes of these configurations worth noting:
                • I typically match a 180-degree turn to what is a little under a full wrist motion for me, so most of my configs might not be agreeable with anyone who likes twitch gameplay.
                • Though I start with what seems closest to the correct YX ratio when making a config, they are often changed to match my preferred patterns of diagonal movement. Usually this means the YX ratio ends up being lower than what is needed to achieve equal movement along both axes.
                • The deadzone used in these configs may be lower than what is normally used by the game in order to combat any jumpy behavior that was originally present. It should not create problems due to it being balanced out with sensitivity.
                • The diagonal dampen setting is geared towards making the distance traveled diagonally equal to that traveled horizontally or vertically with similar mouse strokes, not to matching the position of both distances if were they combined.
                • All of these configs were run on a G9 with the SetPoint pointer speed setting at five and mouse acceleration disabled through SetPoint, the control panel, and the system registry. Windows' pointer speed is also at the default "five" setting.

                9
                Configurations and Requests / Halo 3 - 1800 DPI
                « on: 01:37 PM - 02/23/09 »
                InputUpdateFrequency=60
                AutoAnalogDisconnect=True
                DeadZone=8390
                DeadZoneType=Square
                YXRatio=1.5
                TranslationExponent=0.38
                SensitivityPrimary=3600
                SensitivitySecondary=8000
                DiagonalDampen=0.35
                Smoothness=.2

                The toggle for secondary sensitivity is mapped to an easy-to-reach key for when I need to use the higher setting in vehicles or when using mounted or handheld heavy weaponry. In-game sensitivity is set to ten.

                  Attributes of these configurations worth noting:
                  • I typically match a 180-degree turn to what is a little under a full wrist motion for me, so most of my configs might not be agreeable with anyone who likes twitch gameplay.
                  • Though I start with what seems closest to the correct YX ratio when making a config, they are often changed to match my preferred patterns of diagonal movement. Usually this means the YX ratio ends up being lower than what is needed to achieve equal movement along both axes.
                  • The deadzone used in these configs may be lower than what is normally used by the game in order to combat any jumpy behavior that was originally present. It should not create problems due to it being balanced out with sensitivity.
                  • The diagonal dampen setting is geared towards making the distance traveled diagonally equal to that traveled horizontally or vertically with similar mouse strokes, not to matching the position of both distances if were they combined.
                  • All of these configs were run on a G9 with the SetPoint pointer speed setting at five and mouse acceleration disabled through SetPoint, the control panel, and the system registry. Windows' pointer speed is also at the default "five" setting.

                  10
                  Configurations and Requests / Quake 4 (demo) - 1800 DPI
                  « on: 01:31 PM - 02/23/09 »
                  Because this is a config for the demo it may not work as well with the final product.

                  InputUpdateFrequency=60
                  AutoAnalogDisconnect=True
                  DeadZone=8900
                  DeadZoneType=Circular
                  YXRatio=1
                  TranslationExponent=0.6
                  SensitivityPrimary=2000
                  SensitivitySecondary=2200
                  DiagonalDampen=.2
                  Smoothness=.1

                  Secondary sensitivity was for scoped weapons. Config was used with the maximum vertical and horizontal sensitivity allowed in-game.

                    Attributes of these configurations worth noting:
                    • I typically match a 180-degree turn to what is a little under a full wrist motion for me, so most of my configs might not be agreeable with anyone who likes twitch gameplay.
                    • Though I start with what seems closest to the correct YX ratio when making a config, they are often changed to match my preferred patterns of diagonal movement. Usually this means the YX ratio ends up being lower than what is needed to achieve equal movement along both axes.
                    • The deadzone used in these configs may be lower than what is normally used by the game in order to combat any jumpy behavior that was originally present. It should not create problems due to it being balanced out with sensitivity.
                    • The diagonal dampen setting is geared towards making the distance traveled diagonally equal to that traveled horizontally or vertically with similar mouse strokes, not to matching the position of both distances if were they combined.
                    • All of these configs were run on a G9 with the SetPoint pointer speed setting at five and mouse acceleration disabled through SetPoint, the control panel, and the system registry. Windows' pointer speed is also at the default "five" setting.

                    11
                    Because this is a config for the demo it may not work as well with the final product.

                    InputUpdateFrequency=60
                    AutoAnalogDisconnect=True
                    DeadZone=8900
                    DeadZoneType=Square
                    YXRatio=1.68
                    TranslationExponent=.45
                    SensitivityPrimary=5000
                    SensitivitySecondary=3000
                    SensitivityToggle=MouseRight
                    DiagonalDampen=0.15
                    Smoothness=0.2

                    RE5 happens to lower the dead zone of the joystick when aiming. I had to raise the primary sensitivity to counter the the mismatched dead zone when not aiming. This config was used in conjunction with the maximum look sensitivity allowed in-game.

                      Attributes of these configurations worth noting:
                      • I typically match a 180-degree turn to what is a little under a full wrist motion for me, so most of my configs might not be agreeable with anyone who likes twitch gameplay.
                      • Though I start with what seems closest to the correct YX ratio when making a config, they are often changed to match my preferred patterns of diagonal movement. Usually this means the YX ratio ends up being lower than what is needed to achieve equal movement along both axes.
                      • The deadzone used in these configs may be lower than what is normally used by the game in order to combat any jumpy behavior that was originally present. It should not create problems due to it being balanced out with sensitivity.
                      • The diagonal dampen setting is geared towards making the distance traveled diagonally equal to that traveled horizontally or vertically with similar mouse strokes, not to matching the position of both distances if were they combined.
                      • All of these configs were run on a G9 with the SetPoint pointer speed setting at five and mouse acceleration disabled through SetPoint, the control panel, and the system registry. Windows' pointer speed is also at the default "five" setting.

                      12
                      Configurations and Requests / Shadowrun (demo) - 1800 DPI
                      « on: 01:02 PM - 02/23/09 »
                      Because this is a config for the demo it may not work as well with the final product.

                      InputUpdateFrequency=60
                      AutoAnalogDisconnect=False
                      DeadZone=7350
                      DeadZoneType=Circular
                      YXRatio=1.5
                      TranslationExponent=.45
                      SensitivityPrimary=3000
                      SensitivitySecondary=2000
                      DiagonalDampen=0
                      Smoothness=.1

                      The secondary sensitivity of this config is meant for more precise aiming of the held weapons that have a zoom function. In-game sensitivity is set to the maximum allowed (9) for both axes.

                        Attributes of these configurations worth noting:
                        • I typically match a 180-degree turn to what is a little under a full wrist motion for me, so most of my configs might not be agreeable with anyone who likes twitch gameplay.
                        • Though I start with what seems closest to the correct YX ratio when making a config, they are often changed to match my preferred patterns of diagonal movement. Usually this means the YX ratio ends up being lower than what is needed to achieve equal movement along both axes.
                        • The deadzone used in these configs may be lower than what is normally used by the game in order to combat any jumpy behavior that was originally present. It should not create problems due to it being balanced out with sensitivity.
                        • The diagonal dampen setting is geared towards making the distance traveled diagonally equal to that traveled horizontally or vertically with similar mouse strokes, not to matching the position of both distances if were they combined.
                        • All of these configs were run on a G9 with the SetPoint pointer speed setting at five and mouse acceleration disabled through SetPoint, the control panel, and the system registry. Windows' pointer speed is also at the default "five" setting.
                        [/list]

                        13
                        The beginnings of my trying to find a configuration that doesn't annoy in the Bad Company demo. Settings will be changing to represent my current parameters.

                        1200 DPI
                        Mouse Dead Zone: 0
                        Mouse Update Frequency: 1
                        Dead Zone: 23
                        Dead Zone Type: Circular
                        Y/X Ratio: 2:1
                        Translation Exponent: .4
                        Sensitivity Primary: 19.7
                        Sensitivity Secondary: 34 set to the same key as sprint
                        Smoothness: .15


                        Better configs out there, folks. I don't currently have my XIM1, so I can't fix the many issues with this one.

                        As of now I am still trying to see if I can't get snap movements with the mouse to be more accurate. Also, that .15 for smoothness doesn't seem to make any real difference when compared to 0, I just think I am imagining my being able to follow targets better with that setting. A major improvement, if someone could offer it, would be stable aiming at a higher sensitivity. Currently I have to stop aiming to turn more than 60 degrees from when I was initially facing. A higher secondary sensitivity seems to make the reticule jump too much for fine aiming.

                        Quick update: I'm severely tempted to increase and then move the secondary sensitivity binding from right mouse to the sprint button. The game lowers the turning rate when sprinting by a considerable amount, enough so that it is quite annoying. Think in terms of the transition from on-foot to a vehicle in Halo 3. That's how bad it feels. It does the same for turrets, as well, so a considerably higher sensitivity would likely help more in that situation, too. Not having a higher secondary sensitivity for aiming seems to drop my field of turning from 120-degrees to 90-degrees.

                        14
                        Support / XAE-ME behaving oddly
                        « on: 05:51 AM - 04/25/08 »
                        Well, whatever the problem was, a fresh install of XP solved it. Of my peripherals that could have been conflicting with it, the only ones I have yet to install are the TrackIR and the Saitek Pro Flight Rudder Pedals. Or it could have been anything else, really, given how at times I may install a piece of software that I use only once and then forget to remove from my machine. At least it was not permanent.

                        I finally got around to playing with macro editing in XAE-ME after postponing it due to the configuration being temperamental (had to delete every profile to fix it for some odd reason) whenever I tried to force some form of usability, though now it seems I have run in to another problem. When I run the XAE-ME software, I have it only able to recognize the left control key for the first six or seven seconds before it automatically stops detecting its input, leaving me unable to crouch or go prone until I close XAE-ME and restart. I initially suspected that this was some conflict with the SetPoint2 software I use to map the extra mouse buttons for XAE-ME, but canceling the process and restarting XAE-ME yields the same results as when I am using SetPoint. I was hoping someone who might have stumbled over this inconvenience earlier might have a solution, though I am not done trying yet. I am going to see if a simple macro assigned to LCTRL will manage to bypass this problem, though with that brings me to another difficulty I am having with the macros for XAE-ME.

                        After programming macros that seem to be working when I test them using either either the test function or by assigning them to what I would believe to be every key (with the possible exception to right and left controls), they cease to function correctly after assigning them to the left mouse button. In the case of right-trigger autofire, the mouse simply registers one click and then any input past that is not recognized. This behavior seems to be tied solely to the left mouse button and no other. Another odd attribute is that while right-trigger will not autofire on the left mouse button, the left-trigger will. Again, I suspected SetPoint of being the culprit as to why the macros were not functioning correctly, but disabling SetPoint did nothing to solve the problem. I also bothered to try switching the left and right mouse buttons to see if macros assigned to the right mouse would work as the left button, but that ended up having the exact same problem, with RMB suddenly not being able to have a right-trigger macro tied to it.

                        EDIT: Well, the left mouse button was simple enough to figure out. I had to remove the mapping from it for right trigger. As it was, the game was getting two signals from it, and the single-shot won out. Still no solution for the LCTRL problem, and placing a macro on LCTRL (with either B remapped to something else or also to LCTRL) for B does not work. It is like the key dies when I have XAE-ME running. It is also not my hotkey for the edit/quit function XAE-ME, as that may have significance.

                        I am going to bother testing to see if I can fix either of these issues, but I am moving more and more towards questioning if this is actually a problem with the Logitech G9 because of its onboard memory and profiles. Aside from any information on how I might resolve this, if anyone is using a profile that uses left control for the B-button or a right-trigger macro for the left mouse button, either the profile or the macro would be greatly appreciated.

                        Pages: [1]