OLD MESS - Revision history

Butter100fly: Butter100fly moved page MESS to OLD MESS without leaving a redirect

2017-11-21T19:54:19Z

Butter100fly moved page MESS to OLD MESS without leaving a redirect

← Older revision	Revision as of 19:54, 21 November 2017
(No difference)

Butter100fly at 22:39, 16 May 2017

2017-05-16T22:39:57Z

← Older revision		Revision as of 22:39, 16 May 2017
Line 136:		Line 136:
	* For Retroarch, because I went for the 'experimental' command line option to get things working, you have every system, but bear in mind that RetroArch's stuff takes precidence over MAME's stuff, which can be good and bad. Its bad when you want to access a keyboard key for a computer but its been mapped to 'Fullscreen' in RetroArch for instance (you might still be able to use the MAME menu for lock the keyboard out, haven't tried yet)		* For Retroarch, because I went for the 'experimental' command line option to get things working, you have every system, but bear in mind that RetroArch's stuff takes precidence over MAME's stuff, which can be good and bad. Its bad when you want to access a keyboard key for a computer but its been mapped to 'Fullscreen' in RetroArch for instance (you might still be able to use the MAME menu for lock the keyboard out, haven't tried yet)

	* Writeconfig in the mame ini is always a problem. Ideally you want it on (set to 1) so you can simply make computers and things work (you ALWAYS need to change keymaps for one reason or another), but once its on everything you do gets saved. The most annoying is that the last game stays loaded in whatever device it was in, causing havoc. To make matters worse, MAME's ini system is a Class-Objectbased one, meaning that if you have writeconfig enabled, every time you play a system, a new config is going to get saved based on the current state of the master mame.ini, so you're going to get lots of subtly different ini files in your ini folder over time. I don't have a great solution for this, but I know you need to do something! Ultimately you CAN'T have writeconfig turned on. I suggest you only turn writeconfig on when you have a few hours, and then spend those hours trying to setup the keys etc on every emulator you care about. Then turn writeconfig off (and that means in ALL the inis you have ~~madein~~ those few hours, since every one you created now has writeconfig set to 1 - so notepad++ search and replace), only enabling it when you need to change configuration on a machine. For RetroArch, if you can't be bothered with the hassle, just make sure its off (which it is by default in retroarch's core options). Retroarch maps keys for you....		* Writeconfig in the mame ini is always a problem. Ideally you want it on (set to 1) so you can simply make computers and things work (you ALWAYS need to change keymaps for one reason or another), but once its on everything you do gets saved. The most annoying is that the last game stays loaded in whatever device it was in, causing havoc. To make matters worse, MAME's ini system is a Class-Objectbased one, meaning that if you have writeconfig enabled, every time you play a system, a new config is going to get saved based on the current state of the master mame.ini, so you're going to get lots of subtly different ini files in your ini folder over time. I don't have a great solution for this, but I know you need to do something! Ultimately you CAN'T have writeconfig turned on. I suggest you only turn writeconfig on when you have a few hours, and then spend those hours trying to setup the keys etc on every emulator you care about. Then turn writeconfig off (and that means in ALL the inis you have made in those last few hours, since every one you created now has writeconfig set to 1 - so notepad++ search and replace), only enabling it when you need to change configuration on a machine. For RetroArch, if you can't be bothered with the hassle, just make sure its off (which it is by default in retroarch's core options). Retroarch maps keys for you....

	[[File:MAME-MESS-PV1000.png\|500px]]		[[File:MAME-MESS-PV1000.png\|500px]]
	[[File:RetroArch-MESS-x68000.png\|500px]]		[[File:RetroArch-MESS-x68000.png\|500px]]

Butter100fly at 22:35, 16 May 2017

2017-05-16T22:35:17Z

