Infinite loading screen

[Bartleby]

Ok, i am using Linux and the game just worked fine until i wanted to return to the ranger citadel after Rail Nomad Camp. I hear the right sounds but am still stuck in the loading screen.

after reading many posts about this i think the game is just dead for me now, right? No solution and no known reason. All savegames broken.

[Shacklestein]

I had the same problem. Setting "ulimit -n 4096" and running WL2 from terminal fixed it. For now, at least.

[kyler.stern.pub]

Shacklestein,

Would you be so kind as to provide some clarify regarding what exactly you did? Where exactly did you change the "Setting?"

Thank you,

[kyler.stern.pub]

To add a little more context, Bartleby, I am able to continue playing the game. I have completed multiple missions, multiple saves, I have rebooted the PC multiple times. The only thing, that I see as an issue, at this time, is that when I attempt to enter the citadel, the game locks up when the progress bar reaches about 80%.

Note: I was able to get the setting changed, at least for now. I am not sure if it will remain after a reboot.

At the command line, i simply typed the command provided by Shacklestein and hit enter.

The result for me is the same. Still freezes at the same point. I can hear the music.

[Shacklestein]

Originally posted by kyler.stern.pub:

Would you be so kind as to provide some clarify regarding what exactly you did? Where exactly did you change the "Setting?

1. Open a terminal in the game's folder: ~/.steam/steam/steamapps/common/Wasteland 2 Director's Cut/Linux for me, may be elsewhere for others. My preferred method is to just use the regular file browser to get to the folder and then click the "Open terminal in active folder" button. If that's not available on your setup, you may have to navigate using cd command (change directory).

2a. Type "ulimt -n". This isn't necessary, but just to check what it's set at. Mine returns 1024.

2b. Type "ulimit -Hn" to check the hard limit on how high it can go. Again not necessary unless troubleshooting. Mine returns 4096. Other systems may be higher or lower. In the unlikely even that it's too low, things get more complicated. But that's for a different post.

3. Type "ulimit -n 4096" (or whatever your hard limit is) to increase the number of open files allowed. The exact number shouldn't be that important. 4096 was chosen by those that discovered the workaround. It's probably way overkill, but they didn't want the hassle of experimenting to see where the limit was. By all means try lower numbers if you want.

4 Type "ulimt -n" again, to check that it's gone through. Again only necessary for troubleshooting.

5 Type "./WL2" to start game.

That's all there is to it. There are ways to make the change permanent, but I don't like messing around with my system more than strictly necessary.

Please note that it's possible that the whole ulimit thing is not needed, and all it takes is running the game from terminal instead of through the Steam interface. When I was troubleshooting, I first tried ulimt+Steam with no success. Then came across a post that said to also run game from terminal (forgot where). As that fixed it, I never bothered checking if terminal alone was enough.

[kyler.stern.pub]

Shacklestein,

Worked like a charm. I ran all the commands from the terminal and I am successfully about to enter the Citadel and save. I have not gone any further at this point. I may play later.

I appreciate your assistance and that you took the time to provide the clarity and step by step.

[Red Line]

Had to navigate using command prompt as I am not sure I have option of opening a terminal. Command ulimt -n not recognized by MS-DOS

[Red Line]

Any suggestions as to fix issue using Win 10?

[Shacklestein]

Originally posted by kyler.stern.pub:

Shacklestein,

Worked like a charm. I ran all the commands from the terminal and I am successfully about to enter the Citadel and save. I have not gone any further at this point. I may play later.

I appreciate your assistance and that you took the time to provide the clarity and step by step.

No worries; Glad you got it sorted. Hopefully it'll do the trick for OP as well, if they return to check their post.

Originally posted by Red Line:

Had to navigate using command prompt as I am not sure I have option of opening a terminal. Command ulimt -n not recognized by MS-DOS

Originally posted by Red Line:

Any suggestions as to fix issue using Win 10?

Haven't the slightest clue. This is a Linux-specific fix to an issue with the Linux version of the game, using Linux commands.

If the Win version has a similar problem, you'll need to look for a Win solution.