Windows Nightly discussion thread


#161

[QUOTE=COMBO;39693]Right so i got GBA core working (VBA-M) it was crashing for me because i was trying to run it from archive .zip rather then .gba

Now for Reicast, I tried the solution in core options by switching on “boot from bios” unfortunately now, When i try running a .cdi image of any game… RA crashes to the desktop.

I tried updating the reicast core but still getting crashes now.

How do i unsave this core configuration as i can’t get into quick menu using F1 as the ROM crashes instantly before i can reach this menu… Unless i delete the core from the folder? Anyways… That’s all for now.[/QUOTE] Never had crashing issues with VBA-M, VBA Next or mGBA using zipped ROMs. Not sure what’s causing that for you.

You can open retroarch-core-options.cfg in your RetroArch folder in a text editor and change reicast_boot_to_bios = “enabled” to disabled to revert the config change. Another thing that might help with the memory card problem is deleting the vmu_ files from System/dc (the dc folder should be where you store your Dreamcast games if you don’t have a System folder set in directory settings). The Reicast core is very early in development, so it has lots of issues.


#162

[QUOTE=Awakened;39695]Never had crashing issues with VBA-M, VBA Next or mGBA using zipped ROMs. Not sure what’s causing that for you.

You can open retroarch-core-options.cfg in your RetroArch folder in a text editor and change reicast_boot_to_bios = “enabled” to disabled to revert the config change. Another thing that might help with the memory card problem is deleting the vmu_ files from System/dc (the dc folder should be where you store your Dreamcast games if you don’t have a System folder set in directory settings). The Reicast core is very early in development, so it has lots of issues.[/QUOTE]

I’ll try disabling core config for reicast later this week, and delete the vmu files… Think that DC folder is in the system directory.

As for .zip crashing for GBA… I would like to know the cause, maybe that’s why i can never get MAME ROMs running as it crashes RA instantly.

Maybe opening the ROM contents from the zip then running one file inside may help getting it running… But that’s tedious as there’s so many files within a .zipped MAME ROM.


#163

I think mednafen PSX core are broken somehow. I can’t run any of my PAL Psx games…black screen, only audio is working. USA ntsc and JAP ntsc are working well. MD5 sum for pal bios is ok, also SHA-1. Reverting back core (i kept secure XD) cause PAL games working again.


#164

Does anyone know how to remove a core association to a game in your list of scanned games?


#165

settings > playlists


#166

Open your playlist in a text editor, replace the line pointing to the core with DETECT. Put that playlist in read-only if you don’t want a core association to be written there again.


#167

Thanks alot guys, its working fine now. Much appricated!


#168

The latest Nightly builds have an issue with changing the config options for “savefile_directory =” and “savestate_directory =” to default. I have them set to a certain folder, but with the nightly builds this change doesn’t stay. But everything works fine with the stable build. The bug is probably effecting other custom directories, but I haven’t checked. I had this same issue awhile back with a nightly build and it was fixed the next day, but the bug seems to be back.


#169

I can’t reproduce this I just tried with the latest trunk and it’s fine by all means. I actually compared my config before running and after and it’s 100% the same


#170

Last two Nightly versions crash when i load anything vulkan related.


#171

Same here.


#172

Yes, latest Nightly crashes when trying to run ParaLLEl.


#173

Actually no, it was due to a bad configuration option (Hard GPU Sync"), but now Vulkan works here (on software cores).


#174

Hard GPU sync did always work for me with vulkan before. It’s an important option if you want reduced input lag. Having it ON is not a “bad configuration”.

Edit: Still crashes for me. The only way to not crash is if i have vulkan as default. If my default is “gl” and i use an override for ParaLLEl to use “vulkan” it crashes.

Edit 2: One solution is to keep Vulkan as default and make overrides for ALL other cores to use GL. It’s not the most optimal solution but it works to a few systems i tried.


#175

I’m using a cheaper Toshiba satellite laptop with Windows 10 and as soon as I video threaded to true it segfaults. It’s done this for a while now and I’m not sure if it’s specific to my hardware configuration or if others have had the same issue. I’ll have to check older versions and maybe git bisect to see if it can narrow down when it started as its not been broken in the past. Still persists in nightly as of Sept 12 2016


#176

I am having an issue after updating RetroArch to the latest nightly release.

I have all of my cores configured to have the following directories setup for save files and save states:

C:\Users\Kenny\Dropbox%SYSTEMNAME%

Where %SYSTEMNAME% could be “Super Nintendo Entertainment System” or “Nintendo Entertainment System” etc.

After updating to the latest nightly, they all seem to have changed to the contect directory.

In the .cfg file for whichever core, it shows “default” as both folders.

If I manually change it back to my desired folders, it works as long as I keep RetroArch open, but if I close RetroArch, it seems to default back to the contect directory upon opening.

Sorry if this is the wrong spot to post this, if so, please direct me to the correct location to post!


#177

[QUOTE=BennyKurns;47146]I am having an issue after updating RetroArch to the latest nightly release.

I have all of my cores configured to have the following directories setup for save files and save states:

C:\Users\Kenny\Dropbox%SYSTEMNAME%

Where %SYSTEMNAME% could be “Super Nintendo Entertainment System” or “Nintendo Entertainment System” etc.

After updating to the latest nightly, they all seem to have changed to the contect directory.

In the .cfg file for whichever core, it shows “default” as both folders.

If I manually change it back to my desired folders, it works as long as I keep RetroArch open, but if I close RetroArch, it seems to default back to the contect directory upon opening.

Sorry if this is the wrong spot to post this, if so, please direct me to the correct location to post![/QUOTE]

Are you sure this is the latest build? How are you loading the core configs? configurations-per-core was removed a few weeks ago


#178

[QUOTE=Radius;47147]Are you sure this is the latest build? How are you loading the core configs? configurations-per-core was removed a few weeks ago[/QUOTE]

Thanks for the reply Radius.

I am sure I am using the latest builds, and the latest cores.

I was using configurations-per-core prior to this update.

I use HyperSpin/RocketLauncher as a frontend, not sure if that has any effect on the configuration file, but it does still seem to be using the snes9x config file when loading snes9x.


#179

noob config issue. threaded video doesn’t work on the x86 build if you’re on a x86_64 machine.


#180

[QUOTE=BennyKurns;47190]Thanks for the reply Radius.

I am sure I am using the latest builds, and the latest cores.

I was using configurations-per-core prior to this update.

I use HyperSpin/RocketLauncher as a frontend, not sure if that has any effect on the configuration file, but it does still seem to be using the snes9x config file when loading snes9x.[/QUOTE] 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:

“”" -s “”" . srmPath.FilePath . “” . romName . “.srm”" -S “”" . saveStatePath.FilePath . “” . romName . “.state”""

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.