Show stopper issue - repeatable on multiple devices
Posted: Mon Feb 03, 2020 7:02 pm
Hey there, it appears that Rift is still a supported game but I've tried six different isboxer versions (Currently running the dev release from a few days ago). I'm a longtime multiboxer in EQ/EQ2/D3/DAOC/LOTRO/WOW but first time trying to get Rift to work. I'm having an issue I havent ever experienced in a game before and none of the things that would normally influence the issue seem to have any impact. The game works completely fine and as expected in fullscreen, windowed fullscreen, or windowed when single boxing outside of isboxer. While running even a single session in isboxer it takes repeated interactions with the game to obtain the correct positioning of the cursor. Sometimes it only takes one click away and one click back to resolve, sometimes it takes over 10. When it is having this issue it has two consistent behaviors:
1) The actual cursor is lower and to the right every time by the same amount
2) No interactions of any kind have any affect and are not received by the game client. Keyboards, clicks, mouse overs etc.
When multiboxing this issue is compounded as each process has its own current mouse state and it is essentially impossible to get all 5 sessions to have a healthy cursor at the same time which makes it even worse than manual boxing to navigate and play.
All sessions have the same resolution/fps and my hardware utilization is low. I have tried:
1) All instances on one monitor
2) Five different resolutions
3) All three in-game modes (fullscreen, windowed fullscreen, windowed)
4) Make game believe it is the foreground window
5) Lock cursor inside game window while focused
6) Repeater profile settings (fake cursor, cursor positioning mode scaled to fit, non interactive video fx affect cursor positioning). Even when showing fake cursor is turned on and all cursors move and react properly the bugged sessions still have a maligned cursor
7) Use instant window swapping (on and off)
8) Hotkey switching between instances instead of clicks
9) Using blank config with game wizard setup
I am at my wits end and I cant seem to find a solution. I have tried recreating this issue on two other computers with existing config/default new config with no change.
I have a video of the behavior when in broadcast mode with the fake cursor pass through. 3/5 instances have the wrong cursor, 2/5 have it proper.
Any advice or things to try? Really wanting to play this again but its just not playable in the current state.
1) The actual cursor is lower and to the right every time by the same amount
2) No interactions of any kind have any affect and are not received by the game client. Keyboards, clicks, mouse overs etc.
When multiboxing this issue is compounded as each process has its own current mouse state and it is essentially impossible to get all 5 sessions to have a healthy cursor at the same time which makes it even worse than manual boxing to navigate and play.
All sessions have the same resolution/fps and my hardware utilization is low. I have tried:
1) All instances on one monitor
2) Five different resolutions
3) All three in-game modes (fullscreen, windowed fullscreen, windowed)
4) Make game believe it is the foreground window
5) Lock cursor inside game window while focused
6) Repeater profile settings (fake cursor, cursor positioning mode scaled to fit, non interactive video fx affect cursor positioning). Even when showing fake cursor is turned on and all cursors move and react properly the bugged sessions still have a maligned cursor
7) Use instant window swapping (on and off)
8) Hotkey switching between instances instead of clicks
9) Using blank config with game wizard setup
I am at my wits end and I cant seem to find a solution. I have tried recreating this issue on two other computers with existing config/default new config with no change.
I have a video of the behavior when in broadcast mode with the fake cursor pass through. 3/5 instances have the wrong cursor, 2/5 have it proper.
Any advice or things to try? Really wanting to play this again but its just not playable in the current state.