Posts made by thanosazlin

@zing ok i read the manual before my post hence there was no mention of using a SCART to RCA cable like such.. thx

https://www.walmart.com/ip/1-5m-Scart-to-RCA-Triple-3-x-Phono-Cable-Composite-Audio-Video-Lead/456268071?wmlspartner=wlpa&selectedSellerId=101093150&&adid=22222222227000000000&wl0=&wl1=g&wl2=c&wl3=42423897272&wl4=pla-51320962143&wl5=9010764&wl6=&wl7=&wl8=&wl9=pla&wl10=468976347&wl11=online&wl12=456268071&veh=sem&gclid=Cj0KCQjw_viWBhD8ARIsAH1mCd5uZK0ZaBFXyWsNIzAlSgbncpnSEKoHD0RIeauRhwSVowdCufgq0mcaAqh5EALw_wcB&gclsrc=aw.ds

hi, i'm in the USA and was looking at possibly getting the RGB Dual but use a SCART to RCA cable as we don't have old CRT tubes here in USA that have SCART. would that work ? going from SCART on the Recalbox setup to RCA (Yellow/Red/White) ?

I'm creating a backup image of my 128gb micro SD card for Recalbox. I'm using Win32 Disk Imager software, however i don't know which drive letter to select in windows does it matter ? I mean there is a "Recalbox" and E: "Share" and F: "SDXC" on my SD card , so if i select any one of the 3 drivers to create my backup image will it just image the whole SD card ? meaning that if i go to do a restore then all the 3 partitions will be included ? thanks.

8bitdo NES30 controller using USB cable , NOT BT, with Recalbox fresh load 7.0.1 on pi 4 , was working fine the other day, now suddenly when i plug it in after turning on pi and recalbox it says detected it as new controller wth, so i fire up a BT gamesir controller enter configure controllers it sees the Gamesir i just powered on and the NES30 , but i'm not able to configure the NES 30.. i can unplug the NES30 , it powers off, then power on the NES30 and it connects BT and works fine ??!! what gives here, i mean it was working fine, i tried a different USB cable, same thing on my pi 3 with recalbox 7.0.1 used to work now does not just out of the blue.

i'm scratching my head. oh and i have a 2nd 8bitdo NES30 it does the same thing. I also have 2 SNES30's from 8bitdo they work fine still plugged in USB.. some games i avoid BT because let's be honest there is some times slight tiny delays in BT especially when i'm sitting 12 ft away in a larger theater room . so i have extra long USB cables, and YES i tried short 6 ft normal USB cable as well still same thing. i even left the controllers plugged in on boot up as well.. i mean these were working perfectly fine the other day. there is no way both of them had their USB ports go bad on the controllers at exactly the same time

anyone else have issue ? or have an old 8bitdo NES30 laying around you can connect to 7.0.1 recalbox and test for a week and let me know. again this is not making logical sense to me.

i ran Skraper https://www.skraper.net/ the other day , and i was missing galaga, robocop, and mk3.. so i've been trying to run it again and it's not working at all just loads for forever.. then i cleaned out my mame roms folder on recablox 7.0.1 just now, put in the just galaga , robocop, and mk3 roms and tried to scrape from within Recalbox and it's not finding anything either ??

ok so my Gamesir's work perfectly fine connected usb. So i guess i have to get 25ft usb cables LOL , yeah i have a huge theater room that i sit 16ft from the 65 in screen, so i'll have a little bit of slack in the cables.. If anyone from Recalbox team is reading this, please take this post in combo with the gitlab issue

https://gitlab.com/recalbox/recalbox/-/issues/1378

it's some BT issue and only with the Gamesirs, my old Gamesir 3GS and the new T4 pro.. same thing that happens with Mame in the gitlab issue happens with N64, if using the Gamesirs BT , once i start a game with N64 or MAME the controller still looks connected BT but doens't work i have to turn it off/on , on Mame that works, but on N64 it causes only 1 stick control on the Gamesir and my select and start buttons to work..

so while not ideal i would prefer to be able use BT instead of having a cable dragged across my floor

so my 8bitdo nes30 and snes30 work perfect i mean well limited buttons but yeah , what sucks is my gamesir's worked fine waaay back with recalbox 18.07.14 or something years ago.. i just bought this one off amazon

