Mikal's Forum Posts

  • Have you tried the latest version here: github.com/ConstructFund/proui

  • Use bounding box override

    gritsenko.github.io/c3_spine_plugin

    "If animation is clipping against the bounds of the C3 object, you can use the property bbox override and values to control the bounding box size and center offset. The values are based on Spine project coordinates."

  • Added Linux CEF export support (Ubuntu 22, Steam Deck testing underway).

    construct.net/en/make-games/addons/1124/steamworks-plus

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Updated Steamworks Plus for Linux CEF export (Ubuntu 22 tested.)

    construct.net/en/make-games/addons/1124/steamworks-plus

  • One other item I had to update while testing on another system: 

    patchelf --set-rpath '$ORIGIN' Steam_plus_x64.ext.so

    I don't know if you also had to do this, or there is a parameter I am missing in linking to handle this.

    This change made it possible to search locally for other needed *.so files (such as libsteam...), instead of hardcoded paths.

  • I got it working in wsl.

    I had to revert wsl to Ubuntu 22 LTS, and then the Scrirra C3 Steamworks plugin worked.

    I then compiled my Steamworks Plus extension on Ubuntu 22 (instead of 24), which also worked on wsl Ubuntu 22 (I imagine it will work on Steamdeck).

    As you mentioned about Linux, it seems like a backward and forward compatibility issue. What a mess.

    I've seen comments about compiling differently, statically linking libs, etc.

    Thanks for the model on how to do the linux port, very helpful for Steamworks Plus on linux.

  • Yes, I did, didn't see anything too interesting. I will try a dual boot setup.

    I did download it to a steam deck and as expected, that worked, so that's good.

  • Thanks for the reply.

    I think I have met the requirements, but I will recheck.

    My first experiment on actually running a c3 app in Linux was:

    - Only using the Steamworks addon that you created for Linux. So the .so is from your build (in 22 LTS) (I have not added my linux addon extension yet)

    - Ubuntu 24 (wsl), I have GUI working ok; I had to uninstall some PKG to make the windows open quickly.

    - I downloaded and installed the .deb from steampowered (which required more pkgs to be installed to run)

    - I got the results of the extension library not being listed in JS

    - I then tried the same on my ubuntu 22 LTS VM install and same result.

    I will try using Steam Deck next, using partner.steamgames.com/doc/steamdeck/loadgames, which looks like a 'fun' process. Steam can be so convoluted.

    In general, I feel like I must be missing a step or something, but will keep at it.

  • Thanks, good feedback. I know where to focus.

    What environment do you usually test regarding Linux CEF and wrapper extension and testing?

    I tried out wsl2 on Windows 11 (I installed Linux Steam from steampowered.com). I got Steam running and signed in, exported the Steam test app with the latest addon, downloaded zip to wsl2 unzipped on wsl2 (ubuntu 24), and ran the test from the command line (and from Steam using add game). The C3 app loads and runs fine (correct display), but Steam is marked as unavailable.

    I followed these directions: construct.net/en/tutorials/exporting-linux-steam-deck-3155

    However, it looks like the wrapper extension is not loaded. I connected via remote debugging, but the JS side does not have it on its list. I can launch other Linux Steam Games.

    I also see steamworks-x64.ext.so and libsteam_api.so in the x64 dir w/ the app.

    I also tried on Ubuntu 22 and got the same result (on a Parallels VM in MaCOS)

    I know you at least have it working on Steam Deck, but that's a more complex platform to debug new work. Do you have a recommendation for another environment or something I might have missed?

  • That's great that there is now Linux support for Steamworks (and thanks for sharing the development of the addon in github, so I can use it as a model.)

    I do wonder if I should continue with my Steamworks Plus addon. I see that you added DLC support, which overlaps with some the DLC support in Steamworks Plus. While they should not interfere with each other, I do think with our limited time - I don't want us to duplicate work.

    What is your suggestion here, do you expect to continue adding more features and I can just deprecate Steamworks Plus (and move on to other work, fine by me) or is there another way where we won't be doing overlapping work. I know you want to keep 3rd party devs away from the Steamworks repo, but I am wondering if that is another alternate, where there would not be overlapping work.

  • Ashley I implemented: construct.net/en/make-games/addons/1124/steamworks-plus-webview2

    I'm thinking about adding some more features, but I wanted to check in with the roadmap for the wrappers for linux and macos. I'm wondering if the C3 Steamworks Webview2 addon will add support for the linux and macos wrappers and the possibility of making steamworks-plus also support them or whether there is a different approach.

  • No, it will only work with webgl2. So far, webgpu has not shown a large performance increase in my projects.

  • Version 1.11.0:

    Expose more Greenworks Steam cloud APIs to nw.js and Electron (1.11.0: supports Greenworks v0.18.0 for NW.js v0.92.0, Steamworks SDK 1.60)

    construct.net/en/make-games/addons/244/greengrinds

  • Ok, I realized that it may be because I am trying to use when refactoring an older SDK V1 addon. Perhaps that's where the issue is, this is meant only for SDK V2.

  • Ashley

    This works for me in preview.

    Does this work for you in export to html5 also? In my case it seems to put the files I want to use as modules into c3runtime.js, so they are no longer available for import using the file descriptor.