Old launcher no longer working

Quote:

---

Originally Posted by junmoxiao

Except that Square Enix doesn't treat it as "nothing more than a store." Steam licenses are sold as separate licenses for a separate platform, being treated on the same footing as Windows, Mac, etc. If SE wants to treat Steam as its own platform, then they either need to support that platform or discontinue selling an independent license for it. They do not sell separate licenses for every other digital store that carries FFXIV.

---

Steam isn't a platform, its a store. Regardless of how SE treats the steam license, steam is still nothing more than a store page and on their store page it straight up says;

OS: Windows® 8.1 64 bit, Windows® 10 64 bit, Windows® 11 64 bit.

They do not support linux, they are under no obligation to support linux, nor should they support linux. Linux gives users full access to the OS kernal which is just a breeding ground for hacking/exploits and its the very reason developers like Bungie flat out said they will ban anyone trying to play Destiny 2 on Linux.

Using Linux is a "at your own risk" situation. The game does not officially support it and its on you to deal with those consequences, not SE. They have no obligation to abide to a less than 1% crowd that Linux on their home PC's.

I'm another Linux/Proton user who has been locked out and received the boilerplate "We don't support Linux" response from support. Seems silly that SE would go with an outdated/inherently insecure Microsoft tech when there are free, open-standard options with better security and platform compatibility available.

Gabe Newell plays on steamdeck and he can't login right now, so I am certain this will change tomorrow.

Quote:

---

Originally Posted by Ransu

They do not support linux, they are under no obligation to support linux,

---

Not really asking anyone to support it, just asking them not to break it, on one specific platform. Keep in mind, the game itself runs perfectly fine under Linux. This is strictly a launcher issue. We're not complaining we crash when we go to a place in the world. The launcher within Steam is just being extremely restrictive, a problem not shared by anyone who's not using a Steam-specific key.

Quote:

---

nor should they support linux.

---

Weird thing to say, but okay, sure. And again, 'support' is different from 'avoiding specific breakage.' The only trouble Linux has is with an old, dated technology in a launcher for XIV. Nothing to do with the game at all.

Quote:

---

Linux gives users full access to the OS kernal which is just a breeding ground for hacking/exploits

---

... Oh, wow, okay, sure. Because Linux users are the ones exploiting all the games, especially the ones they can't even play because of anti-cheat. You're gonna have to pick a side, here -- either we're an endangered species or we're prolific.

Quote:

---

and its the very reason developers like Bungie flat out said they will ban anyone trying to play Destiny 2 on Linux.

---

Nah. No anticheat needs kernel access in the first place, not really. It's the easy answer, but it'll always be the laziest answer, and the worst one. They can say whatever they want -- lazy dev is lazy.

Quote:

---

Using Linux is a "at your own risk" situation. The game does not officially support it and its on you to deal with those consequences, not SE. They have no obligation to abide to a less than 1% crowd that Linux on their home PC's.

---

Once again, are we a prolific problem persistently pestering the populace, or are we less than one percent?

Oh, and 'don't fix what ain't broke.' This was an easily avoidable problem given there doesn't seem to be any actual need to push this update. Again, we don't need to be 'supported.' But we also don't need to be hampered.

They could also just make the account linking feature opt-in (or opt-out) instead of mandatory for all users. It's a hoop that non-Steam users aren't even being forced to deal with right now.

There are devs in the Linux community currently working on it as we speak so all we can do is hope wait and be patient for them to work their magics.

Goats: are working on it, they have acknowledged on an issue raised on Github. So hopefully they will get their quick launcher to work with steam and Proton

Unless Gaben comes to the rescue before then but who knows.

Welp, I've managed to install Windows under QEMU-KVM (I find it quite funny, that it was simpler than regular real windows setup, which was refusing to work XD) with a single GPU passthrough, hate it I had to do that in such way, but at least Windows is safely contained within a VM.. and it's much more convenient than dual-boot setup. Now for the game to download..

If anyone would like to try it and need help - lemme know, it's quite simple and useful (not only for 14) :) That's the least we can do before Goats/Wine/SE devs manage to come up with a fix.

The problem with that is if you are on a laptop and cannot passthrough the audio device because its not PCI, I ended up setting up a pulseaudio server and connecting to it with Scream but then when I setup pulseaudio that way my linux desktop would not work properly as the device appeared in use. On my desktop I use hdmi audio so it runs flawlessly.

Quote:

---

Originally Posted by darkvalefor

The problem with that is if you are on a laptop and cannot passthrough the audio device because its not PCI, I ended up setting up a pulseaudio server and connecting to it with Scream but then when I setup pulseaudio that way my linux desktop would not work properly as the device appeared in use. On my desktop I use hdmi audio so it runs flawlessly.

---

Hmm.. tbh I just passed my USB Headphones, but I can see there are lots of guides how to make it work with pulseaudio server.. you can check what is using it by sshing into the host machine and using lsof, maybe you'll find a culprit this way

I presume, you're using Arch Wiki? https://wiki.archlinux.org/title/PCI...ost_via_Scream

I’m using Ubuntu as main OS tho the Arch wiki info is useful for the majority of it, I’ll probably give it another go soon. Ideally I should be able to setup a pulseaudio server as a system service and have my desktop environment connect to it as a client then because the qemu hook script kills your DE, it should be free to connect to the pulseaudio server. I honestly don’t know why I was having that issue in which I couldnt use my audio device on Gnome but I think it is because instead of connecting to the pulseaudio server it was trying to start another pulseaudio server. I just ended up giving up but might be a good time to try and play around with it again.