https://www.8bitdo.com/sn30-pro-plus/

seems these 8bitdo's work best with recalbox , sucks i just bought to brand new gamesir t4's and can't get them to work properly with mame and n64 like i mentioned in my issue i reported in gitlab.

thanks i tried that.. so i'm pretty technical and i'm following everyone's steps i've tried them all..

here is my config from sdl2-jstest

joystick name : 'Gamesir-T4pro_8FA5'
joystick number 0
A = 0 = 304
B = 1 = 305
X = 3 = 307
Y = 4 = 308
select = 10 = 314
start = 11 = 315
L1 = 6 =310
R1 = 7 =311
L2 = 8 = 312
R2 = 9 = 313
stick1 pressdown = 13 = 317
stick2 pressdown = 14 = 318
hat0 1 Up
hat0 4 down
hat0 8 left
hat0 2 right
axis 1 U-/D+
axis 0 L-/R+
axis 3 U-/D+
axis 2 L-/R+

Then here is what i setup in mupen64plus.cfg, i tried mode 0,1, and 2 no differences
[Input-SDL-Control1]

Mupen64Plus SDL Input Plugin config parameter version number. Please don't change this version number.
version = 2
Controller configuration mode: 0=Fully Manual, 1=Auto with named SDL Device, 2=Fully automatic
mode = 1
Specifies which joystick is bound to this controller: -1=No joystick, 0 or more= SDL Joystick number
device = 0
SDL joystick name (or Keyboard)
name = "Gamesir-T4pro_8FA5"
Specifies whether this controller is 'plugged in' to the simulated N64
plugged = True
Specifies which type of expansion pak is in the controller: 1=None, 2=Mem pak, 5=Rumble pak
plugin = "2"
If True, then mouse buttons may be used with this controller
mouse = False
Scaling factor for mouse movements. For X, Y axes.
MouseSensitivity = "2.00,2.00"
The minimum absolute value of the SDL analog joystick axis to move the N64 controller axis value from 0. For X, Y axes.
AnalogDeadzone = "4096,4096"
An absolute value of the SDL joystick axis >= AnalogPeak will saturate the N64 controller axis value (at 80). For X, Y axes. For each axis, this must be greater than the corresponding AnalogDeadzone value
AnalogPeak = "32768,32768"
Digital button configuration mappings
DPad R = "hat(0 Right)"
DPad L = "hat(0 Left)"
DPad D = "hat(0 Down)
DPad U = "hat(0 Up)"
Start = "button(11)"
Z Trig = "button(8)"
B Button = "button(1)"
A Button = "button(0)"
C Button R = "axis(2+)"
C Button L = "axis(2-)"
C Button D = "axis(3+)"
C Button U = "axis(3-)"
R Trig = "button(7)"
L Trig = "button(6)"
Mempak switch = ""
Rumblepak switch = ""
Analog axis configuration mappings
X Axis = "axis(0-,0+)"
Y Axis = "axis(1-,1+)"

i had removed the input.xml saw a post about that. i even created an InputAutoCfg.ini tried that in mupen64plus config dir..

InputAutoCfg.ini
[Gamesir-T4pro_8FA5]
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
DPad R = hat(0 Right)
DPad L = hat(0 Left)
DPad D = hat(0 Down)
DPad U = hat(0 Up)
Start = button(11)
Z Trig = button(8)
B Button = button(1)
A Button = button(0)
C Button R = axis(3+)
C Button L = axis(3-)
C Button D = axis(2+)
C Button U = axis(2-)
R Trig = button(7)
L Trig = button(8)
Mempak switch =
Rumblepak switch =
X Axis = axis(0-,0+)
Y Axis = axis(1-,1+)

that didn't work.. so i'm at a loss here.. another weird thing is when I add the line for "n64.configfile=dummy" when i start N64 emulator it says something like "error unable to configure dummy file".. and none of my buttons work..

so i have to remove that line, but when i tried all the different combos of things, one thing remains solid, i can ONLY use start button and the left most joystick on my Gamesir, then also select key i can hit select/start to exit emulator.. another thing when i start the emulator for n64 (and this haps on mame too) i can't use my Gamesir Bt contoller it works fine in ES right before game starts then i have to power it off and back on to get it work , all other emulators nes, snes, megadrive etc.. all work fine.. i opened an issue for this as well.. i don't know if that has anything to with this or not..

