Search the Community

Showing results for tags 'debuglayer'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • HTML5 Game Coding
    • News
    • Game Showcase
    • Coding and Game Design
  • Frameworks
    • Phaser 3
    • Phaser 2
    • Pixi.js
    • Babylon.js
    • Panda 2
    • melonJS
    • Haxe JS
    • Kiwi.js
  • General
    • General Talk
  • Business
    • Collaborations (un-paid)
    • Jobs (Hiring and Freelance)
    • Services Offered

Found 6 results

  1. Using debug layer produce a infinite loop of warnings in console that freeze scene latest version, same in chrome and mozilla. Stable version return only one warning when using debulLayer
  2. Hi, Today I was playing around with BABYLON.EngineInstrumentation (babylonjs version v3.1-beta-2) and found this playground in your docs: If you enable the debug layer and choose the "Stats" tab everything working fine. But if you switch to any other tab and switch back to "Stats" again, you get a console error "Uncaught TypeError: Cannot read property 'getEngine' of null". Is there anything broken with the Inspector on this version? Best regards, Ller
  3. throws error

    Hi, I'm in the process of updating from 2.4 -> 3.0.7 and our button to show/hide debuglayer doesn't work anymore because the debug layer throws an exception when show() is called. I saw the InspectorURL points to a preview url: // The network tab shows that the script loads Here is the information in the console regarding the exception Uncaught ReferenceError: __extends is not defined at babylon.inspector.bundle.js:408 at INSPECTOR (babylon.inspector.bundle.js:408) at (babylon.inspector.bundle.js:408) at __webpack_require__ (babylon.inspector.bundle.js:21) at Object.<anonymous> (babylon.inspector.bundle.js:49) at __webpack_require__ (babylon.inspector.bundle.js:21) at babylon.inspector.bundle.js:41 at babylon.inspector.bundle.js:44 (anonymous) @ babylon.inspector.bundle.js:408 INSPECTOR @ babylon.inspector.bundle.js:408 global @ babylon.inspector.bundle.js:408 __webpack_require__ @ babylon.inspector.bundle.js:21 (anonymous) @ babylon.inspector.bundle.js:49 __webpack_require__ @ babylon.inspector.bundle.js:21 (anonymous) @ babylon.inspector.bundle.js:41 (anonymous) @ babylon.inspector.bundle.js:44 VM14956:61487 Uncaught TypeError: Cannot read property 'Inspector' of undefined at DebugLayer._createInspector (<anonymous>:61487:48) at HTMLScriptElement.script.onload (<anonymous>:5607:21)
  4. DebugLayer Not Found

    I am getting a not found error for
  5. 1. A parameter to specify an HTMLElement for the Inspector to add itself to? 2. Could the inspector take a parameter for which tab to start on? Reasons: (1) So games with a UI can see the inspector, and (2) so I can use it as an FPS meter I know I'm late to this party, but since it's such a big feature an options argument might be warranted:{ popup: false, parentElement: document.body, initialTab: 3, }) ...or similar.
  6. I have the following CSS for canvas: #canvas { position: absolute; width: 100%; height: 100%; top: 0; margin-bottom: 70px;}I.e. it should appear in full screen. And it does, until I enable the debug layer. Once I've enabled the debug layer, the things are messed up. On desktop everything works as usual, but on mobile the 100% becomes like 30%. I.e. canvas (and all the related controls, background, etc.) that should take 100% of the screen takes only one corner (left&topmost). Upd: If I set engine.setHardwareScaling(1) everything works ok