Messages

1

Technical Support / [Q/A] If I update my XIM4 to the latest 20171004, will I lose my saved profiles?

« on: 06:21 PM - 03/17/18 »

Hello,

I'm currently running XIM4 Firmware Version 20151120.

If I update to the latest 20171004, will I lose my saving profiles and their settings? I have quite a bit of games saved on there.

Thank you.


P.S.

Do I need to update SandhawC to 1.5? I'm still running 1.2 (yes, I'm very lazy about updating, it's a bad habit)

2

Commander / How do I get SandhawC AHK script to recognize a controller button press?

« on: 06:38 PM - 06/10/17 »

Hello,

How do I get AHK script to recognize a button press on the PS4 controller (not the keyboard)? I have SandhawC running and setup, and it's quite simple to to AHK to recognize a button pressed on the keyboard by simply using the function GetKeyState such as:

if GetKeyState("Ctrl")
        //do stuff

But I don't know if AHK can recognize something like "square" or "R1" button pressed on PS4 controller through SandhawC.

3

PlayStation / Re: Looking for Battlefield 4 Players

« on: 03:20 AM - 05/23/16 »

Yep, shotguns got a big damage buff following the major spring patch. And since TDM is small maps, they tend to be more effective.

The best way to use a shotgun is the aim down sights, as that tightens the spread drastically. How most people do it is to make sure that your "snap to" aim assist is enabled and once their crosshairs are hovered near you, just ADS and shoot really fast for a easy kill. If they have full choke attachment on their shotgun, their range is even greater. If they have a pump action, the number of pellets is even greater.

Keep in mind shotguns do the most damage against targets fully exposed and standing. If a target is partially in cover, since they can't control where the pellets go, the damage is reduced. And I believe shotguns do no extra damage with head shot hits. So if only your head is sticking out of cover, your still fairly safe against a shotgun hit. So the trick is to be in cover. Though on maps like Zavod, it is trickier since there are more limited cover options.

Also, bullets you fire actually come out of your head in this game. Visually, it looks like it is existing the gun, but reality it is being fired from your head. That's why sometimes you see only a guy's head sticking out of cover, but his still shooting at you.

4

PlayStation / Re: Looking for Battlefield 4 Players

« on: 01:03 PM - 05/22/16 »

I highly recommend playing team deathmatch if you want to bring out the full power of the xim4

Or other smaller mapped gamemodes with no vehicles. I feel like the xim4 doesn't give much of an advantage over controllers when it comes to vehicle controls (and certainly not when it comes to piloting).

But on team deathmatch or domination, there are no vehicles and everyone is on the ground with their guns. Really good place for a xim. Also if you run with a good squad, you can totally control the map, pretty much spawn trap the opposing team and hold down chock points of the map.

I highly recommend checking out competitive tournaments ESL battlefield 4 videos on youtube. The tournaments only play small map, no vehicle game modes and the players are on the PC. Study their mouse and keyboard movements, those guys have amazing speed & reactions. Good source of studying game mechanics.

5

Commander / Re: no recoil not working

« on: 05:16 PM - 05/16/16 »

Abc, I tried out the script you posted, but it is inconsistent. It moves the mouse down a different amount of pixels every time. 

I did some testing with DllCall and it is extremely inconsistent and unreliable. Especially with higher number of pixels moved. For instance, I tested this by running a single DllCall to move the mouse down 40 pixels everytime I clicked the left mouse button. I pointed my crosshair dot on the same starting location on a wall and checked how far down it moved. Different results almost every time.

This is problematic, as guns with heavy recoil that require a lot of mouse movement down (such as AEK with heavy barrel in Battlefield 4) require a large of amount pixels down. Using DllCall with small amount of pixels moved each time is not enough.

I guess sandhawC has some limitations when it comes to mouse movement. Are there other methods or functions? Also, why doesn't MouseMove function work at all on sandhawC?

6

Commander / Re: Rapid Fire written in AHK not smooth nor consistent

« on: 02:09 AM - 05/16/16 »

Okay, so I made some adjustments to my first attempt.
I realized that there was too many commands being inputted to the xim4 without the proper 8 ms wait time. Especially between mouse up and mouse down.

