Unreal Engine > MSBuild not working on Linux 22.04 Pop Os

Hello i got Pop OS 22.04 based on Ubuntu

With Rider and it says that there are 40 problems with loading the Unreal Engine Project

Intellisense and so forth is working, just the MSBuild doesnt work, idk what i should do

1
7 comments

Hello Ixllegacy123

Could you specify how Rider was installed on your system (using the Toolbox app/snap/tarball)?

0

it is installed from the toolbox where i downloaded the latest version as tar and unpacked it , not snap install

 

on my linux mint build i got the same issue, there rider was installed as flatpak from the installer

0

Same problem.

Ubuntu 22.04
Linux 5.15.0-40-generic #43-Ubuntu SMP Wed Jun 15 12:54:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Rider

JetBrains Rider 2022.1.2
Build #RD-221.5787.36, built on June 2, 2022
Licensed to 
Subscription is active until October 2, 2022.
Runtime version: 11.0.15+10-b2043.56 amd64
VM: Dynamic Code Evolution 64-Bit Server VM by JetBrains s.r.o.
Linux 5.15.0-40-generic
.NET 6.0.3
GC: G1 Young Generation, G1 Old Generation
Memory: 1500M
Cores: 16
Registry:
    indexing.enable.entity.provider.based.indexing=false
    rdclient.asyncActions=false
    ide.new.project.model.index.case.sensitivity=true

Non-Bundled Plugins:
    com.jetbrains.rider.ezargs (1.0.9)

Current Desktop: ubuntu:GNOME

0

i solved this problem by

1. restart PC

2. start Rider

3. it will suggest you to install a plugin called "Structured Logging"

https://plugins.jetbrains.com/plugin/12832-structured-logging

after installing that ( and installing rider plugin in engine ofc ) you can launch the Unreal Engine through rider and then you got no problems anymore

0

Thanks for the update. It sounds like there was an issue with environment variables - variables were picked up after the system (and Toolbox App/Rider) restart. "Structured Logging" plugin does not affect Unreal Engine in any way.

0

I'm also facing this issue on Ubuntu 22.04

0
Hello B3gan,

Apologies for keeping you so long without an answer.
We are sorry to hear that you encountered such a problem.

Were you able to solve the problem?
0

Please sign in to leave a comment.