This thread is intended to inform the possible removal of some features.
I been part of other projects and always a removal or drastic change to XXX feature, causes alot of fuss among the community.
I would like to get some feedback before removing any feature.

1 : Compatibility info/codes
*No longer maintained and compatibility info is really outdated
*Developer that implemented it is no longer here and thus support is no longer available
*Codebase is really messy (everything is hardcoded, adds alot of weight to binary, code is hard to read and thus can't be maintained easily)
*Uses complex codes to add compatibility info to ROMS (which need to be update it for each ROM everything a new option is added/removed!)

2 : Low Battery Warning
*Unnecessary feature (Not really needed anymore, we have battery stats etc when you are in the Pause menu)
*I don't think many if anybody uses this feature

3 : CoverFlow GUI
*No longer maintained and is getting outdated
*Developer that implemented it is no longer here and thus support is no longer available
*Codebase is really messy (everything is hardcoded, adds alot of weight to binary, code is hard to read and thus can't be maintained easily)
*Uses more resources than Classic GUI
*Is starting to lack important features from Classic GUI (proper ROM deletion, full support for translations, tooltips)

Well I think It's great...
1. Low battery warning i think anyone use that
2. CoverFlow style it's cool but I like more the Classic and It's more confortable
3. Compatibility info I think anyone reed it, 'cause they better try, ther own settings....
Finally I agree with this....!

1: I think we should have the compatilbility list revised with simple drop down boxes for each option in DaedalusX64. I'm not as familiar with CSS as I am with PHP and XHTML, but I know it could hide or expand rom information with an easy to use "+" or "-" system. This would allow for faster browsing of the roms in the list anyway. With this improvement to the compatibility list it would also allow for easy exporting for potential integration with DaedalusX64 and I'd be in favor of just restarting the list from scratch because of it (outdated anyway right?). I'd be happy to go over this in futher detail if anyone asks or is willing to help.

Ultimately I think we should keep the compatibility view in some way since it's very noob friendly, which is important. As it currently is in DaedalusX64, the compatibility view is just like a post-it note super glued to a fridge and isn't very practical when trying to apply the information. If anything it needs to get redesigned, but until that happens an omission would be a drastic and an eventually necessary change.


2: I really like having a hard number percentage to view during gameplay. I think, if instead of a warning, it should be an option in the stat display (FPS, rendering, and ect.) in the Global Menu. I'm fine either way, but I enjoy having this option as is in DaedalusX64 since my thumb usually blocks my view of the green LED. It's not necessary yet it's nice, isn't broken at all, and ultimately optional.


3: I've made a habit of just switching to the classic view anyway. I really don't enjoy using cover flow since it also hides most of what I have available to choose from when I share my PSP with friends. If anything I think the slide menu effect would be cool to use vertically with the preview box in classic mode. Even so it's just eye candy and isn't necessary.

1 : Compatibility info/codes useless
2 : low Battery Warning (personnaly I use it ) usless if it cost CPU ressources
3 : CoverFlow GUI useless

1: Compatibility info/codes in my opinion are still a great idea BUT in the correct area of the emulator, for example: at the moment they are found on the Rom selection screen how about having it moved to where it should have been in the first place in the Rom Preferences screen & Advanced Options screens, as the info on there was to change certain aspects of these two screens thus would make lot more sense having it on there, by pressing [] Square, because the amount of times i have had to exit out of a Rom to go back to the main Rom selection screen because i forgot what settings it recommended changing, most annoying.
Also keep compatibility colour on Rom selection screen.
2: Low Battery Warning - I don't use this option myself, as my battery is unable to hold a charge on its own now, needs to be constantly plugged into the mains.
3: I like both classic & cover flow GUI, but as Reamer87 mentioned it only shows a fraction of your available Rom's on the cover flow version, and the most annoying thing on both GUI's is NOT having the option to wrap around when at the end of my Rom's, for example my last Rom is Yoshi's Story (E), if i press down or right, it should jump to the beginning of my Rom's 007 - The World is Not Enough (E), why was this never implemented.....Strange - So get rid of cover flow GUI - Yes i agree.

i need low battery warning cause 10% battery on my slim is like barely a few minutes left of charge xD

Yes, I know a sort of compatibility list feature is needed ,and is in my ToDo, the way I would implement it ,would be similar to PC emulators, that would allow ppl to write their own comments/notes. I could even use a bigger version of our dialogs with small text which should allow up to 80 chars which should be enough to give a good compatible description.

Low battery warning codebase is really small about 40 lines in total counting the menu option (compared to hundreds to thousands lines of code from the other features mentioned), and also is only called once per frame and the pretty much the whole thing is skipped until you reach <10% of you're batter and ultimately is optional, it could stay if many ppl find it useable.

Other ideas I had for this option was to auto savestate, when you reach a critical state about ~1%? and then kick you out off the emulator ASAP since otherwise your PSP would enter in suspend mode which would kill critical parts of the emulator which are allocated in the volatile memory (PSP DLIST, translations/cheats if used) and thus you would get a pretty bad crash.
But yea sucks to bloat the emulator with too many options worst when they don't get to be used at all

@@King Pepper: Intrafont is capable of side-scrolling, it should be doable, I'll take a look and see if I can implement it.

So far most ppl are agreeing in the removal of 1 & 3

how about when low battery warning kicks in it pauses emulation and asks if you wanna make a savestate?

I like the idea, Offtopic: but I would also like an auto-savestate feature that fires at least every minute (even if it pauses the game for a bit). There have been many times while playing a game that I forget to make savestates and I lose a ton of progress because of it. Instead of spacing out and not using savestates I'd voluntarily have them shoved down my throat as a better alternative.

add me to that list. Given how the compat list works in the emulator it would be such a huge annoying beast to change/fix that it's better to scrap it and think of a new one.

On that note, what if the compatibility was a separate txt file, with each rom's compatibility in there. Either pulled up from a set list of variables in the file itself(similar to how it is now but not hard coded inside the emu). Or listed completely in the file and just displayed in the emu.

My reasons for the separate file is so that the community could update and submit new versions of it, and an error of it wouldn't cause any issues like an error made in roms.ini.

Just throwing out ideas.

That's pretty much what I said here, so I agree.

I recall you suggested this feature before, but doesn't seem very practical as N64 savesates are huge (8mbs, since we force EPak), is there any N64 emulator that offers this feature? I think the only practical way would be to auto savesate to RAM and then write to the disk(MS in the case of the PSP) after you close the ROM you are playing, but it'll require extra memory which we can't affort to waste. Also don't forget Daedalus compresses savesates to 7z which reduces 'em to 10% its size which requires alot time to do so (that's why you see an extra delay when saving a state, imagine that happening every minute or so ).



Well Daedalus' roms.ini contains a line called comments= which is used by the PC version to show notes, I can just easily hijack that(compat codes hijacked that entry as well), instead of writing a new parser for it.

Most emulators I've seen don't have an auto savestate feature, but I'd also have to add that most of what I've played are very stable as well. Even Wii64 is stable, however each of those emulators also have more power to work with. If automatically calling funtions isn't a viable way, then how about a warning that can fire every so often as a friendly reminder to save? It may seem pointless, but I'm sure it'll help people who are easily drawn into the games they play.

Call me weird, but I like cover flow;it's aesthetically appealing to me. I usually keep the low battery warning on, just in case. Though, in the end, I don't actually care, whichever change you make...you're the developer, not me.

Maybe there could be a way to connect through wifi to get to the compatibility list on the website. Sorry if this is a dumb idea, I know nothing of any programming languages.