SecondDimension's Forum Posts

  • No problem, bug report is here:

    github.com/Scirra/Construct-3-bugs/issues/4109

    Not sure if the route of this going to end up being construct or chromium, but something very odd is that it does work when you right-click on the project name and select preview project. However if you preview the project using the dropdown shortcut on the toolbar it doesn't work. It also doesn't work when you export as nwjs project.

    (EDIT: Apologies for my first comment on that bug being somewhat emotional. I took a week off from my full time job to do gamedev, something that is very rare opportunity. Everything was working perfectly and now I updated C3 & nwjs and the resulting issues have kind of ruined my week off)

  • Default fullscreen can be achieved by simply running the Browser action "request fullscreen" on start of your 1st layout (ideally based on in-game settings).

    TheRealDannyyy that's exactly what I have always done, it has worked for a long time but it no longer does. I submitted a construct bug which was immediately closed as 'not a bug'. Perhaps this is a new problem for all of us exporting to desktop.

    Ouikka TheWindmiller did either of you officially report this as a bug anywhere?

  • Hi all, I have a topic on the main C3 board, but perhaps I should have just asked in here... how do you all get your games to start in fullscreen on desktop? The method I have used for the past few years doesn't work anymore. Is there an Chromium arg for this?

  • Hi all, this is a question for anyone who makes desktop games for Steam, itch.io etc. I would say it is normally an expectation of players that a desktop game starts in fullscreen (or at least has the option to).

    I have always used a function to request fullscreen when the game starts, this has worked in C2 and C3 for approximately 6 years without a single issue, however for whatever reason it no longer works since I updated to r210.

    So I wondered how other people achieve this?

  • Just wanted to add that I don't think this is specifically an nwjs issue, as I have the exact same problem when using Microsoft Edge.

    Despite Edge not giving me any issues yesterday, this morning it also gives me the 'Unable to save project' error. So I guess all browsers and nwjs have this same current issue.

  • — I agree it's a real pain to update nwjs - I had construct r204.2 and nwjs 44 working together really well. For the first time ever I had no issues, and approaching almost 100% confidence in the software setup, getting loads done. Then the new version of construct forced an nwjs upgrade and we're back to random bugs and fighting with all these conflicting platforms and technologies, not knowing where the fault lies. I worry you will get to that situation where every piece of software blames the other, or the response of 'tell Google to fix it', which is very daunting. It can all get pretty frustrating. I almost wish there was an option to not update and turn off the update prompts when you find a C3/nwjs combo that works.

    I do genuinely adore construct, but it's adds extra frustration for a desktop user making desktop games. I always hold out hope that Scirra would take the desktop side in house one day like they did with the mobile side of things. I guess that would mean maintaining their own version of something like nwjs or electron, so I don't see that being feasible for them any time soon.

    I decided to try Microsoft Edge (the new one based on Chromium), and it seems like the saving problems do not happen on Edge. I do have the issue with random grey boxes appearing, but the actual local folder saves is basically instant and I've had no errors in the past 3 hours - they were happening on Chrome & nwjs every 10 or 15 minutes. I made sure to update both browsers and check again, and so far Edge saves fine and Chrome/nwjs have consistent issues.

    There is definitely a problem with local folder saves, I have now experienced the same issue numerous times on both the nwjs and browser version. Every few saves it takes between 45-60 seconds to save (as opposed to normal 2 or 3 seconds), then soon after these longer save times start I will get this error:

    As I said above I have tried this on the browser version to make sure it wasn't an nwjs problem. I have also tried it on multiple file locations and hard drives on my PC (which I have full admins rights to). This never happened on r204 so must be a Construct issue. By the sounds of it if I submit a bug report with a blank project it will likely be a 'cannot replicate' issue.

    EDIT: Also want to note that once I press OK on the above error, I can try saving it a few more times and the error goes away for a while.

  • Hi, I've had a lot of issues with r210 and nwjs, there is definitely a problem with the dialogue boxes in nwjs 47 (you just get a grey box for everything). I'd recommend trying v46 as that at least functions for me (although still some odd issues).

  • jobel here is a quick list of problems that started when I upgraded:

    • Firstly a lot of issues with opening local folder saves, once every 4 or 5 saves it tells me I don't have permission to save to that folder, but if I keep trying it eventually works. Tried multiple projects and locations and still get the issues.
    • Previewing just gives me a black screen about 30% of the time, so I have to restart everything.
    • Putting the app into fullscreen no longer seems to work on a trigger, as I'm making games for desktop then I have a function which sets the application to fullscreen on startup. This has worked for years but now doesn't. I even made a small file with a single 'on start of layout' event to set the application fullscreen. This works on the browser version of C3, but not in nwjs.
    • Finally I am seeing some weird visual issues, like hidden objects showing for a single frame when the application first previews.

  • Hey TheRealDannyyy I don't like to bother you, but I really need some advice on nwjs and I wondered if you had any ideas. I know nwjs issues aren't really your problem in any official sense, but I'm so frustrated and don't really know where else to go. The latest upgrade to construct r210 forced me to go upgrade from nwjs 44 and I've had loads of issues with my projects. I really just need to go back to the combo of construct r204.2 and nwjs 44.6

    I figured this would be possible by just using nwjs 44.6 and editing the construct package to point to editor.construct.net/r204-2. This opened as expected, but I ran into an issue - the open local project folder option was gone. If I run editor.construct.net/r204-2 in my browser then open local project folder was there. I checked and the settings are identical on my browser and nwjs. So my question really is this - what could be causing nwjs to not show the open local project folder? I would expect it to be identical to the browser version of the editor? Are there some secret settings somewhere or this just a random construct thing?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

    Hi all, posting here in case it helps - I had lost local project folders too, but have now got it back by checking the 'Enable Experimental Features' option. This is on latest stable release r210.

  • DannyV - did you report this? I am having the same issues since updating I think. I have some objects on a hidden layer that are suddenly flashing onto the screen for 1 frame at the start of the layout. No other changes other than updating.