Windows Nightly discussion thread


#181

Oh, I wasn’t aware of this. Weird :confused:


#182

[QUOTE=GemaH;47201]I had this issue for months. I figured it out though. Basically, RocketLauncher forces retroarch to save wherever the AKH tells it to.

You have to edit the Retroarch.ahk that Hyperspin/rocketlauncer uses. Once you open it you find this line:

There are 4 instances of this line. Delete them all carefully without deleting anything else (like an extra space for instance). You may also need to set your save paths in the ahk as well, there are some lines above these where you can set it up.

Once you do that, it should save wherever you want.

As for the “configurations-per-core” it’s not supported anymore by RetroArch itself but other frontends like RocketLauncher and Launchbox can still use those configs.[/QUOTE]

Thank you so much for the reply GemaH.

Everything you said makes complete sense.

I’ll give your recommendations a shot probably sometime this weekend.

Thank you again!


#183

[QUOTE=GemaH;47201]I had this issue for months. I figured it out though. Basically, RocketLauncher forces retroarch to save wherever the AKH tells it to.

You have to edit the Retroarch.ahk that Hyperspin/rocketlauncer uses. Once you open it you find this line:

There are 4 instances of this line. Delete them all carefully without deleting anything else (like an extra space for instance). You may also need to set your save paths in the ahk as well, there are some lines above these where you can set it up.

Once you do that, it should save wherever you want.

As for the “configurations-per-core” it’s not supported anymore by RetroArch itself but other frontends like RocketLauncher and Launchbox can still use those configs.[/QUOTE]

Worked like a charm, thank you GemaH, that would have taken me quite some time to find on my own.


#184

Hey no problem, glad it worked for you.

I know what you mean though, it took me some time to figure it out as well, lol.


#185

I have noticed netplay is not working for Genesis/Megadrive games on both PicoDrive and Genesis Plus GX cores as of the 9/26 nightly. Master System games work, just not Genesis/MegaDrive. I had TCPView open on the server and saw the process listener on the port I specified. When I start the client, it pauses briefly and then continues to start the ROM with the message 'Failed to initialize netplay." TCPView on the server shows the listener dies right after this. The debug output shows the same message on both client and server after attempting connection: “RetroArch [ERROR] :: Content SRAM sizes do not correspond.” A few of the games I tried to not have SRAM and the one I tried that did threw the same error. I’m not sure if this is actually related to how netplay operates at all. I haven’t run into this problem with any of the other cores.


#186

Hi, I’m the guy who’s been fixing and/or breaking Netplay, depending on your perspective ;). That’s a known issue that should hopefully be fixed well before 1.3.7.

If you’re curious: Netplay now allows you to connect at any time, not just immediately upon launch, and more generally, allows you to save and load state with them transferring as expected over Netplay. The problem crops up because both Genesis cores report their SRAM size differently based on when you ask: If you ask at frame 0, they report what I assume to be a correct value, but if you ask later, they report size 0. I don’t know if this is intentional, and maybe they have a bug that they only discover the SRAM size after frame 0, but one way or another it confuses Netplay, because it’s part of how the peers assure they’ve loaded the same game. It’s now known, so either Netplay will be fixed to cope with cores that report in that way, or the cores will be fixed to report consistently.


#187

[QUOTE=Yahweasel;47972]Hi, I’m the guy who’s been fixing and/or breaking Netplay, depending on your perspective ;). That’s a known issue that should hopefully be fixed well before 1.3.7.

If you’re curious: Netplay now allows you to connect at any time, not just immediately upon launch, and more generally, allows you to save and load state with them transferring as expected over Netplay. The problem crops up because both Genesis cores report their SRAM size differently based on when you ask: If you ask at frame 0, they report what I assume to be a correct value, but if you ask later, they report size 0. I don’t know if this is intentional, and maybe they have a bug that they only discover the SRAM size after frame 0, but one way or another it confuses Netplay, because it’s part of how the peers assure they’ve loaded the same game. It’s now known, so either Netplay will be fixed to cope with cores that report in that way, or the cores will be fixed to report consistently.[/QUOTE]

Thanks for explaining all of that. I’m happy to hear you’re working on this and netplay in general. Thanks for your hard work.


#188

Retroarch 1.3.6 stable and nightly from 2016.10.09, does not work on windows XP S3, it just crashes with “The procedure entry point _itoa_s could not be located in the dynamic link library msvcrt.dll”. Patcher from this topic fixed the issue but would be nice if this made into stable at some point.

For some reason since 1.3.3 I think, threaded video does not work for me. I can enable it midgame and it might have some effect but the moment I close retroarch and start again it crashes instantly and I have to change threaded video = “false” before I can use RA again.


#189

The latest nightly release (2016-10-23) for Windows appears to be missing Retroarch.exe, Retroarch.cfg, as well as the Config, Core, and System folders. My understanding is that it would only be missing the cores.


#190

Ah, yeah, looks like the 10/23 build package was broken. 10/24 is fine again.


#191

Should we be able to display unicode characters in the current build? Saw that on twitter and some commits but my Japanese files are garbled still in the file list.


#192

Nightlies starting from 22-10-16 are crashing for me when I want o lunch a game with mednafex psx. 20-10-16 working fine. Can’t provide any info as no command line is displayed with debug mode.


#193

Is anyone else having input detection problems with the latest nightlies?

I have tried 10/25 - 10/30, none seem to detect my dinput or xinput controller, nothing comes up under the device index column in input settings…


#194

[QUOTE=Nadonate;49999]Is anyone else having input detection problems with the latest nightlies?

I have tried 10/25 - 10/30, none seem to detect my dinput or xinput controller, nothing comes up under the device index column in input settings…[/QUOTE]

“Z & X” keyboard input changed to “ESC” & “ENTER” ?


#195

Yep, big changes in menu input are happening ATM


#196

Nice!

1.37 soon?


#197

[I][B]With the ENTER key will not let me download the CORE? Why?

Thank you![/B][/I]


#198

the november issues of nightly seems to bug on me-keeps giving me Not Responding on its title bar and a grey overlay on RA screen although i can still run through the menu using my xbox 360 controller. i have since reverted to earlier releases and dont have this issue. im running RA on window mode switch app time to time.


#199

That’s fixed already


#200

Downloaded the latest nightly and I cannot find the search rom button, I think it used to be the “s” key but it is not working. Tried pressing all the buttons of my keyboard and nothing. What am I doing wrong? I have 500+ roms and I need it, otherwise I have to scroll down rom by rom.