seeseemelk/cool-retro-term
1
0
Fork 0
Code Issues 449 Pull Requests 12 Actions Packages Projects Releases 8 Wiki Activity

Improper frame rendering #703

New Issue
Open
opened 2022-02-25 16:30:45 +01:00 by Digital-Sequence · 11 comments
Digital-Sequence commented 2022-02-25 16:30:45 +01:00 (Migrated from github.com)
Copy Link

I've updated retro term, and saw this
retro-term-issue

On previous version (1.1.1-2 in arch linux) everything is okay

Here's --verbose output

$ cool-retro-term --verbose
Using a variable-width font in the terminal.  This may cause performance degradation and display/alignment errors.
Both point size and pixel size set. Using pixel size.
Using a variable-width font in the terminal.  This may cause performance degradation and display/alignment errors.
qml: Loading settings: {
  "fps": 0,
  "x": 4,
  "y": 22,
  "width": 1912,
  "height": 1054,
  "windowScaling": 1,
  "showTerminalSize": true,
  "fontScaling": 1,
  "fontNames": [
    "IBM_3278",
    "COMMODORE_PET",
    "COMMODORE_PET"
  ],
  "showMenubar": false,
  "bloomQuality": 1,
  "burnInQuality": 0.5,
  "useCustomCommand": false,
  "customCommand": ""
}{
  "backgroundColor": "#000000",
  "fontColor": "#0ccc68",
  "flickering": 0,
  "horizontalSync": 0,
  "staticNoise": 0,
  "chromaColor": 0,
  "saturationColor": 0,
  "screenCurvature": 0.5198,
  "glowingLine": 0,
  "burnIn": 0.6,
  "bloom": 0.2969,
  "rasterization": 0,
  "jitter": 0,
  "rbgShift": 0,
  "brightness": 0.5,
  "contrast": 0.85,
  "ambientLight": 0.1,
  "windowOpacity": 1,
  "fontName": "IBM_3278",
  "fontWidth": 1,
  "margin": 0.5556,
  "blinkingCursor": false,
  "frameMargin": 0.3014
}
qml: Storing settings: {
  "fps": 0,
  "x": 963,
  "y": 22,
  "width": 953,
  "height": 1054,
  "windowScaling": 1,
  "showTerminalSize": true,
  "fontScaling": 1,
  "fontNames": [
    "IBM_3278",
    "COMMODORE_PET",
    "COMMODORE_PET"
  ],
  "showMenubar": false,
  "bloomQuality": 1,
  "burnInQuality": 0.5,
  "useCustomCommand": false,
  "customCommand": ""
}
qml: Storing profile: {
  "backgroundColor": "#000000",
  "fontColor": "#0ccc68",
  "flickering": 0,
  "horizontalSync": 0,
  "staticNoise": 0,
  "chromaColor": 0,
  "saturationColor": 0,
  "screenCurvature": 0.5198,
  "glowingLine": 0,
  "burnIn": 0.6,
  "bloom": 0.2969,
  "rasterization": 0,
  "jitter": 0,
  "rbgShift": 0,
  "brightness": 0.5,
  "contrast": 0.85,
  "ambientLight": 0.1,
  "windowOpacity": 1,
  "fontName": "IBM_3278",
  "fontWidth": 1,
  "margin": 0.5556,
  "blinkingCursor": false,
  "frameMargin": 0.3014
}
I've updated retro term, and saw this ![retro-term-issue](https://user-images.githubusercontent.com/100424861/155740673-9ceec857-e321-4eeb-94ce-68fbef95687a.png) On previous version (1.1.1-2 in arch linux) everything is okay Here's --verbose output ``` $ cool-retro-term --verbose Using a variable-width font in the terminal. This may cause performance degradation and display/alignment errors. Both point size and pixel size set. Using pixel size. Using a variable-width font in the terminal. This may cause performance degradation and display/alignment errors. qml: Loading settings: { "fps": 0, "x": 4, "y": 22, "width": 1912, "height": 1054, "windowScaling": 1, "showTerminalSize": true, "fontScaling": 1, "fontNames": [ "IBM_3278", "COMMODORE_PET", "COMMODORE_PET" ], "showMenubar": false, "bloomQuality": 1, "burnInQuality": 0.5, "useCustomCommand": false, "customCommand": "" }{ "backgroundColor": "#000000", "fontColor": "#0ccc68", "flickering": 0, "horizontalSync": 0, "staticNoise": 0, "chromaColor": 0, "saturationColor": 0, "screenCurvature": 0.5198, "glowingLine": 0, "burnIn": 0.6, "bloom": 0.2969, "rasterization": 0, "jitter": 0, "rbgShift": 0, "brightness": 0.5, "contrast": 0.85, "ambientLight": 0.1, "windowOpacity": 1, "fontName": "IBM_3278", "fontWidth": 1, "margin": 0.5556, "blinkingCursor": false, "frameMargin": 0.3014 } qml: Storing settings: { "fps": 0, "x": 963, "y": 22, "width": 953, "height": 1054, "windowScaling": 1, "showTerminalSize": true, "fontScaling": 1, "fontNames": [ "IBM_3278", "COMMODORE_PET", "COMMODORE_PET" ], "showMenubar": false, "bloomQuality": 1, "burnInQuality": 0.5, "useCustomCommand": false, "customCommand": "" } qml: Storing profile: { "backgroundColor": "#000000", "fontColor": "#0ccc68", "flickering": 0, "horizontalSync": 0, "staticNoise": 0, "chromaColor": 0, "saturationColor": 0, "screenCurvature": 0.5198, "glowingLine": 0, "burnIn": 0.6, "bloom": 0.2969, "rasterization": 0, "jitter": 0, "rbgShift": 0, "brightness": 0.5, "contrast": 0.85, "ambientLight": 0.1, "windowOpacity": 1, "fontName": "IBM_3278", "fontWidth": 1, "margin": 0.5556, "blinkingCursor": false, "frameMargin": 0.3014 } ```
👍 10
ia3crt commented 2022-02-27 11:18:48 +01:00 (Migrated from github.com)
Copy Link

