#PSO2 GAMEGUARD ERROR 114 FULL#
#PSO2 GAMEGUARD ERROR 114 PRO#
#PSO2 GAMEGUARD ERROR 114 WINDOWS#

I'm thinking the long file names could be causing performance issues on most file systems.

#PSO2 GAMEGUARD ERROR 114 WINDOWS#

Reproductionīoot up the game, select a server, select a characterįor what I have looked into and heard from people who are experienced from tinkering with the game on Windows apparently the file names for the assets are extremely long as they are based off the MD5 of the path as well as the file name and extension. Game boots up fine however the framerate dies after selecting a character & loading the main map.

that I have checked whether there are updates for my system available.

that I haven't found an existing compatibility report for this game.

#PSO2 GAMEGUARD ERROR 114 FULL#

Link to full system information report as Gist:.

Driver/LLVM version: 4.6 (Compatibility Profile) Mesa 22.0.0-devel (git-676ccacebc).

Name of the game with compatibility issues: Phantasy Star Online 2: New Genesis.

Issue transferred from posted on T20:12:43: Compatibility Report

Phantasy Star Online 2: New Genesis framerate problems

Said drive is NTFS (the compatdata is symlinked back into a BTRFS user home dir - the same setup I use for all my other games and reports). But I've also no other choice due to lack of space on solid state storage. But as soon as the screen unfreezes, the connection is immediately killed in Error 630 as it jumps into a disconnected Aelio.Ĭould this be linked to the I/O problems? Perhaps. With KSysGuard, I can tell that it's still connected and receiving/sending some KBs of data back and forth for most of this. On Linux, I've noticed that it does get as far as loading the event call, and even receives a local convo from some players amidst the duration of loading, but most of this time is spent staring at a frozen display w/ sound while it's fetching data. The same machine on the Windows partition can successfully connect and load into NGS spawn just fine. Might be a network connectivity error, however I have yet to confirm this on the Windows side.ĥMIN EDIT: So I went back and checked. usually just as the player character spawns in. Which is a good thing.īut like the comment above, NGS seems to have issues.īad IO seems like a very familiar problem NGS has, even on Windows - from my experience, a first boot will always take a really long time but on the high capacity rotational drive I'm playing it on (not enough space on solid state to put it in), in Linux, I can't seem to connect - quits on Error 630. PSO2 classic works perfectly, as far as I can tell. Indeed, I can confirm that the game now boots, on both GE and Experimental. Network: Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8822ceĭrives: Local Storage: total: 593.96 GiB used: 196.73 GiB (33.1%) Graphics: Device-1: Advanced Micro Devices Renoir driver: amdgpu v: kernelĭisplay: x11 server: X.org 1.20.11 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa Machine: Type: Convertible System: HP product: HP ENVY x360 Convertible 15-ee0xxx v: Type1ProductConfigId System: Host: localhost Kernel: 5.12.4-1-default x86_64 bits: 64 Desktop: KDE Plasma 5.21.5 Target: graphical.target Compilers: gcc: 7.5.0 alt: 7 Shell: bash v: 4.4.23 running in: tty 1 inxi: 3.1.00 Info: Processes: 285 Uptime: N/A Memory: 15.57 GiB used: 1.98 GiB (12.7%) Init: systemd v: 234 runlevel: 5 Message: Advanced graphics data unavailable in console for root. Graphics: Device-1: NVIDIA GM204 vendor:.

#PSO2 GAMEGUARD ERROR 114 PRO#

Machine: Type: Desktop Mobo: ASUSTeK model: Z170 PRO GAMING v: Rev X.0x serial: 150647662404153 UEFI: American MegatrendsĬPU: Quad Core: Intel Core i5-6600K type: MCP arch: Skylake-S speed: 4400 MHz min/max: 800/4400 MHz

Pso2 gameguard error 114