Project

General

Profile

Actions

Emulator Issues #13688

open

NetPlay: Allow P1 to switch between GBA and Controller

Added by IngwiePhoenix 15 days ago. Updated 15 days ago.

Status:
New
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Feature request
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?

Pokemon XD

Game ID? (right click the game in the game list, Properties, Info tab)

GXXP01

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

N/A, NTkit/GCZ ISO, produces "Invalid Dump" output

What's the problem? Describe what went wrong.

During NetPlay in Pokemon XD, you can choose to use 4 GBAs to play against each other - the ultimative 16v16, two players versus two players - it's quite epic, did it before, absurd amounts of fun to be had here! However, back then, we did it on actual hardware. What we need now, is the option to replicate this using the Emulator.

I host the instance, but neither the Assign Controls button nor the Gamepad button allow me to change the controller that I use. I assume this goes a little deeper than "fixed controller load order set before VM launch". I would love to have access to the Assign Controls button to switch between the standart controller and GBA mid-emulation to facilitate this feature.

What steps will reproduce the problem?

  1. Launch the Game
  2. Select the third option on the title screen
  3. In the versus select, choose the bottom (GBA vs GBA vs GBA vs GBA)
  4. Upon starting, you can not switch your input, meaning that this mode is unusable.

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

Yes. Version is reported as: 2412-19, updated at the time of writing. It seems to be a nightly release.

Is the issue present in the latest release? For future reference, please also write down the version number of the latest release.

I am not sure, but quite certain.

If the issue isn't present in the latest release, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

Not aware.

If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer

Not graphical.

What are your PC specifications? (CPU, GPU, Operating System, more)

AMD Ryzen 9 3900X
32GB RAM @3200Mhz
NVIDIA RTX 4090
1TB NVMe Boot Drive; game loads off there too.

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

I don't really know what could help...other than, you really should find some friends and give it a try - it's fun :)

Thank you and kind regards,
Ingwie

PS.: I know tickets can be marked as Feature Requests; but I did not see the option for it. Apologies...

Actions #1

Updated by JosJuice 15 days ago

  • Issue type changed from Bug to Feature request

This would be nice to have. The problem is designing a system to sync the controller switch so it happens at the same time on everyone's computers.

The option to set an issue to a feature request isn't available to regular users, so that's nothing to worry about.

Actions #2

Updated by IngwiePhoenix 15 days ago

That, to me at least, seems like the smallest issue. You could set a UNIX timestamp in a near future with a scheduled command. Most of the emulation is multithreaded anyway, sa far as I know? But I don't know if the controller interface (CI) is separated out or not. Either way, at least in my naive assumptions, setting a scheduled job could be an option. :) Those switches do not happen often anyway, so if they are a little delayed, that's totally acceptable.

Actions #3

Updated by AdmiralCurtiss 15 days ago

The switch has to happen at the exact same emulated time on each instance, otherwise the emulators will desync. We're not talking about real-world time, but rather the clock cycle of the emulated GameCube system.

Actions

Also available in: Atom PDF