alastair's Forum Posts

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 4

  • 4 Aug, 2024
  • Quote

  C3 sometimes even goes down for everyone, for hours at a time.

  Subscriptions and not having freedom to use software offline is bad.

  I'm happy to keep giving money to them to support more updates, I just don't like this model.

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 3

  • 27 Jul, 2024
  • Quote

  Humans but without clothes on.

• You do not have permission to view this post

• You do not have permission to view this post

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 19 Jul, 2024
  • Quote

  thanks for explaining what it does.

  I tried talking to Steam about it, they got back to me, and I'm not sure if it helps but they said:

  You can check out our Steam Overlay documentation to troubleshoot these issues.

  Hopefully someone that knows what to do will eventually encounter this problem to help us fix it.

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 3

  • 11 Jul, 2024
  • Quote

  Okay I bought a Lenovo gaming laptop in order to test this.

  And the above comment is correct!

  • The tag "--force_high_performance_gpu" allows my game to use the nvidia GPU! It runs wonderfully smooth.
  • But if I also have the "export for steam" button checked, it will NOT use the nvidia GPU, and instead the weak one, and does not run as well.

  Ashley should we now update the NWJS "Export for Steam" option's "--in-process-gpu" with the new one: "--force_high_performance_gpu"? I'm not sure what the old tag did, but since it's blocking laptop's GPU's from being used maybe it should be changed so the games run better for more of our Steam players.

  
• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 3

  • 8 Jul, 2024
  • Quote

  There was a comment a couple years ago here with a solution:

  github.com/nwjs/nw.js/issues/5732

  I found that the --force_high_performance_gpu flag seems to make NW.js run with a discrete graphics card by default, but with the --in-process-gpu flag it will not work.

  Is that a good tag we can use?

  Is it okay to replace the old "in-process-gpu" which has become common for people to use?

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 8 Jul, 2024
  • Quote

  There use to be issues with people playing games on laptops with NWJS, since I think people said it wouldn't use the graphics card GPU.

  Is this a problem still with nwjs 71+?

  EDIT: Solution was found: https://www.construct.net/en/forum/construct-3/general-discussion-7/gaming-laptops-broken-182785#forumPost1115152

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 26 Jun, 2024
  • Quote

  calminthenight thanks for the idea. I'm surprised it worked for gamerguy1234 but not for a Linux user that's complaining to me.

  This is my settings, could it be something else?:

  
• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 26 Jun, 2024
  • Quote

  Continuing old topic construct.net/en/forum/construct-3/how-do-i-8/try-run-full-screen-nw-js-169783

  gamerguy1234

  On my windows 11 Laptop, if I run either the win32 or win64 files and try to enter full screen mode it just windows in the top left corner

  

  Like This

  calminthenight

  Did you set the resizable window option on export?

  gamerguy1234

  That Worked! Thank you so much!

• Try Construct 3

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

  Try Now Construct 3 users don't see these ads
• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 3

  • 24 Jun, 2024
  • Quote

  An action roguelike platformer. Started working on it years ago haha, but it's now released.

  store.steampowered.com/app/2921600/Angvik_2

  

• You do not have permission to view this post

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 2 Jun, 2024
  • Quote

  fantastic thanks everyone!

  dop2000 when I used the action to set collision cell size to 10x10 it reduces the checks down from 125000 to 800. So it seems it does that cells help a lot to reduce checks!

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 31 May, 2024
  • Quote

  dop2000 thanks for testing too! Maybe we have to set the collision cell size first? Did you have an action doing that?

  Perhaps a manual entry could help to explain this concept.

• • alastair
  • 
  • • Joined 14 Jul, 2007
    • 
    • 249 topics • 2,061 posts
  • 1

  • 30 May, 2024
  • Quote

  Thank you for clarifying that it's still a thing!

  I don't think I'm good at making performance tests, because when I tried doing it I get better performance when it was a subevent. 😅 So I'll just have to trust you.