Jump to content

SylenThunder

Moderators
  • Posts

    7,029
  • Joined

  • Last visited

  • Days Won

    12

Everything posted by SylenThunder

  1. Which is why it is so confusing. Wayland and X11 are basic GUI environments designed for remote connections. They aren't supposed to be your primary desktop enviroment. An excerpt from the Wiki for X Wayland is basically a graphics stack used for the display server. What is Wayland in Linux Distros and Should You Use it? (ubuntupit.com) It sounds like you did something like installing Linux using an option like "KDE on Wayland" for the desktop environment without knowing what you were actually doing.
  2. Then you should be using KDE/Gnome, or one of the actual desktop environments. X11 and Wayland are supporting tools for connecting to remote systems. You don't use them to connect to your local computer desktop. How did you set up this computer?
  3. Curious, why are you using X11 or Wayland to play the game? These are remote desktop communication protocols. You should be playing directly on the machine.
  4. PINNED thread you were supposed to read before starting a thread in this section of the forum.
  5. In that case I would delete the save data in the console. (Easy on PS, not sure how well it is on XB). Afterwards remove and re-install the game. Probably restart the console good between the removal and re-install. Afterwards everything should be refreshed fully, and there shouldn't be any corrupted data left over.
  6. Curious, are you able to create a new character for your own saves? I am not familiar with this type of issue happening on the Console versions, but I suppose it could be similar to the MD5 glitch on the XBox. Aside from both parties validating client files, there isn't a lot you can do because you cannot go in and delete specific data files on the Console Edition of the game. They may need to start a whole new world.
  7. This is correct. It spawns to drop within X distance of a random player that is online. Off the top of my head the distance is random as well, but there are minimum and maximum clamps on it.
  8. There is literally a Pinned thread for this. Please don't raise the dead. We don't need any zombies in the forum.
  9. Console version does not have this. Please be mindful of where you are posting for help. This should be in the Support section.
  10. You just set up a dedicated server. There is a thread here on using Docker. Not sure why you would want a video, as the interface is all headless and the entire process is rather complex. Reading is your best option.
  11. Most likely never. The switch doesn't have the hardware to be able to run this. It likely never will because it is so sub-standard. If you search around here a bit, you can find where I posted the specs and explained in intricate detail why the switch can never run a slightly hardware demanding game. I mean, look at all the issues with Mortal Combat currently. Found the most recent one. I'm sure I went into even more detail in one of the multiplayer threads as well. Do note that the minimum hardware requirements for the game have increased since I posted that. So instead of being three times slower than min spec on the CPU, it is now almost four times slower.
  12. It is already planned post-release. It's not a smart idea to add Workshop support before the modding platform is even finalized, or before the core of the game is finished. Also note that all of this can be done right now, and has been done for literally the past decade. https://community.7daystodie.com/forum/22-game-modification/
  13. Except that it was never a "deadline". See, even you are misreading the text to support your argument. A rough estimate isn't a deadline. It's a hopeful maybe and nothing more.
  14. Given the way a large portion of the community has raked him over hot coals every time he gives a vague estimate that isn't met, I'm honestly not surprised. I'd give up talking on the forums too. It would be really nice too if they just stopped giving any estimates at all. Since the community obviously isn't mature enough to understand the difference between an estimate and a promise.
  15. I usually go with LG or Spectre for my work machines. Good quality, and good cost. Sometimes you can even get a 1440p model on sale for the same as the 1080. This is the one I purchased most recently. https://www.amazon.com/gp/product/B08XD4HMDG This is what we buy in bulk for most users. https://www.amazon.com/gp/product/B0CHHSFMRL This is like what we used to get, but then the prices went up. These used to go for $115-125 https://www.amazon.com/gp/product/B0CBWXTKDW
  16. Survival Servers is one of the worst hosting services you can use. Not only are they sharing multiple systems on sub-standard hardware, but they constantly have issues with bandwidth limitations. Can you clarify on this some? The only issue I'm aware of offhand is when you have mods that affect things like tree and vehicle respawns. Not the lost vehicle commands, but the things that change the items so that they come back after being destroyed.
  17. Also, a bit dated, but still accurate in regard to how small changes to the system core can make a difference. https://steamcommunity.com/app/251570/discussions/4/2247803885925802071/#c2247803885925903682
  18. Voxel SI and enemy AI pathing is primarily managed on the CPU. The game is pretty well CPU-bound, and can be affected a lot by little things like clock speed, RAM speed, and drive I/O speeds. I have a couple of articles on how this game differs from other games in the Support FAQ.
  19. It's even more confusing because Steam doesn't have a designation for Alpha, and all of the versions you can choose from are in the "Betas" tab. Each minor version is numbered a21.1 a21.2 a21.3 and so on. Major builds are a20 a21 a22 ect. Each minor version has different builds. Basically each time TFP updates the client, there is a new build. Hence the build number. So a21.2 b14 is the 14th iteration of a21.2.
  20. Did you configure Swap? Has to be 8GB. Your first log shows you are using Ubuntu, which defaults to 2GB.
  21. Doing that would have had no effect on the save at all. There is something else you did that caused it. Like using settime or something similar. Moving thread to the Support forum, since it obviously doesn't belong in General Discussion for the Console release. Please look around before you post.
  22. First exclude your client and save folder fully from security software. This is covered in detail in the Pinned Support FAQ thread. Afterwards, validate the client files at least twice. MS Store is slightly better than Steam, but I still find that the first pass doesn't always get everything. Then try again. Also try connecting to a different server, and see if you have the same issue, or if it behaves differently.
  23. As beerfly implied earlier, did you ever even turn on the chunk reset feature? It isn't enabled by default, so if you didn't turn it on, that isn't related to what you are experiencing.
  24. I have to say, you have one thing that I have seen in just about every similar report. ALSA lib confmisc.c:855:(parse_card) cannot find card '0' ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_card_inum returned error: No such file or directory ALSA lib confmisc.c:422:(snd_func_concat) error evaluating strings ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1334:(snd_func_refer) error evaluating name ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM default FMOD failed to initialize the output device.: "Error initializing output device. " (60) Forced to initialize FMOD to to the device driver's system output rate 48000, this may impact performance and/or give inconsistent experiences compared to selected sample rate 48000 ALSA lib confmisc.c:855:(parse_card) cannot find card '0' ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_card_inum returned error: No such file or directory ALSA lib confmisc.c:422:(snd_func_concat) error evaluating strings ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1334:(snd_func_refer) error evaluating name ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM default FMOD failed to initialize the output device.: "Error initializing output device. " (60) FMOD initialized on nosound output This is usually because of an audio device missing a driver, or one that doesn't have driver support in Linux. In early experimental testing, I ran into a very similar issue because of a Bluetooth driver problem. Tested that on both Ubuntu 20.04, 22.04, and Debian 10 and 11. Basically, the server is up; but because the system is looping in trying to initialize the device, it isn't able to handle the network traffic data. The fix I performed on my test system was to disable the device in UEFI/BIOS, and remove it from the system hardware list in Linux.
×
×
  • Create New...