ducon2016

Right now x360kb does not allow mixed usage of joysticks and keyboard unfortunately.

Try DInputDisable=1

[WARNING THIS IS EXPERIMENTAL] Outrun 2006 on PC is nice except for the UI, it looks very low res when played on HD monitors. I just made a quick test to see if we could make it better. So sharing the progress so far. I have been playing around with the file format, and wanted to share some of the promising initial results with xBRZ and here with Waifu2x Noise Level 0 and here Waifu2x Noise Level 3 For those interested in trying it Outrun2006Test.7z 1. You will need to make a copy of your Sprite folder 2. Edit Process All.bat and change the path to your Sprite copy folder 3. Run Process All.bat, and when finished copy all the .sz files in the original Sprite folder (NOT THE COPY) 4. Make a copy of OR2006C2C.exe and patch it Offset: 0002D22E Original: DB 44 Patch: 8B 4C Offset: 0002D232 Original: 8B 4C 24 1C 85 C9 7D 06 D8 05 70 80 62 00 Patch: D1 E9 89 4C 24 1C DB 44 24 1C 90 90 90 90 Offset: 0002D246 Original: 85 D2 DB 44 Patch: D1 EA 89 54 Offset: 0002D24C Original: 7D 06 D8 05 70 80 62 00 Patch: DB 44 24 20 90 90 90 90 Few issues: 1. My converter does not fully work with some .sz files yet (the ones commented out in the batch file), which likely will results in bugs when those images are used 2. All art is automatically upscaled, and no solution is ideal right now. Waifu 2x with Noise Level 3 seems the best though. 3. Might be a lot of bugs, it has not been extensively tested

It works with PadCount=2 or 3 or 4 if you have the controls. I use it with two players on my setup, works really well.

@argonlefou might be able to help you.

ATI card or NVidia?

Try to use the latest version of Demulshooter.

Yes I use it with Teknoparrot too it works. You need to put xinput1_4.dll and x360kb.ini in the teknoparrot folder, NOT in the game folder.