https://gitlab.com/recalbox/recalbox/-/issues/1378

i'm just exhausted .

thanks for the suggestion.. so i added "n64.configfile=dummy" to my recalbox.conf file at the end of the file. rebooted. when i started N64 emulator from ES mupen64plus, tried to start Super Mario 64, pop up said something like "could not configure dummy something" sorry i didn't write it down, BUT nothing worked i even powered controller off/on, i had to cold reboot the pi i could not even exit the game..

so i remove the "n64.configfile=dummy" rebooted again so it was good to go and back to way it was.. then if i start Super Mario 64 i am able to use the left joystick on the Gamesir and start button only, that has been the case most times.. I don't know why the other buttons aren't working here is my current mupen64plus.cfg for controller inputs

[Input-SDL-Control1]

Mupen64Plus SDL Input Plugin config parameter version number. Please don't change this version number.
version = 2
Controller configuration mode: 0=Fully Manual, 1=Auto with named SDL Device, 2=Fully automatic
mode = 0
Specifies which joystick is bound to this controller: -1=No joystick, 0 or more= SDL Joystick number
device = 0
SDL joystick name (or Keyboard)
name = "PLAYSTATION(R)3 Controller (47:0D:91:86:A9:4A)"
Specifies whether this controller is 'plugged in' to the simulated N64
plugged = True
Specifies which type of expansion pak is in the controller: 1=None, 2=Mem pak, 5=Rumble pak
plugin = "2"
If True, then mouse buttons may be used with this controller
mouse = False
Scaling factor for mouse movements. For X, Y axes.
MouseSensitivity = "2.00,2.00"
The minimum absolute value of the SDL analog joystick axis to move the N64 controller axis value from 0. For X, Y axes.
AnalogDeadzone = "4096,4096"
An absolute value of the SDL joystick axis >= AnalogPeak will saturate the N64 controller axis value (at 80). For X, Y axes. For each axis, this must be greater than the corresponding AnalogDeadzone value
AnalogPeak = "32768,32768"
Digital button configuration mappings
DPad R = "hat(0 Right)"
DPad L = "hat(0 Left)"
DPad D = "hat(0 Down)
DPad U = "hat(0 Up)"
Start = "button(10)"
Z Trig = "button(9)"
B Button = "button(1)"
A Button = "button(0)"
C Button R = "axis(2+)"
C Button L = "axis(2-)"
C Button D = "axis(3+)"
C Button U = "axis(3-)"
R Trig = "button(7)"
L Trig = "button(6)"
Mempak switch = ""
Rumblepak switch = ""
Analog axis configuration mappings
X Axis = "axis(0-,0+)"
Y Axis = "axis(1-,1+)"

THEN here is what i came up with at linux console running "sdl-jstest" to test my buttons. hopefully it's not too confusing , but basically i list what my buttons are on my Gamesir, then list what they showed up as in "sdl-jstest" like my A button on Gamesir controller is 0 then i list in equal signs and n64 what it corresponds to or least i think it does to n64 in my mupen64plus.cfg file ...

Gamesir T4 pro to N64 buttons

A=0 ====n64 A
B=1 ====n64 B
X=3
Y=4
select=10
start=11 =====n64 Start
L1=6 =====n64 L Trig
R1=7 ====n64 R Trig
L2=8
R2=9 ====n64 Z
D-up=1 ====n64 U
D-down=4 ====n64 D
D-left=8 ======n64 L
D-right=2 ======n64 R
axis 0 = stick1 right =====n64 C button R
axis -0 = stick1 left =====n64 C button L
axis 1 = stick1 down =====n64 C button D
axix -1 = stick1 up =====n64 C button U

axis 2 = stick2 right
axis -2 = stick2 left
axis 3 = stick2 down
axix -3 = stick2 up

yeah i gotta say this N64 config stuff is a beast compared to all the others, i thought mame was tough and i mastered it but N64 is whoop my a**e. Also my D-up, down, left ,right in "sdl-jstest" said they were buttons 1,4,8, and 2 i tried that but then left it was you see with hat0.. but still my dang A and B buttons are not even working

I have a Gamesir T4 Pro BT controller that works fine in ES and all other emulators. this is recalbox 7.0.1

