AlanChatham
DPAD buttons behave incorrect on PS3 (fix)
I have succesfully connected my old Negcon controller to the PS3 with Unojoy, so many thanks for making that possible! However, the (DPAD) directional buttons were all wrong in the game menu (Wipeout HD) while they were working fine in the PS3 main menu.
Looking further into this issue I found that the PS3 expects the DPAD buttons to return a digital value as well as an analogue (sensitivy) value. It seems that Unojoy interprets these analogue values incorrect, as you might suspect when you read the following code snippet. :-)
// Gonna assume these are button analog values for the d-pad.
// NOTE: NOT EVEN SURE THIS IS RIGHT, OR IN THE CORRECT ORDER
uint8_t up_axis;
uint8_t right_axis;
uint8_t down_axis;
uint8_t left_axis;
So I rearranged the lines in usb_gamepad.h as shown below, built a new hexfile and now the DPAD buttons behave correctly in the Wipeout game menu too.
uint8_t right_axis;
uint8_t left_axis;
uint8_t up_axis;
uint8_t down_axis;
Hopefully this helps anybody, I'm back to racing! Thanks again.
I'm using this freeTds file [global] # TDS protocol version tds version = 7.4 client charset = UTF-8
It looks like there's an extra comma (,) character at the end of your option list (the WITH clause) and that the parser chokes on that.
+1
Happens to me as well, MSSQL-OPTIONS does not recognise multiple readers per thread.
@dimitri He just formatted the conf he submitted in a bad way. What he meant is
WITH include drop, create tables, create indexes, reset sequences, workers = 8, concurrency = 1,
and to this appended
multiple readers per thread, rows per range = 50000
Which should produce legitimate conf. You can see his conf is legitimate from his error log:
An unhandled error condition has been signalled: At
include drop, create tables, create indexes, reset sequences,
workers = 8, concurrency = 1, rows per range = 50000
^ (Line 6, Column 32, Position 345)
In context MSSQL-OPTIONS:While parsing MSSQL-OPTIONS.
Might I add, that the parser also chokes on 'matching' as in 'excluding table names matching' for me? It only accepts 'like' in MSSQL, not 'matching' as proposed by documentation? So the official example from the documentation
excluding table names matching 'LocalAccount' in schema 'dbo'
chokes the parser which produces a similar fatal error.
