How do I add emulators to Gameex?

[Greego]

Hi,

 

I finally have Gameex up and running well and overall, it is a great feeling. Mame is running well and looking great and my NES emulator is working well and I can play NES games without a proble. My only problem is getting Project64 Nintendo 64 games to run. Project64 runs well outside of Gameex with no problem. I can play all of my games from windows, however, when I try to play them through Gameex, they won't load, I tried going through the steps from Tempest's thread several years back but couldn't follow all of the troubleshooting steps well.

The problem is when I try to load a game, it goes to a black screen briefly then return to the preview screen and the games never load.

 

[Emulator]

lastgame=
database=[Console] Nintendo NES
command=demo.exe "[rompath]\[romfile]"
showdesktop=False
removebrackets=True
workingpath=C:\Users\Arcade\Desktop\Project64 1.6
manualpath=C:\GameEx\DEMO\N64\manual
cartpath=C:\GameEx\DEMO\N64\cart
boxpath=C:\GameEx\DEMO\N64\boxart
titlepath=C:\GameEx\DEMO\N64\titles
snappath=C:\GameEx\DEMO\N64\video
rompath=C:\Emulation\ROMs\Nintendo N64
romfilter=
startpagelogo=N64
titletext=Nintendo N64
startpagename=Nintendo N64
enabled=True
UseDbName=True
InGameMode=0
MapKeys=True
DontShowInfo=False

[\spoiler]

Edited March 5, 2017 by tthurman
Moved from GameEx Evolution to GameEx

[tthurman]

Per Draco

Quote

The correct command line should be  Command=Project64.exe [ROMPATH]\[ROMFILE]

 

[Draco1962]

Since your original thread centered around adding N64 emulation I merged the two.

[Greego]

54 minutes ago, tthurman said:

Per Draco

 

How do I correct this?

[tthurman]

Open the Setup wizard, and go to the emulator section for project64, you can edit the command line there.

[Greego]

23 minutes ago, tthurman said:

Open the Setup wizard, and go to the emulator section for project64, you can edit the command line there.

I just noticed that the text I posted in my original post above lists the command line related to my NES instead of the N64. Is this an error or does it still show you that the command line info is the problem?

[tthurman]

<disclaimer> I'm no expert on emulators, but if the path is right, and the command line, then it'll run.  When you've got it selected for one console, and configured for another, it's looking at the incorrect "database"

[Greego]

1 hour ago, tthurman said:

<disclaimer> I'm no expert on emulators, but if the path is right, and the command line, then it'll run.  When you've got it selected for one console, and configured for another, it's looking at the incorrect "database"

 

Ok, we're getting somewhere now... I changed the command line to: Project64.exe [rompath]\[romfile] and now when I select a game, it will start up but all I get is a blackscreen but I hear the audio.

just to clarify, I left out the quotes in the above command line because when I left them in, I would just get a black screen that would no longer return to the Gameex dashboard and I would hear an error message popup but could not see it. I also would get no sound from the game I was trying to load. Once I deleted the quotes, the game seem to load normally with sound but it was just a blackscreen. I exited Gameex and loaded the game in Project64 on my desktop and everything worked fine.

 

Addendum:

whenever I exit Gameex, the quotes in the command line automatically return but whenever they are there, I don't even get the sound of the game and still get the black frozen screen. I have to sign out of Windows when that happens.

[Greego]

I still have not found a solution. I am pretty sure the key to all of this is within the Gameex frontend. I have tried JNES, Project64, and 1964. All emulators work just fine in Windows, outside of Gameex but when I try to load ROMs in Gameex, I get a brief black screen then I get returned to the Gameex dashboard. I get a similar reaction with all 3 emulators.  

 

I also tried changing a bunch of the settings within each emulator but none of it helps. I tried comparing settings to my Nintendo Ent. System setting in the Setup Wizard and tried making them both similar but that does not help. If someone can send me any info that may be helpful, I'd appreciate it. 

[RedDog]

Greego, please repost your GameEx.ini file as an attachment so we can see what you have set up now.

Let's focus on one emulator first, such as Project64. Please provide the following info for that emulator:

• The filename of the Project64 executable
• The path to the Project64 executable
• The path to the N64 Roms
• The file format of the N64 Roms
• If the ROMs are zipped, does the zip file contain only one rom or a group of roms?
• If you are using a mapfile, attach the mapfile as well

I use P64, so I can compare your setup to mine.

[Draco1962]

Also, you will want to make sure, if your ROMS are in 7zip format, that you reflect this in the Advanced Emulator setup for P64 by changing to Yes via Setup Wizard.

[Greego]

It's working now. I am not sure how it happened. I just read your posts and said to myself "well, when I get home, I better switch back to Project64 so Reddog can help me out." So as soon as I got home, I let my dog out then ran right for my arcade cabinet like I was an 8 year-old on Christmas. I used the setup wizard to put Project64 back into Gameex and decided to check for the 1 billionth time to see if it work and it did. I don't know what happened or what was done differently this time...

 

I do get a message whenever I exit a N64 game in Gameex though. It was probably the error message I was getting all along but just couldn't see it due to the black screen. It says "switching resolutions failed to initialize direct3d." It flashes this message for less than a second then returns to desktop but , again, it shows it only when I voluntarily exit a game.

 

You guys do not know how happy I am right now. You just do not know how happy I am... This is so very satisfying. Thanks for offering a hand...

[RedDog]

Good deal! The next one will be a lot easier now that you have something that works.

If the direct3d error appears when running PJ64 on it's own (ie outside GameEx), you may want to try a different graphics plugin or a different version of PJ64. I also found an article HERE regarding some of the plugins. I am no where near knowledgeable regarding PJ64 plugins. I am using PJ64 2.1.0.1 with Jabo's Direct3D8 1.7.0.57-ver5. It works so I don't fiddle with it.  

[Greego]

2 minutes ago, RedDog said:

Good deal! The next one will be a lot easier now that you have something that works.

If the direct3d error appears when running PJ64 on it's own (ie outside GameEx), you may want to try a different graphics plugin or a different version of PJ64. I also found an article HERE regarding some of the plugins. I am no where near knowledgeable regarding PJ64 plugins. I am using PJ64 2.1.0.1 with Jabo's Direct3D8 1.7.0.57-ver5. It works so I don't fiddle with it.  

Thanks man. All heroes don't wear cape, bro, and you are my hero. Believe me, I...ain't...fiddling-with-*** when it comes to this setup! This is all I need. I disabled Windows 10 automatic updates and everything so nothing can be updated that will screw up my setup. I am happy and content. That PC is now officially and strictly dedicated to my Gameex arcade setup. If I catch anyone even trying to do anything besides run Gameex on that cabinet there is going to be World War III down in my man cave!