SPOILERS

After one of my party members got imprisoned in Angel Oracle (in this case, it was Rose), all the weapons from her inventory was gone when I completed the Fletcher-quest and freed her. I'm not sure if this is a bug or if I must get the weapons back by talking to someone/finding them in a chest somewhere or something like that.

EDIT: Found the weapons in a locker in the equipment room.

Does anyone is facing the issue with game crashing on loading screen after returning to Ranger Citadel?

Earlier w/o patches or only with patch 1, I was able to workaround it after changing texture quality in display settings. Unfortunately, after patch 2 this workaround is no longer workaround, so currently I am unable to continue playing this game :(

Yes. I am experiencing this too. Windows 7 x64 with 4GB RAM and (sadly) an integraded HD Graphics GPU). I only had one or two crashes until updating from 2 to 4. Now this is 100% reproducable!

Meson Cannons in LA not firing/skipping turns

THIS -This worked for me. I`ve been using it for weeks now. In fact it`s so stable I won`t even bother with the Devs solution until they sound more sure that their method works. When you play an rpg of this kind, you want it to run smoothly and keep running. This ain`t no 8 hour arcade game you can risk losing all your progress on! Far too high a frustration risk.

Additionally, if you have a d3d12 GPU (I have an R9 380 4GB that supports level 12_0 in D3d12 in hardware) you can use the -force-d3d12 switch as well and also get complete stability in the DC. D3d9 still crashes for me after about 20 minutes of play--like clockwork--but I've played 40-hours straight (or more) without a single crash with the d3d12 switch invoked. The only difference between this and the d3d9 switch is that d3d12 runs noticeably faster for me--but both are stable. Using the Catalyst 15.11b drivers (most recent to date.) AMD is releasing a brand new driver set ~Nov24/27 I hear.

I have, since purchase, not been able to start WL2 Director's Cut on my Linux system, and have not put any time or effort into figuring out why until now (the old game worked fine, it seemed, and I had other things to do). It appears to open sharedassets5.resource over a thousand times (1858 times last time I checked), never closing it. I had my file descriptor limit set to 1024, so it failed (symptoms were usually blank/non-starting initial conversation on new game, or outright crash near end of initialization). The fix was to do "ulimit -n 4096" before starting. I haven't really played the game yet, so I can't say if 4096 is enough as there may be other file descriptor leaks.

I know this thread was started for officially recognized issues, but it seems as good a place as any to report this, and my initial search showed no other similar report.

If you want the people who can do something about this to hear your analysis, then no, this is not a good place to report it. Try the inXile forums, is my advice. Or do they have an official bug reporting system? I haven't looked into that.

It's a well known issue. Been posted a few times on GOG and believe it has a sticky on the inXile forums. The OP would be an additional good place to have it.

If it's a well-known issue, why did my search for "ulimit" return nothing (or is there another "well-known" workaround?) If it's a well-known issue, why wasn't it fixed in the last patch? Clearly posting on the official forum did as much good as posting here. If it's a well-known issue, why didn't I see it in the "known issues" post here already?

[rant about game devs' inability to check or report errors removed, since it wouldn't do any good anyway]

GOG forum search is shit.
It's been asked and answered a few times on GOG. Which is why I was agreeing with you that it should be added. Don't let that inconvenience you. Also, it's not a sticky over there.

For some reason after updating to windows 10 the game won't open/star anymore.
How to fix that apart from going back to previous system version?

Also.
I had crashes every time I tried to leave the Citadel during prologue.
I tried deleting registry entries, didn't have the font for the rare bug, have more than twice the RAM needed...
It was K-lite I had to flat-out uninstal, and it worked fine.
I came back once, no problem.
The second time I came back to the citadel, also had systematic crash when trying to leave.
This time I uninstalled Raptr, and it worked.
Third time I came back, crashes again. This time (and this is NOT in the sticky at the beginning), RESTARTING the computer solves the problem. I have no idea how it works and why this happens.

Maybe should be update to include the Director's Cut version as well