Looking at Log1. Thanks @coolspot You press X at 2020-07-30 18:22:28.236, the game reads xinput 6 milliseconds later at 2020-07-30 18:22:28.242 and it is recognized. Then you keep X pressed and press A at 2020-07-30 18:22:28.253, the game reads xinput at 2020-07-30 18:22:28.259 and finds both X and A pressed! Then you keep those pressed and the game those are kept pressed until 2020-07-30 18:22:28.865. What is possible is because the game polls the control at intervals of 16ms, it is expecting both inputs should be pressed within the same strict window. Sorry yes if you reuse the same buttons it will trigger the individual buttons, maybe I should add an option for that. Can you try v15 I just posted today, this could be related to what I fixed for @huntsman360, I was waiting 16ms in some cases which seems to be the exact interval your log exhibits. So I might have fixed it already. 2020-07-30 18:22:28.236 ( 41.486s) [ ] config.cpp:343 INFO| [HookCallback] Key pressed A2 2020-07-30 18:22:28.236 ( 41.486s) [ ] config.cpp:360 INFO| [HookCallback] Key blocked A2 2020-07-30 18:22:28.242 ( 41.493s) [ ] x360kb.cpp:37 INFO| XInputGetState Pad 0 2020-07-30 18:22:28.242 ( 41.493s) [ ] x360kb.cpp:59 INFO| X button pressed 2020-07-30 18:22:28.242 ( 41.493s) [ ] x360kb.cpp:84 INFO| Left Analog Right axis pressed 2020-07-30 18:22:28.242 ( 41.493s) [ ] x360kb.cpp:37 INFO| XInputGetState Pad 1 2020-07-30 18:22:28.253 ( 41.503s) [ ] config.cpp:343 INFO| [HookCallback] Key pressed A0 2020-07-30 18:22:28.253 ( 41.503s) [ ] config.cpp:360 INFO| [HookCallback] Key blocked A0 2020-07-30 18:22:28.259 ( 41.510s) [ ] x360kb.cpp:37 INFO| XInputGetState Pad 0 2020-07-30 18:22:28.259 ( 41.510s) [ ] x360kb.cpp:59 INFO| A button pressed 2020-07-30 18:22:28.259 ( 41.510s) [ ] x360kb.cpp:59 INFO| X button pressed 2020-07-30 18:22:28.259 ( 41.510s) [ ] x360kb.cpp:59 INFO| Left Shoulder button pressed 2020-07-30 18:22:28.259 ( 41.510s) [ ] x360kb.cpp:84 INFO| Left Analog Right axis pressed 2020-07-30 18:22:28.259 ( 41.510s) [ ] x360kb.cpp:37 INFO| XInputGetState Pad 1 2020-07-30 18:22:28.280 ( 41.531s) [ ] x360kb.cpp:37 INFO| XInputGetState Pad 0 2020-07-30 18:22:28.280 ( 41.531s) [ ] x360kb.cpp:59 INFO| A button pressed 2020-07-30 18:22:28.280 ( 41.531s) [ ] x360kb.cpp:59 INFO| X button pressed 2020-07-30 18:22:28.280 ( 41.531s) [ ] x360kb.cpp:59 INFO| Left Shoulder button pressed 2020-07-30 18:22:28.280 ( 41.531s) [ ] x360kb.cpp:84 INFO| Left Analog Right axis pressed 2020-07-30 18:22:28.280 ( 41.531s) [ ] x360kb.cpp:37 INFO| XInputGetState Pad 1 2020-07-30 18:22:28.292 ( 41.543s) [ ] x360kb.cpp:37 INFO| XInputGetState Pad 0 2020-07-30 18:22:28.292 ( 41.543s) [ ] x360kb.cpp:59 INFO| A button pressed 2020-07-30 18:22:28.292 ( 41.543s) [ ] x360kb.cpp:59 INFO| X button pressed 2020-07-30 18:22:28.292 ( 41.543s) [ ] x360kb.cpp:59 INFO| Left Shoulder button pressed 2020-07-30 18:22:28.292 ( 41.543s) [ ] x360kb.cpp:84 INFO| Left Analog Right axis pressed 2020-07-30 18:22:28.292 ( 41.543s) [ ] x360kb.cpp:37 INFO| XInputGetState Pad 1 2020-07-30 18:22:28.309 ( 41.559s) [ ] x360kb.cpp:37 INFO| XInputGetState Pad 0 2020-07-30 18:22:28.309 ( 41.560s) [ ] x360kb.cpp:59 INFO| A button pressed 2020-07-30 18:22:28.309 ( 41.560s) [ ] x360kb.cpp:59 INFO| X button pressed 2020-07-30 18:22:28.309 ( 41.560s) [ ] x360kb.cpp:59 INFO| Left Shoulder button pressed 2020-07-30 18:22:28.309 ( 41.560s) [ ] x360kb.cpp:84 INFO| Left Analog Right axis pressed 2020-07-30 18:22:28.309 ( 41.560s) [ ] x360kb.cpp:37 INFO| XInputGetState Pad 1 2020-07-30 18:22:28.325 ( 41.576s) [ ] x360kb.cpp:37 INFO| XInputGetState Pad 0 2020-07-30 18:22:28.325 ( 41.576s) [ ] x360kb.cpp:59 INFO| A button pressed 2020-07-30 18:22:28.325 ( 41.576s) [ ] x360kb.cpp:59 INFO| X button pressed

It does work with combinations, I use them all the time. You can even set a combination as an input for example I used stuff like DPad Left=C&Left. In the config turn on the log, press the two buttons and send me the log please.

Awesome, glad we could find it and fix it. Thanks for reporting the issue.

Here are all the updated DLLs, x360kb-v15.7z Let me know if it works

I tried something in the code. There is a known performance issue with the keyboard hooks, the code assumed a case would never happen but unfortunately it did, so cleaning it up. Will publish all dlls later today.

Tu as les derniers trucs souvent ici aussi [Hidden Content]

Not sure what it is, try this [Hidden Content]