← Older revision		Revision as of 22:35, 16 May 2017
Line 136:		Line 136:
	* For Retroarch, because I went for the 'experimental' command line option to get things working, you have every system, but bear in mind that RetroArch's stuff takes precidence over MAME's stuff, which can be good and bad. Its bad when you want to access a keyboard key for a computer but its been mapped to 'Fullscreen' in RetroArch for instance (you might still be able to use the MAME menu for lock the keyboard out, haven't tried yet)		* For Retroarch, because I went for the 'experimental' command line option to get things working, you have every system, but bear in mind that RetroArch's stuff takes precidence over MAME's stuff, which can be good and bad. Its bad when you want to access a keyboard key for a computer but its been mapped to 'Fullscreen' in RetroArch for instance (you might still be able to use the MAME menu for lock the keyboard out, haven't tried yet)

	* Writeconfig in the mame ini is always a problem. Ideally you want it on (set to 1) so you can simply make computers and things work (you ALWAYS need to change keymaps for one reason or another), but once its on everything you do gets saved. The most annoying is that the last game stays loaded in whatever device it was in, causing havoc. To make matters worse, MAME's ini system is a Class-Objectbased one, meaning that if you have writeconfig enabled, every time you play a system, a new config is going to get saved based on the current state of the master mame.ini, so you're going to ~~getlots~~ of subtly different ini files in your ini folder over time. I don't have a great solution for this, but I know you need to do something! Ultimately you CAN'T have writeconfig turned on. I suggest you turn writeconfig on, and then spend ~~a couple of~~ hours trying to setup the keys etc on every emulator you care about. Then turn writeconfig off (and that means in ALL the inis you have, since every one you created now has writeconfig set to 1) - so notepad++ search and replace), only enabling it when you need to change configuration on a machine. For RetroArch, if you can't be bothered with the hassle, just make sure its off (which it is by default in retroarch's core options). Retroarch maps keys for you....		* Writeconfig in the mame ini is always a problem. Ideally you want it on (set to 1) so you can simply make computers and things work (you ALWAYS need to change keymaps for one reason or another), but once its on everything you do gets saved. The most annoying is that the last game stays loaded in whatever device it was in, causing havoc. To make matters worse, MAME's ini system is a Class-Objectbased one, meaning that if you have writeconfig enabled, every time you play a system, a new config is going to get saved based on the current state of the master mame.ini, so you're going to get lots of subtly different ini files in your ini folder over time. I don't have a great solution for this, but I know you need to do something! Ultimately you CAN'T have writeconfig turned on. I suggest you only turn writeconfig on when you have a few hours, and then spend those hours trying to setup the keys etc on every emulator you care about. Then turn writeconfig off (and that means in ALL the inis you have madein those few hours, since every one you created now has writeconfig set to 1 - so notepad++ search and replace), only enabling it when you need to change configuration on a machine. For RetroArch, if you can't be bothered with the hassle, just make sure its off (which it is by default in retroarch's core options). Retroarch maps keys for you....

	[[File:MAME-MESS-PV1000.png\|500px]]		[[File:MAME-MESS-PV1000.png\|500px]]
	[[File:RetroArch-MESS-x68000.png\|500px]]		[[File:RetroArch-MESS-x68000.png\|500px]]

Butter100fly at 22:32, 16 May 2017

2017-05-16T22:32:50Z