https://www.amazon.com/gp/product/B07HG51ZYK/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1

seems i can only get start button to work it "seems" on most games, like 1080 Snowboard or WCW vs nWo: World Tour , on Zelda Ocorina of Time one other button other than start works, and i can move link around with joystick.. in the other 2 games 1080 and WCSvsNWO, i get stuck at the beginning of the game after pressing start waiting on prompts and i press every d**n button on the control pad and nothing works.. except start and select because i can start the game at least, then eventually when nothing else works button work i can select/start to exit the emulator ...

so here is my input.xml from the n64 emulator

<inputList>
<input name="AnalogDeadzone" value="4096,4096" />
<input name="AnalogPeak" value="32768,32768" />
<input name="a" value="C Button R" />
<input name="b" value="A Button" />
<input name="x" value="C Button U" />
<input name="y" value="B Button" />
<input name="start" value="Start" />
<input name="select" value="" />
<input name="l1" value="L Trig" />
<input name="r1" value="R Trig" />
<input name="l2" value="Z Trig" />
<input name="r2" value="" />
<input name="l3" value="Mempak switch" />
<input name="r3" value="Rumblepak switch" />
<input name="up" value="DPad U" />
<input name="down" value="DPad D" />
<input name="right" value="DPad R" />
<input name="left" value="DPad L" />
<input name="joystick1up" value="Y Axis" />
<input name="joystick1down" value="Y Axis" />
<input name="joystick1left" value="X Axis" />
<input name="joystick1right" value="X Axis" />
<input name="joystick2up" value="C Button U" />
<input name="joystick2down" value="C Button D" />
<input name="joystick2left" value="C Button L" />
<input name="joystick2right" value="C Button R" />
</inputList>

Then here is my buttons from ES config for the Gamesir

I am just looking for help on what i might be doing wrong or misinterpreting for N64 controller mappings, again LOL even when i'm waiting on prompt in one of the games i mentioned i press every d**n button and nothing happens , any help appreciated.

i recently got a pi 4, loaded Recalbox 7.0.1 on it.. for N64 rom 1080 Snowboarding, it runs good on pi3 Recalbox 7.0.1 , now i'm just taking the default emulators on a vanilla Recalbox 7.0.1 bare in mind.. here is what comes with 7.0.1 on pi3

runs fine on Libetro Mupen64plus and Mupen64plus_next on pi 3.

then, copy the 1080 snowboarding rom over to my pi 4 and i only get 3 choices for n64 emulators

if i use the Mupen64plus or Mupen64plus_next i get the distorted video on screen you see below... if i use Libertro_parallel_n64 it runs almost like normal, except the sound is so awful like a shorted out stero speaker, so it's practically unplayable as well.. I can however start Zelda ocarina of time and it's fine audio and video , i suspect there might be other roms that have the same issue but these are the 2 for my testing of pi 4 recalbox.. anyone else having this issue ??

FIXED!!! thanks to toniosj, see the gitlab link at the beginning of this post.. but essentially it's due to my 4K tv and he had me change some setting in config.txt, so visit the gitlab issue for specifics

https://gitlab.com/recalbox/recalbox/-/issues/1384#

Edit your "config.txt" file on /boot folder:
-If you're using PuTTy use "mount -o remount,rw /boot" commmand.
-If you're using WinSCP open console (Ctrl + T), enter command "mount -o remount,rw /boot" and click Execute.
From this file search for hdmi_group and hdmi_mode and set both as following :
hdmi_group=1
hdmi_mode=4
Don't forget to remove '#' char on those lines if present.

OK so see the gitlab issue , they suggested i test on a 1080p TV as i was using a 4k TV. it works perfect on the 1080 p tv.. so i have Shaders set to None and Shaders Set is set to None... in game setting in ES (or RB menu ) ..

i set shader to all of the ZFAST there was more than one of those settings, none helped they all had the issue. there was a bunch more settings in Shaders Set but i didn't bother testing any other one. there is like 150+ i think :(.. besides like i mentioned hopping over to a 1080p tv to test works fine. shouldn't recalbox 7.x work on 4k tv's ? i have a visio 4k HDR 65 in.

is anyone else having this issue ?? for me it happens on nes rom , mame rom, doesn't matter.. i opened this issue on gitlab and attached video

