Hardware stretch

[Tempest]

What would we have to do if we didn't have to constantly fix things?

For starters, I wouldn't fool with the U versions, they are beta versions, and generally buggy.

I'm assuming you didn't compile mame32, but your post gives mixed signals, so I can't tell....

This is my favorite site for Mame options:

http://www.mameworld.net/easyemu/mameguidenew/mameguide.html

What you want to check is the core input options for the track ball issues, in your mame.ini. I would take a few minutes, and go through the Mame.ini file line by line and check all of your settings. I would also delete anything in the GameEX Mame options line, and just use the ini. It is much easier to debug, when there is only one set of options. Also, I believe that mame32 likes the mame.ini file in the mame32\ini folder, while mame likes it in the mame folder (Root). Go through your Mame.ini, and let us know how it turns out. Also, are you using mame32?

[deano7]

What would we have to do if we didn't have to constantly fix things?

For starters, I wouldn't fool with the U versions, they are beta versions, and generally buggy.

I'm assuming you didn't compile mame32, but your post gives mixed signals, so I can't tell....

This is my favorite site for Mame options:

http://www.mameworld.net/easyemu/mameguidenew/mameguide.html

What you want to check is the core input options for the track ball issues, in your mame.ini. I would take a few minutes, and go through the Mame.ini file line by line and check all of your settings. I would also delete anything in the GameEX Mame options line, and just use the ini. It is much easier to debug, when there is only one set of options. Also, I believe that mame32 likes the mame.ini file in the mame32\ini folder, while mame likes it in the mame folder (Root). Go through your Mame.ini, and let us know how it turns out. Also, are you using mame32?

I started off using Mame, I did compile both of them. Now I am back to mameui32. So this is so irritating!!! It is the same problem as before. When I run Tempest through MameUI32, it works great. I have the vector at 2.9. When I run through gameex, the lines are very faint and it is using a 1.0. But, I am POSITIVE that gameex is running the same friggin mameui32 file? This is making me crazy. All I wanted to do was play joust with the hardware stretched...

How do I get rid of the gameex file you mentioned?

I fixed the spinner and trackball problem. Before it would just say 'mouse X' but now it actually registers in the settings page and it now says mouse 2x for the spinner and mouse 3x for the trackball. I don't know why there is now a difference, but hey it is working so I am not complaining.

[deano7]

This thing is possessed. Now in Gameex, the dial and trackball control is set to 'mouse x' and even though it registers to scroll through the mame setting menu, it never registers the trackball or spinner when I try to assign one to the game.

Everything is working just fine in mameui32, but nothing is working correctly when I open it through gameex.

If gameex is using mameui32 as the mame executable, I just don't see how the settings wouldn't be exactly the same as they are in mameui32? What am I missing?

If the original answer still stands and I need to run Mame instead of mameui32, do I just rename the mameui32.ini file to mame.ini?

[bkenobi]

This may not be taken as a friendly suggestion, but I think your best bet at this point is to create a new directory for MAME and start a fresh config. You can copy your cfg directory over, but I would keep everything else new. When you configure too many versions of MAME in the same directory, things can get too complicated and confusing. That's just my opinion based on my own personal struggles way back when (and even recently to tell the truth ).

We can help better when the situation is simpler as well...

[deano7]

This may not be taken as a friendly suggestion, but I think your best bet at this point is to create a new directory for MAME and start a fresh config. You can copy your cfg directory over, but I would keep everything else new. When you configure too many versions of MAME in the same directory, things can get too complicated and confusing. That's just my opinion based on my own personal struggles way back when (and even recently to tell the truth ).

We can help better when the situation is simpler as well...

OK, I'll do it tomorrow.

But still the thing I can't get over is this. If both mame and mameui32 work correctly when run separately from gameex, it seems to me that there must be something wrong with gameex to, no? I just don't see how it could have anything to do wtih the Mame folder, considering it is working fine on it's own. If gameex simply opens mame in a separate window and is running the same file, UGH

Thanks for the input guys, I really appreciate it since I am completely stumped...

[bkenobi]

