Exported version is an older version of my game, not the one I'm asking Construct to export.

Hello,

Today I have a big problem which I guess should be really easy to solve but it has been driving me crazy for quite some time.

Here is what I'm doing:

- I export a full version of my game and test it.

- I then activate the events dedicated to turn it into a demo version. (which is working perfectly in the preview)

- I then export the demo version of my game.

- When I test the demo version, it's actually the full version of it, even if I hardcode the fact that it's a demo (i.e. not just turning my "isdemo" variable to true but actually deactivating the non-demo event in the code).

I guess this is a due to cache problems or something similar. I asked chatGPT and did everything it told me (disabling cache in Chrome, deleting the folders in appdata/local, deleting the previous files in the download folder, changing the project's name in the project properties, closing and relaunching Construct) but nothing helps, it's impossible to actually export a correct demo version of my game.

And I'm 100% sure my events are correct. I also simply added a "demo" tag on the title screen to make sure it is the correct version that is exported, and it's not there in the export.

Any tips on managing to export a version of a game that is actually the one I'm asking Construct to export?

Thanks!

I've posted a video on youtube where I show the problem:

youtu.be/FAxbETYQga8

Here is what happen :

- I preview my game

- I add a big DEMO white text on the title screen.

- I preview the game, the big white DEMO text is present.

- I export my game.

- I play the exported version, the big white DEMO text is not present.

- I preview in editor again, the text is there.

Thanks for your help! I already tried your proposal 3, 4 and 5 before posting and it didn't help. I'll try the other 2 and I'll post here if it solves the problem.

Seems like I'm doing something really wrong and I would like to find a clean and definitive solution if it's possible, but in the meantime, being able to export successfully would already be something.

So, I tried the following:

- Save the project locally, reload it from the local drive and export it.

- download the project from the export manager instead of the download button.

- I turned off Windows Defender, in the custom settings and in the advanced settings.

None of that worked.

Then, the best part, I loaded the game project on ANOTHER computer, and exported it from that computer, then ran it on that computer, and as incredible as it sounds, it was STILL not working!

As a final try, I deleted the Steamworks plugin and exported, and with it removed, it WORKED!

So, as stupid as it sounds, it seems to be the Steamworks plugin is causing this bug.

I recently had more problems with Steamworks plugin (see here), so at least for me it seems to not be usable in its current state Ashley . Unless something is wrong with my computer or the way it is setup, or I don't know what.

If you need more information about this problem, I'd be happy to help. I can imagine I'm not the only person in the world to run into this kind of problems.

IIRC Construct doesn't cache any project logic when you export, so it will regenerate all project logic on every export. If it isn't updating something correctly, it should be easy to prove it with a minimal project that you can file a bug report with. However I don't recall ever seeing such an issue with Construct.

Honestly my best guess is that with large complex software projects, you probably forgot about something and have a bug in your own project logic, or made some mistake somewhere in your testing process. It's easy to do - I sometimes get mixed up with things like preparing Construct releases. There's a lot of moving parts and things like whether or not storage is clear or whether it's running in release vs. development mode are easy to confuse. In particular if you move it all over to a new fresh machine and it works the same, my best guess is it is actually working correctly.

Other than that, based on your other thread, it sounds like maybe something weird is happening to your system. Try using a different machine for a while.

That's the best I can do with telepathic debugging - our bug report guidelines are there because that's how to make sure issues get fixed.

Thank you so much for your reply.

I'll be sure to triple check everything and if I manage to reproduce the problem in a minimal project, I'll enter a bug report.