https://gitlab.com/recalbox/recalbox/-/issues/1384

so here is the weird part it's not my pi 4 and it's not my roms.. how? well the same roms , see the issue for details, run fine on recalbox 7.0.1 on my pi3, and i loaded retropie latest on my pi4 and ran same roms perfectly fine, so apples to apples logically it's not my pi4 i was starting to think it was.. this has to be a bug in recalbox 7.0.1

so i found out my roms are not an issue it's Recalbox 7.0.1 on pi4, those roms run perfect on my pi3 recalbox 7.0.1 .. Also i took the liberty as i said to put Retropie latest on my pi4 and those same roms donkey kong, mk, they run perfectly fine..

so this sound issue is only on pi4 recalbox 7.0.1, and it happens on other systems as well even NES, i have the same issue where the sound just hisses ,skips , pops , crackles, i took a video of it and place it here on my google drive.

https://drive.google.com/file/d/1YExb_NTXyeLAHIAKwETkbH8-cFa0NUqd/view?usp=sharing

to heck with all this :). my pi 3 with 18.07.13 runs the GameSir BTs fine and my Arcade roms, BUT they won't recognize my 8bitdo N30s and SN30s . But my pi 4 with 7.0.1 will see the 8bitdo N30s and SN30s, but it won't work well as i explained with my GameSir BTs and the Arcade roms.. so... I'll just have the 2 and use one for arcade and 1 for consoles , this is craziness that 1 vs the other has issues like i mentioned.. oh well.

so i got complete set of mame2003 0.78 roms and mame2003 plus

MAME2003_Reference_Set_MAME0.78_ROMs_CHDs_Samples
MAME_2003-Plus_Reference_Set_2018

i took dkong, mk, from each and i tried with their respective emulator i used mame2003 plus with the roms from the Plus 2018 set and used mame2003 emulator for the roms from the mame2003 0.78 set .. still the same audio is bad sounds like extremely bad speaker connection on either rom.. and both run very very slowwwwww, unplayable. again on my pi3 with 18.07.13 from years ago i know i have a mame2003 rom set 0.78, well again it runs flawless.

anything else i can try ? i'm about read to return this pi4 to amazon and order a pi 3 and just settle for using it

sure np i will try that and report back.

i just got a pi 4 and loaded 7.0.1 , testing all my roms from set 0.78.. 2 example issues..

Donkey Kong - works fine in my pi 3 recalbox 18.07.13 using libretro-mame2003. Try to run it on my pi4 7.0.1 using mame2003plus says missing sample files. if i try to run using mame2003 on 7.0.1 same thing no samples found.. i check /share/bios/mame2003/samples on my pi 3 18.07.13 and i'm not even having to use sample files, unless samples are store somewhere else ?? so trying to understand why apples to apples this rom won't work on 7.0.1 using mame2003 the same as it does on my pi 3 18.07.13 ??

pi3 recalbox 18.07.13

pi4 recalbox 7.0.1

Mortal Kombat - running as mame2003plus or mame2003 on pi 4 recalbox 7.0.1 the audio is not working it's there but ,well hard to describe, it's like cutting in out and you can't really hear it, also the game runs very sllllooowwww on my pi 4 with 7.0.1 . IF i fire up my pi 3 with recalbox 18.07.13 works perfectly..

i'm beginning to wonder why i even got a pi 4 now and recalbox 7.0.1 LOL. can anyone help here this is not making logical sense to me ?? thx

so i'm really b*mmed , i hadn't used my pi and console games in over a year.. i'm sening my pi 3 to my best bud, i was going to load latest Recalbox on it , but had all these issues, so i'm sending it to him with 18.07.13 and the 2 GameSir BT controllers as a birthday gift. I had bought myself a new Pi 4 with 2 newer model GameSirs and d**n it i just can't get it to work with Recalbox 7.x , least with these GameSirs.. so i'm going to just have to load Retropie on it until someone picks up this issue on Gitlab.. but i won't be able to do any repro for them if they as because the pi 3 is leaving me tomorrow. It's weird that the Pi 4 !!! even has the same issues. Unfortunately i don't have a 18.07.13 image for the Pi 4 since i only have had it for a week, and don't know if 18.07.13 would even work on a Pi 4. man i hope they help me resolve this soon.