Bizarre Sega Super GT Plus Problem

[Ganondorf]

For some reason, in the service menu of Sega Super GT Plus, pressing service or test seems to read as being pressed twice. So, for example, trying to change the region by pressing service on the country makes it quickly change then back again. I thought it was a problem with my wireless keyboard as it sometimes inputs twice when pressed in other situations (such as typing) but after reassigning service and test to a controller, the issue persists. This does not happen in regular Sega Super GT, nor in any other game.

[Bart]

Some games have buggy or non-functioning service menus, unfortunately. It's emulation-related and I'm not sure what the precise cause of it is yet.

[Ganondorf]

Some games have buggy or non-functioning service menus, unfortunately. It's emulation-related and I'm not sure what the precise cause of it is yet.

Ah, right, thanks. I was beginning to think my XBox 360 controller was failing, as the triggers weren't working either (turns out I hadn't configured them to do anything!).

[jeff0811]

Some games have buggy or non-functioning service menus, unfortunately. It's emulation-related and I'm not sure what the precise cause of it is yet.

Ah, right, thanks. I was beginning to think my XBox 360 controller was failing, as the triggers weren't working either (turns out I hadn't configured them to do anything!).

YOU NEED TO EXCUTE X360CE to activate xinput.
AND ADD fOllow PARAMETER WHEN STARTUP SUPERMODEL EMULATOR
-input-system=xinput

AND ADD FOLLOW PARAMETER for configuration
-CONFIG-INPUTS

[Bart]

Some games have buggy or non-functioning service menus, unfortunately. It's emulation-related and I'm not sure what the precise cause of it is yet.

Ah, right, thanks. I was beginning to think my XBox 360 controller was failing, as the triggers weren't working either (turns out I hadn't configured them to do anything!).

YOU NEED TO EXCUTE X360CE to activate xinput.
AND ADD fOllow PARAMETER WHEN STARTUP SUPERMODEL EMULATOR
-input-system=xinput

AND ADD FOLLOW PARAMETER for configuration
-CONFIG-INPUTS

Note that whenever you run Supermodel with -input-system, you also have to pair that same option with -config-inputs (because the config dialog uses the input system, too, so you want to make sure it is using the right one). For XInput:

supermodel -config-inputs -input-system=xinput

[unfnknblvbl]

First of all, I just heard about this emulator this morning, about five minutes before I left for work. Man, I haven't been this excited about an emulator coming out since Modeler with the Model 2 games. From what I can see, it runs flawlessly on my system (aside from the issue I'm about to describe...)

Some games have buggy or non-functioning service menus, unfortunately. It's emulation-related and I'm not sure what the precise cause of it is yet.

Ah, right, thanks. I was beginning to think my XBox 360 controller was failing, as the triggers weren't working either (turns out I hadn't configured them to do anything!).

YOU NEED TO EXCUTE X360CE to activate xinput.
AND ADD fOllow PARAMETER WHEN STARTUP SUPERMODEL EMULATOR
-input-system=xinput

AND ADD FOLLOW PARAMETER for configuration
-CONFIG-INPUTS

Surely if Supermodel has been compiled with XInput enabled, we shouldn't need an XInput -> DInput translator?

The problem I'm seeing is that I can't configure my X360 pads & wheel. At all. No matter what I press, the config window just gives me a rude look and the command window says;

Code: Select all

Common Controls:
 P1 Start [KEY_1,JOY1_BUTTON10]: Ret/c/s/a/r/Down/h/b/q/Esc?

If I just close the blank config window, then it reverts back to default settings... which aren't fun with a wheel (no accelerator).

What are the values for XInput that I can just enter into the .ini file manually, rather than bang my head against the desk?

[nikdd]

Surely if Supermodel has been compiled with XInput enabled, we shouldn't need an XInput -> DInput translator?

It's not a XInput->DInput translator. The -input-system option just specifies whether to use the XInput API or the DirectInput API to handle attached X360 pads. An X360 controller will work with both APIs but you will have slightly limited functionality when running with just the DirectInput API (no vibration effect and inability to use the two triggers at the same time). So, just run Supermodel with -input-system=xinput and everything should be fine.

The problem I'm seeing is that I can't configure my X360 pads & wheel. At all. No matter what I press, the config window just gives me a rude look and the command window says

Did you ensure that the blank emulator window (not the command window with the text instructions in it) was the top-most window? If not, click on it with the mouse to make sure it's in front. This is the common mistake that catches people out. When we get around to implementing a proper GUI in Supermodel this will no longer be a problem.

If that's not the reason, then press 'i' on the config screen to check that your X360 controller is in the list of attached joysticks.

If it's not there, then you'll need to check your drivers etc. I don't have a X360 controller so I don't know what exactly needs to be installed to get it working properly - someone else on here should be able to help you there.

]What are the values for XInput that I can just enter into the .ini file manually, rather than bang my head against the desk?

They are the same as any other attached joystick or controller. You just need to work out what number the system assigns the X360 controller to in the list of attached joysticks and then use that to specify the controller's axes and buttons, eg JOY1_XAXIS, JOY1_BUTTON1 etc. Check the README.txt for more details about input mappings.

Cheers, Nik.