Crosscode refuses to boot on Arch Linux.

[Linker]

I hate to ask for tech support here, but I am at a loss for what is wrong, and I can't see to find any info anywhere online. Basically I click to start the game, Steam claims it's running, then says it isn't.
I am on Arch Linux, and have just done a system update, and on reboot the game stopped working. Though the packages that were updated seemed completely unrelated to the game or steam at all.
Any attempt of help at all is appreciated...

[Linker]

Alright I've uploaded my /etc/fonts file to my site if anyone is still interested trying to fix it with only the included nwjs, though I think I might use the solution myself.
It is at http://linkerlabs.net/fonts, if you need any more system files I'll be happy to upload them, but I do want to update my system sooner or later.

[hagabaka]

引用自 Linker：

Alright I've uploaded my /etc/fonts file to my site if anyone is still interested trying to fix it with only the included nwjs, though I think I might use the solution myself.
It is at http://linkerlabs.net/fonts, if you need any more system files I'll be happy to upload them, but I do want to update my system sooner or later.

I'm getting the same error with those font config files. It seems like the files are in the newer format, since they contain "<its:rules ...>" which is what causes the older versions of fontconfig fail.

[Cheeseness]

Hey friends! We're trying to hunt down the earliest NW.js version that includes newer fontconfig (so as to minimise potential upgrade related work). Looking at dates on the relevant issues, it seems that the change was reverted and reapplied a couple of times. 0.33.0 was the first version to include Chromium 69 stable, 0.34.0 has Chromium 70 stable, and 0.35.5 has Chromium 71 stable.

I suspect that 0.35.5 is probably going to be the one to aim for, but if anybody affected is keen to be a guineapig and confirm, that would be great.

You should be able to copy the files from the Linux release archive into the CrossCode game folder and rename the "nw" binary to "CrossCode".

https://nwjs.io/blog/v0.33.0
https://nwjs.io/blog/v0.34.0
https://nwjs.io/blog/v0.35.5

[Jefffafa]

I just tested out all three versions of nw.js. I ran a system update right before testing this out.


v0.33:
I didn't get the fontconfig errors and I saw the initial loading screen, but the game immediately crashed with the error

/proc/self/exe: symbol lookup error: ~/.local/share/Steam/steamapps/common/CrossCode/assets/modules/greenworks-0.13.0/linux64/greenworks-linux64.node: undefined symbol: _ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorE

v0.34
Game Runs :)
I get the following errors but after playing for about 10 minutes I didn't run into any issues.

[17085:17112:1018/013641.210126:ERROR:web_database_backend.cc(113)] Cannot initialize the web database: 2
[17085:17085:1018/013641.310984:ERROR:desktop_window_tree_host_x11.cc(1125)] Not implemented reached in virtual void views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType)
[17157:17165:1018/013704.880225:ERROR:broker_posix.cc(106)] Error sending sync broker message: Broken pipe (32)

v0.35.5
Runs with the following output still couldn't find any issues with the gameplay

[17315:17315:1018/013911.214580:ERROR:x11_input_method_context_impl_gtk.cc(144)] Not implemented reached in virtual void libgtkui::X11InputMethodContextImplGtk::SetSurroundingText(const base::string16 &, const gfx::Range &)


I think the X11 errors are being caused by Xwayland since I'm running Wayland instead of a native X session. So looks like v0.34 is a good bet. I'll run this version and play for a bit and let you know if I find anything else with it.

Thanks for the update!

[Ofara]

I dont have access to my PC to test this now, but I tried running CrossCode with latest nwjs (both ways: running the installed nw, and overwriting files and renaming executable) and both worked fine without any problems. Very nice considering the PC has an AMD iGPU with the opensource drivers.

[Cheeseness]

引用自 Jefffafa：

I just tested out all three versions of nw.js. I ran a system update right before testing this out.

Thanks!

BTW, were you testing with mouse and keyboard, or gamepad input?

[Jefffafa]

I was using mouse and keyboard, but I'll test out a game pad and update after.

[Linker]

引用自 Cheeseness：

Hey friends! We're trying to hunt down the earliest NW.js version that includes newer fontconfig (so as to minimise potential upgrade related work). Looking at dates on the relevant issues, it seems that the change was reverted and reapplied a couple of times. 0.33.0 was the first version to include Chromium 69 stable, 0.34.0 has Chromium 70 stable, and 0.35.5 has Chromium 71 stable.

I suspect that 0.35.5 is probably going to be the one to aim for, but if anybody affected is keen to be a guineapig and confirm, that would be great.

You should be able to copy the files from the Linux release archive into the CrossCode game folder and rename the "nw" binary to "CrossCode".

https://nwjs.io/blog/v0.33.0
https://nwjs.io/blog/v0.34.0
https://nwjs.io/blog/v0.35.5

