Github messages for voidlinux
 help / color / mirror / Atom feed
From: Dr64h <Dr64h@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Vulkan glitching out on some applications since a recent Void-Linux update ?
Date: Sun, 02 Jun 2024 14:09:10 +0200	[thread overview]
Message-ID: <20240602120911.06E5A272BC@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50545@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]

New comment by Dr64h on void-packages repository

https://github.com/void-linux/void-packages/issues/50545#issuecomment-2143822502

Comment:
> > > after a few tests:
> > > It happens on both minecraft vulkanmod & Quake2RTX (native wayland - both), but not with gamescope. Can it be plasma ?
> > 
> > 
> > About a week and a half ago, I had blinking artifacts with RX570 when opening games in plasma, but they were not specifically related to Vulkan and they disappeared after the update.
> 
> which update ?

KDE components update, i don't know exactly which component is responsible for this artifacts, i think it's something with kwin and screen synchronization.

When you turn on the "full screen" mode the game is responsible for screen sync, and when you change it to "window mode" or "borderless full screen window", then the kwin is responsible for screen sync. But it doesn't mean that exactly the screen sync is responsible for this artifacts, it can be another different graphics things, effects, which turns on/off when you change window modes.

  parent reply	other threads:[~2024-06-02 12:09 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27 19:05 [ISSUE] [Help-Wanted] " SpidFightFR
2024-05-27 19:07 ` SpidFightFR
2024-05-27 19:07 ` SpidFightFR
2024-05-28  2:06 ` Luciogi
2024-05-28  4:41 ` SpidFightFR
2024-05-28  4:43 ` Luciogi
2024-05-28  5:25 ` Luciogi
2024-05-28  5:38 ` SpidFightFR
2024-05-28  5:38 ` SpidFightFR
2024-05-28  7:32 ` Luciogi
2024-05-28  7:49 ` Luciogi
2024-05-28  9:30 ` SpidFightFR
2024-05-28  9:31 ` SpidFightFR
2024-05-28  9:32 ` SpidFightFR
2024-05-28 13:11 ` Luciogi
2024-05-28 17:15 ` SpidFightFR
2024-05-28 17:15 ` SpidFightFR
2024-05-28 17:16 ` Luciogi
2024-05-28 17:57 ` SpidFightFR
2024-05-28 17:58 ` SpidFightFR
2024-05-28 18:04 ` SpidFightFR
2024-05-28 18:10 ` SpidFightFR
2024-05-28 18:37 ` SpidFightFR
2024-05-28 18:50 ` [ISSUE] [CLOSED] " SpidFightFR
2024-05-28 18:50 ` SpidFightFR
2024-05-28 18:56 ` SpidFightFR
2024-05-28 19:01 ` SpidFightFR
2024-06-01 12:30 ` Dr64h
2024-06-01 12:33 ` Dr64h
2024-06-01 13:40 ` SpidFightFR
2024-06-02 12:09 ` Dr64h [this message]
2024-06-02 12:17 ` Dr64h
2024-06-02 17:23 ` SpidFightFR
2024-06-04 18:23 ` SpidFightFR
2024-06-04 18:23 ` [ISSUE] [CLOSED] " SpidFightFR

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240602120911.06E5A272BC@inbox.vuxu.org \
    --to=dr64h@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).