[Bug 55965] New: Divide by zero error with Trackmania 2020 when loading tracks [D3DMetal]

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=55965

Bug ID: 55965
           Summary: Divide by zero error with Trackmania 2020 when loading
                    tracks [D3DMetal]
           Product: Wine
           Version: unspecified
          Hardware: arm
                OS: Mac OS X
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]

Created attachment 75555
  --> https://bugs.winehq.org/attachment.cgi?id=75555
backtrace log of game crashing when loading into a game.

Hi all, bit at a loss on where exactly to report this. I'm trying here first
and if it's not a problem with wine itself, please tell me where to poke
exactly.

So Trackmania 2020 has a rather weird error when it comes to using Apples new
GPTK layer. The game works amazingly... in the editor. You can load tracks and
drive them (with pretty remarkable quality).

However, when you load a track or join a server, the game crashes with a divide
by zero error. Additionally, in the editor, some graphical elements are weird
(i.e, some trees are not rendering, weird blown out textures etc) and you can't
render the track (aka "calculate shadows").

Luckily TM2020 is free to play to recreate this. Just open the game and try to
load any track. You can also recreate the editor weirdness by using the scenery
blocks.

I have used Whisky, Crossover (where this error log comes from), PortingKit and
vanilla wine and each yields the same results with various versions (all
released within the last 4-5 months). There's a bug report on Whisky on this
issue that's flagged specifically as an issue with wine (also I posted a
comment with no response: https://github.com/Whisky-App/Whisky/issues/235). I
currently use Parallels to play (which works fine, of course using a different
method of emulation), but with the new GPTK update the performance increase is
apparently massive, so it would be nice to see this fixed.

I'm not going to make this harder by guessing, as I am not super technical with
Wine. However looking at the backtrace and just glancing at the error-log I
think the problem is down to Wine's interaction with GPTK/D3DMetal, or with
GPTK/D3D/Apple itself.

Weirdly, I don't *think* this is a WINE bug necessarily, TM2020 is my favourite
game, so more than anything I kinda want to know *where* exactly to report this
error in detail if not here. Plus I want someone far more well versed than me
to explain how to report this bug.

Is this an Apple issue or a WINE issue or a skill issue?

Thanks for your help and all your hard work!