Hi,
i´m on Win 7 using the DIY Adapter for dummies with
Cp2102
Teensy ++ 2.0
Logitech Software is installed and profiler is running. Using the EMUG29PS4 Firmware and Profile LogitechDrivingforceGT_G29.XML.
When i start GIMX everything seems to work fine. If i set Messages to curses i can see all Inputs made with the DFGT and Buttonwise every input from the DS4
BUT my PS4 won´t take any Input. Simply nothing happens.
Log looks like :
option -l with value `log.txt'
option -c with value `LogitechDrivingForceGT_G29.xml'
option -p with value `COM9'
status flag is set
subpos flag is set
force_updates flag is set
native mode is already enabled for HID device \\?\hid#vid_046d&pid_c29a#6&2f3dfcd0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} (PID=c29a)
Detected USB adapter: G29 PS4.
using default refresh period: 5.00ms
macros are not available for: joystick PS4 Controller (0)
Warning: can't open macro directory C:\Users\Dirk\AppData\Roaming//gimx//macros/
0 1445733692.649682, wheel (17)
Exiting
I can´t see the problem. Please help.
Also what about the Vendor ID of the DFGT... where do i need to put that?
Thx in advance
Narf76
DFGT won´t work...
Re: DFGT won´t work...
Sure. No reaction. On bot DS4 and DFGT.
But under Curses this Button press Shows up.
But under Curses this Button press Shows up.
Re: DFGT won´t work...
Yes 3.10 Updated Yesterday actually first tries were on 3.00 and Updated in between.
Re: DFGT won´t work...
Could you try the EMUPS4 firmware together with the Dualshock4.xml config?
GIMX creator
Re: DFGT won´t work...
I tested EMUPS4 with not the Dualshock4.xml but wit PS4_Battlefield4_foxy.xml to use mouse and keyboard but the result is basically the same. Inputs gets recognised
from GIMX but it seems they don´t get to the PS4.
Is there a way to test the adapterfunction?
from GIMX but it seems they don´t get to the PS4.
Is there a way to test the adapterfunction?
Re: DFGT won´t work...
What´s that? And how can i check if it´s there or not?
Re: DFGT won´t work...
Sorry, I meant load, not loss, and at90usb1286, not at90usb1280.
I think you did not load the right firmware. The teensy ++ 2.0 has the at90usb1286 chip, not the atmega32u4.
I think you did not load the right firmware. The teensy ++ 2.0 has the at90usb1286 chip, not the atmega32u4.
GIMX creator