SecondDimension's Recent Forum Activity

  • As I said on the linked thread, thanks so much for the advice!

  • Fib hey thank you so much for taking the time to write that up, seems to be just what I need. I can live without it during preview if I know it will work when exporting. I will give it a go in my project today. Hopefully this will help anyone else with these issues too!

  • It definitely doesn't work in nwjs, I use Construct on desktop via nwjs and I tested exporting multiple projects ot nwjs. None of my projects work. I also just recreated a very simple project in nwjs and tested - it didn't work

  • 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.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

    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.

SecondDimension's avatar

SecondDimension

Member since 12 Mar, 2013

Twitter
SecondDimension has 1 followers

Connect with SecondDimension

Trophy Case

  • 11-Year Club
  • Forum Contributor Made 100 posts in the forums
  • Regular Visitor Visited Construct.net 7 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

15/44
How to earn trophies