Jump to content

Search the Community

Showing results for tags 'microsoft edge'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • HTML5 Game Coding
    • News
    • Game Showcase
    • Facebook Instant Games
    • Web Gaming Standards
    • Coding and Game Design
    • Paid Promotion (Buy Banner)
  • Frameworks
    • Pixi.js
    • Phaser 3
    • Phaser 2
    • Babylon.js
    • Panda 2
    • melonJS
    • Haxe JS
    • Kiwi.js
  • General
    • General Talk
    • GameMonetize
  • Business
    • Collaborations (un-paid)
    • Jobs (Hiring and Freelance)
    • Services Offered
    • Marketplace (Sell Apps, Websites, Games)

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Twitter


Skype


Location


Interests

Found 2 results

  1. Well, good news is that Microsoft is going to support WebVR in the Edge browser. This is great, since it means that the Hololens and similar AR device may be accessible to web programming. However, to make it work with these devices, the WebVR spec just added and deprecated some functions. Apparently AR devices provide detailed rendering info that wasn't addressed in the WebVR 1.0 spec - the 1.1 upgrade fixes that. Migration Guide: https://github.com/w3c/webvr/blob/gh-pages/migration.md Updated samples: https://webvr.info/samples/ JS Shim for Chromium (which still has the 1.0 spec) https://github.com/w3c/webvr/blob/gh-pages/js/webvr-1-1.js The big issues: Replace VRDisplay.getPose() with VRDisplay.getFrameData() Use projection matrices provided by VRFrameData, instead of computing from VREyeParameters.fieldOfView() Use the view matrices from VRFrameData, instead of computing from pose + eye offsets
  2. I'm trying to implement controller support and have been testing using the Xbox One's MS Edge browser. Everything renders fine & runs well (sounds, animation etc.) but the controller doesn't respond. I used the code from the examples, and when I switch between 'browser' & 'gamepad' mode in the Xbox UI, the "controller connected" code (game.input.gamepad.supported && game.input.gamepad.active && pad.connected) executes fine and shows the correct connected / disconnected status. However, it appears that the browser only receives a single response from the pad while connecting / disconnecting as whatever action I do or button I press whilst connecting triggers endlessly until I disconnect via the Xbox UI. By trialling all of the different inputs I can see that it's recognised the same as a 360 controller (Phaser.Gamepad.XBOX360_DPAD_UP etc.) but I'm at a loss at why it won't work correctly, only receiving inputs on connect. I even tried browsing the the phaser.io examples pages using the XB1 browser but found that they didn't work as expected either. I know there *are* browser games for the XB1 that work with the controller (I.e. http://playboxie.com/x1) but does anyone know of one that uses GamePad mode with Phaser (rather than emulating mouse controls) so I can take a look at an example that works as I'm at a loss?
×
×
  • Create New...