[r223 NWjs 0.13.0 7] Serious problem

0 favourites
  • 5 posts
From the Asset Store
13 dynamic orchestral tracks for your media project. Includes standard, no percussion and looped versions.
  • Problem Description

    C2 seem to get stuck in full screen mode. Even across projects. If I add a "Browser - Request full screen" and run the application through NWjs. It does go full screen as expected. However if I disable the "Request full screen" in the code it still goes full screen when preview. Even if I make a new clean project with no event at all in it and preview it, it still goes into full screen mode. Even after restarting C2 the project that seems to have used the "Request full screen" is stuck in that mode.

    Can anyone try this and confirm this issue? It is really weird. (ALSO BE SURE TO TEST IT IN A NEW PROJECT!!)

    Attach a Capx

    https://dl.dropboxusercontent.com/u/109921357/Stuck_fullscreen/Stuck_fullscreen.capx

    Description of Capx

    Just request full screen

    Steps to Reproduce Bug

    1. F4 to preview the project. It will go to full screen.

    2. Disable "Request full screen" and run the program again.

    Observed Result

    Regardless of whether Request full screen is used or not, it will keep going full screen even after it have been disabled. Even across different projects.

    Expected Result

    Affected Browsers

    NW.js 0.13.0 B7 and B6

    Operating System and Service Pack

    Windows 7

    Construct 2 Version ID

    r223

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I can reproduce this bug only on computer with bad graphic drivers (as a VM) (export build with C2 r221 nw13beta5-6-7)

  • I can reproduce this bug only on computer with bad graphic drivers (as a VM) (export build with C2 r221 nw13beta5-6-7)

    I use Nvidia newest driver 361.91 so it should be up to date.

  • Just updated to NWjs 0.13.0 rc 1, which didn't solved the problem.

  • NWjs 0.13.0 rc 2 seems to have fixed this issue.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)