Just as a quick test, I'm going to eject the existing fake projection and replace it with a mat*vec multiply with the layout you suggested. Worst case, there's another intervening matrix along the line that hasn't been ID'd yet. Best case, it still works! Thanks!
-
it's super confusing that they have .x,.y .w as well as .p[0] to .p[3]
I've been doing a pretty poor job of explaining the whole thing, but there is no .w, just .x and .y - any other interpolants (Z, W, anything else) get specified in a parameter array. https://github.com/mamedev/mame/blob/master/src/devices/video/poly.h … And, the driver itself: https://github.com/mamedev/mame/blob/master/src/mame/drivers/namcos23.cpp …pic.twitter.com/CVk2r0yHWJ
-
-
the mysterious 24 word packet that you originally posted, is that what these matrices look like typically or is it supposed to be weird for this game? what does it look like for a game that renders correctly?
-
Based on looking at the underlying game code, it appears to be a standard function that's used by each game to set up at least the projection matrix. Here's what it is in the scene I screenshotted: 1.0, 0.0, -0.414215, 0.0 0.0, 1.0, -0.310669, 0.0 0.0, 0.0, -1.0, 0.0
- Näytä vastaukset
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.