I have the same issue. Digging up found there was the same bug in 2019. It is related to Nvidia. I tested it to use the Igpu on my laptop instead of the nvidia drivers, and sure enough cool-retro-term rendered fine.

I have the same issue. Digging up found there was the same bug in 2019. It is related to Nvidia. I tested it to use the Igpu on my laptop instead of the nvidia drivers, and sure enough cool-retro-term rendered fine.
Digital-Sequence commented 2022-02-27 19:37:18 +01:00 (Migrated from github.com)
Copy Link

I have the same issue. Digging up found there was the same bug in 2019. It is related to Nvidia. I tested it to use the Igpu on my laptop instead of the nvidia drivers, and sure enough cool-retro-term rendered fine.

You mean nouveau drivers?

> I have the same issue. Digging up found there was the same bug in 2019. It is related to Nvidia. I tested it to use the Igpu on my laptop instead of the nvidia drivers, and sure enough cool-retro-term rendered fine. You mean nouveau drivers?
KickingAnimal commented 2022-02-27 21:57:05 +01:00 (Migrated from github.com)
Copy Link

Also having this issue on Arch with official nvidia drivers.

Also having this issue on Arch with official nvidia drivers.
ia3crt commented 2022-02-27 22:04:38 +01:00 (Migrated from github.com)
Copy Link

No, sorry for not specifying. So far Nouveau seems to render fine, same as amdgpu and intel. In my case, the problem seems exclusive to the privative Nvidia drivers... I am not 100% sure because amdgpu was tested on a different machine, and nouveau on a different distro (but same 5.16.11 kernel)

> No, sorry for not specifying. So far Nouveau seems to render fine, same as amdgpu and intel. In my case, the problem seems exclusive to the privative Nvidia drivers... I am not 100% sure because amdgpu was tested on a different machine, and nouveau on a different distro (but same 5.16.11 kernel)
Digital-Sequence commented 2022-02-28 13:53:16 +01:00 (Migrated from github.com)
Copy Link

