Beiträge von bionade24

Zitat von qwert

Das geht gar nicht anders. 3 Jahre Nutzungsdauer (gerade so die Afa Vorgabe erfüllt) und raus mit dem alten Zeugs.

Vor 3 Jahren war der aktuelle PC sicher nicht neu. Außerdem wird der alte PC wohl kaum im Altmetall landen, dafür ist er noch zu gut. Den bekommt dann eine Person die sich sonst aktuelleren low-end Kram gekauft hätte. Generell ist es sicher richtig nicht ständig Neues zu kaufen, ist aber immer leicht zu schwatzen wenn man auf absehbare Zeit das Geld für seine Wunschanforderungen beisammen hat.

mandigritsch hat hier bringt es hier auf den Punkt. 16GB VRAM sind bei einer Neuanschaffung muss um diesmal was zukunftsfähiges zu kaufen, die gewählte CPU macht auch keinen Sinn. Anderer Vorschlag: Warum rüstest du deine aktuelle Kiste nicht ein bisschen auf? Eine neu Graka und evtl. mehr RAM würde viel bewirken während ein 12700k bei Tpf2 wohl nur marginal Verbesserungen bringen wird. Ist dein PC so auf Kante genäht?

Außerdem klingt der Name deines aktuellen RAMs danach als hätte der XMP und dafür scheinen 2600Mhz ein bissl langsam. Überprüf doch mal ob du das anmachen kannst.

Hast du es bereits gespielt?

Zitat von Carbonunit

Bei mir war die Ursache wahrscheinlich der Kornspeicher aus dem Asset-Menue Landmarks (siehe Screenshot)

Da es bei mir die Bushaltestelle war & die bei dir auch so eingezwängt ist, würde ich behaupten die eigentliche Ursache ist die Haltestelle die so knapp platziert ist. Wierum du nun der Haltestelle den Platz für die größere Kollisionsbox gibst spielt keine Rolle. Ich habe diese Assets definitiv nicht installiert und eigentlich waren an der Problemstelle nicht wirklich mods involviert (0 height bridge ist ja nix permanentes).

Gamescope is the Wayland compositor of SteamOS. You can use it as an intermediate layer if some games have problems related to window management. It installs a signal handler if not set otherwise so you'd have to kill the process. So it's definitely not window management related.

Click the Link for a guide on how to enable Steam runtime logging and where to obtain the log.

I couldn't pin the problem down to one mod, but after I teared the bus capacity booth down and rebuild it, the problem was gone. So I guess the reason are the 0 height rail bridges in the background and the proximity of the booth to them. Having this problem nowhere else on the map further convinces me that the bridges and/or the proximity to the elevated rails are the problem. N0neGiv3N

Have you already tried running Tpf2 inside Gamescope? After you installed gamescope, go into the game setting add insert this in the launch options: gamescope -W 1024 -H 768 -r 60 -- %command%

Maybe also start Steam with logging for the Steam runtime enabled and post the steam runtime log of Tpf2: https://github.com/ValveSoftwa….md#essential-information

Zitat von ncharly

Habe diese rote Fähnchen gehabt

Mod können das "rote Fähnchen" auch beim Hinzufügen haben, das ist die Entscheidung der Modersteller.

severityAdd = "CRITICAL",       

Wenn das in der mod.lua drin steht, bekommst du das rote Fähnchen beim Hinzufügen. https://www.transportfever2.co…?id=modding:modcomponents

Zitat von eis_os

If TPF2 writes it own dmp file because it can't init the Renderer,
it's technical not crashing from a system standpoint

I pretty convinced I had cases where Tpf2 writes it's down dump and raises SIGABRT afterwards, which leads to a core dump. Are the codepaths that lead to a the creation of a minidump never calling abort() in the end?

I used minidump-stackwalk to read the dump, but couldn't understand much from it because missing debug symbols and I've only worked with core files so far. Is there a wiki entry which sections are may contain relevant information regarding the crash cause? I couldn't find one.

Zitat von meki

also weird only tf2 has this problem everything else works both opengl and vulkan

Which Linux native games installed via Steam do work for you meanwhile?

I think I now tried everything to help you install systemd-coredump, which is crucial for finding a solution (other than installing another distro). Please get help on some Linux mint forum, as I do not know their exact differences to Ubuntu.

Zitat von N0neGiv3N

Did you find a resolution?

I'm pretty sure it's related to the mods I added the day since there weren't even miniscule artifacts on screenshots before, but on this day the red hats appeared even on sparsely populated towns. I haven't played since then and will report back when I've done it.

Zitat von PeterLustig

Hast Du mal den Texturencache geleert?

The texture cache can't be the reason for objects on a wrong place. It may be the reason of color issues of single objects. But never of this kind of stuff. DH-106 has most likely already indentified the technical happening in the beginning of the thread.

When the drivers are too outdated for you, you're using the wrong Distro. It's not like you're compiling Linux-next and you also didn't manage to fix your installation of newer drivers and no have broken dynamic linking in the userspace part of your gpu drivers. This is just what you get if you buy a GPU from the company that is so miserly with Linux devs that their Linux GPU drivers are only usable from 6 months after the product launch on. Or only buy their products when they're more than a year old. You wouldn't get your card running on Windows 7 or a very old Windows 10, either.

