E. Megas
Published
Crash right after you press a button on the title screen.
A "Code Error" window appears with the following debug data:
############################################################################################ FATAL ERROR in Vertex Shader compilation ShaderName: shd_pal_swapper
memory:67:22: error: syntax error, unexpected NEW_IDENTIFIER
at gml_Script_pal_swap_set ############################################################################################
stack frame is gml_Script_pal_swap_set (line 0) gml_Object_obj_calcia_Draw_0
Same crash after pressing Space on the title screen--but the error message is different now?
After pressing Space on the title screen, the game crashes right after the image fades out, and presents me with a dialog containing the following error message:
############################################################################################ FATAL ERROR in Fragment Shader compilation ShaderName: shd_pal_swapper
memory:40:8: E5005: Function "tex2Dlod" is not defined. at gml_Script_pal_swap_set ############################################################################################
stack frame is gml_Script_pal_swap_set (line 0) gml_Object_obj_calcia_Draw_0
...As you can see here, the error message is different this time..
Crash at undisplayable video as soon as you get into the lobby (it's made progress, though!).
After completing the tutorial, the lobby displays briefly but cuts to a video that doesn't display (only a white screen is shown; the audio for it plays). Right after the video "ends" the game locks up. Clicking around the blank screen does nothing; pressing Esc returns a clicking sound. The only way to exit is to stop the game using Steam, to close the window (if game is in Windowed mode), or presumably to kill the process.
As above, the opening video also doesn't display (white screen, audio for it plays as normal); however, unlike the above, this video can be skipped by pressing any key or mouse button. The rest of the game up until the lock-up after the lobby video described above works perfectly, completely without incident (title screen, name registration, tutorial, settings adjustment).
Part of the issue at hand most likely involves the internal video codec Bandai Namco is using being somehow unsupported.
Otherwise, this is a huge step up from that "Failed to create IGameClient instance!" dialog box and I hope whatever this last issue is, it's squashed so we see something playable as intended.
Lobby now accessible, but game exits after starting Casual Match: "You were kicked because cheating was detected"
The unskippable white video that appears right after the lobby menu (that locked up the game in my last report--and it will likely reappear to announce future seasons, as the title screen video obviously still has this problem, too) no longer appears, allowing me access to everything in it except Ranked Match (which is obviously level-locked). Everything offline works flawlessly until entering a Casual Match--when a match is found, right after the loading screen which follows team introductions, the game boots me back to the title screen with the dialog "You were kicked because cheating was detected." followed by a second dialog that claimed that it couldn't find the network and couldn't connect--causing a forced exit. (When I entered the lobby again I noted that I was given the standard penalty for leaving a match, so I figure I shouldn't be doing this too often.)
...So I've come this far to learn--as with the rest of you--that the EAC situation hasn't yet been resolved. This is obviously something that needs to be discussed with Bandai Namco--sooner rather than later, because the Steam version of the Gundam Battle Operation test was supposed to have similar EAC configuration issues (and that is on track to eventually have a full Steam release, too).
tl;dr 1.)There is still a codec issue that prevents video data (not accompanying audio) from playing, potentially halting use of the game (Proton issue?); 2.) Unlike other Bandai Namco titles (like Jojo All-Star Battle R), EAC has not been properly configured for Linux support, and will kick you off of the game if you try to join a match (evangelical issue with Bandai Namco--someone, most likely at Valve, has to contact them about this).
I would venture to guess that EAC Linux support has now been enabled. I believe that this game should now be playable.
Patches of slowdown, though I think this may be related to a network issue as opposed to a graphical one.
The opening movie still fails to display (audio plays normally but the video displays as a white screen). Fortunately, this can still be skipped.
Patches of slowdown (as above).
Assuming we can get past the video display issue (fortunately for Season 4 there hasn't been an "unskippable" opening video), Gundam Evolution should now be playable on Linux and, theoretically, Steam Deck. But EAC was the biggest hurdle, and we're past it. At the half anniversary, our long national nightmare is finally over!
Game freezes at black fullscreen after fully loading EAC.
This may not necessarily be an issue with EAC in and of itself--Given that there's no specific EAC error thrown either in a dialog (like Gundam Evolution used to) or in the console, the fact that the entire game refuses to start is a point of serious concern.
Further investigation is needed.
Going past the title screen returns "SendMessage() error." and crashes as the game window is opened.
Very confusing, as other reports here say this works perfectly on other systems. No information in the logs that seems to point out the error either (only some UnityMemory parameter setup and Fossilize complaining about a couple of pipeline handles not being registered).
Changed versions to 8.0-2. Now runs perfectly--just don't run it with VSync on, or Proton Experimental (as of the date of this report). X\
VSync is enabled by default--this somehow causes massive amounts of slowdown. Disabling VSync under Screen Settings fixed this issue.
If the game is allowed to run idle on the title screen/attract mode, it will automatically exit (or crash without error?) after three or four loops. Uncertain whether this is intended behavior.
Follow-up to the report just before this one. Not without some issues, still, and that exit with the attract mode loop is confusing, but I suppose now it'll do. Please note that this game doesn't have any analog support (which is to be expected as the original Saturn port didn't have it either); I'd suggest you dig out your USB arcade stick for this anyhow ^^;
Works flawlessly except for having to manually map my gamepad.
Buttons were assigned to the keyboard by default; I had to map them to my gamepad manually via the configuration menu in order to use my gamepad instead of the keyboard.
Until the cause of these crashes are identified, I don't believe it would be safe to recommend.
Crashes seem to be linked to holding down a D-pad direction and/or a button during gameplay (a gamepad was used for control). Unable to reproduce predictably but the game seems to reliably crash in some way within three minutes of gameplay.