No, sorry for not specifying. So far Nouveau seems to render fine, same as amdgpu and intel. In my case, the problem seems exclusive to the privative Nvidia drivers... I am not 100% sure because amdgpu was tested on a different machine, and nouveau on a different distro (but same 5.16.11 kernel)

I would install nouveau drivers, but it doesn't support power management. Also, if you saw neofetch output, you know that my GPU is discrete, and its name is gt1030

> > > > No, sorry for not specifying. So far Nouveau seems to render fine, same as amdgpu and intel. In my case, the problem seems exclusive to the privative Nvidia drivers... I am not 100% sure because amdgpu was tested on a different machine, and nouveau on a different distro (but same 5.16.11 kernel) I would install nouveau drivers, but it doesn't support power management. Also, if you saw neofetch output, you know that my GPU is discrete, and its name is gt1030
ia3crt commented 2022-02-28 18:06:27 +01:00 (Migrated from github.com)
Copy Link

I would install nouveau drivers, but it doesn't support power management. Also, if you saw neofetch output, you know that my GPU is discrete, and its name is gt1030

If you have and Intel card, or Ryzen AMD (newer than gen I), I would recommend using hybrid graphics via bbswitch and optimus manager. Cool-Retro-Term and any other 2D app will launch with the integrated graphics, and GPU hungry games will launch with the Nvidia drivers. You can also force launch something with Nvidia with the "__NV_PRIME_RENDER_OFFLOAD=1" parameter.. The only caveat is that you won't have a spare GPU to do a passtrough for virtual machines.

> I would install nouveau drivers, but it doesn't support power management. Also, if you saw neofetch output, you know that my GPU is discrete, and its name is gt1030 If you have and Intel card, or Ryzen AMD (newer than gen I), I would recommend using hybrid graphics via bbswitch and optimus manager. Cool-Retro-Term and any other 2D app will launch with the integrated graphics, and GPU hungry games will launch with the Nvidia drivers. You can also force launch something with Nvidia with the "__NV_PRIME_RENDER_OFFLOAD=1" parameter.. The only caveat is that you won't have a spare GPU to do a passtrough for virtual machines.
njhanley commented 2022-03-03 22:37:41 +01:00 (Migrated from github.com)
Copy Link

4abbe33 introduced this issue.

4abbe33 introduced this issue.
vananasun commented 2022-10-03 15:16:05 +02:00 (Migrated from github.com)
Copy Link

bump, same issue while using 1.2.0 on Manjaro with NVIDIA proprietary drivers on an RTX 3060ti

bump, same issue while using 1.2.0 on Manjaro with NVIDIA proprietary drivers on an RTX 3060ti
0atman commented 2022-10-03 15:32:27 +02:00 (Migrated from github.com)
Copy Link

Same problem here on Ubuntu 22.04 with propitiatory nvidia drivers.

Will be trying nouveau as a fix, thanks!

Same problem here on Ubuntu 22.04 with propitiatory nvidia drivers. Will be trying nouveau as a fix, thanks!
0atman commented 2022-10-03 15:59:06 +02:00 (Migrated from github.com)
Copy Link

Nouveau did fix the frame, but very often locks up my computer when changing settings XD

Nouveau did fix the frame, but very often locks up my computer when changing settings XD
WhiskeyTuesday commented 2022-12-13 06:55:49 +01:00 (Migrated from github.com)
Copy Link

If you're okay with recompiling from source there's a workable temporary fix in one of the other issues:
https://github.com/Swordfish90/cool-retro-term/issues/739#issuecomment-1347784249

If you're okay with recompiling from source there's a workable temporary fix in one of the other issues: https://github.com/Swordfish90/cool-retro-term/issues/739#issuecomment-1347784249
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bounty
bug
duplicate
enhancement
help wanted
invalid
priority
high
priority
low
question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
seeseemelk
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: seeseemelk/cool-retro-term#703
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?