To start, I want to say I appreciate your input.
Starting with some context, I was using Unreal 5.5.4 - given my professional background I figured I could map any UI differences without much trouble. I even dove into the Enhanced Input system, which IIRC you might have helped me with when. I tried 5.6, but it just crashed on my computer consistently after about 5 minutes of operation. I planned to revisit once a patch or two came out.
The Quixel Bridge problem was less about it working and more about my ability to follow along with the course. I tried to find assets in FAB, but I simply could not see the same sorts of things the lectures were showing, which made it insanely difficult to follow along. If GDTV updates the course to use just FAB, then that problem goes away. That said, given they have a specific Linux build for Quixel Bridge I would expect it to at least kind of work. It simply did nothing on my system.
Your take on VS Code is interesting to me. I have been using it heavily for going on ten years now, albeit not without a healthy number of extensions. That is really the beauty of these tools - a solid extension community can solve most frustrations with them. I used a few IntelliJ-based editors waaay back in the day. They seem solid, but they were always rather heavy to boot. I also did not like the idea of having to install (and definitely not pay for) a separate program for every language I use, especially when feature-wise probably 80% of that binary code is identical. I have been keeping my eye on JetBrains Fleet, but it is nowhere near ready for prime-time yet. That said, I can give Rider a try and see if it wins me over. My experience with VS Code and Unity for the first section of that course went fine - Intellisense never broke, performance was fine, and all of my lovely extensions worked with it just fine. I cannot say the same of my Unreal experience with VS Code - if that is what you base your opinion of VS Code on I can see why you call it the worst. That sucked, but it is hard for me to discern how much of it was on which side of the fence. I did see the Intellisense break for the Multiplayer teacher’s Visual Studio (not Code), which led me to suspect it was more an Unreal or Unreal support problem versus a native VS Code one.
As far as my “train wreck” comment goes, This is where I was unclear - when I say it was a train wreck, I am referring to my experience with it. Unreal has countless games successfully built in it. As does Unity, for that matter. These are complex pieces of software that work in the contexts that they were built. Unreal was not built for Linux, clearly, nor does it sound like they care to make it so. Unity has worked fine on Linux thus far, but I have not gotten the same amount of experience with it to say whether or not it is better supported. All I can say is first impressions give the implication I would be less frustrated with the tooling using Unity.
For my personal set-up, all of my woes were discovered using Ubuntu Studio - an Ubuntu flavor that uses KDE Plasma. Epic says to use Ubuntu, but it does not clarify if the flavor matters. It could be that it does, but that would be highly limiting if only the main flavor of Ubuntu is supported. That said, a move to the main flavor of Ubuntu would be feasible for me, and much easier to swallow than a move back to Windows. I use the proprietary GPU drivers as Unreal made it abundantly clear it will not even attempt to run with the open source ones. And for “set-up” I followed their Linux page instructions more or less to a T, minus a couple steps that I had already done prior (like having the latest and greatest Clang installed). If I went wrong, it would be hard for me to say where, and their forums offered me no help. I will try Discord, though. I did not even realize there was one (albeit that is a rookie mistake - there is a Discord server for everything these days).
Unreal is a great engine, for sure - this was not supposed to be a shot at its capabilities. My experience with it on Linux - and the hostility of its owning company toward Linux in general - does not instill confidence that it is the right choice for any Linux user. You have convinced me of a couple avenues I could try to see if it can be salvaged without too much trouble. That said, there is only so much more struggling I am willing to put up with. I am already a month behind where I planned on being trying to work through these issues and ultimately trying to figure out my next move. I need to get the momentum back or I am doomed to fall out of it altogether.
Thank you again for your input!