← Older revision		Revision as of 22:32, 16 May 2017
Line 136:		Line 136:
	* For Retroarch, because I went for the 'experimental' command line option to get things working, you have every system, but bear in mind that RetroArch's stuff takes precidence over MAME's stuff, which can be good and bad. Its bad when you want to access a keyboard key for a computer but its been mapped to 'Fullscreen' in RetroArch for instance (you might still be able to use the MAME menu for lock the keyboard out, haven't tried yet)		* For Retroarch, because I went for the 'experimental' command line option to get things working, you have every system, but bear in mind that RetroArch's stuff takes precidence over MAME's stuff, which can be good and bad. Its bad when you want to access a keyboard key for a computer but its been mapped to 'Fullscreen' in RetroArch for instance (you might still be able to use the MAME menu for lock the keyboard out, haven't tried yet)

	* Writeconfig in the mame ini is always a problem. Ideally you want it on (set to 1) so you can simply make computers and things work (you ALWAYS need to change keymaps for one reason or another), but once its on everything you do gets saved. The most annoying is that the last game stays loaded in whatever device it was in, causing havoc. To make matters worse, MAME's ini system is a Class-Objectbased one, meaning that if you have writeconfig enabled, every time you play a system, a new config is going to get saved based on the current state of the master mame.ini, so you're going to getlots of subtly different ini files in your ini folder over time. I don't have a great solution for this, but I know you need to do something! Ultimately you CAN'T have writeconfig turned on. I suggest you turn writeconfig on, and then spend a couple of hours trying to setup the keys etc on every emulator you care about. Then turn writeconfig off (and that means in ALL the inis you have, since every one you created now has writeconfig set to 1)		* Writeconfig in the mame ini is always a problem. Ideally you want it on (set to 1) so you can simply make computers and things work (you ALWAYS need to change keymaps for one reason or another), but once its on everything you do gets saved. The most annoying is that the last game stays loaded in whatever device it was in, causing havoc. To make matters worse, MAME's ini system is a Class-Objectbased one, meaning that if you have writeconfig enabled, every time you play a system, a new config is going to get saved based on the current state of the master mame.ini, so you're going to getlots of subtly different ini files in your ini folder over time. I don't have a great solution for this, but I know you need to do something! Ultimately you CAN'T have writeconfig turned on. I suggest you turn writeconfig on, and then spend a couple of hours trying to setup the keys etc on every emulator you care about. Then turn writeconfig off (and that means in ALL the inis you have, since every one you created now has writeconfig set to 1) - so notepad++ search and replace), only enabling it when you need to change configuration on a machine. For RetroArch, if you can't be bothered with the hassle, just make sure its off (which it is by default in retroarch's core options). Retroarch maps keys for you....
	- so notepad++ search and replace), only enabling it when you need to change configuration on a machine. For RetroArch, if you can't be bothered with the hassle, just make sure its off (which it is by default in retroarch's core options). Retroarch maps keys for you....

	[[File:MAME-MESS-PV1000.png\|500px]]		[[File:MAME-MESS-PV1000.png\|500px]]
	[[File:RetroArch-MESS-x68000.png\|500px]]		[[File:RetroArch-MESS-x68000.png\|500px]]

Butter100fly: /* Tips */

2017-05-16T22:31:35Z

Tips

← Older revision		Revision as of 22:31, 16 May 2017
Line 136:		Line 136:
	* For Retroarch, because I went for the 'experimental' command line option to get things working, you have every system, but bear in mind that RetroArch's stuff takes precidence over MAME's stuff, which can be good and bad. Its bad when you want to access a keyboard key for a computer but its been mapped to 'Fullscreen' in RetroArch for instance (you might still be able to use the MAME menu for lock the keyboard out, haven't tried yet)		* For Retroarch, because I went for the 'experimental' command line option to get things working, you have every system, but bear in mind that RetroArch's stuff takes precidence over MAME's stuff, which can be good and bad. Its bad when you want to access a keyboard key for a computer but its been mapped to 'Fullscreen' in RetroArch for instance (you might still be able to use the MAME menu for lock the keyboard out, haven't tried yet)

	* Writeconfig in the mame ini is always a problem. Ideally you want it on (set to 1) so you can simply make computers and things work (you ALWAYS need to change keymaps for one reason or another), but once its on everything you do gets saved. The most annoying is that the last game stays loaded in whatever device it was in, causing havoc. To make matters worse, MAME's ini system is a Class-Objectbased one, meaning that if you have writeconfig enabled, every time you play a system, a new config is going to get saved based on the current state of the master mame.ini, so you're going to getlots of subtly different ini files in your ini folder over time.		* Writeconfig in the mame ini is always a problem. Ideally you want it on (set to 1) so you can simply make computers and things work (you ALWAYS need to change keymaps for one reason or another), but once its on everything you do gets saved. The most annoying is that the last game stays loaded in whatever device it was in, causing havoc. To make matters worse, MAME's ini system is a Class-Objectbased one, meaning that if you have writeconfig enabled, every time you play a system, a new config is going to get saved based on the current state of the master mame.ini, so you're going to getlots of subtly different ini files in your ini folder over time. I don't have a great solution for this, but I know you need to do something! Ultimately you CAN'T have writeconfig turned on. I suggest you turn writeconfig on, and then spend a couple of hours trying to setup the keys etc on every emulator you care about. Then turn writeconfig off (and that means in ALL the inis you have, since every one you created now has writeconfig set to 1)
			- so notepad++ search and replace), only enabling it when you need to change configuration on a machine. For RetroArch, if you can't be bothered with the hassle, just make sure its off (which it is by default in retroarch's core options). Retroarch maps keys for you....
	I don't have a great solution for this, but I know you need to do something! Ultimately you CAN'T have writeconfig turned on. I suggest you turn writeconfig on, and then spend a couple of hours trying to setup the keys etc on every emulator you care about. Then turn writeconfig off (and that means in ALL the inis you have, since every one you created now has writeconfig set to 1)
	- so notepad++ search and replace), only enabling it when you need to change configuration on a machine.

	For RetroArch, if you can't be bothered with the hassle, just make sure its off (which it is by default in retroarch's core options). Retroarch maps keys for you....

	[[File:MAME-MESS-PV1000.png\|500px]]		[[File:MAME-MESS-PV1000.png\|500px]]
	[[File:RetroArch-MESS-x68000.png\|500px]]		[[File:RetroArch-MESS-x68000.png\|500px]]

