|
No longer possible to run MAME on a single thread?
#379353 - 11/04/18 05:22 AM
|
|
|
Basically what the subject says. The -multithread option is gone, so it looks like MAME assigns affinity automatically but is there a way to force it into a single thread?
|
|
|
|
Re: No longer possible to run MAME on a single thread?
[Re: "The Manuel"]
#379354 - 11/04/18 05:53 AM
|
|
|
> Basically what the subject says. The -multithread option is gone, so it looks like > MAME assigns affinity automatically but is there a way to force it into a single > thread?
That option never forced MAME to a single thread. All it did was enable/disable asynchronous blit. MAME could still spawn additional threads for triangle rendering, discrete matrix solvers, etc. when it was disabled. The asynchronous blit feature has been removed completely, so MAME will never create a thread for that any more.
There are environment variables you can set to control the number of threads created for matrix solvers and triangle rendering, but I can't remember what they are.
It's not possible to stop MAME from creating a thread to handle output notifiers and HTTP server.
|
|
|
|
Re: No longer possible to run MAME on a single thread?
[Re: Vas Crabb]
#379355 - 11/04/18 06:10 AM
|
|
|
OK. Thanks for the info.
One more, unrelated: It seems like with BGFX, triplebuffer doesn't work. The test I made was to disable throttling and enabling triplebuffer. In D3D, this keeps the framerate in sync with the monitor's RR but not with BGFX.
|
|
|
|
Re: No longer possible to run MAME on a single thread?
[Re: "The Manuel"]
#379366 - 11/04/18 11:00 PM
|
|
|
The triplebuffer option only applies to the D3D driver.
|
|
|
|
Re: No longer possible to run MAME on a single thread?
[Re: anikom15]
#379374 - 11/05/18 03:09 AM
|
|
|
Oh, got it. I had read it was a windows only option in the MAME doc site but did not realize it was limited to D3D. It all makes sense now.
Thanks for bringing me up to speed.
|
|
|