Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06463 Interface Minor Always Dec 29, 2016, 12:10 Dec 29, 2016, 15:05
Tester Tatsuya79 View Status Public Platform MAME (Official Binary)
Assigned To Resolution No change required OS Windows Vista/7/8 (64-bit)
Status [?] Closed Driver
Version 0.181 Fixed in Version Build 64-bit
Summary 06463: Brightness & Contrast values in custom ini files get ignored
Description Outside of mame.ini, when using a particular game / driver ini, brightness and contrast values aren't working.
Steps To Reproduce I tried to create a segas16a.ini with:
brightness 0.67
contrast 1.6
I launched aliensynjo and looked at slider option; brightness and contrast are at 1.0 unaffected.

I made an aliensynjo.ini with those same values.
Got the contrast value working once, then nothing at a second launch! Brightness is ignored.

Same behaviour in opengl or bgfx.
mame.ini works.
Additional Information
Flags
Regression Version
Affected Sets / Systems
Attached Files
 
Relationships
There are no relationsihp linked to this issue.
Notes
3
User avatar
No.13516
Tafoid
Administrator
Dec 29, 2016, 14:06
As far as I am aware in your instance, the segas16a.ini should be in a "source" subfolder in order to be taken correctly.
This differential was needed due to some source/driver names being the same as setnames and still requiring separation of the two.

From 0.179 development we had this commit:
https://mail.google.com/mail/u/0/?tab=wm#search/source.ini/157dbd824484aaac
It addressed a long standing issue of what I mentioned above - same setname/driver instances and the need to separate them, as noted in 03045

So, just create a folder in your INI called "source" and place the sega16a.ini file in there and it should work as expected.
User avatar
No.13518
Tatsuya79
Tester
Dec 29, 2016, 14:48
Oh thanks that's working!
It's hard to notice such changes sometimes.

I notice that the game ini works now if I remove the misplaced segas16a.ini.
User avatar
No.13519
Tafoid
Administrator
Dec 29, 2016, 15:04
Since this isn't a bug, I'm closing the report.
Glad it is working for you now.