07784: vulgus and clones: gameplay too slow shot the cannon (only UI port)

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07784	Gameplay	Major	Always	Nov 8, 2020, 11:27	Nov 12, 2020, 08:10

Tester	J.J.Boy	View Status	Public	Platform	MAME (Unofficial Binary)
Assigned To	Robbbert	Resolution	Fixed	OS	Windows 10 (32-bit)
Status [?]	Resolved			Driver	capcom/vulgus.cpp
Version	0.226	Fixed in Version	0.227	Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	07784: vulgus and clones: gameplay too slow shot the cannon (only UI port)
Description	Official MAME binary is OK,but MAMEUI64 and ARCADE64 are BAD.
Steps To Reproduce
Additional Information	video recording with windows10 xbox game bar (because mame can't record this move)
Github Commit

Flags
Regression Version
Affected Sets / Systems	vulgus and clones

Attached Files	vulgus.mp4 (2,251,658 bytes) Nov 8, 2020, 11:27 Uploaded by J.J.Boy

No.18137 Robbbert Senior Tester Nov 8, 2020, 12:26	Unable to confirm. Tested both MAMEUI64 and ARCADE64, no slowdown when the cannon was fired.
No.18139 Tafoid Administrator Nov 8, 2020, 23:38 edited on: Nov 8, 2020, 23:49	Unable to duplicate with baseline MAME and I tried a few recent release versions to check for slowdown you show in video. I also checked a fresh install of 0.226 to check arcade64/mameui and still no duplication here. Robbbert, who maintains the UI/Arcade builds, says it isn't happening for him - I'm not sure what to suggest. All my attempts to watch demo and even play all showed 100% speed. What are your system specs? There is zero reason that I can discern, emulation wise, that this action should cause your to drop your emulation speed so drastically. I can only suggest that it may have something to do with your input triggering perhaps a Windows option or something outside of MAME. Try a fresh install and see how that goes or try remapping to other keys or taking any external controllers out of the loop entirely. I'll leave open for a short time for a response.
No.18140 J.J.Boy Tester Nov 9, 2020, 05:46	testing HW info: Core i5-10210Y 16GB (Onenetbook Onemix3Pro) Windows10 home 64bit And I had a new awareness. ARCADE64/MAMEUI boot from cmd ...FINE! boot from UI ...NOT fine.
No.18148 Robbbert Senior Tester Nov 11, 2020, 07:51	I don't think this report should exist at MT, because it only involves derivatives. However, others can make the final judgement. Now, as to the actual problem, it is confirmed in MAMEUI64 and ARCADE64, when running the game from the menu. Tracing revealed that when the cannon is fired, it causes the AY8910 to issue a storm of "EShape" messages into the verbose log. Now, winui's verbose handler is not very efficient, because on every call it has to open "verbose.log", write the information, fflush and close it. So, due to this storm, the game would stutter. MAME uses a different method which is why the issue isn't noticed there. Now, winui is not considered a development environment, and so debug messages can be removed with impunity. So, the "EShape" message has been commented out (in MAMEUI and ARCADE only), thereby fixing the problem.
No.18149 hap Developer Nov 11, 2020, 09:10	Yeah, that message can be removed from mainline MAME too. Is it an old leftover from someone's testing? Arcade games don't use envelopes much. But it's often used on homecomputers.
No.18150 Tafoid Administrator Nov 11, 2020, 12:25	This was way back when Couriersud was working on ay8910 sound chip over a decade ago - 03043 Not sure if anything came of it but I remember spending a lot of time looking for and logging those messages.