Well, there's most definitely something wrong. The problem is likely related to the paths that you are specifying in the GameEx setup, but it makes it hard to tell when there's too many configurations involved. I'm pretty sure it's been mentioned in the thread earlier (I haven't gone back to check), but GameEx creates a file in the GameEx Start folder called "Run Last Game.bat". This file contains the exact set of commands that GameEx used to run the last game. If you run that batch file, you should see exactly the same thing as when you run the game from within GameEx. Basically, you can use this file to check whether things are set up correctly or not.

What I was basically trying to say is that if you set up MAME from scratch again and then point GameEx to the new version of MAME, you will be able to see what the problem is in a simpler form that we might be able to help with.

[Tempest]

I agree 100% with Bkenobi, and as long as your starting over, let's try first with just standard mame. Don't even bother to compile it first, just set it up, run it to see what's not working, make a few changes in the mame.ini using the link I posted as a guide, and run it again.

Don't use GameEX at first either, you can run Mame from a batch file easily:

c:
cd "C:\Program Files\Mame0127"
mame.exe tempest -rompath "D:\Mame 0.128 roms"

The first line is the drive mame is on

The second line is the location of your mame.exe

Third line: Name of your mame.exe Nameofgame -rompath "your rom path"

Just type that into notepad, and save it as mame.bat. Anytime you want to run mame, double-click the bat file.

The key is to take it slow, if you do too much at once, you won't know where things went wrong. once you get it running the way you want from running the mame.bat file, then set it up in GameEex. If you have any problems, post!

[deano7]

I agree 100% with Bkenobi, and as long as your starting over, let's try first with just standard mame. Don't even bother to compile it first, just set it up, run it to see what's not working, make a few changes in the mame.ini using the link I posted as a guide, and run it again.

Don't use GameEX at first either, you can run Mame from a batch file easily:

c:
cd "C:\Program Files\Mame0127"
mame.exe tempest -rompath "D:\Mame 0.128 roms"

The first line is the drive mame is on

The second line is the location of your mame.exe

Third line: Name of your mame.exe Nameofgame -rompath "your rom path"

Just type that into notepad, and save it as mame.bat. Anytime you want to run mame, double-click the bat file.

The key is to take it slow, if you do too much at once, you won't know where things went wrong. once you get it running the way you want from running the mame.bat file, then set it up in GameEex. If you have any problems, post!

OK, getting closer. But, with getting closer comes new problems ;-)

Brand new mame directory and I only have the necessary stuff. Things are working fine in mameui32 and in mame with the cool little bat file tempest told me about.

In gameex, Tempest works fine. I can use the spinner and the vector lines are coming through at 2.9. beautiful.

The only wierd thing is that in the settings, I have to change "mouse x" to "mouse 3 x" on every game. Why is that? Is there a way to make a global change?

The biggest problem is that most of my games do not play through gameex at all. If I click on 1941, it shows the control layout but then it goes back to the 1941 information page instead of launching it. Most of my games will not even play through gameex, but I have no problems getting them to play through mameui32 or through a .bat file for Mame. What would cause gameex to just abort launching?

Thanks for the help guys, I am getting there!!!!

Dean

[deano7]

Well, I installed version 9.77 of gameex and now the games work. Settings are all working except for.... you guessed it, the hardware stretching.

After all of this, I am back to square one. Hardware stretching works fine in mame and mameui32. When I run it through gameex, hardware stretch doesn't work.

I am down to barebones in my mame file, so any ideas on what could be the issue with hardware stretching in gameex?

[Tempest]

So far as the settings, you need to go into the mame menu {Tab} Input (General) > Player1 (2,3,4) controls, and set up your spinner there.

I don't have a clue about the hardware stretching....

[deano7]

So far as the settings, you need to go into the mame menu {Tab} Input (General) > Player1 (2,3,4) controls, and set up your spinner there.

I don't have a clue about the hardware stretching....

OK, I finally found the solution... Hopefully someone that has this problem will benefit from this weekend of monkeying around with it.

For some reason, DDRAW hardware stretching doesn't work for me in gameex even though it works in mame and mameui32. If I change the video option to d3d version 9, the image is stretched in gameex as well. So, the benefits are that I now have a very orderly and tidy Mame folder and a much better understanding of gameex and mame.

Trouble ticket officially closed!

Thanks for the education guys!

[Tempest]

Good Deal!

[bkenobi]

Interesting. This is something I wouldn't have run across then since I use D3D. I'm glad you figured it out and even more happy that you posted the solution! Have fun!