|
CPS2 not loading settings
#382690 - 06/06/19 04:51 PM
|
|
|
It doesn't matter what you put inside ini\source\cps2.ini, mame just ignore it. I was testing my joystick with 'ctrlr' option but latter figure it out that it ignores whatever you save in there, last thing I try was:
Code:
gamma 0.1
No error, no warning, nothing.
|
|
|
| Dullaron |
|
Diablo III - Dunard #1884
|
|
|
|
|
Reged: 07/22/05
|
|
Posts: 6125
|
|
Loc: Fort Worth, Tx
|
|
|
|
Send PM
|
|
|
Re: CPS2 not loading settings
[Re: 7n004]
#382692 - 06/07/19 01:18 AM
|
|
|
> It doesn't matter what you put inside ini\source\cps2.ini, mame just ignore it. I was
> testing my joystick with 'ctrlr' option but latter figure it out that it ignores
> whatever you save in there, last thing I try was:
> gamma 0.1
>
> No error, no warning, nothing.
Download from https://www.mamedev.org/ and which version?
|
W11 Home 64-bit + Nobara OS / AMD Radeon RX 5700 XT / AMD Ryzen 7 3700X 8-Core 3.59 GHz / RAM 64 GB
|
|
|
Re: CPS2 not loading settings
[Re: Dullaron]
#382695 - 06/07/19 09:23 AM
|
|
|
> Download from https://www.mamedev.org/ and which version?
Mame 210 official build, Fedora Linux x64 (30)
This is really strange, my 'cfg' and 'ini' folders are populated with files, if I empty this folders and set a single cps2.ini file with a single setting, it works.
I will look further to pinpoint the pattern that is causing this.
|
|
|
|
Re: CPS2 not loading settings
[Re: 7n004]
#382698 - 06/07/19 09:34 PM
|
|
|
This is what causing all the trouble, there was a folder name 'source' at mame working directory that had a 'cps2.ini' file inside it with this settings:
Code:
filter 1
snapshot_directory snap/cps2
samplerate 32000
I don't remember why is there, maybe I was running some tests. If you set 'mame.ini' like this:
Code:
gamma 0.9
And in ini\source\cps2.ini like this:
Code:
gamma 0.1
Mame ignores both gamma settings and use default '1.0', matter of fact, mame ignores whatever settings you use in there, that is why mame was ignoring my joystick settings with 'ctrlr'.
Why mame reads ini files outside the ini directory if there is a inipath setting to point out the path to ini files?
Maybe this make sense in Windows but in Linux, our 'mame.ini' and main ini files goes at '$HOME/.mame', maybe removing '.' from the inipath could help I guess.
Anyway, this still don't explain why mame ignored both gamma settings (or my ctrlr setting) set on both 'mame.ini' and 'ini\source\cps2.ini'.
|
|
|
|
Re: CPS2 not loading settings
[Re: 7n004]
#382699 - 06/08/19 01:23 AM
|
|
|
Code:
C:\Emus\MAME> mame.exe sfa3 -verbose
Attempting load of mame.ini
Parsing mame.ini
Attempting load of mame.ini
Parsing mame.ini
Attempting load of horizont.ini
Attempting load of arcade.ini
Attempting load of raster.ini
Parsing raster.ini
Attempting load of source\cps2.ini
Attempting load of sfa3.ini
Starting plugin data...
Attempting load of mame.ini
Parsing mame.ini
Attempting load of mame.ini
Parsing mame.ini
Attempting load of horizont.ini
Attempting load of arcade.ini
Attempting load of raster.ini
Parsing raster.ini
Attempting load of source\cps2.ini
Attempting load of sfa3.ini
MAME by default has the INI string set as ".;ini;ini/presets". It doesn't matter the platform. That means it will look for current directory first (".\source\" included), then ".\ini\", then ".\ini\presets". When no ini, of course it will look for the best available. And it looks like the best available was "source\" because is near the executable root. If you want to avoid these kind of troubles I suggest you to avoid configuration collisions and pay more attention to the verbose command.
|
|
|
|
Re: CPS2 not loading settings
[Re: BIOS-D]
#382706 - 06/08/19 05:36 AM
|
|
|
> MAME by default has the INI string set as ".;ini;ini/presets". It doesn't matter the
> platform. That means it will look for current directory first (".\source\" included),
> then ".\ini\", then ".\ini\presets". When no ini, of course it will look for the best
> available. And it looks like the best available was "source\" because is near the
> executable root.
Well, in Linux platform the default is '$HOME/.mame;.;ini', that means it will look first at '$HOME/.mame' or '/home/username/.mame', working directory '.' (where the executable is located), then the 'ini' folder, there is no 'ini/presets' for Linux. If we would translate that to Windows environment we use the %HOME% variable like '%HOME%\mame;.;ini;ini/presets'.
>If you want to avoid these kind of troubles I suggest you to avoid
> configuration collisions and pay more attention to the verbose command.
This configuration conflict are expected according to mame own documentation:
https://docs.mamedev.org/advanced/multiconfig.html
What ever setting I put in those files, it will be in a direct conflict with the defaults in 'mame.ini', like setting a lower audio sample rate for an old computers that don't need 48 kHz.
This should not be a trouble, the documentation show one thing, when you do it for real it fails, mame didn't stack the settings as it should, it just ignores it. The verbose command didn't help at all, what helped me to understand what was wrong was an app called GLSOF that is a similar tool like Windows filemon.
|
|
|
|
Re: CPS2 not loading settings
[Re: 7n004]
#382707 - 06/08/19 06:50 AM
|
|
|
That's good to know considering I'm in the process to leave Windows for good (thanks telemetry). But my point still stands, you're over complicating simple things and you wouldn't have these issues if you keep it simple. And it's obvious you're over complicating things because you can't keep track of what you are doing and what the system expects. Either stick to config files per game, per system or at least don't collision cfg with ini files in extra abusive manners. Only a recommendation, less headache.
Remember: General INI first, then INIs per system come next, then CFG for every game come to the very end. It's useless to set a setting if you're gonna override it a next step after. Who sane enough configures mixer volumes before starting a game anyway? That's overboard useless.
|
|
|
|
Re: CPS2 not loading settings
[Re: BIOS-D]
#382708 - 06/08/19 01:58 PM
|
|
|
Hey BIOS-D!
> That's good to know considering I'm in the process to leave Windows for good (thanks
> telemetry).
At home I have 3 firewalls, one at desktop (TinyWall) and other two using OpenWRT+Iptables to counter Windows 10 telemetry and also using Spybot Anti-Beacon (among other tools) and local policy settings.[1][2]
And I started doing this after I noticed that my Samsung TV was accessing the internet while it was off back in 2012 way before Vault7, back in the day TV's didn't have mics but when you turn the TV off it start to access the internet and record audio of whatever happens in the room with their speakers. I've confirmed this by using tcpdump, there was audio data and codecs been transmitted to a remote amazon storage.
https://www.consumerreports.org/privacy/turn-off-samsung-tv-snooping/
https://www.wired.com/2017/03/worried-cia-hacked-samsung-tv-heres-tell/
To make matters worse, this also happens with LG, Sony and every single TV that is 'Smart'.
> But my point still stands, you're over complicating simple things and you
> wouldn't have these issues if you keep it simple. And it's obvious you're over
> complicating things because you can't keep track of what you are doing and what the
> system expects. Either stick to config files per game, per system or at least don't
> collision cfg with ini files in extra abusive manners. Only a recommendation, less
> headache.
I'm systematic and perfectionist, I like to have things in order and organized. In 'mame.ini' I set things that I'll not change like video/audio modes, etc. In 'arcade.ini' I set my CRT filters so all my arcade games has the CRT effect while this doesn't affect other systems, so on and so forth.
> Remember: General INI first, then INIs per system come next, then CFG for every game
> come to the very end. It's useless to set a setting if you're gonna override it a
> next step after.
Thanks!
> Who sane enough configures mixer volumes before starting a game
> anyway? That's overboard useless.
Actually it is not, that is why the controls are there after all. Let me explain.
If we take those CPS2 boards you can see it has a RCA audio output socket, the line level reference for this type of signal it's 0.316 Volts or -10dBv at 600 ohms, I'm not an Arcade specialist but I believe the Jamma audio signal follows the same line level reference. If we mesure the output audio levels from mame it's way too hot in comparison with that line level reference, mame sound output hits '-6dBv' and sometimes '0dBv'. CPS2 games hit over '-6dBv' this causes the sound to be over saturated or too loud some times and this over saturated signal causes distortion at the high frequency range like sound effects, explosions, etc. That is why I adjust it to match the real hardware sound levels.
The sound check/test available in some systems are there so you can level match the board output level with the power amplifier used. The 'BEATMANI' machines with that big speakers and subwoofers uses sine waves so you can adjust the correct 'dBv' levels with the power amp so when the music start pumping, it will be clean, powerful and free from distortion in all frequency ranges. This is nothing new, this level matching happens in studios, when you buy a new head unit for your car that uses a RCA cable to connect to your power amp.
That is why we need controls to adjust the sound levels by system and not per game because, for example, the electronics in a CPS2 board doesn't change, so the levels on a CPS2 board is the same for all other games.
The text it's too big already so:
https://www.youtube.com/watch?v=ZlT32D-0tRU
https://www.youtube.com/watch?v=O0VVWHjV130
That is why I adjust my levels. 
|
|
|
Previous 
Index 
Next 
Threaded 
CPS2 not loading settings
Reply
[Re: 
