Skip to content
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

model could not input blender #92

Closed
fantangCK opened this issue Jan 31, 2022 · 11 comments
Closed

model could not input blender #92

fantangCK opened this issue Jan 31, 2022 · 11 comments

Comments

@fantangCK
Copy link

fantangCK commented Jan 31, 2022

https://developer.blender.org/T95344
I can input the model created by mineway v902.But I can't input the model by v911
the model created by mineway.if it isn't blender problem I think it is mineway

@fantangCK
Copy link
Author

I tested version 902 to version 908 and found that the problem occurred when mineway first supported version 908 of minecraft version 1.18

@erich666
Copy link
Owner

Thanks for reporting this. Unfortunately, I can't currently reproduce the error on Blender 2.92 or 3.0.1. I exported without changing any options in Mineways to an OBJ file and imported it successfully into Blender, then applied MCPrep to its materials. Looks fine.

So, that means I need more information from you. Could you send me your OBJ, MTL, and texture files for your export? That way I can see exactly what settings you've used and can try to reproduce the problem on my end. You might consider making a very small export that reproduces the problem, e.g., export just a single grass block from Mineways and see if that reads into Blender. Any testing is appreciated! But, not required - if you want to simply attach a zip here of your files, I will hopefully be able to reproduce your problem here. If you can't attach here, email to me at erich@acm.org. Oh, and let me know what version of Blender you are using.

image

@fantangCK
Copy link
Author

Thanks for reporting this. Unfortunately, I can't currently reproduce the error on Blender 2.92 or 3.0.1. I exported without changing any options in Mineways to an OBJ file and imported it successfully into Blender, then applied MCPrep to its materials. Looks fine.

So, that means I need more information from you. Could you send me your OBJ, MTL, and texture files for your export? That way I can see exactly what settings you've used and can try to reproduce the problem on my end. You might consider making a very small export that reproduces the problem, e.g., export just a single grass block from Mineways and see if that reads into Blender. Any testing is appreciated! But, not required - if you want to simply attach a zip here of your files, I will hopefully be able to reproduce your problem here. If you can't attach here, email to me at erich@acm.org. Oh, and let me know what version of Blender you are using.

image

my blender version 3.0.1
and my blender model had been sent to you email.
my email is wy0701@vip.qq.com

@erich666
Copy link
Owner

erich666 commented Feb 1, 2022

Thanks for sending on the model. I just read it into Blender 3.0.1 successfully: File -> Import -> OBJ, read in the .obj file, and got the image below. I also applied MCPrep to the model successfully, no problem there.

I'm sorry to say I cannot reproduce whatever error it is you are having on Blender. I guess maybe uninstall and reinstall the latest Blender? I don't have any other ideas. The OBJ file also displays fine in G3D, so seems to be correct. If you figure anything out, please do let me know.

image

@erich666
Copy link
Owner

erich666 commented Feb 1, 2022

Looking more closely at https://developer.blender.org/T95344, I tried googling on "blender enum non-color not found in Linear sRGB" - didn't turn up anything that looks identical to your error (that wasn't listed as fixed already).

I do hope you try removing and then reinstalling Blender and not add any add-ons at that point, then load the OBJ. Perhaps an add-on is causing the problem?

@erich666
Copy link
Owner

erich666 commented Feb 1, 2022

One other idea: send me an export of the same world from verion 9.07 or earlier (but 9.07 is ideal, since you say that export works - I definitely made some changes to material export in 9.04, for example, so want to rule those changes out), where you say things were working. I can then do a "diff" between the two versions and maybe give you some idea what changed (or you can do a diff of the MTL files, which is where I would guess the problem might be, yourself - I recommend Beyond Compare for comparing files).

@SirHaxe
Copy link

SirHaxe commented Feb 1, 2022

Are you able to import any other obj files?

@fantangCK
Copy link
Author

fantangCK commented Feb 1, 2022

Are you able to import any other obj files?

yep,model exported by v902 can be import

@fantangCK
Copy link
Author

One other idea: send me an export of the same world from verion 9.07 or earlier (but 9.07 is ideal, since you say that export works - I definitely made some changes to material export in 9.04, for example, so want to rule those changes out), where you say things were working. I can then do a "diff" between the two versions and maybe give you some idea what changed (or you can do a diff of the MTL files, which is where I would guess the problem might be, yourself - I recommend Beyond Compare for comparing files).

I just test that delete .mtl file then it just can be imported.I think the problem is occurred at its file

@erich666
Copy link
Owner

erich666 commented Feb 1, 2022

Right, I figured it must be the MTL file - I haven't touched the meshes in the OBJ file in a long while.

Thanks for emailing me the before and after model files. The main difference is that the line:
#map_d model-Alpha.png

is no longer commented out, i.e., it's now:
map_d model-Alpha.png

I tested both models, importing each into Blender 3.0.1, and they both import fine. MCprep works on both models.

The "map_d" lines in the .mtl file are something I added in version 9.04 (not 9.08), to improve the import of materials into Blender. This line makes cutout objects (such as flowers) look better when first imported into Blender. I also uncommented map_d because the program jmc2obj also uses map_d; I figured if they've done it for awhile, it would be OK for Mineways to do it, too. I see from your original report that you get the same problem with that program: "When I input my minecaft save model(by jm2obj), blender reports this".

I'm sorry it is causing you problems. My advice remains that you should consider reinstalling Blender. If that does not solve the problem, you could manually edit the .mtl files that jmc2obj or Mineways produces and change all "map_d" to "# map_d" to comment them out.

Since I cannot reproduce this problem on Blender (older or latest versions), I cannot fix anything. I suspect this is a problem with your installation of Blender, but I will try this test on two other machines with Blender on them, next week, just to be sure.

@erich666
Copy link
Owner

Tested on a different PC, same thing - OBJ imports fine, cutout transparency is properly interpreted with materials with map_d defined. Blender 2.93.5 and 3.0.1 tested. So, keeping this one closed, since I can't reproduce it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants