saltemishel Posted April 28, 2017 Share Posted April 28, 2017 Hi All, Has anyone encountered a shader compilation error in babylon.js on Internet Explorer(IE) 11? In Chrome it works fine. I am curious in why does this happen? Is this a bug? Device Specifications: Intel Core i5-5200U CPU 2.2GHz 4GB Ram Intel(R) HD Graphics 5500 Direct3D11 Windows 8.1 Pro Everything works on IE11 windows 8.1 on my other laptop though. This is the device model that I'm using: https://www.lazada.com.my/dell-latitude-3550-business-class-notebook-i5-5200u270ghz1tb4gbintel-hd5500156ledwin-81-pro-9906952.html Console output for my project. BJS - [17:05:17]: Unable to compile effect with current defines. Trying next fallback. BJS - [17:05:17]: Vertex shader:legacydefault BJS - [17:05:17]: Fragment shader:legacydefault BJS - [17:05:17]: Unable to compile effect with current defines. Trying next fallback. BJS - [17:05:17]: Vertex shader:legacydefault BJS - [17:05:17]: Fragment shader:legacydefault BJS - [17:05:17]: Unable to compile effect: BJS - [17:05:17]: Vertex shader:legacydefault BJS - [17:05:17]: Fragment shader:legacydefault BJS - [17:05:17]: Defines: #define NORMAL #define NUM_BONE_INFLUENCERS 0 #define BonesPerMesh 0 #define LIGHT0 #define HEMILIGHT0 #define HEMILIGHT1 BJS - [17:05:17]: Error: Shader compilation errors (117, 1): syntax error, unexpected UNSUPPORTED_TOKEN Attached also the error log that we found in the babylon basic scene playground on this same device in IE 11. If there is any other details you need please let me know. Thank you errorlog.txt Quote Link to comment Share on other sites More sharing options...
GameMonetize Posted April 28, 2017 Share Posted April 28, 2017 Hello can you try with the v3.0 that you can find here: https://github.com/BabylonJS/Babylon.js/tree/master/dist/preview release Quote Link to comment Share on other sites More sharing options...
saltemishel Posted May 2, 2017 Author Share Posted May 2, 2017 Hi Deltakosh, So I replaced Babylonjs v2.5 with BabylonJS version 3.0 for my project. Attached the errorlogs that I have collected. -errorlog3 game.txt is the error log when opening my project. Chrome still works with version 3.0. For IE 11 it seems that the mesh object seems to be there but it is not rendering. Happens in v3 and the previous v2.5. Playground exhibited this error as well for 3.0 attached error log as well. -errorlog Playground-3-0.txt which is the error log for opening playground with 3.0 alpha I have re-formatted the logs hopefully it is clearer. Thank you. errorlog Playground-3-0.txt errorlog3 game.txt Quote Link to comment Share on other sites More sharing options...
GameMonetize Posted May 3, 2017 Share Posted May 3, 2017 Will have a look ASAP Quote Link to comment Share on other sites More sharing options...
saltemishel Posted May 4, 2017 Author Share Posted May 4, 2017 Thanks, looking forward to the good news. Quote Link to comment Share on other sites More sharing options...
GameMonetize Posted May 4, 2017 Share Posted May 4, 2017 Unfortunately I cannot reproduce the issue on my computers. This should be a driver issue Quote Link to comment Share on other sites More sharing options...
saltemishel Posted May 9, 2017 Author Share Posted May 9, 2017 Aww..it's ok, turns out threejs doesn't work on that mechine too. 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.