It probably was finished. The chip as I recall reading is just a handy sort of math chip for dealing with sprites quicker. The game uses alot of sprites and I guess to avoid slowdowns the game takes advantage of this chip to make everything much faster. I don't have anything more specific than that on it. It's involved in helping take some CPU load off by processing sprite data. Probably related to building the actual sprite table for the PPU to display.
i would like to know if he's ever going to finish FX implementation , but i understand his decission His family comes first (y)
OBC1 support (yeah, did it anyway ). Metal Combat: Falcon’s Revenge now works. Menu: Start button now brings up the 10 most recently played games instead of only one Menu: File browser now ignores files with the “hidden” and “system” attributes Partial-size BS-X games should now load correctly Fixed a PSRAM mapping bug in BS-X support that caused sprite corruption or worse on some games (notably Treasure Conflix) Map SRAM to the whole bank instead of just the lower half on LoROM games <=16Mbits. Fixes saving in some games, at least Ys III - Wanderers from Ys. Next up will be cheat support and possibly advanced SuperCIC utilization.
I'm happy to see an update, it's been a while. But how ironic that yesterday I got my new lamp for my projector and set up the SFC in my "so called theater room" and plan to get rid of the CRT for the time being "no more light gun support for a while". Playing F-Zero on a 70" screen is pretty awesome though.
I heard the new firmware introduces sprite glitches that should be fixed in the next one, so I resist getting it, despite the one-game compatibility improvement.
Well Chrono trigger for one, glitches like hell on this new firmware. Same goes for Final fantasy 3, it seems like it happens when big sprites hit the screen ... i don't know for certain. but chrono trigger is the best one to try this out...
You mean that intro part with the giant frog? That's maybe kind of an analog issue, happens at random but seems to be consistent throughout a power cycle. I've had it appear very strongly, and then not at all, with the same sd2snes, in the same console, after turning it off and on again. It even happens when using a simple EEPROM cartridge, although seemingly a bit less pronounced. Long story short, I don't think it can be fixed, and it's not related to a specific firmware release.
Well it happens during the game, and it did happen a lot of times during my playthrough on firmware 1,6 and as I do recall i'm not the only person with this problem, but i was to lazy to go back to firmware 1,5 So ... i think i needed to reset my snes about 50 times during my playthrough, no kidding
Does it actually crash? If so it would be helpful if someone could take pictures or even better, videos of it because I have never had that happen to me.
i had alot of crash too with crono trigger with this boss i had changed my sdcard with other sdcard with only the cronotrigger rom and... no more crash. strange :|
I'll try to film it during my playthrough ... i guess that should be over a week or 2 will keep you informed
Just got my SD2SNES in the mail yesterday and I'm loving it! SNES + XRGB Mini + SD2SNES + IGR is amazing! I've been on an SNES "kick" these past few weeks/months. Slowly finding and unboxing my childhood system; cleaning it and all of the carts... Researching the SNES, RGB video signals, digital audio, board revisions, mods I could potentially do... I ended up buying new RGB cables, an XRGB mini, SD2SNES, flash card, 6 foot controller extension cables, and I'm about to dive into the digital audio side of things (I just like the idea of hooking the SNES up to my own DAC/AMP).. I also have a Super Famicom and a Game Doctor SF7, but I'm still in the process of cleaning that setup. ikari's menu looks a hell of a lot cooler though! Firmware v1.7 preview 1 was a little sketchy but Firmware v1.7 preview 2 seems to have fixed most all of my issues. The Lion King dump I made doesn't want to play nice, so I might have to clean the cart/sf7 and try dumping it again... oh well, task for another day.