This is my new code, which is now consistent and has a much faster rapid fire.

Code: [Select]

#NoEnv  ; Recommended for performance and compatibility with future AutoHotkey releases.
#UseHook ; Because Od1n said so
; #Warn  ; Enable warnings to assist with detecting common errors.
SendMode Input  ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir%  ; Ensures a consistent starting directory.


~LButton::

while(GetKeyState("LButton","P")=1) {
Sleep, 27
Click down
Sleep, 27
Click up
}
return
I pretty much switched a g18 in battlefield 4 to single fire and could not tell the difference between that and full auto. If anyone here has got a even faster rapid fire written, please let me know.

However, still tons of problems to fix. Rapid fire is an easy script to write, but I could not get auto mouse move to be consistent. Seems like everytime I use DllCall with mouse_event, xim4 has different results everytime.

7

Commander / Re: Rapid Fire written in AHK not smooth nor consistent

« on: 02:07 AM - 05/16/16 »

Wouldn't it be easier to just have a mouse that you can use macros on, like the bloody series?

But doesn't the bloody mouse DPI cap at 3,200?

I'm a player who plays on high sensitivity and I tried 3,200 DPI and could not get my mouse to move nearly as fast as I wanted. I use the logitech G502 with 12,000 DPI and I love it for the high sensitivity.

8

Commander / Re: Rapid Fire written in AHK not smooth nor consistent

« on: 11:58 PM - 05/15/16 »

Okay, so I made some adjustments to my first attempt.
I realized that there was too many commands being inputted to the xim4 without the proper 8 ms wait time. Especially between mouse up and mouse down.

This is my new code, which is now consistent and has a much faster rapid fire.

Code: [Select]

#NoEnv  ; Recommended for performance and compatibility with future AutoHotkey releases.
#UseHook
; #Warn  ; Enable warnings to assist with detecting common errors.
SendMode Input  ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir%  ; Ensures a consistent starting directory.


~LButton::

while(GetKeyState("LButton","P")=1) {
Sleep, 27
Click down
Sleep, 27
Click up
}
return
I pretty much switched a g18 in battlefield 4 to single fire and could not tell the difference between that and full auto. If anyone here has got a even faster rapid fire written, please let me know.

However, still tons of problems to fix. Rapid fire is an easy script to write, but I could not get auto mouse move to be consistent. Seems like everytime I use DllCall with mouse_event, xim4 has different results everytime.

9

Commander / Rapid Fire written in AHK not smooth nor consistent

« on: 07:50 PM - 05/15/16 »

Hello, I've recently started experimenting with AHK scripts on sandhawC. My sandhawC displays my polling rate at a steady 125 Hz, 8 ms, unless I rapidly click my right mouse button.

I know that the xim4 has inconsistency with running rapid/complex commands on scripts, so I decided to play around with sandhawC and test out the easiest script to run: rapid-fire.

My test program:

Code: [Select]

#NoEnv  ; Recommended for performance and compatibility with future AutoHotkey releases.
#UseHook ;
SendMode Input  ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir%  ; Ensures a consistent starting directory.

Ins::Suspend
LButton::
Loop
{
Click
Sleep, 10

If (GetKeyState("LButton","P")=0)
Break
}
I've changed the sleep time around many times and it always fires any semi-auto gun too slowly and inconsistently. I know that spamming clicks isn't a good idea since the xim4 has a polling rate of 8 ms.
 But even when I change the sleep time to a massive 1000 (1 second), the fire rate is still inconsistent!

How can I make it fast and smooth for xim4? It runs and tests smooth on Windows, but that's expected.

10

Game Support / Re: The Division Beta 1/29 - 1/31/16

« on: 06:58 PM - 01/30/16 »

Thanks for the feedback! Sounds like I might be better off getting it on PC, as slow and controls are a dealbreaker for me. What FPS is Division running at on the PS4, does anyone know?

Locked in at 30 FPS for both Xbox and PS4, I believe was what developers have officially stated

I'd listen to other people's personal opinions before settling with a choice, since I am someone who is very picky with smooth and fast aim. I'm sure there are some people on this forum who do not have a problem with the division beta's aiming

