Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Does not work

See original GitHub issue

I tried your site, and it fails to load resources. After cloning this repo and doing npm install/start it failed to download PS1 bios, after patching that, I tried to load a z64 rom, and it fails with the following exceptions…

TypeError: context.createVertexArray is not a function
    initScene http://127.0.0.1:8000/assets/frontend/bundle/libretro.js:983
    onload http://127.0.0.1:8000/assets/frontend/bundle/libretro.js:1449

[XmlHttpRequest] Direct file system constructor usage is deprecated for this file system, and will be removed in the next major version. Please use the 'XmlHttpRequest.Create({"index":"file index as an object","baseUrl":"/assets/frontend/bundle/"}, callback)' method instead. See https://github.com/jvilk/BrowserFS/issues/176 for more details.

THREE.WebGLRenderer: image is not power of two (1680x936). Resized to 1024x512 
<img src="/assets/img/cover.png" width="1680" height="936">


Error: WebGL warning: texImage2D: Invalid internalformat: 0x8058

Error: WebGL warning: checkFramebufferStatus: Framebuffer not complete. (status: 0x8cd6) COLOR_ATTACHMENT0Attachment has no width or height.

uncaught exception: abort(8) at jsStackTrace@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_mr_libretro.js:1017:13
stackTrace@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_mr_libretro.js:1034:12
abort@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_mr_libretro.js:13378:44
nullFunc_iii@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_mr_libretro.js:11720:466
b8@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_libretro.wasm:wasm-function[8626]:0x493a79
_input_joypad_pressed@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_libretro.wasm:wasm-function[2344]:0x163d6b
_rwebinput_is_pressed@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_libretro.wasm:wasm-function[2339]:0x163337
_rwebinput_input_state@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_libretro.wasm:wasm-function[2331]:0x162c19
_input_keys_pressed@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_libretro.wasm:wasm-function[1237]:0xf67bd
_runloop_check_state@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_libretro.wasm:wasm-function[594]:0xa40e6
_runloop_iterate@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_libretro.wasm:wasm-function[593]:0xa361b
_emscripten_mainloop@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_libretro.wasm:wasm-function[2326]:0x162576
dynCall_v@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_libretro.wasm:wasm-function[8585]:0x4936a0
Module.dynCall_v@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_mr_libretro.js:12998:37
browserIterationFunc@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_mr_libretro.js:1851:18
runIter@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_mr_libretro.js:1968:13
Browser_mainLoop_runner@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_mr_libretro.js:1906:26
requestAnimationFrame/<@http://127.0.0.1:8000/assets/frontend/bundle/parallel_n64_mr_libretro.js:2312:20

TypeError: bindVertexArray is undefined

Issue Analytics

State:
Created 4 years ago
Comments:20 (20 by maintainers)

Top GitHub Comments

4reactions

BiatuAutMiahncommented, Aug 8, 2019

I do not think so, I will be sure to post in correct issue next time

2reactions

avaercommented, Aug 8, 2019

That’s probably a legitimate Exokit bug, but this is still not the avenue to file it.

I’ll paste that over as an issue in the Exokit repository.

Top Results From Across the Web

What is another word for "doesn't work"? - WordHippo

What is another word for doesn't work? ; busted · down ; out · unfunctional ; unsound · disabled ; kaput · unavailing...

Is there any difference between "it's not working" and "it doesn ...

It is correct to say "It's not working" when something is broken permanently, however, if something is broken forever (or permanently), stating, "It...

138 Synonyms & Antonyms for NOT WORKING - Thesaurus.com

invalid · worthless; unfounded. bad · baseless · fallacious ; on the blink · not working continuously. bonkers · broken · busted ;...

something will not work/start/open etc Definitions and ...

Definition of SOMETHING WILL NOT WORK / START / OPEN ETC (phrase): saying you cannot make something do something.

What do "it doesn't work" and "phrase" mean? [closed]

1 Answer 1 · it is frequently used to mean that something mechanical or that has a function is broken and does not...