Having some trouble getting the drop down list to show any details.

As you can see in the screenshot it’s just blank. Outside of that, everything Assetto Corsa works great.

I have tried following the method at the following link however it doesn’t work at all for me. I can make it through the process up to the point where you should be able to launch CM but it just fails to launch.

https://gist.github.com/ANBAL534/4f1693536f17b75ebcc8016e0d4cc071#gistcomment-3872704

If I install AC fresh, using experimental or GE-Proton9-7 it will launch CM, but none of the drop down menus work, they just appear like in the screenshot.

I’m assuming that this may be related to some kind of .net issue but before I go digging around trying to manually change stuff, I figured I’d check if any one else has seen this issue.

  • mranderson17@infosec.pub
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    6 months ago

    Unfortunately I don’t know what is causing the exact issue you are having, however here are a few things I found when doing this myself that are “gotchas” (not immediately obvious).

    1. This is the reason your fonts are all Times New Roman. Go to that key using protontricks regedit and delete all the font replacements.

    2. Anything you put in $HOME/.steam/root/steamapps/common/assettocorsa stays there, even if you uninstall the game. If you want to “start over” you have to uninstall the game and then delete the whole assettocorsa directory there, and the wine prefix in $HOME/.steam/root/steamapps/compatdata/244210

    3. AC and content manager work without .net changes in the latest GE but you do need corefonts which you can install with protontricks. If you want to be extra sure you have the right .net you can install dotnet472 but I don’t believe this is necessary anymore as it will be installed automatically or is already installed. You may get a wine .net error the first time you launch the game but it’s only the first time.

    4. If you choose to use CSP you have to unzip the archive you get from either Patreon or acstuff.ru and manually copy the dwrite.dll file into $HOME/.steam/root/steamapps/common/assettocorsa on EVERY upgrade. The zip installer built into CM doesn’t do this correctly on Linux. It will cause rain not to work if you choose to use the Patreon version if you don’t do this manual step.

    I think you should start over and make sure the assettocorsa directory is clean before re-installing the game. It could be missing fonts, but it’s hard to say. You can back it up somewhere if you have data in there you need.

    • skizzlesOP
      link
      fedilink
      arrow-up
      2
      ·
      6 months ago

      Thank you for that.

      It didn’t help but it definitely got me moving in the right direction. I remembered that I recently (yesterday) enabled the testing and kde-unstable repos in my system so I could install Plasma 6.1 to check it out. Prior to this change I had CM working properly but was having issues getting CSP to work. Well, I figured out a workaround to getting CSP to work (after this change) by just copying over my install directory from windows on top of the install in Linux. However since I had already updated to Plasma 6.1 it came with the new issue of the drop down menus.

      I was using Wayland. Just swapped over to X11 and it’s working as intended. So something with Plasma 6.1 on Wayland is causing the issue.

      So mostly a bunch of messing around with my system is probably what is causing the issue and for whatever reason disabling the testing and unstable repos isn’t allowing me to revert back to the previous version of Plasma. Not really sure why but that’s a totally different issue.

      I really appreciate the time you took to give me such an in depth response.

      • mranderson17@infosec.pub
        link
        fedilink
        arrow-up
        1
        ·
        6 months ago

        Interesting, it is working for me in wayland and the drop down menus are fine but I’m using sway which is a totally different wayland implementation than what KDE is doing. I’m glad you found a workaround.

    • skizzlesOP
      link
      fedilink
      arrow-up
      4
      ·
      6 months ago

      I didn’t at first, but after the response from @mranderson17 I ended up doing just that. Which seems to have resolved that issue.

      Prior to enabling testing/unstable repos for access to Plasma 6.1, CM was working fine on Wayland. However after the update it seems to have broken it but changing to X11 fixes the issue. So it’s likely a combination of me messing with my system and something with Plasma 6.1.