Argh, what OS/GPU are you on? Anything suspicious in the stdout text field or JS console?
I've only tested on OSX 10.9.2, Intel HD4000 so far and it works both in FF Stable, Nightly and Chrome. I'll test more configs tomorrow at work, and depending on the outcome update the public demos without VAO, and add hidden demos with VAO enabled for testing. Thanks! -Floh. Am Dienstag, 25. Februar 2014 21:18:00 UTC+1 schrieb Alon Zakai: > > I tested the new demos you posted, and I just get black rendering (either > with a grey or no background) on firefox, but works on chrome. This might > be a VAO issue as we saw similar problems in the past. It could also be my > linux GL drivers, though... > > - Alon > > > > On Tue, Feb 25, 2014 at 4:17 AM, Floh <[email protected] <javascript:>>wrote: > >> Tested on the Nebula3 demos and looking good :) Can't say much yet about >> performance unfortunately since some other long-running stuff is hogging my >> laptop which will take another couple of hours. But everything compiles and >> runs just fine. >> >> I'll see if I can get the demos at www.flohofwoe.net/demos.html updated >> in the next couple of days. There are a few new demos (nothing impressive >> looking, only for testing some specific engine features), and I'd like to >> turn on VAO and depth-render-textures (the latter has some problems in FF >> Nightly on some configs at the moment, see here: >> https://bugzilla.mozilla.org/show_bug.cgi?id=948002). >> >> ...and congratulations on the fastcomp backend, can't wait 'til this goes >> into LLVM upstream and becomes an "official" backend :D >> >> Cheers, >> -Floh. >> >> Am Montag, 24. Februar 2014 23:42:01 UTC+1 schrieb Alon Zakai: >> >>> Hi everyone, >>> >>> Fastcomp, the new backend, has been turned on by default on the incoming >>> branch. Details: >>> >>> https://github.com/kripken/emscripten/wiki/LLVM-Backend >>> >>> Note that this is just on by default - as in that link, you can disable >>> it if you want - but you shouldn't :) >>> >>> Also note that this is on the incoming branch, not master. If you are on >>> master, nothing has changed. >>> >>> Please test your project on the incoming branch. In general, things >>> should just work - except compile more quickly. The main risk is if your >>> project uses a deprecated feature or hits a new bug. We will not merge >>> incoming to master probably for some time as we get feedback and make sure >>> things are stable. >>> >>> Note that there are incoming branches in all 3 repos now: emscripten, >>> emscripten-fastcomp and emscripten-fastcomp-clang. As mentioned in the link >>> above, you should use the SAME branch in all. If you use incoming in >>> emscripten, you MUST also use incoming in the other two, otherwise they >>> might not be compatible. >>> >>> - Alon >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "emscripten-discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
