My large project slows my computer to a crawl when exporting, so I exported last night when away from the computer and was planning on doing the actual download step the next day, but the next day I open C3 and the Export Manager only contains 2 older ones from July, despite the fact that last night I checked it and it had the latest export from last night (in August). It's the same C3 app/browser (Chrome), but different Export Manager contents. What happened to the export? Thanks

construct.net/en/tutorials/using-xbox-live-uwp-apps-3

How do most if any C2/3 creators make a living income if not for consoles? My games are always too big in GB to fit under the archaic 100MB limit of phone games (unless they finally upped that limit by now, with how many GB smartphones hold these days, but a quick search suggests it's only gone up to 200MB for those of us who can't code to somehow include 'additional assets' without a tutorial that makes it easy--maybe one that C3 can write up for us?), plus people are used to phone games being free and ad-supported, and I'm not sure if ads alone lead to the big bucks.

I said this many times before, but I think C3 should embrace consoles, not run away from them. My current hope now is the handheld Steam Deck. (Which runs C3 games so fast and smoothly that I actually have to slow down aspects of my game--that I based on how slowly it ran in Preview--that are actually too fast on the Deck! Which is of course a good thing. And, no size limits for games to load up! As long as internal storage has at least a few GB free.) Assuming I have no issues with players happening upon my game in the Steam store without knowing it exists. Theoretically even online multiplayer would work on Steam, something I gave up on long ago because it wasn't allowed on Xbox's Creators Collection.

I think C3 should aim to be a console game creator. Think about it: At least Xbox games are possible on C3. Why deprecate what little console ability C3's export has? It's true that in my experience the total game size shouldn't exceed about 250 MB to run on Xbox (or else you get the infinite red loading bar even without preloading sounds) but at least it's a popular console for selling smaller games on. Why not at the very least keep Xbox/UWP going? Even if it [may be] impossible to increase the runnable size.

I also before wondered if C3 could make a deal with another company, such as Game Maker Studio or Unity, to allow C2/3 games to be imported into their software just for the sake of taking advantage of their ability to export to Xbox/PS/Switch. "Made with Construct3 & Unity".

I've always been a console guy from a young age, plus as I said my serious games are GBs in size. I hope Steam and especially the Steam Deck can finally be the answer for making a livable income making games.

I built a multiplayer game using p2p scirra signaling server & it works well. Will it still work if published to Xbox, or would I have to use Xbox multiplayer services? If so, how would I access those services & would I have to change my code to use Xbox servers? I plan to publish to Xbox using the new plug-in features.

I think you have to have the game accepted thru IDena@Xbox which I never pulled off. Although I don't know if any programming is required for that even if they did accept your game?

Our game is officially certified on Steam Deck and we never had these issues. All buttons and sticks work as they should.

Try changing "Steam input" option in controller settings in Steam.

I searched every corner of the options there but I can't figure out what you mean other than mapping Gamepad buttons manually which I already did of course. (I was looking for some tick box called 'Steam Input') To reiterate, my problem is that the following buttons don't translate or connect between C3 and Steam Deck: Right Trigger, Left Trigger, Select, Start, D-Pad. In other words, I feel like what C3 calls the "Right shoulder trigger" button doesn't find a matching button on Steam Deck (where it's called the "R2" button). But, for example, the "Right shoulder button" DOES work, despite that it's called the "R1" button on Steam Deck. If every button worked for you right away, why don't they work for me? Of course I also have the Gamepad input in C3 set to 0, for player 1.

I notice in testing my game on Steam Deck that at some point the LocalStorage must have been deleted or cleared or otherwise gone missing, so that I lost my game save that I was using while testing. Not a big issue when testing, as long as this doesn't mean that coming out with actual updates post-release could possibly clear or somehow ignore existing LocalStorage or Game Save. To confirm, there's no danger to updates somehow causing LocalStorage or Gave Saves to be deleted or otherwise no longer used, correct? And of course the Steam Deck retains LocalStorage and Game Saves, including after game updates and console restarts, correct?

Thanks

In C2, Ctrl+W merely closes the layout or event sheet, as it should, never the entire software. In C3, it closes the entire thing. For those of us with large projects, this results in another half an hour up to one hour wait just for trying to close an event sheet. The entire project has to open again, which takes at least half an hour each time, cutting into your work day, plus another wait to load the preview/images again for the first time after reopening the project. It's not right for one innocent tapping of Ctrl+W to once again result in that wonderful yell: "SHIT!!!" Since I'm also in the good habit of hitting Ctrl+S very often, I unfortunately lose that protection after hitting Ctrl+W that asks if you want to close the project without saving, which prevents the exit. The best fix would be to return Ctrl+W to closing the active layout or event sheet, but since C3 runs in a browser, maybe the next update can just add an option in settings to confirm exit. Thankfully I use C2 and just buy 1 month of C3 when it's time to export so I'm not saddled with C3, but would be a good change to make for those who use C3 all the time with large projects. I'll see if I can put this in as a feature request on the github.

But are you talking about a change in how we have to work with screenshot data in C3 vs C2? It worked perfectly in C2, so just trying to quickly find the difference.

My game handled snapshots perfectly in C2, but I had to load it up in C3 to export to Steam, am 2 weeks into it, just need to figure out what the heck changed about snapshots between C2 and C3, as it's the only feature in my game that isn't working anymore. My game has a built-in snapshots system where player can save up to 40+ snapshots which all show up in one gallery as seen below and they can save any snapshots to their safe, as the oldest snapshots get overwritten by design by new ones when space runs out, etc. This worked perfectly in C2, where every time a snapshot of canvas is taken, it saves the snapshot data as a localstorage key of Snapshot(number that global variable is on for next snapshot position) and then when you enter the gallery it loads all the localstorage values for all existing snapshots from "Snapshot1" to "Snapshot42" at most, where all of the blueish objects is a different snapshot and clicking on it shows the full version. Again, all worked perfectly in C2. Is there a change I need to do somewhere in C3? Such as at the moment the snapshot is taken, or the way it's saved to localstorage, or the way it's loaded from it.