Awesome! It boots now!
I'm using the latest version of NWJS because yolo, but I'll report any issues I run into.
I'm about to email the devs about it now, as, in time, other linux distros should start have the same issues as they start updating things at their own pace. They've already updated the NWJS version once (and you can use the old one in the betas section), so I don't think it is completely out of the question to eventually update a third one.

[Cheeseness]

引用自 Linker：

Awesome! It boots now!
I'm using the latest version of NWJS because yolo, but I'll report any issues I run into.
I'm about to email the devs about it now, as, in time, other linux distros should start have the same issues as they start updating things at their own pace. They've already updated the NWJS version once (and you can use the old one in the betas section), so I don't think it is completely out of the question to eventually update a third one.

I'm currently working with the developers to narrow down which one of those three specific releases is the best candidate for resolving these issues without introducing other problems.

Definitely keen to hear feedback on those if you're keen to give them a try.

[Linker]

引用自 Cheeseness：

引用自 Linker：

Awesome! It boots now!
I'm using the latest version of NWJS because yolo, but I'll report any issues I run into.
I'm about to email the devs about it now, as, in time, other linux distros should start have the same issues as they start updating things at their own pace. They've already updated the NWJS version once (and you can use the old one in the betas section), so I don't think it is completely out of the question to eventually update a third one.

I'm currently working with the developers to narrow down which one of those three specific releases is the best candidate for resolving these issues without introducing other problems.

Definitely keen to hear feedback on those if you're keen to give them a try.

Ah should I stop my email then? I haven't sent it yet lol.
(I take an eternity to write simple emails)
Definitely open to guinea pig testing though.

[Cheeseness]

引用自 Linker：

Ah should I stop my email then? I haven't sent it yet lol.
(I take an eternity to write simple emails)
Definitely open to guinea pig testing though.

Nothing wrong with reaching out if you want to ^_^

I've been testing to see whether newer builds break font compatibility on distros that are so far unaffected, and it's looking positive. I don't currently have a machine/spare machine to install Arch or any other affected distro on at the moment, so confirmation of how v0.33.0, v0.34.0, and v0.35.5 behave on affected people's machines is super valuable information.

Jefffafa's feedback is good, but I'm still keen to hear corroboration/confirmation that both gamepad and mouse/keyboard input are behaving (best to be safe when errors about unimplemented input functions are being thrown).

[DarkeoX]

Hi all, hit by this bug too:

I tried using:

nw.js v0.41.2
Node v12.9.1
Chromium 77.0.3865.90
commit hash: d801c7d-4ecee4f-bf62c46-a19bb09

I don't see fontconfig related errors now but I can't launch the game:
[568667:568667:1021/101636.691437:ERROR:component_loader.cc(164)] Failed to parse extension manifest.

EDIT:

NVM, I was just lost in NWJS way of launching app, just read the doc that says to point the folder rather than some specific file and it worked.

[hagabaka]

引用自 Cheeseness：

Hey friends! We're trying to hunt down the earliest NW.js version that includes newer fontconfig (so as to minimise potential upgrade related work). Looking at dates on the relevant issues, it seems that the change was reverted and reapplied a couple of times. 0.33.0 was the first version to include Chromium 69 stable, 0.34.0 has Chromium 70 stable, and 0.35.5 has Chromium 71 stable.

I suspect that 0.35.5 is probably going to be the one to aim for, but if anybody affected is keen to be a guineapig and confirm, that would be great.

You should be able to copy the files from the Linux release archive into the CrossCode game folder and rename the "nw" binary to "CrossCode".

https://nwjs.io/blog/v0.33.0
https://nwjs.io/blog/v0.34.0
https://nwjs.io/blog/v0.35.5

0.34.0 and 0.35.5 worked for me. Steam Controller works too as long as the game is launched from Steam.

0.33.0 shows a full screen briefly and crashes, and prints in the console "symbol lookup error: /home/hagabaka/.local/share/Steam/steamapps/common/CrossCode/assets/modules/greenworks-0.13.0/linux64/greenworks-linux64.node: undefined symbol: _ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorE"

[Cheeseness]

Just to follow up, a new build of the game using NW.js 0.35.5 is in testing and will hopefully be released soon. Thanks for your help, people <3

[Xenoryt]

Just recently got crosscode. Can confirm v0.35.5 works as well as the version of nwjs-bin in the AUR (version 0.42.4).

However, for both versions I have issues with steam controller inputs not being properly mapped (Left stick was Start; Start was RT; and was only able to aim to the left with the right pad). Was able to fix using the SC Controller suggested in https://steamcommunity.com/app/368340/discussions/1/1700542332325163878/

Force disable steam input for CrossCode and use SC Controller to map steam controller as xbox controller.