[Bug 45345] Unity Game Lines Infinite shows a blank screen

[wine-bugs at winehq.org]

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

--- Comment #15 from Matteo Bruni <matteo.mystral at gmail.com> ---
(In reply to Olivier F. R. Dierick from comment #14)
> (In reply to Matteo Bruni from comment #11)
> > (In reply to Olivier F. R. Dierick from comment #10)
> > > Created attachment 61648 [details]
> > > Friday the 13th Killer Puzzle wine-staging 3.10 terminal output
> > > 
> > > Friday the 13th Killer Puzzle (Unity engine game) is also affected.
> > 
> > No, your issue (which is bug 39754) looks unrelated to this bug.
> 
> Both my issue and the OP's are the same: Blank screen in Unity game.
> 
> Nothing tells me that my issue is caused by 'multisampling resolve not being
> implemented for typeless resources'. There are many more lines common to my
> terminal output and the OP's that may be symptoms of the true cause of the
> issue.

Does hacking away the return right next to the FIXME() make any difference for
you?

> Bug 39754 has been recycled more than once and the current symptoms
> described there is 'blank screen in multiple games'.

Yeah, that's unfortunate. It should have been closed when the "first pass"
implementation of multisample resolve was implemented. Alas it was repurposed
for the (still missing) typeless resource case and changing things again at
this point IMHO isn't particularly valuable.

> The summary is
> irrelevant as it's not conforming to the bug writing guidelines because the
> analysis might not be correct.

The current summary of bug 39754 is obviously correct.

> Bug 43983 was marked duplicate of bug 39754 and it didn't even have a
> terminal output attached. So tell me how bug 43983 is a duplicate of bug
> 39754 and my issue would, but not this bug?

I'm sure Józef tested the game from bug 43983 himself, I'd tend to trust his
judgment.

> As far as I can tell, this bug is a duplicate of bug 39754.

It doesn't look like it to me. The OP's log has no mention of typeless
multisample resolve while it has multiple references to
GL_FRAMEBUFFER_INCOMPLETE_MULTISAMPLE errors, apparently caused by mixing
multisample depth / stencil buffers with a single sample color buffer. That's
the likely culprit IMHO.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.