-
-
Notifications
You must be signed in to change notification settings - Fork 35.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FBXLoader: Fbx Models containing .tif-format textures do not work #24416
Comments
No, I don't think that's a good idea. You really should not use
Adding extensibility and flexibility means modules tend to become more complex. The project favored simplicity in the past for various reasons. So the idea is that you copy |
@Mugen87 There are many scenes using .tif-format textures in the game field, and my project is only for previewing character modeling made by game modelers, and their models are all .tif-format textures. Of course, extra things can be done for a better preview (such as converting the texture format of the model), here is to find a simpler method, so there are the above problems. |
If there's some open source code for loading tiff we could do a |
You can learn about the |
If you okay with |
Let's do it 👌 |
hey
When I use an fbx model with a .tif-format texture, I find that the texture is not displayed on the browser. This raises some questions, and I hope to find answers.
Why wasn't support for .tif-format textures considered?
After consulting some information and related issues(Problems with .tif-textures in obj-models. #436), I learned that many browsers do not natively support .tif-format textures. By observing the source code of
ImageLoader
, I found that three.js works by displaying images throughimg
tags.Is it possible to make three.js support .tif-format by extending
ImageLoader
? In fact, I made the image display by modifying theImageLoader
component, usingtiff.js
to load thetiff resource
, and using canvas to convert it topng
.Another problem is derived from the above problem.
FBXLoader
does not seem to provide any extensibility. Each subcomponent is directlynew
in the method. When I want to modify or extend the logic of some subcomponents, I have to put the entireFBXLoader
Taking it out for modification alone makes the modification cost very large and is not conducive to subsequent maintenance. May I ask if this is the original intention of the original design (do not want others to modify the source code) or other reasons?The text was updated successfully, but these errors were encountered: