You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m curious if it’s possible to integrate an internal VMU into this project and share it with BlueRetro. BlueRetro’s VMU management is currently quite buggy, and it lacks support for the VMU screen.
Key Questions:
Is there a way for both projects (this one and BlueRetro) to work together on the same Dreamcast port?
Could the MaplePad project potentially include a port passthrough feature? For example, the input would be a Dreamcast port, and the output would also be a Dreamcast port. This would allow the pad to be managed while keeping the VMU functionality on the MaplePad side.
Testing Observations:
I tested an internal BlueRetro setup with a Bluetooth pad on "Port 1." When I connected a real Dreamcast pad with a VMU, the VMU was disabled.
I also tried removing the VMU from BlueRetro and disconnecting the alternative pad, but the real VMU remained disabled.
I suspect this issue occurs because BlueRetro and MaplePad are trying to use the same port simultaneously.
Proposed Solution:
If MaplePad could support a passthrough feature, it might allow the pad to be managed while the VMU functionality is handled separately. This could potentially resolve the conflict and improve VMU management.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I’m curious if it’s possible to integrate an internal VMU into this project and share it with BlueRetro. BlueRetro’s VMU management is currently quite buggy, and it lacks support for the VMU screen.
Key Questions:
Is there a way for both projects (this one and BlueRetro) to work together on the same Dreamcast port?
Could the MaplePad project potentially include a port passthrough feature? For example, the input would be a Dreamcast port, and the output would also be a Dreamcast port. This would allow the pad to be managed while keeping the VMU functionality on the MaplePad side.
Testing Observations:
I tested an internal BlueRetro setup with a Bluetooth pad on "Port 1." When I connected a real Dreamcast pad with a VMU, the VMU was disabled.
I also tried removing the VMU from BlueRetro and disconnecting the alternative pad, but the real VMU remained disabled.
I suspect this issue occurs because BlueRetro and MaplePad are trying to use the same port simultaneously.
Proposed Solution:
If MaplePad could support a passthrough feature, it might allow the pad to be managed while the VMU functionality is handled separately. This could potentially resolve the conflict and improve VMU management.
Looking forward to your thoughts!
Beta Was this translation helpful? Give feedback.
All reactions