Jump to content

SylenThunder

Moderators
  • Posts

    7,079
  • Joined

  • Last visited

  • Days Won

    12

Record Comments posted by SylenThunder

  1. Also note that that laptop isn't going to do well at 4k. You will want to drop your resolution to 1440p or 1080p. Doesn't matter that it's a 12th-gen with a 3080. You might as well have a desktop 8th gen with a 1070. 

     

    Your video driver is also from June. Install this one. Don't forget to opt out of the GeForce Experience bloatware, and you should choose Advanced to perform a clean install.

     

    This is a driver issue. It's not a bug with the client. You're probably just using the crap "Microsoft Certified" driver that Windows installs with major updates. It doesn't include full Direct3D support, and causes this issue.

  2. Might want to remove the mod. Just nuke the Mods folder.  It fails to load because you installed it wrong, but still...

     

    Your log also looks like it shows normal exit. Just loaded it up and went back out again.

  3. EOS is a new feature with a20. Has existed since shortly before the build went public, so it isn't something recent.  There is already a report here about underscores in player names causing a problem.

    If it only happens at the home base, maybe the problem is in something here.

  4. One thing I see... Player name with underscore. Really screws up the current system. Here is an example with "captin_corpse".

    2022-01-12T22:13:23 203.128 INF PlayerSpawnedInWorld (reason: JoinMultiplayer, position: 1511, 37, -1720): EntityID=171, PltfmId='Steam_76561197977919855', CrossId='EOS_0002b27c56224d73a6bf05d1ad4bcaea', OwnerID='Steam_76561197977919855', PlayerName='captin_corpse'
    2022-01-12T22:13:24 203.189 ERR Invalid platform name in user identifier: captin

    Aside from that, I'm not seeing anything in the log.

  5. 44 minutes ago, shahruh10 said:

    I do wish that the logs were anonymized. Which is why I left it out.

    They don't contain private information.

     

    I see where the error is in the log, and I'm not noticing any obvious cause previous to it. Please ensure that you have fully excluded the client from security software, and then verify the files a couple of times.  Instructions on the former are here.

     

    Once that's done, restart your system and try a new save. See if it occurs again.

  6. 6 hours ago, trevorjd said:

    LOL no. All we have are Allocs and botman. By sanitise, I mean do basic due diligence to ensure there's no personal information, sensitive information, passwords whatever in the log segment.  If it were a short excerpt of a minute or three either side of an incident then sure, no problem but here we're potentially sending a hour or two's worth of logs from our prime time.

    There is no PI in the files. The server IP is obfusticated , and player information isn't PI.

     

    Send the full log, don't edit it, and note the times when it happens.

  7. Curious about the actual steps you followed to configure this, and any logs you have on it.

     

    No need to install SteamCMD with LGSM, you just run the installer script.

     

    There is a lot of information missing from this report. I've been running servers on, and supporting, LGSM for a couple of years now without any issue.

×
×
  • Create New...