Work program in the game LINEAGE 2
Forum rules
Please read the forum rules before posting for the first time.
The more information you can provide, the quicker and more accurately someone can help.
NOTE: To reduce spam, new users can not post links, files or images until they have at least 4 posts.
Please read the forum rules before posting for the first time.
The more information you can provide, the quicker and more accurately someone can help.
NOTE: To reduce spam, new users can not post links, files or images until they have at least 4 posts.
Work program in the game LINEAGE 2
Hello. The question is as follows. I play in Lineage 2 decided to use the side mouse button so that when clicked, runs a series of actions that stopped pressing this button. For example, the following combination: {HOLD<3>}{F1}{WAIT<1>}{HOLD<3>}{LEFT}{HOLD<3>}{UP} the meaning of this combination is the following: when pressing the side button of the mouse, the following happens in the game happens press and hold F1 (the key is in-game macro in which the character begins to beat the enemies with special abilities for 3 seconds then pause for 3 seconds on hold for 3 seconds pressing the LEFT (when this character in the game turns left) the next one is holding the pack (and the character starts to run forward for 3 seconds) and then this cycle repeats until I this key is not pressed again. This algorithm works well and the cycle persists. But there comes a point at 3-4 cycle that the program X-MONSIEUR hangs and stops working. Not jelanie her work is expressed in the following: in the normal mode, when I press the mouse button in the program directory the mouse keys light up in yellow and hangs programs such action is not, and what would the program work again you have to disable the program and enable it again. What is the reason? Thank you.
Re: Work program in the game LINEAGE 2
What version are you using?
If you are on 2.7 or earlier, then how have you configured the simulated yets? ie. What method have you chosen?
If you have delays in there, you should select the method called "In another thread" otherwise it will block the main thread, cause the hook to time out and that will stop XMBC working.
2.8 resolves this by sending everything in another thread. You can try the latest beta by downloading it from the Beta thread here.
Thanks.
Phil
If you are on 2.7 or earlier, then how have you configured the simulated yets? ie. What method have you chosen?
If you have delays in there, you should select the method called "In another thread" otherwise it will block the main thread, cause the hook to time out and that will stop XMBC working.
2.8 resolves this by sending everything in another thread. You can try the latest beta by downloading it from the Beta thread here.
Thanks.
Phil
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)
--[ Administrator & XMBC Author ]--
Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)
Re: Work program in the game LINEAGE 2
I am using version 2.7. Used the method of "simulated keys (undefined) -> 7 sticky (repeat until the button is pressed again)" method is good because when you click is the action cycle. Now I will try as you said, the results will be written. Thank you.
Re: Work program in the game LINEAGE 2
Good day! Conducted experiments with the function <a simulated key>, or rather with podhola <in another thread> everything works fine without problems, but I need a function that will repeat pressing the F1 button again and again, this function is suitable only <7 sticky (repeat until the button is pressed again)> and with this feature there are problems in the game Lineage 2 the cycle is repeated 2-3 times and then the program X-MOUSE hangs and stops responding to mouse clicks it is reflected in the fact that in the program window X-MOUSE clicking on the mouse button, a line do not burn yellow. How can that be? Thank you.
Re: Work program in the game LINEAGE 2
> How can that be?
Well it could be anything!
Firstly:
1. Are there any errors in the log file (please send it to me).
2. Can you turn on debug logging and see if you can repeat the "crash" or error. Then can you also send me that log file with the debug info which may be more useful (either post it here or email it to me).
Normally if the button does not turn the box yellow on the config screen, it means the mouse hook is no longer active/installed. This can happen if it a) times out (does not respond for 5 seconds) or b) crashes in some other way. With 2.8 beta, all the input is sent from another thread, but the repeat timer I think is still in the main thread - so that could be interfering with the hook.
Does it only happen in the game OR does it happen in any other windows app? If its only in the game it might be more difficult for me to investigate (as I dont have that game).
Thanks,
Phil
Well it could be anything!
Firstly:
1. Are there any errors in the log file (please send it to me).
2. Can you turn on debug logging and see if you can repeat the "crash" or error. Then can you also send me that log file with the debug info which may be more useful (either post it here or email it to me).
Normally if the button does not turn the box yellow on the config screen, it means the mouse hook is no longer active/installed. This can happen if it a) times out (does not respond for 5 seconds) or b) crashes in some other way. With 2.8 beta, all the input is sent from another thread, but the repeat timer I think is still in the main thread - so that could be interfering with the hook.
Does it only happen in the game OR does it happen in any other windows app? If its only in the game it might be more difficult for me to investigate (as I dont have that game).
Thanks,
Phil
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)
--[ Administrator & XMBC Author ]--
Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)
Re: Work program in the game LINEAGE 2
Thanks for a good answer. If you honestly ask the cycle in another program not kept, asked the cycle only in the game (be sure today will probyvat and analyze). As for the error log, I'm in the game a few more times, I will ask the cycle pressing the F1 key, and immediately he will send you to identify errors. Good-bye.
Re: Work program in the game LINEAGE 2
Hello. Made a detailed report about the issue, including photos from the screen. Tell me how in the forum to post pictures or they can somehow send you by e-mail?
Re: Work program in the game LINEAGE 2
Now you have 5 posts you should be able to post images using the IMG button above.
Alternatively, PM or email it to me (phil at highrez.co.uk) and let me know just in case it gets caught in my spam folder (although I hope it will not!).
Thanks,
Phil
Alternatively, PM or email it to me (phil at highrez.co.uk) and let me know just in case it gets caught in my spam folder (although I hope it will not!).
Thanks,
Phil
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)
--[ Administrator & XMBC Author ]--
Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)
Re: Work program in the game LINEAGE 2
In these photos I tried to register.
LOG FILE:
********************************************************************************************************************************
17-09-2014 18:10:14.0242> X-Mouse Button Control v2.7 (x86) Startup. Commandline '/notportable'
17-09-2014 18:10:14.0367> Running on Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 32-bit, Hook Timeout: 5000 ms
17-09-2014 18:10:14.0367> X-Mouse Button Control is running using an elevated administrative account (UAC elevation)
17-09-2014 18:10:14.0367> Startup folder: 'C:\Program Files\Highresolution Enterprises\X-Mouse Button Control\'
17-09-2014 18:10:14.0367> Settings (and log) folder: 'C:\Users\Дима\AppData\Roaming\Highresolution Enterprises\XMouseButtonControl\'
17-09-2014 18:10:14.0367> Hooking the mouse...
17-09-2014 18:10:14.0367> Successfully hooked into the mouse messages.
17-09-2014 18:10:15.0788> No keyboard layout loaded, nothing to unload.
17-09-2014 18:10:15.0788> Current language is 0x04190419
17-09-2014 18:10:15.0788> Checking installed keyboard layout: 0x04190419
17-09-2014 18:10:15.0788> Using keyboard language 0x04190419
17-09-2014 18:10:15.0788> HookThread: Successfully set the mouse hook 0x50259
17-09-2014 18:10:15.0788> HookThread: Successfully set the keyboard hook 0x2025F
17-09-2014 18:10:15.0788> Successfully created the main message window.
17-09-2014 18:14:07.0182> CMyMessageWnd::OnSetup - Clear hotkeys...
17-09-2014 18:14:07.0182> CMyMessageWnd::OnSetup - Opening setup dialog.
17-09-2014 18:15:20.0581> CMyMessageWnd::OnSetup - Setup dialog closed.
17-09-2014 18:17:07.0833> Display resolution changed (1366, 768)
17-09-2014 18:21:05.0577> Display resolution changed (1366, 768)
17-09-2014 18:21:13.0972> CMyMessageWnd::OnSetup - Clear hotkeys...
17-09-2014 18:21:13.0972> CMyMessageWnd::OnSetup - Opening setup dialog.
17-09-2014 18:22:52.0609> Display resolution changed (1366, 768)
17-09-2014 18:25:05.0085> Display resolution changed (1366, 768)
17-09-2014 18:27:19.0246> Applying changes to X-Mouse Button Control settings...
17-09-2014 18:30:12.0049> Applying changes to X-Mouse Button Control settings...
17-09-2014 18:31:03.0201> Unable to remove keyboard hook. Error 0x0000057C
17-09-2014 18:31:03.0201> Unable to remove mouse hook. Error 0x0000057C
17-09-2014 18:31:03.0201> Hook thread exited with result 1
17-09-2014 18:31:04.0059> RemoveMouseHook took 858ms
17-09-2014 18:32:15.0118> CMyMessageWnd::OnSetup - Setup dialog closed.
17-09-2014 18:37:29.0475> CMyMessageWnd::OnSetup - Clear hotkeys...
17-09-2014 18:37:29.0475> CMyMessageWnd::OnSetup - Opening setup dialog.
17-09-2014 18:38:44.0262> Applying changes to X-Mouse Button Control settings...
17-09-2014 18:38:45.0292> CMyMessageWnd::OnSetup - Setup dialog closed.
17-09-2014 18:38:47.0351> CMyMessageWnd::OnSetup - Clear hotkeys...
17-09-2014 18:38:47.0351> CMyMessageWnd::OnSetup - Opening setup dialog.
LOG FILE:
********************************************************************************************************************************
17-09-2014 18:10:14.0242> X-Mouse Button Control v2.7 (x86) Startup. Commandline '/notportable'
17-09-2014 18:10:14.0367> Running on Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 32-bit, Hook Timeout: 5000 ms
17-09-2014 18:10:14.0367> X-Mouse Button Control is running using an elevated administrative account (UAC elevation)
17-09-2014 18:10:14.0367> Startup folder: 'C:\Program Files\Highresolution Enterprises\X-Mouse Button Control\'
17-09-2014 18:10:14.0367> Settings (and log) folder: 'C:\Users\Дима\AppData\Roaming\Highresolution Enterprises\XMouseButtonControl\'
17-09-2014 18:10:14.0367> Hooking the mouse...
17-09-2014 18:10:14.0367> Successfully hooked into the mouse messages.
17-09-2014 18:10:15.0788> No keyboard layout loaded, nothing to unload.
17-09-2014 18:10:15.0788> Current language is 0x04190419
17-09-2014 18:10:15.0788> Checking installed keyboard layout: 0x04190419
17-09-2014 18:10:15.0788> Using keyboard language 0x04190419
17-09-2014 18:10:15.0788> HookThread: Successfully set the mouse hook 0x50259
17-09-2014 18:10:15.0788> HookThread: Successfully set the keyboard hook 0x2025F
17-09-2014 18:10:15.0788> Successfully created the main message window.
17-09-2014 18:14:07.0182> CMyMessageWnd::OnSetup - Clear hotkeys...
17-09-2014 18:14:07.0182> CMyMessageWnd::OnSetup - Opening setup dialog.
17-09-2014 18:15:20.0581> CMyMessageWnd::OnSetup - Setup dialog closed.
17-09-2014 18:17:07.0833> Display resolution changed (1366, 768)
17-09-2014 18:21:05.0577> Display resolution changed (1366, 768)
17-09-2014 18:21:13.0972> CMyMessageWnd::OnSetup - Clear hotkeys...
17-09-2014 18:21:13.0972> CMyMessageWnd::OnSetup - Opening setup dialog.
17-09-2014 18:22:52.0609> Display resolution changed (1366, 768)
17-09-2014 18:25:05.0085> Display resolution changed (1366, 768)
17-09-2014 18:27:19.0246> Applying changes to X-Mouse Button Control settings...
17-09-2014 18:30:12.0049> Applying changes to X-Mouse Button Control settings...
17-09-2014 18:31:03.0201> Unable to remove keyboard hook. Error 0x0000057C
17-09-2014 18:31:03.0201> Unable to remove mouse hook. Error 0x0000057C
17-09-2014 18:31:03.0201> Hook thread exited with result 1
17-09-2014 18:31:04.0059> RemoveMouseHook took 858ms
17-09-2014 18:32:15.0118> CMyMessageWnd::OnSetup - Setup dialog closed.
17-09-2014 18:37:29.0475> CMyMessageWnd::OnSetup - Clear hotkeys...
17-09-2014 18:37:29.0475> CMyMessageWnd::OnSetup - Opening setup dialog.
17-09-2014 18:38:44.0262> Applying changes to X-Mouse Button Control settings...
17-09-2014 18:38:45.0292> CMyMessageWnd::OnSetup - Setup dialog closed.
17-09-2014 18:38:47.0351> CMyMessageWnd::OnSetup - Clear hotkeys...
17-09-2014 18:38:47.0351> CMyMessageWnd::OnSetup - Opening setup dialog.
Re: Work program in the game LINEAGE 2
Hi, unfortunately you didn't turn on debug logging so there is not much to go by.
However, the following entries would suggest that the hook has been removed by something other than XMBC...
Any chance you could repeat after turning on debug logging? You can do this in the advanced settings dialog, or you can enable global hotkeys and toggle it on and off with hotkeys. You have to press apply on the main main window before the debug logging is activated - and it will be deactivated next time you run XMBC or when you turn it off manually.
Without that its going to be near impossible to know what exactly is causing the hook to be removed. With debug logging it might be more obvious!
Thanks,
Phil
However, the following entries would suggest that the hook has been removed by something other than XMBC...
So it looks like my assumption that the hook has either locked up or been removed by Windows for some reason is quite likely.17-09-2014 18:31:03.0201> Unable to remove keyboard hook. Error 0x0000057C
17-09-2014 18:31:03.0201> Unable to remove mouse hook. Error 0x0000057C
17-09-2014 18:31:03.0201> Hook thread exited with result 1
Any chance you could repeat after turning on debug logging? You can do this in the advanced settings dialog, or you can enable global hotkeys and toggle it on and off with hotkeys. You have to press apply on the main main window before the debug logging is activated - and it will be deactivated next time you run XMBC or when you turn it off manually.
Without that its going to be near impossible to know what exactly is causing the hook to be removed. With debug logging it might be more obvious!
Thanks,
Phil
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)
--[ Administrator & XMBC Author ]--
Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)
Re: Work program in the game LINEAGE 2
I understood you. I will try to fix the problem using your advice, the results will be written. Thank you.
Re: Work program in the game LINEAGE 2
Also, the screen shot is still 2.7. Have you tried the 2.8 Beta yet to see if it already fixes the problem?
If not, can you do so? As I said, the simulated keystrokes has been significantly re-written and improved.
EDIT: I have found a problem in this area in 2.8 Beta 14. I have fixed it and it will be in 2.8 Beta 15. Dont bother with 2.8 Beta UNTIL I have release beta 15 (shortly)
EDIT 2: 2.8 Beta 15 is now out - please try it.
Thanks,
Phil
If not, can you do so? As I said, the simulated keystrokes has been significantly re-written and improved.
EDIT: I have found a problem in this area in 2.8 Beta 14. I have fixed it and it will be in 2.8 Beta 15. Dont bother with 2.8 Beta UNTIL I have release beta 15 (shortly)
EDIT 2: 2.8 Beta 15 is now out - please try it.
Thanks,
Phil
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)
--[ Administrator & XMBC Author ]--
Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)