03372: burnforc, burnforco: Refuses to show title on titlescreen.

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
03372	Graphics	Minor	Always	Aug 3, 2009, 12:58	Jun 27, 2013, 22:11

Tester	hap	View Status	Public	Platform
Assigned To	Phil Bennett	Resolution	Fixed	OS
Status [?]	Resolved			Driver	namco/namcos2.cpp
Version	0.133u1	Fixed in Version	0.145u1	Build
		Fixed in Git Commit		Github Pull Request #

Summary	03372: burnforc, burnforco: Refuses to show title on titlescreen.
Description	The titlescreen should include a zooming "Burning Force" and some small sprites scrolling by. This is probably POSIRQ timing related, hacking in a fix causes fourtrax to show glitches though (more severe than this one).
Steps To Reproduce
Additional Information
Github Commit

Flags
Regression Version	0.127u1
Affected Sets / Systems	burnforc, burnforco

Attached Files	0000.png (13,015 bytes) Aug 3, 2009, 13:10
	0001.png (18,113 bytes) Aug 3, 2009, 13:10
	burnforc.gif (61,092 bytes) Jun 27, 2013, 22:11 Uploaded by M.A.S.H.

No.04758 Tafoid Administrator Aug 3, 2009, 13:09	Confirmed regression version. Added screens of what it looks like (from 0.127).
No.04761 hap Developer Aug 3, 2009, 13:42	In 0.133 it was better than it is now: the title didn't show the 1st time, but after demo mode (and every time after that) it's fine. You could say it's a gradual regression :P
No.09046 haynor666 Tester Oct 20, 2012, 14:39	It works fine in 147u1 so I guess it might marked as fixed.
No.09047 hap Developer Oct 20, 2012, 18:00 edited on: Oct 20, 2012, 19:39	care to find out appoximately when it was fixed? edit ok, Tafoid took care of that =)
No.09623 M.A.S.H. Senior Tester Jun 27, 2013, 22:11	Burning Force has a broken waterline because of the changes in 0.145u1 (see gif). Source change in machine\namcos2.c line 500 from: pC148Reg[(addr>>13)&0x1f] = data&0x0007; to int reg = (addr >> 13) & 0x1f; // If writing an IRQ priority register, clear any pending IRQs. // Dirt Fox and Winning Run require this behaviour if (reg < 8) space.device().execute().set_input_line(pC148Reg[reg], CLEAR_LINE); pC148Reg[reg] = data & 0x0007; ---- If you changed it back to 0.145 the waterline is correct again!