I'd strongly suggest you switch to Ubuntu 23.10, the most recent Fedora or Arch (archinstall is official now). Cinnamon desktop is in the repos for all of them, no need for Mint. The share objects that try to link wrong should be fixable but even if I'd sit in front of your Computer it'll may take some hours for me if I'm really unlucky.

https://ubuntu.pkgs.org/22.04/…1-0ubuntu3_amd64.deb.html should exist, maybe you don't have the universe Repo activated in the apt sources? sudo apt edit-sources and remove the comment around universe. If it's not in there, pls search on the internet on how to enable Ubuntu universe or get some guide how to do this on Mint if they deviate from Ubuntu there.

Zitat von meki

if i dont actively activate basalt shouldn't it just be silent or idle

I didn't care to check if it installs some layers so you may be right. Given that Tpf2 in OpenGL mode crashes with a seemingly not graphics related issue, we don't have to care about it yet. But Vulkan certainly loads it all the time or Steam wouldn't have picked it up.

Nr. 2 is a wrong assumption, I guess I didn't state the explicitly enough ;D You have both Snap and Flatpak installed but installed Steam via apt. Steam does still have its own runtime container with different libraries, though. Forget 2 and this for now.

Hallo, ich hatte während er GPU-Shortage mal ein GeForce Now Abo, Tpf2 konnte man damals nicht spielen, nur ausgewählte Spiele. Mods gibt's afaik immer noch nicht, du hast auch kaum Stellschrauben. Nur weil GFNow Steam, EGS & co nutzt, hast du noch lange keinen vollen virtuellen Computer, alles ist abgeriegelt. Da gibts andere Anbieter. GeforceNow hat sich doch früher nur wegen der guten Preis-Leistung gelohnt.

I looked into the runtime diagnostics. Uninstall the ppa driver and use the stock, like already said in 4. The weird paths l mentioned

 "runtime" : {
    "path" : "/mnt/steam/SteamLibrary/steamapps/common/SteamLinuxRuntime/var/steam-runtime",
    "version" : "0.20231024.64411",
    "issues" : [
      "unexpected-location"
    ],
    "overrides" : {
      "list" : [
        "overrides/lib/",
        "overrides/lib/i386-linux-gnu/",
        "overrides/lib/i386-linux-gnu/aliases/",
        "overrides/lib/i386-linux-gnu/aliases/libOSMesa.so.6 -> /usr/lib/i386-linux-gnu/libOSMesa.so.8",
        "overrides/lib/i386-linux-gnu/aliases/libXaw7.so.7 -> /usr/lib/i386-linux-gnu/libXaw.so.7",
        "overrides/lib/i386-linux-gnu/aliases/libbz2.so.1 -> /usr/lib/i386-linux-gnu/libbz2.so.1.0",
        "overrides/lib/i386-linux-gnu/aliases/libcurl-gnutls.so.3 -> /usr/lib/i386-linux-gnu/libcurl-gnutls.so.4",

are from pressure-vessel, which is from the Steam runtime, so that explains that. And because you have Steam mounted at /mnt/steam, it creates those links to work. But shouldn't be a problem.

Please also remove VkBasalt.

I took a look into your installed packages:

1. systemd-coredump is still missing, the Linux mint link I posted has an URL that apt can read to install the pkg.
2. You have both flatpak and snapd installed, and since your minidump had those weird paths, it's very certain that you installed Steam via Snap or Flatpak. That's also explains why the vulkaninfo output is fine but your game launch errors. Your game doesn't use the same libraries as it's not really installed on the host but in a "container".
3. Uninstall libvulkan-dev. You do not need the validation layers unless you develop or run a wlroots based compositor in Vulkan mode. You seem to have installed in explicitly. This removal will also some other pkgs as this is a metapkg.
4. Are libdrm-radeon1 and libdrm-amdpu1 to different gpu drivers? If so, you have 3 Gpu drivers installed, as the latter name is installed in 2 versions. Use the boring amdgpu driver from your distro, no matter if some internet moron told you that "xy gives me more performance" while it's only 3fps in certain games. If you're inexperienced, you'll run into more trouble than it'll help you anything. https://wiki.archlinux.org/title/AMDGPU

Sorry my bad, I need the "Runtime diagnostics", not the system information from Steam.

How you installed steam or smth. related to systemd-coredump? Please be precise in your posts, this isn't the 1st time I just have to guess.

If it's steam you're asking about, posting the steam system information may be the quickest way, we'll have to see. But posting the output of apt list --installed would be a good idea for further troubleshooting anyway.

According to Linux Mint's website, a pkg called systemd-coredump does exist. https://community.linuxmint.co…are/view/systemd-coredump

May you please also answer this question:

Zitat von bionade24

Have you installed Steam via Snap or Flatpak?

Scheint wohl von einem neun Mod verursacht zu sein.

Steam screenshot:

1. Screenshot Tpf2:

2. Screenshot Tpf2:

Also alle screenshots bis heute sind ok, aber auf denen von heute an anderen Standorten sind besser versteckt auch diese Zipfelmützen zu finden, wie am Rand der Bushaltestelle in Screenshot 1.

Dass der 1. Screnshot auch kaputt ist war mir noch gar nicht aufgefallen. Ich werde jetzt mal alle anderen Screenshots die ich gemacht habe abchecken, bisher dachte ich alle die wären ok Wie schon geschrieben, ingame war nix davon sichtbar., erst im Screenshot.