verofess / palworld-server-unoffical-fix Goto Github PK

View Code? Open in Web Editor NEW

932.0 11.0 32.0 6.23 MB

This is an unofficial palworld server binary distribution project that fixes some problems with the original server.

Batchfile 100.00%

palworld-server-unoffical-fix's Introduction

palworld-server-unoffical-fix's People

Contributors

Stargazers

Watchers

palworld-server-unoffical-fix's Issues

Linux-Server用了这个补丁之后好像服务端FPS变低很多

win系统 .exe程序该如何使用

您好作者不知道是否我使用win系统.exe程序方式错误运行PalServer-Win64-Test-Cmd-Patch-Update-2.exe程序后先显示缺少tbb.dll组件下载下载组建后再次运行程序显示Failed to open descriptor file .../.../Pal.uproject

[Feature Request]: Extra Logging for ensuring the patched file is successfully installed

First of all, Thx for your great job on this!!!!

But I have a small suggestion and I don't know if it is a good idea (and don't know if it is doable)

Can we have some extra "print" or "logging" so user can check they install this patched server correctly?
Or we need to wait for few hour to check it doesn't memory leak.

租用伺服器的話, 要怎樣用你的修復檔呢?

租用伺服器的话, 要怎样用你的修复档呢?
因为架服的工具都是HOSTING那边给承包了
没法直接使用你的EXE文件覆盖QQ

【BUG】使用Update-3-Beta，服务器内存还是会爆

服务器配置：Ubuntu 2核8g内存，

请问，我应该如何记录相关日志。

Gather feedback for new official updates | 收集新官方更新的反馈

As you can see, a new update has been officially launched, and on my machine it looks like they have fixed the memory leak problem. If they have fixed it I will focus on the development of third-party APIs.

Please provide feedback to help me determine if this issue has been fixed

如各位所见，官方推出了新的更新，在我的机器上看起来他们已经修复了内存泄漏的问题，如果他们已经修复我会将注意力放在第三方API的开发上。

请提供反馈来帮我确定这个问题是否已经修复

Patch 3 崩溃问题

PalServer-Linux-Test 0x0000000000200000 + 64d89f4 PalServer-Linux-Test 0x0000000000200000 + 64fb0a3 PalServer-Linux-Test 0x0000000000200000 + 64faf3f PalServer-Linux-Test 0x0000000000200000 + 65a6a39 PalServer-Linux-Test 0x0000000000200000 + 657f76e PalServer-Linux-Test 0x0000000000200000 + a05b62e PalServer-Linux-Test 0x0000000000200000 + 9b33cbb PalServer-Linux-Test 0x0000000000200000 + 996c6b4 PalServer-Linux-Test 0x0000000000200000 + 3d284cb PalServer-Linux-Test 0x0000000000200000 + 3d2962e PalServer-Linux-Test 0x0000000000200000 + a760818 libc.so 0x00007ff8fb502000 + 23d0a PalServer-Linux-Test 0x0000000000200000 + 3d27029

不知道日志有没有帮助

0.1.3.0 Update-4崩溃，大概开了十几个小时

服务端崩溃，大概开了十几个小时，机器上的内存肯定是够大的，也没吃满

版本是PalServer-Linux-Test-Patch-Update-4-Beta
说起来好像感觉没有流畅太多（

内存转储
https://drive.google.com/file/d/1ehTDZprYtzRzdLFln6xIEckArDsi4Snb/view?usp=sharing

日志
Shutdown handler: initalize.

