07342: HLSL with any vector based game: HLSL is not able anymore to show points of vector objects.

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07342	Image Enhancement	Minor	Always	May 29, 2019, 15:12	Jun 18, 2020, 19:18

Tester	u-man	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	Open	OS	Windows 10 (64-bit)
Status [?]	Acknowledged			Driver
Version	0.209	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	07342: HLSL with any vector based game: HLSL is not able anymore to show points of vector objects.
Description	HLSL is not able anymore to show points of vector objects. I do not mean points in general. I mean the points from a drawn object: lines, triangles, rectangles etc.
Steps To Reproduce	start any vector game with enabled HLSL. start any vector game with enabled software rendering for comparison.
Additional Information	I can not tell what the reason/change for this problem is, but losing point drawing for vectors, is losing a essential characteristic in any vector based game.
Github Commit

Flags
Regression Version	0.180
Affected Sets / Systems	HLSL with any vector based game

Attached Files

No.16486 u-man Tester May 29, 2019, 15:19	This is the reason, why we FIRST need a complete HLSL port to BGFX, before any new shaders or changes are added to BGFX. MAME and HLSL is the only program, that features FX for vector-games. It would be a shame, if that would be ditched in favor for BGFX.
No.16487 Tafoid Administrator May 29, 2019, 15:42	What version is this being reported against. It is expected that people report using the latest released binary from mamedev.org, but you reported 0.202. Can you confirm/change your entry for release version to match the latest version you've experienced regression with? Also, no need to flag something for 32-bit and 64-bit both - unless it is an issue EXPLICIT to a certain build, no need to add those flags.
No.16489 u-man Tester May 29, 2019, 18:38 edited on: May 29, 2019, 19:01	Sorry for the mistakes. The reported bug exists since 0.180 till today. No exceptions. Next time no flags, unless it is explicit... promised. The reason why i even reported this, is for any "remaining" future conversions from HLSL to BGFX, because it would not be enough, just to convert "current" HLSL .fx files.
No.16491 Tafoid Administrator May 29, 2019, 19:03 edited on: May 29, 2019, 19:05	So, you are asserting that 0.180 is the latest tested version you checked? This will not do. The regression version field is for the noticed version where the regression took place. If you are also stating 0.180 as the last tested version, that is nearly 30 months of releases where a bug could have been fixed. Please only report things if found confirmed in the most recent integer release and make sure that version is reported. That's all I care is that the user took the time to make sure current releases are still behaving the same.
No.16492 u-man Tester May 29, 2019, 19:06	Dude, i thought it is clear what i said. It started at 0.180 and persists till latest MAME 0.209 .
No.16493 Tafoid Administrator May 29, 2019, 21:07	You mention that in your note, but the report has 0.180 as the reported version - that is what I was referring to. Your reporting version should be the last version you tested (0.209). I've changed that in your report. I'm just trying to let you know that there are expectations here.