This update fixes the following issues present in version 0.9.0.2:
- Palette corruption on various PSP units
- Bug in the sound rendering engine that would cause occasional sound slowdowns
Updates from 0.9.0.1 (just to reiterate):
- Added various game image types missing from the initial release
- New virtual keyboard
- Added monitor type selection (color/grayscale)
- Fixed a serious memory leak, which would manifest itself when opening ZIP files
- Fixed the “tape loading hang” bug
- Added +3 support
- Added Kempston joystick support
- Added “hack cursor” support (keyboard up/down/left/right)
- Lots of code reshuffling
>> Bug in the sound rendering engine that would cause occasional sound slowdowns
sounds like the problem PSPectrum had, where bringing up the OSK fixed it!
nice to hear this isnt an issue now
yet to test this, but rest assured i will!
Loading a zip file which contains anything else with a .SCL file or a .TAP file cause my PSP (slim) to crash
The Gluk menu is a very nice feature though
Which formats specifically are giving you trouble?
I know extended DSK images don’t load correctly, but if other formats are giving you trouble, send me an email.
Thanks
P.S. Gluk menu?
I have two problems with Fuse PSP version 0.9.0.25
If I have configured two or more PSP buttons to be the same spectrum button only last in the config list will works. For example, I want d-pad and analog stick be the same – d-pad goes after analog in controls config tab’s list, so only it will works – d-pad will do nothing. May be it’s not so critical bug, but it takes time to assign none action to “unlock” other buttons.
Next issue is that if I make, for example, CAPS button sticky pressed using O, then exit virtual keyboard, then activate it again with L – I will see CAPS like still pressed, but in fact I must release it with triangle and press again to make works.
… d-pad goes after analog in controls config tab’s list, so only it will works – d-pad will do nothing …
sorry – I mean analog will do nothing cause it goes before d-pad
I’m aware of these two issues, though it’s good that you mention them, as I considered them to be low-priority.
These will most likely be fixed in the next version.