FBX Loader example silently fails on iOS 9.3 (latest for iOS 9)

[benguild]

Description of the problem

Self-explanatory based on title. This is a fairly dated iOS version at this point, but the FBX example silently fails to load: https://threejs.org/examples/webgl_loader_fbx.html (just doesn't do anything... no errors reported)

There's no issue with the OBJ loader, or other examples, though: https://threejs.org/examples/webgl_loader_obj.html

Three.js version

• Dev
• r94
• ...

Browser

• All of them
• Chrome
• Firefox
• Internet Explorer
• Safari

OS

• All of them
• Windows
• macOS
• Linux
• Android
• iOS (9.3)

Hardware Requirements (graphics card, VR Device, ...)

Tested on iOS Simulator, can also test on a real device as I have an iPhone 4s lying around here somewhere. (but there's probably no difference)

[Mugen87]

(but there's probably no difference)

Please perform a test on the real device. Simulators and real devices are not always comparable, especially in context of GPU related code.

[benguild]

Just checked. It's the same ... nothing loaded. Usually the Simulator does work, it's just slower since it's not native.

[Mugen87]

Thanks for testing. Can you please perform a test with a different browser than Safari?

BTW: I'm not able to reproduce the issue on an Android smartphone (Pixel).

[benguild]

I'm not able to reproduce this issue on any other hardware/Simulators that I have access to at the moment. It works fine in the iOS 10 and 11 Simulators, and on native hardware running those iOS versions as well. However, both the Simulator and native hardware running iOS 9[.3] exhibit this issue and return nothing in the console as to why it's not working.

Therefore, as far as I know, there's an incompatibility with iOS 9[.3] only, and it's on the software level. All other third-party browsers on iOS are required to use the same WebKit rendering that the OS provides, which is what Safari uses, so testing in another browser is unnecessary in this case unless another browser somehow implements its own WebGL extension... which would be unusual. — This issue is about Safari (the default) and all other typical browsers, and not those instances/exceptions.

To reproduce, download Xcode from the Mac App Store, install the iOS 9.3 Simulator from Preferences (normally it only bundles the latest iOS release), and then open that example on the iOS Simulator's version of Safari.

As mentioned, the OBJ and other loaders work fine. It's just the FBX loader and/or its dependencies that are exhibiting this issue.

[Mugen87]

Does this example work? https://threejs.org/examples/#webgl_animation_skinning_morph

The FBXLoader example is animated whereas the OBJLoader examples are static.

[benguild]

Yeah, that works fine. (animated + static both work)

[Mugen87]

All other third-party browsers on iOS are required to use the same WebKit rendering that the OS provides, which is what Safari uses, so testing in another browser is unnecessary in this case unless another browser somehow implements its own WebGL extension... which would be unusual.

Can you still make a test with Chrome, please? Just to be sure 😇

[benguild]

I don't have access to the App Store on that device at the moment, unfortunately. However, since this is an issue with Safari on iOS 9.3 specifically (typical use), if you'd prefer to scope the issue to be about iOS 9.3 Safari instead of that entire iOS release, I guess we could and if the workaround trickles down into fixing all of the other instances as well, that'd be a bonus.

[RemusMar]

testing in another browser is unnecessary in this case unless another browser somehow implements its own WebGL extension... which would be unusual.
This issue is about Safari (the default) and all other typical browsers, and not those instances/exceptions.

That's a false statement.
The "not showing skinned mesh" is a very old bug on various mobile devices / browser combinations.
The same issue with (the latest version or not) Firefox Android.
But on the same Android device Chrome works just fine ...
Talking about Firefox Android, I've reported the issue 5 months ago, they were able to replicate it, but the bug is still not fixed.
Honestly, WebGL development does not look good at all.

[benguild]

@RemusMar RE: #14482 (comment) — Just to reiterate, I'm referring to iOS specifically and Apple's App Store guidelines:

2.5.6 Apps that browse the web must use the appropriate WebKit framework and WebKit Javascript.

and...

4.7 HTML5 Games, Bots, etc.
Apps may contain or run code that is not embedded in the binary (e.g. HTML5-based games, bots, etc.), as long as code distribution isn’t the main purpose of the app, the code is not offered in a store or store-like interface, and provided that the software (1) is free or purchased using in-app purchase; (2) only uses capabilities available in a standard WebKit view (e.g. it must open and run natively in Safari without modifications or additional software); your app must use WebKit and JavaScript Core to run third party software and should not attempt to extend or expose native platform APIs to third party software; (3) is offered by developers that have joined the Apple Developer Program and signed the Apple Developer Program License Agreement; and (4) adheres to the terms of these App Review Guidelines (e.g. does not include objectionable content). Upon request, you must provide an index of software and metadata available in your app. It must include Apple Developer Program Team IDs for the providers of the software along with a URL which App Review can use to confirm that the software complies with the requirements above.

Regardless, like I said, this is an issue in iOS 9.3 Safari anyway.

Reference: https://developer.apple.com/app-store/review/guidelines/

[benguild]

@RemusMar #14482 (comment) — If you want to reference your issue(s) here, please feel free to do so if they're related.

[benguild]

@Mugen87 RE: #14482 (comment) — This example does also work... https://threejs.org/examples/?q=fbx#webgl_loader_fbx_nurbs

The completion block for loader.load() is not called on the originally referenced example. However, on that one, it is.

Could it be an issue with inflating certain binary files?

[benguild]

Also, I tried another binary FBX file and that one didn't work on iOS 9.3 either.

[looeee]

The FBXloader is the only loader using Map internally. @benguild can you check that Map is supported in your version of Safari?