Existing per-process limit (soft=1048576, hard=1048576) is enough for us (need only 1048576)
Increasing per-process limit of core file size to infinity.
Existing per-process limit (soft=18446744073709551615, hard=18446744073709551615) is enough for us (need only 18446744073709551615)
LogPakFile: Display: Found Pak file ../../../Engine/Programs/CrashReportClient/Content/Paks/CrashReportClient.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../Engine/Programs/CrashReportClient/Content/Paks/CrashReportClient.pak.
LogPakFile: Display: Mounted Pak file '../../../Engine/Programs/CrashReportClient/Content/Paks/CrashReportClient.pak', mount point: '../../../Engine/'
LogICUInternationalization: ICU TimeZone Detection - Raw Offset: +0:00, Platform Override: ''
LogInit: Build: ++UE5+Release-5.1-CL-0
LogInit: Engine Version: 5.1.1-0+++UE5+Release-5.1
LogInit: Compatible Engine Version: 5.1.0-0+++UE5+Release-5.1
LogInit: Net CL: 0
LogInit: OS: Debian GNU/Linux 11 (bullseye) (6.1.57-0-lts), CPU: AMD Ryzen 9 3950X 16-Core Processor, GPU: NVIDIA PCI-id: 10de-1401 (1043-8520)
LogInit: Compiled (64-bit): Dec 31 2023 20:12:22
LogInit: Compiled with Clang: 13.0.1 (https://github.com/llvm/llvm-project 75e33f71c2dae584b13a7d1186ae0a038ba98838)
LogInit: Build Configuration: Shipping
LogInit: Branch Name: ++UE5+Release-5.1
LogInit: Command Line: -Abslog="/palworld/Pal/Saved/Logs/Pal-CRC.log" -Unattended -ImplicitSend "/palworld/Pal/Saved/Crashes/crashinfo-Pal-pid-21-529916A2C55B44F7A8E2E4D3AC4EDAC8/" -unattended
LogInit: Base Directory: /palworld/Engine/Binaries/Linux/
LogInit: Allocator: Mimalloc
LogInit: Installed Engine Build: 1
LogInit: Presizing for max 100000 objects, including 0 objects not considered by GC, pre-allocating 0 bytes for permanent pool.
LogInit: Object subsystem initialized
[2024.01.27-09.53.25:599][ 0]LogConfig: Applying CVar settings from Section [ConsoleVariables] File [Engine]
[2024.01.27-09.53.25:599][ 0]LogInit: Unix hardware info:
[2024.01.27-09.53.25:599][ 0]LogInit: - we are the first instance of this executable
[2024.01.27-09.53.25:599][ 0]LogInit: - this process' id (pid) is 84, parent process' id (ppid) is 21
[2024.01.27-09.53.25:600][ 0]LogInit: - we are not running under debugger
[2024.01.27-09.53.25:600][ 0]LogInit: - machine network name is 'dc1-ins1'
[2024.01.27-09.53.25:600][ 0]LogInit: - user name is 'steam' (steam)
[2024.01.27-09.53.25:600][ 0]LogInit: - we're logged in locally
[2024.01.27-09.53.25:600][ 0]LogInit: - we're running with rendering
[2024.01.27-09.53.25:600][ 0]LogInit: - CPU: AuthenticAMD 'AMD Ryzen 9 3950X 16-Core Processor' (signature: 0x870F10)
[2024.01.27-09.53.25:600][ 0]LogInit: - Number of physical cores available for the process: 16
[2024.01.27-09.53.25:600][ 0]LogInit: - Number of logical cores available for the process: 32
[2024.01.27-09.53.25:600][ 0]LogInit: - Cache line size: 64
[2024.01.27-09.53.25:600][ 0]LogInit: - GPU Brand Info: NVIDIA PCI-id: 10de-1401 (1043-8520)
[2024.01.27-09.53.25:600][ 0]LogInit: - Memory allocator used: Mimalloc
[2024.01.27-09.53.25:600][ 0]LogInit: - This binary is optimized with LTO: no, PGO: no, instrumented for PGO data collection: no
[2024.01.27-09.53.25:600][ 0]LogInit: - This is an internal build.
[2024.01.27-09.53.25:600][ 0]LogCore: Skipped benchmarking clocks because the engine is running in a standalone program mode - CLOCK_MONOTONIC will be used.
[2024.01.27-09.53.25:600][ 0]LogInit: Unix-specific commandline switches:
[2024.01.27-09.53.25:600][ 0]LogInit: -ansimalloc - use malloc()/free() from libc (useful for tools like valgrind and electric fence)
[2024.01.27-09.53.25:600][ 0]LogInit: -jemalloc - use jemalloc for all memory allocation
[2024.01.27-09.53.25:600][ 0]LogInit: -binnedmalloc - use binned malloc for all memory allocation
[2024.01.27-09.53.25:600][ 0]LogInit: -filemapcachesize=NUMBER - set the size for case-sensitive file mapping cache
[2024.01.27-09.53.25:600][ 0]LogInit: -useksm - uses kernel same-page mapping (KSM) for mapped memory (OFF)
[2024.01.27-09.53.25:600][ 0]LogInit: -ksmmergeall - marks all mmap'd memory pages suitable for KSM (OFF)
[2024.01.27-09.53.25:600][ 0]LogInit: -preloadmodulesymbols - Loads the main module symbols file into memory (OFF)
[2024.01.27-09.53.25:600][ 0]LogInit: -sigdfl=SIGNAL - Allows a specific signal to be set to its default handler rather then ignoring the signal
[2024.01.27-09.53.25:600][ 0]LogInit: -crashhandlerstacksize - Allows setting crash handler stack sizes (204800)
[2024.01.27-09.53.25:600][ 0]LogInit: -noexclusivelockonwrite - disables marking files created by the engine as exclusive locked while the engine has them opened
[2024.01.27-09.53.25:600][ 0]LogInit: -httpproxy=ADDRESS:PORT - redirects HTTP requests to a proxy (only supported if compiled with libcurl)
[2024.01.27-09.53.25:600][ 0]LogInit: -reuseconn - allow libcurl to reuse HTTP connections (only matters if compiled with libcurl)
[2024.01.27-09.53.25:600][ 0]LogInit: -virtmemkb=NUMBER - sets process virtual memory (address space) limit (overrides VirtualMemoryLimitInKB value from .ini)
[2024.01.27-09.53.25:600][ 0]LogInit: - Physical RAM available (not considering process quota): 63 GB (64228 MB, 65769980 KB, 67348459520 bytes)
[2024.01.27-09.53.25:600][ 0]LogInit: - VirtualMemoryAllocator pools will grow at scale 1.4
[2024.01.27-09.53.25:600][ 0]LogInit: - MemoryRangeDecommit() will be a no-op (re-run with -vmapoolevict to change)
[2024.01.27-09.53.25:600][ 0]LogInit: - PageSize 4096
[2024.01.27-09.53.25:600][ 0]LogInit: - BinnedPageSize 65536
[2024.01.27-09.53.25:603][ 0]LogUObjectArray: 419 objects as part of root set at end of initial load.
[2024.01.27-09.53.25:603][ 0]LogUObjectAllocator: 89056 out of 0 bytes used by permanent object pool.
[2024.01.27-09.53.25:603][ 0]LogUObjectArray: CloseDisregardForGC: 0/0 objects in disregard for GC pool
[2024.01.27-09.53.25:603][ 0]LogPaths: Warning: No paths for game localization data were specifed in the game configuration.
[2024.01.27-09.53.25:603][ 0]LogInit: Using OS detected language (en-US-POSIX).
[2024.01.27-09.53.25:603][ 0]LogInit: Using OS detected locale (en-US-POSIX).
[2024.01.27-09.53.25:603][ 0]LogInit: Warning: No paths for engine localization data were specifed in the engine configuration.
[2024.01.27-09.53.25:603][ 0]LogTextLocalizationManager: No localization for 'en-US-POSIX' exists, so 'en' will be used for the language.
[2024.01.27-09.53.25:603][ 0]LogTextLocalizationManager: No localization for 'en-US-POSIX' exists, so 'en' will be used for the locale.
[2024.01.27-09.53.25:603][ 0]LogInit: Using OS detected language (en-US-POSIX).
[2024.01.27-09.53.25:603][ 0]LogInit: Using OS detected locale (en-US-POSIX).
[2024.01.27-09.53.25:603][ 0]LogTextLocalizationManager: No localization for 'en-US-POSIX' exists, so 'en' will be used for the language.
[2024.01.27-09.53.25:603][ 0]LogTextLocalizationManager: No localization for 'en-US-POSIX' exists, so 'en' will be used for the locale.
[2024.01.27-09.53.25:603][ 0]LogPackageLocalizationCache: Processed 2 localized package path(s) for 1 prioritized culture(s) in 0.000317 seconds
[2024.01.27-09.53.25:603][ 0]CrashReportCoreLog: CrashReportClientVersion=1.0
[2024.01.27-09.53.25:603][ 0]CrashReportCoreLog: CrashReportReceiver disabled
[2024.01.27-09.53.25:603][ 0]CrashReportCoreLog: DataRouterUrl: https://o1291919.ingest.sentry.io/api/6513339/unreal/4a1a3921f51f4975b4cf8dd19022cb20/
[2024.01.27-09.53.25:604][ 0]CrashReportCoreLog: Initial state = Unknown UploadState value
[2024.01.27-09.53.25:604][ 0]CrashReportCoreLog: Initial state = Unknown UploadState value
[2024.01.27-09.53.25:604][ 0]LogCrashDebugHelper: DepotName: //UE5/Release-5.1
[2024.01.27-09.53.25:604][ 0]LogCrashDebugHelper: BuiltFromCL: 0
[2024.01.27-09.53.25:604][ 0]LogCrashDebugHelper: EngineVersion: 5.1.1-0+++UE5+Release-5.1
[2024.01.27-09.53.25:604][ 0]LogCrashDebugHelper: BuildVersion: ++UE5+Release-5.1-CL-0
[2024.01.27-09.53.26:573][ 0]CrashReportCoreLog: Got 3 pending files to upload from 'crashinfo-Pal-pid-21-529916A2C55B44F7A8E2E4D3AC4EDAC8'
[2024.01.27-09.53.26:573][ 0]CrashReportCoreLog: State change from Ready to SendingFiles
[2024.01.27-09.53.26:573][ 0]CrashReportCoreLog: CompressAndSendData have 3 pending files
[2024.01.27-09.53.26:573][ 0]CrashReportCoreLog: CompressAndSendData compressing 394 bytes ('/palworld/Pal/Saved/Crashes/crashinfo-Pal-pid-21-529916A2C55B44F7A8E2E4D3AC4EDAC8/Diagnostics.txt')
[2024.01.27-09.53.26:573][ 0]CrashReportCoreLog: CompressAndSendData compressing 152 bytes ('/palworld/Pal/Saved/Crashes/crashinfo-Pal-pid-21-529916A2C55B44F7A8E2E4D3AC4EDAC8/CrashReportClient.ini')
[2024.01.27-09.53.26:573][ 0]CrashReportCoreLog: CompressAndSendData compressing 5760 bytes ('/palworld/Pal/Saved/Crashes/crashinfo-Pal-pid-21-529916A2C55B44F7A8E2E4D3AC4EDAC8/CrashContext.runtime-xml')
[2024.01.27-09.53.26:581][ 0]LogInit: Using libcurl 7.83.1
[2024.01.27-09.53.26:581][ 0]LogInit: - built for Linux
[2024.01.27-09.53.26:581][ 0]LogInit: - supports SSL with OpenSSL/1.1.1n
[2024.01.27-09.53.26:581][ 0]LogInit: - supports HTTP deflate (compression) using libz 1.2.12
[2024.01.27-09.53.26:581][ 0]LogInit: - other features:
[2024.01.27-09.53.26:581][ 0]LogInit: CURL_VERSION_SSL
[2024.01.27-09.53.26:581][ 0]LogInit: CURL_VERSION_LIBZ
[2024.01.27-09.53.26:581][ 0]LogInit: CURL_VERSION_IPV6
[2024.01.27-09.53.26:581][ 0]LogInit: CURL_VERSION_ASYNCHDNS
[2024.01.27-09.53.26:581][ 0]LogInit: CURL_VERSION_LARGEFILE
[2024.01.27-09.53.26:582][ 0]LogInit: CurlRequestOptions (configurable via config and command line):
[2024.01.27-09.53.26:582][ 0]LogInit: - bVerifyPeer = false - Libcurl will NOT verify peer certificate
[2024.01.27-09.53.26:582][ 0]LogInit: - bUseHttpProxy = false - Libcurl will NOT use HTTP proxy
[2024.01.27-09.53.26:582][ 0]LogInit: - bDontReuseConnections = false - Libcurl will reuse connections
[2024.01.27-09.53.26:582][ 0]LogInit: - MaxHostConnections = 16 - Libcurl will limit the number of connections to a host
[2024.01.27-09.53.26:582][ 0]LogInit: - LocalHostAddr = Default
[2024.01.27-09.53.26:582][ 0]LogInit: - BufferSize = 65536
[2024.01.27-09.53.26:582][ 0]CrashReportCoreLog: Sending HTTP request: https://o1291919.ingest.sentry.io/api/6513339/unreal/4a1a3921f51f4975b4cf8dd19022cb20/?AppID=CrashReporter&AppVersion=5.1.1-0%2B%2B%2BUE5%2BRelease-5.1&AppEnvironment=Release&UploadType=crashreports&UserID=-000003e8%7C%7C
[2024.01.27-09.53.27:140][ 0]CrashReportCoreLog: OnProcessRequestComplete(), State=SendingFiles bSucceeded=1
[2024.01.27-09.53.27:140][ 0]CrashReportCoreLog: State change from SendingFiles to SendingFiles
[2024.01.27-09.53.27:140][ 0]CrashReportCoreLog: All uploads done
[2024.01.27-09.53.27:140][ 0]CrashReportCoreLog: State change from SendingFiles to Finished
[2024.01.27-09.53.27:608][ 0]CrashReportCoreLog: Final state (Receiver) = Finished
[2024.01.27-09.53.27:608][ 0]CrashReportCoreLog: Final state (Receiver) = Unknown UploadState value
[2024.01.27-09.53.27:608][ 0]LogCore: Engine exit requested (reason: CrashReportClientApp RequestExit)
[2024.01.27-09.53.27:608][ 0]LogExit: Preparing to exit.
[2024.01.27-09.53.27:610][ 0]LogExit: Object subsystem successfully closed.
[2024.01.27-09.53.27:610][ 0]LogModuleManager: Shutting down and abandoning module HTTP (12)
[2024.01.27-09.53.27:633][ 0]LogModuleManager: Shutting down and abandoning module SSL (11)
[2024.01.27-09.53.27:633][ 0]LogModuleManager: Shutting down and abandoning module CrashDebugHelper (8)
[2024.01.27-09.53.27:633][ 0]LogModuleManager: Shutting down and abandoning module CoreUObject (6)
[2024.01.27-09.53.27:633][ 0]LogModuleManager: Shutting down and abandoning module PakFile (4)
[2024.01.27-09.53.27:633][ 0]LogModuleManager: Shutting down and abandoning module RSA (3)
[2024.01.27-09.53.27:636][ 0]LogExit: Exiting.
dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
CommonUnixCrashHandler: Signal=11
Engine crash handling finished; re-raising signal 11 for the default handler. Good bye.

swap问题

不知道有没有人遇见过这种情况

root@iZn4addrzagtf9opmjdcdyZ:~# swapon --show
NAME                      TYPE SIZE  USED PRIO
/root/myswapfile/swapfile file  64G 32.6M   -2

root@iZn4addrzagtf9opmjdcdyZ:~# sudo sysctl -p
vm.swappiness = 80
kernel.sysrq = 1
net.ipv4.neigh.default.gc_stale_time = 120
net.ipv4.conf.all.rp_filter = 0
net.ipv4.conf.default.rp_filter = 0
net.ipv4.conf.default.arp_announce = 2
net.ipv4.conf.lo.arp_announce = 2
net.ipv4.conf.all.arp_announce = 2
net.ipv4.tcp_max_tw_buckets = 5000
net.ipv4.tcp_syncookies = 1
net.ipv4.tcp_max_syn_backlog = 1024
net.ipv4.tcp_synack_retries = 2
net.ipv4.tcp_slow_start_after_idle = 0

root@iZn4addrzagtf9opmjdcdyZ:~# cat /proc/sys/vm/swappiness
80

如上所示我的swap为64g 并且swappiness的值为80可以确定是已经生效的了但是哪怕内存满载崩溃掉 swap的占用也不会超过百分之1 可谓是奇怪至极。。

Linux 服务器效果不明显

波谷是设置的每天6点自动重启。

1.3.0 Update 2检查了文件hash确认是替换了的，目前来看CPU使用，和内存增长速度和更新前区别不大

更新了beta3跑一段时间看看

player can't join server

sometime some player can't joins server got to restart server then some player can join but some still got a problem
is this related to your unofficial fix? or can you fix it
谢谢你

[反馈] 延迟问题

当在据点的帕鲁过多时，服务器的RTT会飙升到100+ms，但跑图远离据点的帕鲁时RTT会稳定在80ms
系统是Windows

如果是内网穿透自己本地起的服务器没有使用steamcmd的情况呢

大佬这个文件是不是只对通过steamcmd实现的服务器生效，是否有对PalServer-Win64-Test.exe生效的对应文件

Good job

Thanks

不同版本的反馈

系统：Ubuntu 22
CPU：24核心 8255C
内存：48G

游戏内FPS

PalServer-Linux-Test-Patch-Update-4-Beta

1.3.0 Update 3

服务器内存占用

总结，似乎有一点效果，内存占用不再非常夸张，未使用前单一服务端能占用超过30G内存。

非常不错的项目,有办法提高服务端的FPS吗?

服务端的FPS一般跟那些配置有关系呢? CPU?还是内存?

目前版本 RCON 存在的两个 bug，看看能否尝试修复？

两个都是 rcon 指令的问题：

ShowPlayers 指令在服务器内有玩家的时候无法执行。
Broadcast 指令内无法发送空格和中文之类的，发送一段英文只会保留第一个单词，即使带了 "" 也不行。

Server Crash

My server suddenly crash for the first time i don't know that it related to the fix all not aswell
Here the crash report just in case it useful for you 谢谢你

3 9851B2AF4A586FEF1A5F6396BECA6693 UECC-Windows-D22015CE4232976E708FA9B814C2CD32_0000 false false false Crash Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000920 5108 7883 false false false UE-Pal PalServer-Win64-Test-Cmd Test WindowsServer Windows Server Unset PalServer 5.1.1-0+++UE5+Release-5.1 CommandLineRemoved 0 th-TH ++UE5+Release-5.1-CL-0 **UE5*Release-5.1-CL-0-Win64-Test false false C:/Users/Administrator/Desktop/steamcmd/steamapps/common/PalServer/Pal/Binaries/Win64/ C:/Users/Administrator/Desktop/steamcmd/steamapps/common/PalServer/ 8B4289B147E0F6E1A4CE5F971011EF8B 8b4289b147e0f6e1a4ce5f971011ef8b CSNE-SUTT-MP9S Administrator 0 6 12 1 AuthenticAMD AMD Ryzen 5 3600X 6-Core Processor Microsoft Basic Render Driver Windows Server 2019 (Release 1809) [10.0.17763.737] 68646203392 78846750720 4096 64 0 0 0 0 0 0 0 0 0 0 PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd PalServer_Win64_Test_Cmd kernel32 ntdll PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2af6304 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2a310f2 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 27dd935 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2e2a959 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2f1969d PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 463c28a PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 4951606 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 494e547 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 4947cbf PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 494ec51 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 4950f6f PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 4951bdd PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 4bb18a1 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 4bb2395 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 13dc7ac PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 12aefab PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 129dd5c PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 4b3c91d PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 49c21cc PalServer-Win64-Test-Cmd 0x00007ff672c00000 + b16c92 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + b2078c PalServer-Win64-Test-Cmd 0x00007ff672c00000 + b2085a PalServer-Win64-Test-Cmd 0x00007ff672c00000 + b226b6 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + b2b4d4 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 5cbfd36 KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 02A06584261446217D0E910CA656958771946CBB ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d7772c PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 5d4a49e VCRUNTIME140 0x00007ffce3820000 + f73f ntdll 0x00007ffceeb60000 + a477f ntdll 0x00007ffceeb60000 + 4bef ntdll 0x00007ffceeb60000 + a34ee PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2af6304 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2a310f2 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 27dd935 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2e2a959 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2f1969d PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 463c28a PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 4951606 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 494e547 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 4947cbf PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 494ec51 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 4950f6f PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 4951bdd PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 4bb18a1 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 4bb2395 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 13dc7ac PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 12aefab PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 129dd5c PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 4b3c91d PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 49c21cc PalServer-Win64-Test-Cmd 0x00007ff672c00000 + b16c92 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + b2078c PalServer-Win64-Test-Cmd 0x00007ff672c00000 + b2085a PalServer-Win64-Test-Cmd 0x00007ff672c00000 + b226b6 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + b2b4d4 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 5cbfd36 KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 true 6620 GameThread ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2beaa3d PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2beba7a PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2bd66f0 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4b004 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 2324 Foreground Worker #0 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2beaa3d PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2beba7a PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2bd66f0 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4b004 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 5212 Foreground Worker #1 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2beaa3d PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2beba7a PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2bd66f0 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4b004 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 3640 Background Worker #2 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2beaa3d PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2beba7a PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2bd66f0 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4b004 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 6884 Background Worker #3 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4adfe PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 4016 BackgroundThreadPool #0 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2bd48a3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4b004 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 5304 Reserve Worker #0 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2bd48a3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4b004 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 5136 Reserve Worker #1 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2bd48a3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4b004 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 6388 Reserve Worker #2 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2bd48a3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4b004 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 740 Reserve Worker #3 ntdll 0x00007ffceeb60000 + 9fde4 KERNELBASE 0x00007ffcebac0000 + 396c1 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2f69b21 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 2380 HttpManagerThread ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 13a0046 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 7036 OnlineAsyncTaskThreadNull DefaultInstance(1) ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d1a60e PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4b004 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 7076 OutputDeviceRedirector ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4adfe PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 6316 IOThreadPool #0 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4adfe PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 1456 IOThreadPool #1 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4adfe PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 1316 UnknownThreadPool #0 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4adfe PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 868 UnknownThreadPool #1 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4adfe PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 6332 UnknownThreadPool #2 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4adfe PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 7024 UnknownThreadPool #3 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4adfe PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 2784 UnknownThreadPool #4 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2c4adfe PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 5144 UnknownThreadPool #5 ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 33302e5 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 4424 FMessageBus.DefaultBus.Router ntdll 0x00007ffceeb60000 + 9fde4 KERNELBASE 0x00007ffcebac0000 + 396c1 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d8860a PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 112c456 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 4532 LiveLinkMessageBusDiscoveryManager ntdll 0x00007ffceeb60000 + 9f7e4 mswsock 0x00007ffcea3c0000 + a68d mswsock 0x00007ffcea3c0000 + bc0e WS2_32 0x00007ffcedaa0000 + 143ee PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2f5b729 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2f5e2ee PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2141bde PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 5540 FTcpListener ntdll 0x00007ffceeb60000 + 9f7e4 KERNELBASE 0x00007ffcebac0000 + 383d3 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d89b6b PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2e9ecc2 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d87b57 PalServer-Win64-Test-Cmd 0x00007ff672c00000 + 2d82a9a KERNEL32 0x00007ffcebd80000 + 17974 ntdll 0x00007ffceeb60000 + 6a271 false 6600 FAsyncPurge 638419042032050000 1 Win64 [Windows Server 2019 (Release 1809) [10.0.17763.737] 64b] AMD Ryzen 5 3600X 6-Core Processor 1.0 C:\Users\Administrator\Desktop\steamcmd\steamapps\common\PalServer\Pal\Binaries\Win64\tbb.dll C:\Users\Administrator\Desktop\steamcmd\steamapps\common\PalServer\Pal\Binaries\Win64\PalServer-Win64-Test-Cmd.exe C:\Users\Administrator\Desktop\steamcmd\steamapps\common\PalServer\Engine\Binaries\Win64\EOSSDK-Win64-Shipping.dll C:\Users\Administrator\Desktop\steamcmd\steamapps\common\PalServer\Engine\Binaries\ThirdParty\DbgHelp\dbghelp.dll C:\Users\Administrator\Desktop\steamcmd\steamapps\common\PalServer\Engine\Binaries\ThirdParty\Steamworks\Steamv153\Win64\steam_api64.dll C:\Users\Administrator\Desktop\steamcmd\steamapps\common\PalServer\Engine\Binaries\ThirdParty\Windows\WinPixEventRuntime\x64\WinPixEventRuntime.dll 1 false 0 0 WindowsServerNo errors NullRHI WindowsServer 16 <__sentry>{ "tags": { "version": "0.1.3.0", "callstackhash": "456F51F00B4F68F1D8A19314F4107E581E44A294","revision": "47084", "platform": "Windows", "players": "15", "session_id": "none_null_1706299519" } }

Error message "tdd.dll" missing when running on windows

Error message "tdd.dll" missing when running on windows
But I installed all the required runtime environments
Please tell me what is this thing that needs dll

替换后运行出现error

如图，启动时会接连出现2个error提示，但是能进入游戏，把提示框关掉之后，加入游戏/游戏过程中还会弹出第二个提示框，不知道什么情况或存在什么影响

我怀疑官方的多核优化会跑在虚拟核心上

CPU是R5 5600 没超频关了cate 和双cpps，电源管理高性能。使用官方多线程优化启动项开启服务器会出现fps低于30fps(30-26fps）的情况，不使用反而回到29-33fps,就很神奇。以及32G内存它似乎不怎么吃物理内存，全跑到缓存和虚拟内存了。

内存还是会随着跑图变大，并且人走后不会回收

刚进去3g，但传送点传一遍就11g了

tbb.dll not found

English video

Hello! I was curious if you could make/get someone to make a showcase video of the patch in English similar to this one https://www.bilibili.com/video/BV1ua4y1C7Rg/

支持ARM指令集吗？

【请教大佬】这个是怎么调试优化的

是逆向工程吗？可以简单讲下分析思路吗？想了解一下！
感谢大佬！

{Question] How to use in docker?

1.4.1版本内存貌似优化了

1.4版本更新后服务端内存依旧爆炸

官方于今天中午发布了1.4版本更新
测试了一下问题好像还是没有经过修复
服务器为linux平台
经过测试服务器6人左右大后期存档的情况下更新后服务器内存情况：

麻烦问一下这个1.4版本还会制作非官方修复吗？真正的官方修复到底什么时候才能到来。。。。

大佬，有个bug问题不知道你这边逆向后有没有看到过，可以帮忙看下么

新版本当公会抓到一定数量帕鲁就会坏档，在线被弹出服务器，弹框【您与主机的连接已中断。】，然后再进去就是卡loading的现象

目前我的档公会成员不管是谁，抓到第五只就会坏档
我们想把不玩的人T出公会，会长T人无法成功，一直等待中

各位大佬，Linux服务端怎么配置才能让他工作在多核心模式下？

各位大佬，Linux服务端怎么配置才能让他工作在多核心模式下，配置是8核32G，我看他一直跑的是单核

你们会存在跑两步退一步的情况吗？

比如高处落下，或爬高点。

https://api.xiaoheihe.cn/v3/bbs/app/api/web/share?link_id=116003397

根据这个帖子测试出来是Serverfps的问题，但是设置了貌似阿里的服务器跑不上这个帧率

有没有人知道是什么问题？

CPU吗？14900K在不调整帧率也会出现只是更少，测试官方服务器和大部分社区服都这样

打了补丁掉线后回档。。。

俩服都是打完补丁基本上同时掉的线而且回档了

Any idea on how to fix rubberbanding ?

The patch did help for the memory leaks but I'm still experiencing a lot of rubber bands on a 32Gb 12 cores server

关于Linux端内存优化的问题

使用了提供的Linux端内存优化的文件后，存储空间占用较大，目前已经到达100G的大小，有什么办法么？

[winServer]缺少tbb.dll

windows版本需要安装什么依赖库？

[讨论] 感觉差别不大？

打完补丁还是能吃到30G的提交，CPU占用和服务器FPS也差不多，是我机子太差了没啥效果吗（

平均4人在线的朋友服

前

后

注意

以下脚本暂时不能使用需要作者提供Linux的补丁文件patch.bin。脚本仅仅作为示例

PALWORLD_PATH="/palworld"
PATCH_URL="https://github.com/VeroFess/PalWorld-Server-Unoffical-Fix/raw/main/patch/0.1.3.0/windows/patch.bin"

mkdir "${PALWORLD_PATH}/patch"
cd "${PALWORLD_PATH}/patch"
echo "Download: patch"
wget "${PATCH_URL}" -O patch.bin
wget -c https://github.com/sisong/HDiffPatch/releases/download/v4.6.9/hdiffpatch_v4.6.9_bin_linux64.zip -O hdiffpatch.zip
unzip -u hdiffpatch.zip

echo "Backup: "${PALWORLD_PATH}/Pal/Binaries/Linux/PalServer-Linux-Test.bak""
cp -u "${PALWORLD_PATH}/Pal/Binaries/Linux/PalServer-Linux-Test"  "${PALWORLD_PATH}/Pal/Binaries/Linux/PalServer-Linux-Test.bak"
echo "Patch ..."
"${PALWORLD_PATH}/patch/linux64/hpatchz" -f "${PALWORLD_PATH}/Pal/Binaries/Linux/PalServer-Linux-Test.bak" patch.bin "${PALWORLD_PATH}/Pal/Binaries/Linux/PalServer-Linux-Test"
echo "Patch: done"

# cp -f "${PALWORLD_PATH}/Pal/Binaries/Linux/PalServer-Linux-Test.bak" "${PALWORLD_PATH}/Pal/Binaries/Linux/PalServer-Linux-Test"

verofess / palworld-server-unoffical-fix Goto Github PK

palworld-server-unoffical-fix's Introduction

The era of PalWorld-Server-Unofficial-Fix has come to an end!

PalWorld-Server-Unoffical-Fix 的时代结束了！

Warn! It is very possible that there are two different servers in Linux! The basic server I use is Palworld Dedicated Server (ID: 2394010). Some people reported that the appid is different after replacing the file. Please check in advance!

警告！Linux很有可能存在两个不同的服务端！我使用的基础服务端为 Palworld Dedicated Server (ID：2394010 )，有人反馈替换文件后出现appid不同的问题，请提前检查！

Now we have Discord! Some friends and I believe this game has great potential, so we're preparing to create an unofficial server-side script system for it. Of course, if you have any questions about unofficial fixes, we also have a dedicated channel for that!

现在我们有了Discord! 我和一些朋友认为这个游戏非常有潜力，所以我们准备为他制作非官方的仅服务端脚本系统。当然如果你有关于非官方修复的问题我们也有对应的频道！

PalWorld-Server-Unoffical-Fix

Fix what?

How to use?

It's safe?

PalWorld 服务器非官方修复

修复了什么？

如何使用？

它安全不？

palworld-server-unoffical-fix's People

Contributors

Stargazers

Watchers

Forkers

palworld-server-unoffical-fix's Issues

游戏内FPS

服务器内存占用

注意

Recommend Projects

Recommend Topics

Recommend Org