Butter100fly at 22:30, 16 May 2017

2017-05-16T22:30:43Z

← Older revision		Revision as of 22:30, 16 May 2017
Line 134:		Line 134:

	===Tips===		===Tips===
	* For Retroarch, because I went for the 'experimental' command line option to get things working, you have every system, but bear in mind that RetroArch's stuff takes precidence over MAME's stuff, which can		* For Retroarch, because I went for the 'experimental' command line option to get things working, you have every system, but bear in mind that RetroArch's stuff takes precidence over MAME's stuff, which can be good and bad. Its bad when you want to access a keyboard key for a computer but its been mapped to 'Fullscreen' in RetroArch for instance (you might still be able to use the MAME menu for lock the keyboard out, haven't tried yet)
	be good and bad. Its bad when you want to access a keyboard key for a computer but its been mapped to 'Fullscreen' for instance (you might still be able to use the MAME menu for lock the keyboard out, haven't tried yet)

	* Writeconfig in the mame ini is always a problem. Ideally you want it on (set to 1) so you can simply make computers and things work (you ALWAYS need to change keymaps for one reason or another), but once its on everything you do gets saved. The most annoying is that the last game stays loaded in whatever device it was in, causing havoc. To make matters worse, MAME's ini system is a Class-Objectbased one, meaning that if you have writeconfig enabled, every time you play a system, a new config is going to get saved based on the current state of the master mame.ini, so you're going to getlots of subtly different ini files in your ini folder over time.		* Writeconfig in the mame ini is always a problem. Ideally you want it on (set to 1) so you can simply make computers and things work (you ALWAYS need to change keymaps for one reason or another), but once its on everything you do gets saved. The most annoying is that the last game stays loaded in whatever device it was in, causing havoc. To make matters worse, MAME's ini system is a Class-Objectbased one, meaning that if you have writeconfig enabled, every time you play a system, a new config is going to get saved based on the current state of the master mame.ini, so you're going to getlots of subtly different ini files in your ini folder over time.

Butter100fly at 22:24, 16 May 2017

2017-05-16T22:24:58Z

← Older revision		Revision as of 22:24, 16 May 2017
Line 122:		Line 122:
	and load all softlists		and load all softlists

	FAQ		===FAQ===
	* Can I make my own softlist folders/MAME emulators using some tool?		* Can I make my own softlist folders/MAME emulators using some tool?
	No, not at the moment, its on the roadmap. I promise to keep this up to date		No, not at the moment, its on the roadmap. I promise to keep this up to date
Line 133:		Line 133:
	(You can right click a rom in QuickPlay to show you the command-line its going to run, and right click the command line to copy it)		(You can right click a rom in QuickPlay to show you the command-line its going to run, and right click the command line to copy it)

	Tips		===Tips===
	* For Retroarch, because I went for the 'experimental' command line option to get things working, you have every system, but bear in mind that RetroArch's stuff takes precidence over MAME's stuff, which can		* For Retroarch, because I went for the 'experimental' command line option to get things working, you have every system, but bear in mind that RetroArch's stuff takes precidence over MAME's stuff, which can
	be good and bad. Its bad when you want to access a keyboard key for a computer but its been mapped to 'Fullscreen' for instance (you might still be able to use the MAME menu for lock the keyboard out, haven't tried yet)		be good and bad. Its bad when you want to access a keyboard key for a computer but its been mapped to 'Fullscreen' for instance (you might still be able to use the MAME menu for lock the keyboard out, haven't tried yet)

Butter100fly at 16:04, 7 May 2017

2017-05-07T16:04:13Z

← Older revision		Revision as of 16:04, 7 May 2017
Line 117:		Line 117:
	* Put the path to your mame roms in that ini file, so in my case i went		* Put the path to your mame roms in that ini file, so in my case i went
	rompath "F:\MAME\ROMS"		rompath "F:\MAME\ROMS"
	(your software list roms should be in that path). Setup additional stuff as you like		(your software list roms should be in that path). Setup additional stuff as you like

	* Now retroarch knows where your games are, you can send MAME arguments as you would do with MAME natively, and you can access the MAME menu when you're playing games. Which means you can play all emulators		* Now retroarch knows where your games are, you can send MAME arguments as you would do with MAME natively, and you can access the MAME menu when you're playing games. Which means you can play all emulators

Butter100fly at 15:40, 7 May 2017

2017-05-07T15:40:44Z

← Older revision		Revision as of 15:40, 7 May 2017
Line 1:		Line 1:

	[[File:MAME-MESS-a2600.png]\|500px]		[[File:MAME-MESS-a2600.png\|500px]]
	[[File:MAME-MESS-MSX.png\|500px]]		[[File:MAME-MESS-MSX.png\|500px]]

Butter100fly at 15:26, 7 May 2017

2017-05-07T15:26:45Z

← Older revision		Revision as of 15:26, 7 May 2017
Line 137:		Line 137:
	be good and bad. Its bad when you want to access a keyboard key for a computer but its been mapped to 'Fullscreen' for instance (you might still be able to use the MAME menu for lock the keyboard out, haven't tried yet)		be good and bad. Its bad when you want to access a keyboard key for a computer but its been mapped to 'Fullscreen' for instance (you might still be able to use the MAME menu for lock the keyboard out, haven't tried yet)

	* Writeconfig in the mame ini is always a problem. Ideally you want it on (set to 1) so you can simply make computers and things work (you ALWAYS need to change keymaps for one reason or another), but		* Writeconfig in the mame ini is always a problem. Ideally you want it on (set to 1) so you can simply make computers and things work (you ALWAYS need to change keymaps for one reason or another), but once its on everything you do gets saved. The most annoying is that the last game stays loaded in whatever device it was in, causing havoc. To make matters worse, MAME's ini system is a Class-Objectbased one, meaning that if you have writeconfig enabled, every time you play a system, a new config is going to get saved based on the current state of the master mame.ini, so you're going to getlots of subtly different ini files in your ini folder over time.
	once its on everything you do gets saved. The most annoying is that the last game stays loaded in whatever device it was in, causing havoc. To make matters worse, MAME's ini system is a Class-~~Object~~
	~~based~~ one, meaning that if you have writeconfig enabled, every time you play a system, a new config is going to get saved based on the current state of the master mame.ini, so you're going to ~~get~~		I don't have a great solution for this, but I know you need to do something! Ultimately you CAN'T have writeconfig turned on. I suggest you turn writeconfig on, and then spend a couple of hours trying to setup the keys etc on every emulator you care about. Then turn writeconfig off (and that means in ALL the inis you have, since every one you created now has writeconfig set to 1)
	~~lots~~ of subtly different ini files in your ini folder over time. I don't have a great solution for this, but I know you need to do something! Ultimately you CAN'T have writeconfig turned on. I suggest you turn writeconfig on,
	and then spend a couple of hours trying to setup the keys etc on every emulator you care about. Then turn writeconfig off (and that means in ALL the inis you have, since every one you created now has writeconfig set to 1)
	- so notepad++ search and replace), only enabling it when you need to change configuration on a machine.		- so notepad++ search and replace), only enabling it when you need to change configuration on a machine.

	For ~~retroarch~~, if you can't be bothered with the hassle, just make sure its off (~~its at the top of mame.ini~~). Retroarch maps ~~the~~ keys for you~~, so hey~~...		For RetroArch, if you can't be bothered with the hassle, just make sure its off (which it is by default in retroarch's core options). Retroarch maps keys for you....

	[[File:MAME-MESS-PV1000.png\|500px]]		[[File:MAME-MESS-PV1000.png\|500px]]
	[[File:RetroArch-MESS-x68000.png\|500px]]		[[File:RetroArch-MESS-x68000.png\|500px]]