Dad72 Posted February 10, 2018 Share Posted February 10, 2018 occlusionType not working in firefox : http://www.babylonjs-playground.com/#QDAZ80#5 Works on Chrome. I have the impression that Firefox has more and more problems with time. They are not getting better ... I also have some malformed xml problem on all my .json, .babylon files... Quote Link to comment Share on other sites More sharing options...
Guest Posted February 12, 2018 Share Posted February 12, 2018 Yes I agree.. I filled this bug on their DB: https://bugzilla.mozilla.org/show_bug.cgi?id=1437535 Quote Link to comment Share on other sites More sharing options...
Dad72 Posted February 12, 2018 Author Share Posted February 12, 2018 There is no possibility to disable occlusionType for firefox, the time that this bug is fixed? Quote Link to comment Share on other sites More sharing options...
Guest Posted February 12, 2018 Share Posted February 12, 2018 I will if the resolution takes too long but we are already turning off other webgl2 features on Firefox. At some point I will turn webgl2 off completely Quote Link to comment Share on other sites More sharing options...
Dad72 Posted February 12, 2018 Author Share Posted February 12, 2018 If firefox has a lot of problem with webgl2, can disable webgl2 just for firefox. I hope they will solve all the problems of webgl2. Quote Link to comment Share on other sites More sharing options...
Guest Posted February 12, 2018 Share Posted February 12, 2018 Me too! Quote Link to comment Share on other sites More sharing options...
Dad72 Posted February 20, 2018 Author Share Posted February 20, 2018 I'm going to see where this bug was, it does not seem not currently tracked and still not confirm. I am really disappointed with Firefox over time. Some years ago, I loved him a lot, I developed with him, but now I find Google Chrome much better, I remember that when we report a bug, it is tracked and considered. But with Firefox, we do not know if we waste our time to report something to them. I dream of a world where there is only one browser for all with one standard standard. I know, it's utopian... Quote Link to comment Share on other sites More sharing options...
Guest Posted February 21, 2018 Share Posted February 21, 2018 Clearly Quote Link to comment Share on other sites More sharing options...
Dad72 Posted March 10, 2018 Author Share Posted March 10, 2018 This bug is still at the same point and still not confirm. I think he does not take it into account. Should disable occlusion for Firefox in my opinion because this bug will last very long I imagine Quote Link to comment Share on other sites More sharing options...
Guest Posted March 12, 2018 Share Posted March 12, 2018 Can you link the bugzilla bug? Quote Link to comment Share on other sites More sharing options...
Dad72 Posted March 13, 2018 Author Share Posted March 13, 2018 It was you who made this bug here https://bugzilla.mozilla.org/show_bug.cgi?id=1437535 But he seems at a standstill. It is not confirm. Quote Link to comment Share on other sites More sharing options...
Guest Posted March 13, 2018 Share Posted March 13, 2018 lol true! I'll try to reach out to firefox developers Quote Link to comment Share on other sites More sharing options...
Guest Posted March 13, 2018 Share Posted March 13, 2018 but wait it works on my firefox! (v59) Quote Link to comment Share on other sites More sharing options...
aWeirdo Posted March 13, 2018 Share Posted March 13, 2018 Is v59 a preview version? I'm running on 58, Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0 and no updates seem to be available. Quote Link to comment Share on other sites More sharing options...
Guest Posted March 13, 2018 Share Posted March 13, 2018 seems to be an update yes Quote Link to comment Share on other sites More sharing options...
aWeirdo Posted March 13, 2018 Share Posted March 13, 2018 Ahh, the update just became available now. can confirm it works Quote Link to comment Share on other sites More sharing options...
Dad72 Posted March 13, 2018 Author Share Posted March 13, 2018 I confirm, it works now with version 59. So they have to correct. He could have told us that he took charge of the problem. The bug is still considered open and not confirm on bugzilla. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.