Brian Hoffman

Resolution? Crt Tv are low res.

Its never a fun task to remap all your emulators, but you will find yourself woth a more stable configuration. You will also note this step for your next build. Hind sight is always 20/20.

There are programs like AHK that can remap keys, even gameex has remapping features. I would/did remap my Ipac, buttons like ctrl,shift are also windows hotkeys, when pressing multiple buttons you can find emus crashing, losing focus. Its really better to map to non-hotkey/function buttons.

Hmm, it *should* retain your favorites. I do remember something about new builds that don't, for one reason or another. Good luck! in any event make a back up

I think it may have been Steveuneven or BSebastian01, forgive me if I am wrong. I believe there was a dupe post of a question at emumovies forum where it got answerd by matt or me. We do tend to hang out various places. Ill see if I can find it. I think this is resolved though. Thanks for the kind words Lucas

OS? There have been issues with emulators and timing in vista and 7. There was a good write up from the guy who programs ootake emulator about how to fix it. Taken from : http://www.ouma.jp/ootake/delay.html In "Ootake", the "Delay Problem" is solved(reduced) by using two strategies. The First Strategy... When "Instruction that sees the state of joypad" comes, "Latest state of the Windows Joypad Input" is always acquired. In a lot of emulators, "State of Windows Joypad Input" is acquired only once in one frame(1/60 seconds). As a result, if the joypad is input according to the timing immediately after acquisition, about one frame input will be delayed. It can be solved by the above-mentioned strategy. However, this strategy makes the emulation processing considerably heavy. In "Ootake" for that, if "Instruction that sees the state of joypad" comes continuously, the frequency that "State of Windows Joypad Input" acquires is limited. Concretely, when "State of Windows Joypad Input" is acquired, "Processed scanning lines No." is recorded. And, when the following "Instruction that sees the state of joypad" comes, if "Be still processing it at same scanning lines No.", the acquisition of "State of Windows Joypad Input" is omitted. This method makes the reaction early enough, and processing doesn't become heavy too much. * However, the emulator certainly becomes heavy for this processing. However, I think that it is necessary processing to "The happiness of the game is not ruined". The Second Strategy... The emulated processing is delimited by "about 1/240 seconds (1/60 seconds are divided into four)" unit. As a result, operation approaches "State of the passage of time in a real machine". When the emulator works by "PC that there is room at the processing speed", it becomes as shown in figure below (Flow of 1/60 seconds). ->[ Emulate Processing ]->[ Wait V-Sync Processing (Rest) ]->[Draw Processing]->(To head) In a word, the time of "Rest until the V-Sync signal comes" becomes long. (Oppositely, in "PC that there is no room in performance", this "Rest" decreases, and the time of "Emulate Processing" becomes long.) At the time of this "Rest", the input judgment of joypad cannot be done. As a result, the period when joypad can be input narrows. It causes to be input delaying one frame. Then, the method like the figure below (flow of 1/60 seconds) is executed in "Ootake". ->[Emu.]->[Rest]->[Emu.]->[Rest]->[Emu.]->[Rest]->[Emu.]->[Rest]->[Draw]->(To head) In a word, the "Rest" is put every about 1/240 seconds (Divide without taking a rest to one degree). As a result, the flow of the passage of time near a real machine is made. The input judgment of joypad is prevented being delayed by this method. Moreover, not only the reaction of the joypad but also the accuracy of emulation(Timer interruption etc.) rises by this processing. Especially, this is important in the reproduction of the tone of PSG (wavy memory + noise) sound. * In "Ootake", when "Light PSG" is chosen by "Volume" menu, it becomes usual operation every 1/60 seconds. About the cause of becoming "Bigger Delay Problem" In "Two strategies of Ootake" previously described, about one frame is prevented being delayed. To my regret, there is a cause of "Big Delay Problem (about 2-4 frames)" that becomes a problem any more. It is "Problem of DirectX(Direct Input) of Windows". If "Direct Input of Windows" is not used well, a big delay is generated. It seems to be different according to the library used. I am adding the following code for the development environment of Ootake (MinGW+DirectX library). #define DIRECTINPUT_VERSION 0x0500 "Direct Input" of "Version 5(old)" is used. As a result, the least input delay has been achieved. (confirm the operation on WindowsXP) When the version above "Version 5(old)" is used, a big input delay is generated in Ootake, too. There is a possibility that the person who had made "Direct Input of an old version" loved playing a game more. Or, there is a possibility that the delay occurs when the library is old. To our regret, there are a lot of emulators where this delay problem occurs. The problem is caused in "VirtuaNES (Excellent NES emulator)", too. The problem is caused in "BuleMSX (Excellent MSX emulator)", too. *2008.9.20 It was considerably improved now (ver2.8 wonderful!). These are very too good. In "Nestopia" and "ParaMSX(latest bata)", this problem is not caused. When the "action & shooting game" are played seriously and compared, the difference is remarkable. (In "VirtureNES" and "BuleMSX", if improved it is glad as one user.) * The above-mentioned is a confirmation of operation in "WindowsXP SP2" environment.

I guess my first question would be, What is running in the background of your PC that is taking focus away from Gameex every 20 minutes? Have you installed gameex on a diffrent pc, played a video file from it just to see if it is some rogue service?

Hmm, may be a bit of a stretch but.... In mame there is a default.cfg and when you run each game it creates a gamename.cfg, individual configs will override default configs. Sooooo..... Perhaps there is a config these two games are using that override the default.

A ) The command line for skipcrc is -nocrc and should be in the same place you set daphnes globaloptions in the gameex config. B ) I have no idea why DL2 does not work for you, it works fine for me. Id check the daphnelog C ) -fasboot does not go in the framefile, and is probably why it is not working. Only a couple games support the flag. See the Daphne Command line options here. https://www.daphne-emu.com/mediawiki/index.php/CmdLine

