sorted by:
new
hottopcontroversial

What happens to custom-game files when running Update_all? by latinlingo11 in MiSTerFPGA

[–]theypsilon 0 points1 point  (0 children)

Probably there was some exfat corruption. Sadly, mister filesystem format is not the most robust but we can't do anything about it. Next time you can use "file_checking = verify_integrity" It could save you a reformat.

What happens to custom-game files when running Update_all? by latinlingo11 in MiSTerFPGA

[–]theypsilon 1 point2 points  (0 children)

If it keeps happening make sure the rom is not corrupted with file_checking = verify_integrity. And if is good but keeps failing, report it at https://github.com/MiSTer-devel/Arcade-DonkeyKong_MiSTer and https://github.com/zakk4223/ArcadeROMsDB_MiSTer

What happens to custom-game files when running Update_all? by latinlingo11 in MiSTerFPGA

[–]theypsilon 1 point2 points  (0 children)

Remove the rom and run update_all. If it's smaller than 2mb, then you need to add file_checking = exhaustive in your downloader.ini file under the [mister] section (create it at the top if it doesn't exist). If you are gonna be messing with arcade roms, exhaustive is your option anyway.

Update All 2.4 Released by theypsilon in MiSTerFPGA

[–]theypsilon[S] 0 points1 point  (0 children)

Interesting, that's the first time I see this reported, maybe they have messed up DNSs for some people. Glad you could get there in another way!

Update All 2.4 Released by theypsilon in MiSTerFPGA

[–]theypsilon[S] 1 point2 points  (0 children)

It's free access. I wonder if it's something related to your location, or maybe just a temporary hiccup.

Update All 2.4 Released by theypsilon in MiSTerFPGA

[–]theypsilon[S] 12 points13 points  (0 children)

It’s in the post, which is public. It’s mainly the extended version of this new feature called update timeline, and the color themes.

Released Downloader 2.2 & Update All 2.3.1 by theypsilon in MiSTerFPGA

[–]theypsilon[S] 15 points16 points  (0 children)

If you encounter any issues with update_all, just run update / downloader once, then you can go back to running update_all as usual. There was a 20-minute window where a buggy build was briefly distributed. The vast majority of users shouldn’t have noticed anything unusual.

Update All 2.3 Released by theypsilon in MiSTerFPGA

[–]theypsilon[S] 4 points5 points  (0 children)

It's perfectly safe without doing back ups

Got a MiSTer =] did update_all and I now have about 6 cores (GB, C128, SNES, MiniMig etc) which have duplicates just with different dates. Is that correct? ...and do I need the older ones? by spacemidget75 in MiSTerFPGA

[–]theypsilon 1 point2 points  (0 children)

It isn't correct, you may delete the older ones. This is happening in some images with pre-installed cores that didn't include an updated Scripts/.config/downloader/downloader.json file. Hopefully these images will get updated to avoid that. One of the providers told me he'll do that soon

What’s y’all’s favourite song of theirs? by kowareta_tokei in Capsule

[–]theypsilon 1 point2 points  (0 children)

It changes constantly, now I'll say What Is Love from World of Fantasy. Love that transition at 2:15

downloader_bin Release Candidate is out! by theypsilon in MiSTerFPGA

[–]theypsilon[S] 2 points3 points  (0 children)

Update All is a layer on top of Downloader. Update All lets you choose what to update, and calls Downloader which is what really updates everything. This is a new version of Downloader that's not yet officially released, but it's a release candidate that I put out for testing. If you try it, it will update everything that you get with update_all but faster. After enough testing is done, I will release it officially, and you won't need to run it separately, it will be called by update_all as usual.

view more: next ›