doomsdayforte
Published
Apart from the freezes I got, the game ran quite well. The unfortunate thing is that I didn't have these freezes until I updated graphics.
Sometimes the game would freeze on the boss death fadeout. The audio would start the victory theme, but I'd be unable to do anything afterwards. This only started happening on upgrading drivers to nVidia 470.161.03; I had no issues on 470.141.03. Disabling boss fadeouts seems to have stopped the problem.
I also had freezes when those bee enemies would divebomb to the ground and explode, like the warp effect was messing with the game, but I just played a run where it didn't happen. I don't remember if I had gone to Proton 7.0 when that happened.
I have no experience with the Windows version of the game, but the game ran perfectly for me.
The only thing that stood out to me as a concern or 'this is not normal' situation is the text during the story sequences being faster than the spoken dialog. There were one or two lines that were either slightly cut off by another line, but I have no idea if this is how it is on Windows or not.
The movie files need to be renamed from "name.wmv" to "name.wmv.bak" in order to start the game.
A couple of hitches. The snowy area brought the worst performance, but that's understandable given the heavy snow falling there.
I originally played this on my old Mint install, and I got consistent lockups in an early area ('a man's head worn for a hat' was the topic of discussion), but I managed to get as far as training with Patan's Tusk, the final weapon, before I got another this time around. In normal play, I had it happen in The Dam chapter, and I got through it by lowering the resolution to minimum and equipping another weapon. I was able to return to my normal resolution and I had no other issues even when using that weapon until the very end of the game, where the 'dodge the credits' minigame brought another freeze.
You need to rename the extensions on the movie files in "[install]/data/video" to .bak since the game will not boot otherwise.
I still can't determine what's causing the lockups as I experienced with Sonic & All-Stars Racing Transformed (possibly hardware related), but at least this game didn't trip them as often as SART.
As long as you keep the game on Borderless and adjust the settings for speed, you should be fine.
There are augmented reality signs, "Visions", that appear in the cities and other locations. Every one of these had serious artifact problems no matter what I did. The water texture outside of the OSF HQ in Suou also had this same effect. Screenshot for example: https://steamcommunity.com/sharedfiles/filedetails/?id=2924510078
In trying to get a better framerate out of the game, I swapped from Borderless to standard Fullscreen. The game started to softlock at random times, first in the shop, then in the middle of a cutscene. Switching back to Borderless stopped these from happening.
While running the game on medium settings, the game would start out running fine, but it would eventually slow and chug on the framerate, even when nothing was happening. Setting everything to low stopped this from happening.
Apart from the issues introduced by Fullscreen, I had the game softlock during the first Phase 9 Yuito boss battle when transitioning from cutscene to gameplay. It only happened once.
I played this to completion of Yuito's story on the Free Weekend, thus why it shows as unowned.
PROTON_FORCE_LARGE_ADDRESS_AWARE=1
Because the config tool doesn't work, I had to open Launcher.exe in Wine (separate from Proton), set the game up as desired, then transfer the generated settings.xml file to the proper folder in compatdata.
Sometimes running the game in "windowed/fullscreen" as the game called it would look weird, like the game was running at a low resolution blown up to fullscreen size. There were also some weird shadows/shading, like a somewhat pixelated shadow on Knuckles' white eye area on the victory results screen.
Sometimes the game graphics would freeze, and I would lose all input and have to restart the machine manually.
Occasionally, the game would hang (video stops, audio keeps playing) during races. It would most often hang in menus, usually when selecting a venue in World Tour mode. Sometimes the game would recover, but other times, it would need a full system restart.
I originally played with updated graphics drivers (nvidia-driver-525) and was able to get the game to work on Proton 7.0. I had the lockups then and in another game, so I decided to use the older nvidia-driver-470 that I was using before on my other reports, hoping for a more stable experience. The other game worked better with it (so far), but SART would give me only a white screen for a split second. Every other version of Proton newer than 4.11 did this.
The config tool gives an unhandled exception error either as soon as it's loaded or when you try to access the Graphics options. It is unable to see the graphics card, showing it as 'undefined', and will throw another error before stopping entirely. And yet it works perfectly in Wine 8.0.
I can abide the 15-second freezes in the middle of a race, the three or four times it happened total. When it locks so badly I have to hold the power button to do anything, that's just not cool.
Apart from the few crashes I had and some dropping frames, the game ran quite all right.
A couple of areas had dropping frames even when there wasn't any action happening on screen, like in Gallowsbog.
I had a number of crashes that happened out of the blue, plus some that happened as the result of my actions (mostly clicking and dragging items between inventories in Croakwood). I also had the game softlock once when using the controller and sending Katarina back to town from Croakwood, but I didn't try the controller again after that.
Investing any points in Katarina's Wail of Vengance skill provided by the Blue Blood DLC will erroneously inflate her damage per second display. While the actual damage output doesn't change, the in-game weapon comparison will take this inflated number into account, throwing off her performance in combat.
I haven't played this in Windows, so I don't know if this is a Linux bug or not.
I finished the game after 19 hours, but I couldn't have crashed more than five times overall.
I followed the directions here (https://lastremnant.fandom.com/wiki/PC_Tweaking#Decreasing_texture_pop-in) for decreasing texture pop-in. This was not necessary to run the game, but it was just for additional performance enhancement.
This only happened one time, but the game audio all went static, and the frame rate dropped dramatically/started dropping frames. It went away when I went to the title screen.
The game locked up on me twice, once during a text cutscene, another as soon as a battle began. These were somewhat close to each other (same day), but there were no other issues with freezing or the like.
I put all of the graphics settings to as high as I could get them, and I didn't have any slowdown. There still is texture pop-in despite the .ini edit, but playing TLR through Proton feels equal to playing it on Windows.
It worked perfectly out of the box.
During the THINK! autorunner sections, there were some parts where the game felt like it'd start applying frameskipping though they were brief and rare.
Other than the small frameskip issue I had, everything else about this was perfect in terms of running and working.
