Psyonico Posted January 3 Posted January 3 Hoping this is the right place for this. My computer is fairly new (~6 months old) when I built it, I was running Nobara 36. Homecoming ran perfectly on it. I later installed windows instead (long story) and have since gone to a dual boot system with Fedora 39 being the default, and still being able to boot into Windows 11 if needed. Anyway, In windows and on Nobara I was able to run the game at 4k with everything maxed without any lag whatsoever, now, on my new Fedora install and the exact same settings as when I was in Nobara/Windows, I'm getting about 10 FPS even on the character select screen. I've narrowed it down (i think) to something with Lutris or Homecoming, as the couple of games that I've tried running through Steam are working perfectly. I've tried different WINE versions through Lutris to no avail. Currently I have it set up as wine-ge-8-25-x86_64 (which was the default when I installed it.) I tried doing a "Reset Graphics Options" In the Homecoming Launcher, and it ran it at a very small resolution and things set to "default" and it seemed like it was running alright, but when I set it back to 4k, I started having issues. I tried booting up the game in windows again and it worked just fine. some system specs for you # System Details Report --- ## Report details - **Date generated:** 2024-01-03 16:48:54 ## Hardware Information: - **Hardware Model:** Micro-Star International Co., Ltd. MS-7E12 - **Memory:** 128.0 GiB - **Processor:** AMD Ryzen™ 9 7950X × 32 - **Graphics:** AMD Radeon™ RX 6950 XT - **Graphics 1:** AMD Radeon™ Graphics - **Disk Capacity:** (null) ## Software Information: - **Firmware Version:** 1.30 - **OS Name:** Fedora Linux 39 (Workstation Edition) - **OS Build:** (null) - **OS Type:** 64-bit - **GNOME Version:** Not Available - **Windowing System:** Wayland - **Kernel Version:** Linux 6.6.8-200.fc39.x86_64 I have also tried both Wayland and X11, it did not make a difference. I tried disabling my iGPU in my BIOS just in case the game was trying to run on that, again, no difference. Hopefully someone has an idea on what I'm missing at this point. Thanks all! What this team needs is more Defenders
Kai Moon Posted January 4 Posted January 4 Since the problem started when you changed distros, might help to check the kernel driver, modules, and OpenGL. Could you paste or attach the text output from lspci -v -s `lspci | awk '/VGA/{print $1}'` glxinfo | grep OpenGL 1
Psyonico Posted January 4 Author Posted January 4 I think something isn't right in that lspci command, when I try to run it, I just get the Usage/display modes/Display options information. I think you're trying to get the lspci info for my gpu out of that, so I did just an lspci, got the slot address (in this case it was 3:00.0) and then ran lspci -v -s '3:00.0' The results are below. If this is not what you were expecting, let me know. lspci -v -s '3:00.0' 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6950 XT] (rev c0) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Device 2420 Flags: bus master, fast devsel, latency 0, IRQ 133, IOMMU group 15 Memory at f800000000 (64-bit, prefetchable) Memory at fc00000000 (64-bit, prefetchable) I/O ports at f000 Memory at fcb00000 (32-bit, non-prefetchable) Expansion ROM at fcc00000 [disabled] Capabilities: <access denied> Kernel driver in use: amdgpu Kernel modules: amdgpu When I run the glxinfo command I get the following: OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon RX 6950 XT (radeonsi, navi21, LLVM 17.0.6, DRM 3.54, 6.6.8-200.fc39.x86_64) OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.3.1 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.3.1 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.3.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: What this team needs is more Defenders
Psyonico Posted January 7 Author Posted January 7 I'm hoping someone has some insight into this What this team needs is more Defenders
lemming Posted January 7 Posted January 7 I usually run via "wine ~/.wine/drive_c/Games/Homecoming/bin/win64/launcher.exe > ~/down/hclaunch.log 2> ~/down/hclaunch.err &" and if you run the diag client, even more info gets dumped into those log files. (I found several popmenu errors using this method) Definitely sounds like a graphics driver issue.
Psyonico Posted January 7 Author Posted January 7 You solved my problem... I tried running it through WINE instead of lutris and it runs perfectly... I guess I'll just update my desktop shortcut to run that instead of through lutris. 1 What this team needs is more Defenders
lemming Posted January 7 Posted January 7 29 minutes ago, Psyonico said: You solved my problem... I tried running it through WINE instead of lutris and it runs perfectly... I guess I'll just update my desktop shortcut to run that instead of through lutris. Huh. I did start running my launcher via that command when I was having some issues with lutris on a different computer. I think my issue was sound at the time.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now