I made a really basic frontend for CEN64 that was overhauled by Beannaich . If there's any problems with it I can try to fix them, as well any features you want let me know I can see what I can do.
I recommend using the new one that was made by thedax

This is mighty handy. Though non of my dumps work as it complains the system can't find the specified path. And like nmaster64 suggested, it could be because of the spaces used in the filenames or path.

Perhaps consider having the label for "Pifrom" say "Pifrom / Pitdata" ? I say this because the Pifdata that MESS uses is the exact same file and some of us on emutalk (including me) did not realize this.

I'd greatly appreciate it. We had several pages back in the Emutalk thread being all confused about what the heck the "pifrom" is and couldn't find diddly-swat information on it. It turns out that all the info on the (Google-indexed) internet regarding the PIF calls it the 'pifdata', most likely because that's what MESS calls it and it obviously came before Cen64.

I would prefer both. I like the flexibility of saving it to anywhere, but if you save to the application directory then the settings would work no matter what drive letter you run the program from and therefore allow the program to be portable.

I would suggest to default it to its own directory at the moment. Later on, you could add an option if there's demand for it.
Also, how difficult would it be to have the CEN64 window automatically closed if the user runs another ROM without closing it first? At the moment, it seems multiple CEN64 instances are allowed.

ShadowFX wrote:I would suggest to default it to its own directory at the moment. Later on, you could add an option if there's demand for it.
Also, how difficult would it be to have the CEN64 window automatically closed if the user runs another ROM without closing it first? At the moment, it seems multiple CEN64 instances are allowed.

Wouldn't be too hard, could add dolphin like control buttons too. Sadly only a "Play" and "stop" button could be implemented, no "pause". Go ahead and list all the features you'd like to see (within reason) now, and I'll get working on them.

Normally I would say controller button-mapping, fullscreen settings, and RetroArch filter support, but I've no idea if those are even possible via GUI-only functionality.

I'll elaborate on any one of those if you do actually confirm that it's possible.

EDIT: Well I definitely know that this is a GUI function - on first launch ask if you want to run in "normal" or "Portable" mode; in this case 'Normal' = settings in AppData while 'Portable' = settings in program director. The program can tell if it's a first-time run by the lack of any config file in either the program directory or the AppData folder, and said config file will only be created in the according location once the user selects "Normal" or "Portable" mode.

Also if there are settings files in both the program directory and the AppData folder, the settings in the program directory should take priority.

Normally I would say controller button-mapping, fullscreen settings, and RetroArch filter support, but I've no idea if those are even possible via GUI-only functionality.

I'll elaborate on any one of those if you do actually confirm that it's possible.

EDIT: Well I definitely know that this is a GUI function - on first launch ask if you want to run in "portable mode" or not. In this case portable mode = settings in program directory, non-portable/normal mode = AppData

No, no, and no. All of those are built in to CEN64, the GUI is just a launcher/ROM browser. The reason a "pause" button can't be added is because I can't suspend the emulation (maybe I can, I'll confirm that soon) from outside, but I can completely destroy it or create it. As far as booting and asking if you want to run in portable mode, I think I'll just allow the same directory. Allowing other directories would require 2 settings files. One to tell the program where the real settings are, and the real settings. Too much hassle for a free program at the moment.

beannaich wrote:No, no, and no. All of those are built in to CEN64, the GUI is just a launcher/ROM browser. The reason a "pause" button can't be added is because I can't suspend the emulation (maybe I can, I'll confirm that soon) from outside, but I can completely destroy it or create it.

Or can the GUI and therefore programs like Sizer only control the windowed size? Therefore couldn't it make a "pseudo" fullscreen by scaling up the program window and overlaying it on-top of a black image?

Forgive my ignorance, as I've said before on Emutalk I'm much more of a hardware guy so I don't really know much at all about coding and stuff.

ShadowFX wrote:Well, I can indeed think of a few suggestions for the CEN64 GUI:

- Usage of proper names like ROM instead of rom, Rom etc.

Are there any instances of this in the new version? I was pretty particular when I redesigned the GUI to fix things like that. Most of the features you wanted are done or being tested now.

Nintendo Maniac 64 wrote:Or can the GUI and therefore programs like Sizer only control the windowed size? Therefore couldn't it make a "pseudo" fullscreen by scaling up the program window and overlaying it on-top of a black image?

Depends, you could hook the openGL calls and make a full screener, but that takes a lot of effort and I'm doing this for free.

This is going to seem like the pickiest thing ever, but isn't a lower-case v usually used when designating a version number? Like v1.6 vs V1.6.

On a less picky note, I noticed that the user cannot customize the "File", "Size", and "Compatibility" headings other than resizing them. Normally in windows you can rearrange them by dragging and you can enable/disable them via right-clicking on them.

But I can't enjoy it yet because my desktop PC only supports SSE3 at max. >_> Only my HTPC supports SSSE3 and runs a 64bit OS, but people are asleep so I cannot go out into my living room and risk booting it up. (also note my laptop supports SSSE3 but only runs a 32bit OS for driver compatibility).

A statusbar is a convenient way to display useful information of the emulation status, instead of overlaying this on the video (if that is possible at all for CEN64). May I ask what is hindering you to implement this?

Can you check to see if its actually running in your task manager because I just downloaded it and it started just fine. Shouldn't be crashing at all. and the generated appdata is ignored now as well. i wonder if its loading off screen..

is it possible to check the md5 hash on the file. mines F75F2B9F91379D11D717F3AD4636D004 I wondering if its corrupt tried another computer not getting any crashes. if thats not the case ill have to look into this even more