sreisig1 Posted October 26, 2014 Posted October 26, 2014 Ok. So to swap them, I just switched usb ports each was plugged into, so they swapped. Which now they have they correct health on screen. But I changed crosshair color in mame menu (hitting tab) and it doesn't changed their colors? have a crosshairs folder in mame folder with images. In mame menu (tab) I can change the color using the file names as in the crosshairs folder, but it doesn't physically change them
klizine Posted October 26, 2014 Posted October 26, 2014 Ok. So to swap them, I just switched usb ports each was plugged into, so they swapped. Which now they have they correct health on screen. But I changed crosshair color in mame menu (hitting tab) and it doesn't changed their colors? have a crosshairs folder in mame folder with images. In mame menu (tab) I can change the color using the file names as in the crosshairs folder, but it doesn't physically change them Sorry dude, I think that's how windows stores it... might wanna get someone smarter than me to assist with that. But let me understand again. The gun that you want to be player 1 is blue?
sreisig1 Posted October 26, 2014 Posted October 26, 2014 Now I'm confused haha. For some reason the whole time, before any swapping of any sort. Player one had/has blue crosshair but red health on screen. Area 51s player 1 is supposed to be red since that's how the game was designed. So I swapped usbs hoping to make left gun be player two instead, giving it blue health on screen, but it has red crosshair now. So went to swap crosshair color in settings, but it doesn't change it. Hard to explain. Maybe should try to explain when I'm sober again. Hah
sreisig1 Posted October 26, 2014 Posted October 26, 2014 Right now. My left blue gun is acting as player two since I swapped usbs, giving it the blue health on screen. But it has a red crosshair for some reason. So I went to change crosshair color in settings. Changed it to blue, but nothing changes on screen. Make sense? All I need to do now is have changing crosshair colors work, and I'll be fine. Doesn't really matter if my left side of the cabinet is player two gun. You can still play 1 person using just a player two gun. I think I explained it ok haha
sreisig1 Posted October 26, 2014 Posted October 26, 2014 Is there a way to change mames default crosshair colors? Or another location to change the default? By default in MAME player 1 crosshair is blue and player 2 is red. Need that swapped.
klizine Posted October 26, 2014 Posted October 26, 2014 Is there a way to change mames default crosshair colors? Or another location to change the default? By default in MAME player 1 crosshair is blue and player 2 is red. Need that swapped. Not that I know of... why can't you hit Tab, then Crosshair options, then press over when selecting P1 crosshair and change to mame-red?
sreisig1 Posted October 26, 2014 Posted October 26, 2014 Got i working as it should. Reset mame and hyperspin and the crosshair cookies swapped. Yes!! :) so just need to be taught now how to compil mame to get no nah and high score
klizine Posted October 26, 2014 Posted October 26, 2014 Awesome!!!! I'll try to write something up now. are you 64 or 32 bit? I'll cater to you.
sreisig1 Posted October 26, 2014 Posted October 26, 2014 64 bit. Thanks bro! My fiancé will be happy in not ditching her anymore to try and configure these guns. Well, she doesn't know, or maybe does, that it's time to configure other systems. Shhh
klizine Posted October 26, 2014 Posted October 26, 2014 It may not be the best way, but it works for me: Go to http://www.mamedev.org/tools/ and download "mingw-mame-w64-20140905.exe" for 64. Install to C:\MinGW Go to http://www.mamedev.org/release.html and under Official Source Code Packages download mame0155s.zip. Open mame0155s.zip and you will find mame.zip. Create a folder called 155 (or whatever you want) and place in the source folder so it looks like this --> C:\MinGW\source\155. Now extract mame.zip contents here. Go to http://forum.arcadecontrols.com/index.php/topic,64298.0.html?PHPSESSID=g7h9mpec9om39o89l7c653mjt0 Next to 155 right click then Save link as... and save hi_155_2.txt to C:\MinGW\patches Go to http://headsoft.com.au/index.php?category=mame&page=mc64 and download Mame Compiler 64 v1.3. I installed mine to my MAME folder, but you can put it anywhere. Now it's go time. Open Mame Compiler 64 Set your MinGW Folder as C:\MinGW Set your Mame Source Folder as C:\MinGW\source\155 **(if you didn't name it 155 set it to whatever you ended up calling that folder) set your Diff Patch File to C:\MinGW\patches\hi_155_2.txt Then click Apply Patch. You should see mostly green text. Once that has finished successfully, then you will click GO! (this is where you spend a few minutes with your fiance...but don't forget your compiler!!!) Once completed you should have your mame64.exe compiled!! It will be located in C:\MinGW\source\155 (or whatever you called it) all you need is the mame64.exe. copy and replace the one we just got working. You can rename it mame.exe if you don't feel like updating hyperspin... then try 'er out! Continue on if you want to save hi scores.... Go to http://www.mameworld.info/highscore/download.htm download hiscore.dat by Clicking the top Click Here button. Save this in the root of your MAME folder where your mame or mame64 exe resides!!!!!!!! not in dats folder (if it exists) Create a folder named "hi" along side all your other mame folders (crosshair, cfg, etc) Then just make sure in your mame.ini that the line reads: hiscore_directory hi
dougan78 Posted October 26, 2014 Posted October 26, 2014 Fyi... i had to set my calibration delay to like 30. I had people just holding all the buttons down.
sreisig1 Posted October 26, 2014 Posted October 26, 2014 Klizine, thanks for the extensive writeup. Giving it a go now. I don't see a source folder in MinGW. Do I need to create it? And then create the 155 folder within it? Dougan, Yea I agree, I've changed mine to 15 seconds. Already ran into issues of the guns going into calibration mode when I don't want them to.
klizine Posted October 26, 2014 Posted October 26, 2014 Klizine, thanks for the extensive writeup. Giving it a go now. I don't see a source folder in MinGW. Do I need to create it? And then create the 155 folder within it?Dougan, Yea I agree, I've changed mine to 15 seconds. Already ran into issues of the guns going into calibration mode when I don't want them to. Not a problem. ... ok so I may have created the source folder too... I try to make this for the long term. so when 156 comes out, i can just create a folder and do this process again. The name doesn't matter just so much as that you can point the tool to it.
sreisig1 Posted October 27, 2014 Posted October 27, 2014 Does it matter that I used a different drive other than C, even though my locations are correct? Getting an error applying patch. "Error applying patch. PatchDiff(): The system cannot find the file specified"
klizine Posted October 27, 2014 Posted October 27, 2014 No, it doesn't matter what the drive letter is. However it needs to know where to look. That error means the paths aren't correct. just double check... use the buttons on the right of where the path is to manually find them.
klizine Posted October 28, 2014 Posted October 28, 2014 The paths are correct can you take a screenshot like below?
sreisig1 Posted October 28, 2014 Posted October 28, 2014 MinGW location: Source location: Patches location:
klizine Posted October 28, 2014 Posted October 28, 2014 but in the screenshots above all of the locations are pointing to your C: Drive. But in the tool you were pointing them to M. In the MAME Compiler you need to point them to the correct locations, so for you it should be C:\MinGW not M:\MinGW etc.
sreisig1 Posted October 28, 2014 Posted October 28, 2014 but in the screenshots above all of the locations are pointing to your C: Drive. But in the tool you were pointing them to M. In the MAME Compiler you need to point them to the correct locations, so for you it should be C:\MinGW not M:\MinGW etc. Sorry. The original shot with the m drive is before I tried moving everything to the c drive. Same issues with everything being c drive.
klizine Posted October 28, 2014 Posted October 28, 2014 The only thing I see looking odd is your MinGW folder. I only have a folder called mingw64-w64, with sub folders below that. Try deleting and re-installing mingw-mame-w64-20140905.exe
sreisig1 Posted October 28, 2014 Posted October 28, 2014 The only thing I see looking odd is your MinGW folder. I only have a folder called mingw64-w64, with sub folders below that. Try deleting and re-installing mingw-mame-w64-20140905.exe That worked. So far have all green after hitting apply. On to the next step.
sreisig1 Posted October 28, 2014 Posted October 28, 2014 Compiling finished. I don't have a mame64.exe in my source folder now? Don't see it anywhere
sreisig1 Posted October 28, 2014 Posted October 28, 2014 Compiling Mame... Using Parameters -j3 TARGETOS=win32 TARGET=mame OSD=windows ARCHOPTS=-march=native PTR64=1 NOWERROR=1 Linking obj/windows64/build/vconv.exe... Archiving obj/windows64/libocore.a... Archiving obj/windows64/libutil.a... Archiving obj/windows64/libz.a... Archiving obj/windows64/libflac.a... Archiving obj/windows64/lib7z.a... Linking obj/windows64/build/verinfo.exe... Linking obj/windows64/build/m68kmake.exe... Archiving obj/windows64/mame/acorn.a... Archiving obj/windows64/mame/alba.a... Archiving obj/windows64/mame/alpha.a... Archiving obj/windows64/mame/amiga.a... Archiving obj/windows64/mame/ascii.a... Archiving obj/windows64/mame/atlus.a... Archiving obj/windows64/mame/bmc.a... Archiving obj/windows64/mame/comad.a... Archiving obj/windows64/mame/cvs.a... Archiving obj/windows64/mame/dataeast.a... Archiving obj/windows64/mame/dgrm.a... Archiving obj/windows64/mame/dooyong.a... Archiving obj/windows64/mame/dynax.a... Archiving obj/windows64/mame/edevices.a... Archiving obj/windows64/mame/eolith.a... Archiving obj/windows64/mame/f32.a... Archiving obj/windows64/mame/fuuki.a... Archiving obj/windows64/mame/gaelco.a... Archiving obj/windows64/mame/gameplan.a... Archiving obj/windows64/mame/gottlieb.a... Archiving obj/windows64/mame/ibmpc.a... Archiving obj/windows64/mame/irem.a... Archiving obj/windows64/mame/itech.a... Archiving obj/windows64/mame/kaneko.a... Archiving obj/windows64/mame/metro.a... Archiving obj/windows64/mame/nasco.a... Archiving obj/windows64/mame/nintendo.a... Archiving obj/windows64/mame/nix.a... Archiving obj/windows64/mame/nmk.a... Archiving obj/windows64/mame/omori.a... Archiving obj/windows64/mame/orca.a... Archiving obj/windows64/mame/pacific.a... Archiving obj/windows64/mame/pacman.a... Archiving obj/windows64/mame/pce.a... Archiving obj/windows64/mame/phoenix.a... Archiving obj/windows64/mame/psikyo.a... Archiving obj/windows64/mame/rare.a... Archiving obj/windows64/mame/sanritsu.a... Archiving obj/windows64/mame/seibu.a... Archiving obj/windows64/mame/seta.a... Archiving obj/windows64/mame/snk.a... Archiving obj/windows64/mame/sony.a... Archiving obj/windows64/mame/stern.a... Archiving obj/windows64/mame/sun.a... Archiving obj/windows64/mame/suna.a... Archiving obj/windows64/mame/tch.a... Archiving obj/windows64/mame/technos.a... Archiving obj/windows64/mame/thepit.a... Archiving obj/windows64/mame/toaplan.a... Archiving obj/windows64/mame/tong.a... Archiving obj/windows64/mame/unico.a... Archiving obj/windows64/mame/univers.a... Archiving obj/windows64/mame/upl.a... Archiving obj/windows64/mame/valadon.a... Archiving obj/windows64/mame/venture.a... Archiving obj/windows64/mame/vsystem.a... Archiving obj/windows64/mame/yunsung.a... Archiving obj/windows64/mame/shared.a... Compiling src/osd/windows/video.c... Generating H8-300 source file... src/emu/cpu/cpu.mak:650: recipe for target 'obj/windows64/emu/cpu/h8/h8.inc' failed process_begin: CreateProcess(NULL, python src/emu/cpu/h8/h8make.py src/emu/cpu/h8/h8.lst o obj/windows64/emu/cpu/h8/h8.inc, ...) failed. make (e=2): The system cannot find the file specified. make: *** [obj/windows64/emu/cpu/h8/h8.inc] Error 2 make: *** Waiting for unfinished jobs....
Recommended Posts
Archived
This topic is now archived and is closed to further replies.