07333: bbusters and clones: Strange players AI behaviour in attract mode of Beast Busters world version.

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07333	Gameplay	Minor	Always	May 24, 2019, 01:51	May 28, 2019, 15:49

Tester	VasiliyFamiliya	View Status	Public	Platform	MAME (Official Binary)
Assigned To	Duke	Resolution	Fixed	OS	Windows 10 (64-bit)
Status [?]	Resolved			Driver	snk/bbusters.cpp
Version	0.209	Fixed in Version	0.211	Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	07333: bbusters and clones: Strange players AI behaviour in attract mode of Beast Busters world version.
Description	All 3 players are concentrating their fire in the right bottom corner of the screen mainly, and destroying the zombies exclusively using a grenades almost.
Steps To Reproduce	Just wait till gameplay demonstration begin.
Additional Information	The bug video is here: https://yadi.sk/i/W7lOdHZJeByhdw
Github Commit

Flags
Regression Version	0.128u4
Affected Sets / Systems	bbusters and clones

Attached Files

No.16468 Hydreigon Tester May 24, 2019, 02:30	This is how the demo mode behaves on actual hardware.
No.16469 Robbbert Senior Tester May 24, 2019, 05:37	From: http://www.mameworld.info/ubbthreads/showflat.php?Cat=&Number=382541
No.16470 Osso Moderator May 24, 2019, 06:38 edited on: May 24, 2019, 06:58	It doesn't do it if you disable the default EEPROM provided in the driver, so it's probably something in there that the World version doesn't like. I'll see if I can create a default EEPROM which still works and doesn't cause this bug. Edit: nope, it seems it doesn't like the values written to the EEPROM after calibration.
No.16472 Tafoid Administrator May 24, 2019, 07:05 edited on: May 24, 2019, 08:08	I've traced the version it first started happening, 0.143u8. Looking at the files touched during that update, I can only conclude either 68k change(s) or Core Input Changes might be at play. EDIT I was mistaken Issue I found was related to the nvram as it changed locations in that version "nvram\bbusters.nv" vs. "nvram\bbusters\eeprom." So, in essence, I was using the nvram I had made before the regression and not deleting it until it forced it to not be seen by moving it's location. The 0.128-0.129 regression is correct, traced to 0.128u4
No.16473 MetalGod Senior Tester May 24, 2019, 08:49 edited on: May 24, 2019, 08:49	All the versions of the game affected, not only World version.
No.16483 Tafoid Administrator May 28, 2019, 15:49	Fixed. Please be sure to delete your current contents of nvram\bbusters in order for it to work properly.