Mala FE with project64 emulation

[slsimon]

I noticed that project64 does not exit out of the games correctly with the ESC button pressed most of the time.  During exit on some of the games the ESC key works fine.  I have the configuration in mala to use the exit hook and also tried configuring an exit hook key in mala with no available luck.  I have also looked through the configuation settings within the project64 emulator and did not see any settings pertaining to any exit configuration.  Actually, I am looking in the project64 install directory and don't even see an ini file.  Hmm, not sure where else to troubleshoot this issue. 

Can anyone tell me if there is a wrapper that has been developed to properly exit out of project64 with the alt-f4 key press?  That seems to be the only way that I can currently exit out of the nintendo 64 emulator without having to press ctrl-alt-delete to stop the project64 service from running.  Again, this is for most games but some actually exit correctly with the esc key.  Thanks for any heads up!! 

[Dustin Mustangs]

There is a wrapper for pj64 that takes care of this.  I believe I got it off jcrouse's website.  I think I may have heard that it doesn't work with the most up to date version of pj64, but I'm not sure.  If that is the case, search for closemul.  That should be able to take care of this also.

 

[SGT]

Project64 allows (at least the version I use) the key to exit the program to be configured from within the menus.  After configuring make sure you stop using the Mala exit hook so it doesn't interfere.

Note that I'm using the last beta of Project64.  Older versions may not allow this?  If you don't have the option, I like closemul for a lot of my emuls.

http://lustar.free.fr/clusters/closemul/

[slsimon]

Thanks for the replys.  I have version 1.6 for project64 installed and the keyboard key configuration tab is not a function of this version.  Seems like as soon as one gets these emulators installed and configured, a new version is out with new functionality  .  I will be working on this install later today.  As usual, everyone here is full of knowledge and is of great help. 

I am hoping that the nulldc developers will implement the option to hide the mouse cursor during game emulation play sometime soon.  That's one of those outstanding configuration to do's on my list at some point is to try to find a fix to remove the mouse in that emulator. 

Thanks, Shane 

[slsimon]

Project64 allows (at least the version I use) the key to exit the program to be configured from within the menus.  After configuring make sure you stop using the Mala exit hook so it doesn't interfere.

Note that I'm using the last beta of Project64.  Older versions may not allow this?  If you don't have the option, I like closemul for a lot of my emuls.

http://lustar.free.fr/clusters/closemul/

I am trying to reassign the default key of alt-f4 to the esc key.  I select remove on the highlighted exit menu item to remove the default key mapping and am not sure how to assign the exit menu to the esc key.  If I select detect key and press the esc button, I get a message saying that the key is already assigned to another function.  I will keep on playing with the config.  SGT, can you help me determine what I am doing wrong?  Thanks,

Found that the esc key was also assigned to the full screen mode as well as the alt+return key.  Not sure why both keys need to be assigned to do one function but I removed the esc key function for full screen and configured for the exit menu and the key assigned correctly.  Now time to test!!  Thanks SGT for you screenshot. 

[slsimon]

Receiving the following error within mala when trying to run the version 1.7.0.49 version of project64.  Outside of Mala, works fine. 

Error message:  Attempt to open file failed. 

I can press esc to exit out of error message and another press of esc closes the start of the emulation screen so I know the esc key works anyway.  Thanks,

[SGT]

Regarding the ESC key.  You'll have to go through and see what the ESC key is currently being used for and change it to a different key before it will let you assign the ESC key to exit.  It's been so long, I had forgotten about that, and I don't remember what the default use of the ESC key was.  I don't think it will take you long to find it by using the menus.

I see you already figured that out...

Regarding the "attempt to open file failed", I think there was a change in the later versions of Project64 which requires quotation marks around the rom name.  In Mala, try changing the Project64 command line to:

Code: [Select]

"%path%\%rom%.%ext%"
Yours probably doesn't have the quotation marks.

[slsimon]

Regarding the ESC key.  You'll have to go through and see what the ESC key is currently being used for and change it to a different key before it will let you assign the ESC key to exit.  It's been so long, I had forgotten about that, and I don't remember what the default use of the ESC key was.  I don't think it will take you long to find it by using the menus.

I see you already figured that out...

Regarding the "attempt to open file failed", I think there was a change in the later versions of Project64 which requires quotation marks around the rom name.  In Mala, try changing the Project64 command line to:

Code: [Select]

"%path%\%rom%.%ext%"
Yours probably doesn't have the quotation marks.

Putting the quotes around the command line code worked.  Just so I can attempt to understand, what changed within project64 that made the mala command line configuration change?  I am still trying to figure out the whole mala command line setup and just want to attempt to figure out why the command line changed.  Again, thanks for your help.  I did notice that thre is even a later version of project64 floating around out there, version 1.7.0.55 I believe.  I am wondering if its worth updating to this version while I am at it.  Is there a page somewhere that tells users what if any enhancements were added to the later versions of project64 emulator?  Thanks, Shane

[SGT]

Mala passes the command line to Project64.  Project64 developers decided to implement quotes around the command line probably because with spaces in the rom names, its hard to determine what is the rom name and what is extra parameters being passed to it.  By requiring quotes, the code can easily determine where the rom name begins and ends.

You have to log in to see the Beta development change logs.  It used to require a donation to do that and download the latest files, but it looks like they removed the donation link because of some Paypal issue.  I have all the latest files from the beta site, but my version still says 1.7.0.49.  There is a graphics plugin (Direct3D8.dll) that I'm using which is 1.7.0.56.  However my version of PJ64 stills says 1.7.0.49 at the top.