As gameex has a built in video and audio player why are you trying to launch windows media player? Also you are not posting your config so it is hard to guess at why it is failing.

Mine is different, there is a part to read INI. I attached it here. mame.zip

Gameex will display any game you have in your roms folder, as long as the criteria matches your rom filter. EG.. *.ZIP will only show zip files, if your roms are not ZIP it may not show them. It also explains why you do not see update list.

I have a lightgun I have never used. Maybe I should break it out. EDIT: I do believe you just have to enable it in the Mame.ini and ensure it works in windows.

Chd games do run slow, you need a core2duo @ 2.6 Ghz to play most well. Games like Killer instinct and Carnevil should be ok, NFL Blitzs will be playable. Gaunlet legends is playable on my Quadcore I7, but its a 300.00 cpu. It just depends on your wallet For MAME intergrated graphics is fine. Other emulators like M2 and NullDC, Makaron, Playstation 1 and 2 may require a little bit more.

Have you pressed the space button, To back out of that, close and restart gameex

Ya I see, completely. I actually glad you mention MAME32/UI, as a (official?) derivative of mame, there is nothing it can do that command line mame cant. Regular MAME you can create a Mame.ini and edit it to manipulate resolutions, toggle off and on features, enable joypads etc.. There is also command line switches that can be run when running mame to enable these features. Like any windows application point and click is easier to use than command prompt, I can see why its so popular. It like daphne loader is a gui that manipulates the program but does not really add functionality just automate some processes. Gameex runs mame32 the same way it runs mame or any of its variations. This is what all frontends do, automate processes, runs emulators against arguments to load a rom, go fullscreen and mount drives etc. Using a single or multiple commands, so the user presses one button and can watch the magic happen as all of a sudden their game or program is loading without having to go to numerous places or even understand how it works. You will notice in daphne loader you can toggle off and on the ability to see the command it generates to load daphne up. Those can can copied and pasted into the gameex config and it will run the game just like you were running it from the loader, which runs Daphne by the command line. I see you idea when you say just call Daphne loader to run the game, but you have to ask your self how it works, Even using daphne loader you still have to setup, select virtual laser disk player, point to the framefile etc. Only then can you select a game from the screen and press load game, this is without configuring the options. Then we ask ourselves what we do once that is done, we launch the program, wait to see the screen to pick our game, scroll down the list till we find our game, then click load. That is several steps we take for granted. In a program you would have to make it launch daphne loader, wait till it see that is has loaded by the active title window, the program would have to realize the rom you picked from the gameex list then scan the listbox for the chosen game, then it would have to select it and then choose load. This is alot of work for a program that normally supports command line loading. Which is what gameex produces normally. For the emulators and programs that do not support command line there have been gracious members of our forum that have developed scripts,loaders,wrappers to make it all happen. Hope this helps Note: I do realize there are countless unofficial mame builds that do add functionality, even then they can still function the way described above. When you say "*I have always used MAME32 for this reason. As well, when I want to troubleshoot, I don't have to worry about reading inis or the command line (unless absolutely necessary, which it almost NEVER is). You see?" For program authors, script/wrapper writers it is imperative to know/ understand command line. For us when it fails it IS because of the INI or command line, we understand in detail how these emulators work. Tom does too, this is why he allowed for ROM to be separate from the command line options and made the games separate from each other as they take separate options. unlike other emulators that pass only a few universal variables. You and others have much success with Gameex because it is highly polished and configurable and we have a dedicated team to make sure each and everything works or can work, one way or another. EDIT: Haha, After my long winded post I realize Frequency has said the same thing, in much less words. I was on a roll I swear his post wasn't there when I started typing. Trying to multitask.

Update list only exists for MAME. It may be below all your other options, keep pressing down and it may appear. You can also attach your Gameex.ini

Daphneloader just takes the options and sends/create the command line. Think of it as a frontend. Now Gameex is also a frontend, the options are specified in the configuration and the commmand line is created and sent. There is no need for a frontend to launch a frontend to launch a game. Ranzo, put together a pretty comprehensive guide about Daphne in this thread, there are also some links to some good Daphne information. http://www.gameex.info/forums/index.php?showtopic=8226&view=findpost&p=60311

Sounds like an active desktop issue. You will find in conjuction to changing your theme, which some software will do. It can affect active desktop which can affect how your desktop wallpaper is applied, do you notice when you boot up windows you see a difrent background then when it finishes loading. Id disable active desktop and see if your problem goes away. Of course I can be completely wrong about this too. If just seems to fit right now. http://www.computerhope.com/issues/ch000593.htm

Hmm, Id try a diffrent codec pack. Klite or similar. Gameex also has some settings to define what media engine is run. I honestly think its a codec issue.

Ranzo, Sorry, I had thought you got that figured out. You should be able to edit your post, choose full editor, manage attachments, remove attachment. If that does not work it could be a permission issue. At one point in time we had a contributor remove all their stuff so it may be like that on purpose. I'll remove your old manual. BH

Well, for turbocd it could be that the virtual drive letter has changed, it may have mounted to E: before but now it may be a diffrent letter. Id mount a disc in d-tools then configure the emulator. Fusion should load the isos so check the command and post your contents of runitgame.bat along with your config.

Id think No Intro, or run your set against a nointro dat file and clrmamepro. Other than that we cant help much, strictly speaking we try to not talk much about roms.

It should go back into gameex can you post your config?

Im guessing you have some video card driver loading as a service, perhaps even a try utility exists. That is not loaded immediately when gameex is called so your getting the directX error. you can create a AHK script to wait 3-5 seconds then call Gameex, this may delay enough to run successfully.