11

Game Support / Re: The Division Beta 1/29 - 1/31/16

« on: 03:31 AM - 01/30/16 »

How well would you say the look and aim mechanics work with a mouse on the xim4 in this game? For example I thought GTA V was extremely bad, where as Destiny works great for the most part. Where on that scale would you put division? I know there is no dedicated ST yet, but just going by initial impressions.

This is all just my personal opinion, but on the PS4, I would say the Division beta aim and look mechanic is kinda bad and fairly choppy and not smooth at all, not just with the mouse and keyboard, but also with the controller a bit as well. Even using the analog stick sometimes I get a bit of choppy aim every now and then. With the M&KB, I feel the max sensitivity settings in the game could be higher, so making wide spins is a bit slow. Also when aiming down a rifle scope equipped weapon with a mouse, the sensitivity is super slow, so sniping was  tough.

All in all, I'm not sure if using a xim4 gives us a big advantage in the division beta. One method I have found to work nicely with the xim4 is if you are given the chance, rush up to your opposing player and fight them at very close range. Do not aim down weapon, just fire from the hip (that way you don't lose movement speed) and strafe left and right like mad and/or make circle around them. Some controller players do not have a very high sensitivity so they can't turn fast enough or they will struggle to hit you strafing with their analog stick. And since your using a mouse, use the high sensitivity precision to your advantage and you should be able to hit them pointblank from the hip while on the move.

Again, this is all just my personal take on the beta. I'd like to know what other xim4 users think of the aim mechanics of this game. Also, since this is just a beta, they might iron out the choppy aim in the full release and we'll be able to play with an official Divison ST. Applying the Splinter Cell Blacklist ST helps, as recommended by Od1n

12

XIM 4 Discussions / Logitech G502 Multi key macro feature not working well on XIM4

« on: 02:56 AM - 01/14/16 »

Hello,

On the Logitech G502, I noticed there is a multi key macro feature in the on-board memory. I know that the left and right mouse buttons cannot be changed to have this feature, but other buttons on the mouse can. Also, there are limitations, such as no repeating loop for this.

On the Logitech gaming software, I have binded one of the buttons on the G502 with a multi key when pressed; to fire once, delay, fire again, delay, fire again. Basically a 3 round burst every time I click the button. It works fine when the G502 is plugged into a PC.

However, when I plug into the XIM4, it does not work well. It does not register properly, 70% of the time, nothing happens, 29% of the time, it fires only once, 1% of the time, it works right and fires a 3 round burst. I thought the delay between shots might be too short for the XIM4 to register, so I made it a whopping 500ms delay and still does not work well. Does anyone who use a Logitech G502 have found a solution?

13

Game Support / Re: MGS V

« on: 07:14 AM - 12/22/15 »

Yes, the game's max sensitivity is as slow as a drunken snail. This applies to both Singleplayer and Online.

I personally don't feel like mouse + kb have a huge advantage over controllers in MGSV because of that. Nonetheless, I enjoyed the game.

14

XIM 4 Discussions / Re: Reproducable IOS app problem

« on: 03:23 PM - 12/17/15 »

I'm using the iPhone 4S and have noticed this bug happen to me as well, but only twice though. I just closed the app and restarted it and xim4 manager connected with no problem 5 seconds later. So it's totally not a big deal for me. Other than that, I can connect my iPhone to my xim4 almost all the time without having to restart the app.

15

Hardware Compatibility / GMYLE Keyboards compatible with Xim4?

« on: 03:14 PM - 12/17/15 »

Does anyone have any experience with using GMYLE keyboards on the xim4 and if they are compatible? From what I can tell, they tend to make inexpensive apple lookalike products.

The particular keyboard I'm looking at is this:
http://www.amazon.com/GMYLE%C2%AE-Ultra-Thin-Wired-Keyboard/dp/B003PHJJV6/ref=sr_1_11?ie=UTF8&qid=1450378366&sr=8-11&keywords=chiclet+keyboard

It's a very cheap wired chiclet keyboard with backlight, and since the Redragon Karura is on the red list of xim4, this is my #2 choice.