[unclet]

I am still trying to figure out the whole mala command line setup

%path% = the value you entered into the "Rom Path" line
%rom% = the name of the ROM file which MALA finds for you without the extension
%ext% = the extension of the ROM file

For example, lets say you have the following settings configured in MALA for project64:

  Executable = C:\Emulators\project64\project64.exe
  Rom Path = C:\Emulators\roms\project64
  Rom Extension = ZIP
  Command Line = "%path%\%rom%.%ext%"

Now lets say you selected the game Paperboy to play from the MALA gamelist.  Based on the above settings, then MALA will try to execute (as it's "Command line") the following:

     C:\Emulators\project64\project64.exe "%path%\%rom%.%ext%"

.... which is the same as the following:

     C:\Emulators\project64\project64.exe "C:\Emulators\roms\project64\Paperboy.zip"

Hope this allows you to understand how the MALA command line parameters are used.


Now...... why did it use to work without the double-quotes in MALA?   I would guess it would still work without using the double-quotes as long as you do NOT have any (space) characters within the path MALA is trying to execute.

For example, when the double-quotes are NOT used:

This might still start the game fine:

 1)    C:\Emulators\project64\project64.exe C:\Emulators\roms\project64\Paperboy.zip

and this might NOT start the game (notice the space between Mario and Party):

 2)    C:\Emulators\project64\project64.exe C:\Emulators\roms\project64\Mario Party.zip


In (2), MALA would start the project64.exe with the following input information:

     C:\Emulators\roms\project64\Mario Party.zip

but since it does not include the double-quotes then Project64 might interpret it as .....

    C:\Emulators\roms\project64\Mario

and Project64 will not find a game called "Mario" only so nothing will start.

So my guess is that whenever you tried out MALA before and it worked then you did not have any spaces involved, but now you do.  This is just my guess, but you can easily test whether Project64 works without double-quotes by having no spaces in the command line which is sent to Project64.

Of course, the newer version of Project64 could simply being checking for leading and trailing double-quotes and if they are not present then it ignores the request .....

Perhaps I provided to much information        Figured I would include all this stuff and let people read about it if they want to .....

[slsimon]

I am still trying to figure out the whole mala command line setup

%path% = the value you entered into the "Rom Path" line
%rom% = the name of the ROM file which MALA finds for you without the extension
%ext% = the extension of the ROM file

For example, lets say you have the following settings configured in MALA for project64:

  Executable = C:\Emulators\project64\project64.exe
  Rom Path = C:\Emulators\roms\project64
  Rom Extension = ZIP
  Command Line = "%path%\%rom%.%ext%"

Now lets say you selected the game Paperboy to play from the MALA gamelist.  Based on the above settings, then MALA will try to execute (as it's "Command line") the following:

     C:\Emulators\project64\project64.exe "%path%\%rom%.%ext%"

.... which is the same as the following:

     C:\Emulators\project64\project64.exe "C:\Emulators\roms\project64\Paperboy.zip"

Hope this allows you to understand how the MALA command line parameters are used.


Now...... why did it use to work without the double-quotes in MALA?   I would guess it would still work without using the double-quotes as long as you do NOT have any (space) characters within the path MALA is trying to execute.

For example, when the double-quotes are NOT used:

This might still start the game fine:

 1)    C:\Emulators\project64\project64.exe C:\Emulators\roms\project64\Paperboy.zip

and this might NOT start the game (notice the space between Mario and Party):

 2)    C:\Emulators\project64\project64.exe C:\Emulators\roms\project64\Mario Party.zip


In (2), MALA would start the project64.exe with the following input information:

     C:\Emulators\roms\project64\Mario Party.zip

but since it does not include the double-quotes then Project64 might interpret it as .....

    C:\Emulators\roms\project64\Mario

and Project64 will not find a game called "Mario" only so nothing will start.

So my guess is that whenever you tried out MALA before and it worked then you did not have any spaces involved, but now you do.  This is just my guess, but you can easily test whether Project64 works without double-quotes by having no spaces in the command line which is sent to Project64.

Of course, the newer version of Project64 could simply being checking for leading and trailing double-quotes and if they are not present then it ignores the request .....

Perhaps I provided to much information        Figured I would include all this stuff and let people read about it if they want to .....

Very valuable information.  Thanks Unclet for your thorough work.  Sounds like another possible revision later in your guide to me.  Eventually I will get the hang of the mala command line settings.  As far as the directories go, I did not change any of the locations.  The file names stayed the same as well.  I do have a better understanding of what mala is looking for now when attempting to run multiple emulators.  Thanks,

[unclet]

I do have a better understanding of what mala is looking for now when attempting to run multiple emulators

that was the main goal   

I will add this information to the document when I get home tonight.   

All of these command line placeholder values are located on the MALA site under "Help/Command line placeholder".  There are other place holder values defined which you can use in the Pre/Post Commands, encoder config line and control panel viewers. 

Here is the information from the MALA website

[slsimon]

I found this link containing a nomousy utility that may work with hiding the mouse in nulldc.  I am not sure how to go about using this utility within mala and or nulldc.  Can anyone provide any suggestions?  See below link.  Thanks,

http://www.apps4apps.filetap.com/nomousy.html




I am hoping that the nulldc developers will implement the option to hide the mouse cursor during game emulation play sometime soon.  That's one of those outstanding configuration to do's on my list at some point is to try to find a fix to remove the mouse in that emulator. 

Thanks, Shane 
[/quote]