|
0 / 0 / 0 Регистрация: 16.11.2013 Сообщений: 70 |
|
|
1 |
|
|
16.10.2014, 08:25. Показов 13736. Ответов 3
Подскажите пожалуйста, почему Blender выдает ошибку при импорте объектов, допустим при попытке импорта объекта в формате (.obj) вылетает такая ошибка Миниатюры
__________________
0 |
|
Programming Эксперт 94731 / 64177 / 26122 Регистрация: 12.04.2006 Сообщений: 116,782 |
16.10.2014, 08:25 |
|
Ответы с готовыми решениями: Ошибка при импорте Ошибка при импорте БД Ошибка при импорте БД Ошибка при импорте 3 |
|
0 / 0 / 0 Регистрация: 16.11.2013 Сообщений: 70 |
|
|
16.10.2014, 11:14 [ТС] |
2 |
|
Вопрос отпал, сам разобрался.
0 |
|
Модератор 2886 / 1744 / 178 Регистрация: 19.02.2011 Сообщений: 6,434 |
|
|
16.10.2014, 11:26 |
3 |
|
И в чем была причина?
0 |
|
0 / 0 / 0 Регистрация: 07.12.2015 Сообщений: 1 |
|
|
07.12.2015, 19:06 |
4 |
|
Столкнулся с аналогичной проблемой, долго думал… потом опомнился))) Проблема проста — нечего было выпендриваться и указывать недопустимые символы в пути к файлу (т.е. путь в папку, в которой хранились файлы сохранений), апострофы и т.д. Обычное переименование папки лечит проблему мгновенно)
0 |
|
0 / 0 / 0 Регистрация: 16.11.2013 Сообщений: 70 |
|
|
1 |
|
|
16.10.2014, 08:25. Показов 13575. Ответов 3
Подскажите пожалуйста, почему Blender выдает ошибку при импорте объектов, допустим при попытке импорта объекта в формате (.obj) вылетает такая ошибка Миниатюры
__________________ 0 |
|
Programming Эксперт 94731 / 64177 / 26122 Регистрация: 12.04.2006 Сообщений: 116,782 |
16.10.2014, 08:25 |
|
Ответы с готовыми решениями: Ошибка при импорте Ошибка при импорте БД Ошибка при импорте БД Ошибка при импорте 3 |
|
0 / 0 / 0 Регистрация: 16.11.2013 Сообщений: 70 |
|
|
16.10.2014, 11:14 [ТС] |
2 |
|
Вопрос отпал, сам разобрался. 0 |
|
Модератор 2886 / 1744 / 178 Регистрация: 19.02.2011 Сообщений: 6,434 |
|
|
16.10.2014, 11:26 |
3 |
|
И в чем была причина? 0 |
|
0 / 0 / 0 Регистрация: 07.12.2015 Сообщений: 1 |
|
|
07.12.2015, 19:06 |
4 |
|
Столкнулся с аналогичной проблемой, долго думал… потом опомнился))) Проблема проста — нечего было выпендриваться и указывать недопустимые символы в пути к файлу (т.е. путь в папку, в которой хранились файлы сохранений), апострофы и т.д. Обычное переименование папки лечит проблему мгновенно) 0 |
You stumbled upon a curious problem with filename handling in the .obj format, that isn’t well defined in the specification. I will discuss this with the Blender devs, perhaps the importer needs small adjustments to parse the file correctly under these specific circumstances. Since it worked in 2.79b it can be considered a regression.
TL;DR The handling for filenames with blanks isn’t well defined in the .obj format specification and Blender expected a different format than what was provided in your file.
The Problem
The .obj is a text format for storing 3D models. The format contains various attributes that describe the geometry of the model. Typically the .obj is accompanied by a .mtl which describes the material and textures applied to the model. In order to keep track which files belong together, the .obj may contain a mtllib attribute followed by the filename of the .mtl.
Usually the beginning of an .obj would look something like this:
# Blender v2.80 (sub 74) OBJ File: ''
# www.blender.org
mtllib test.mtl
o Cube
v 1.000000 1.000000 -1.000000
v 1.000000 -1.000000 -1.000000
In case of your file it is:
#
mtllib "tree stump1 original model.mtl"
usemtl tree_stump1_original_model
v 4.136163 -1.200306 -10.798826 0.113725 0.152941 0.141176
v 4.140683 -1.205297 -10.794383 0.117647 0.156863 0.145098
Notice that the filename contains quotations marks. This is causing the problem. The software you used to export this model quoted the filename to avoid confusion on how to interpret the filename. While this is common practice in other file formats the specification for .obj doesn’t mention quoting filenames and says specifically:
Blank space and blank lines can be freely added to the file to aid in formatting and readability.
Which can be interpreted as blanks in filenames can be stored as is, which is precisely what Blender does. Unfortunately Blender’s importer doesn’t expect the quotation marks in the filename therefore misinterpreting the correct filepath. This results in the aforementioned error in your question.
The Fix
Open the .obj file in a text editor of your choice an remove the quotes and save. It should look like this:
#
mtllib tree stump1 original model.mtl
usemtl tree_stump1_original_model
v 4.136163 -1.200306 -10.798826 0.113725 0.152941 0.141176
The file can now be imported by Blender.
You stumbled upon a curious problem with filename handling in the .obj format, that isn’t well defined in the specification. I will discuss this with the Blender devs, perhaps the importer needs small adjustments to parse the file correctly under these specific circumstances. Since it worked in 2.79b it can be considered a regression.
TL;DR The handling for filenames with blanks isn’t well defined in the .obj format specification and Blender expected a different format than what was provided in your file.
The Problem
The .obj is a text format for storing 3D models. The format contains various attributes that describe the geometry of the model. Typically the .obj is accompanied by a .mtl which describes the material and textures applied to the model. In order to keep track which files belong together, the .obj may contain a mtllib attribute followed by the filename of the .mtl.
Usually the beginning of an .obj would look something like this:
# Blender v2.80 (sub 74) OBJ File: ''
# www.blender.org
mtllib test.mtl
o Cube
v 1.000000 1.000000 -1.000000
v 1.000000 -1.000000 -1.000000
In case of your file it is:
#
mtllib "tree stump1 original model.mtl"
usemtl tree_stump1_original_model
v 4.136163 -1.200306 -10.798826 0.113725 0.152941 0.141176
v 4.140683 -1.205297 -10.794383 0.117647 0.156863 0.145098
Notice that the filename contains quotations marks. This is causing the problem. The software you used to export this model quoted the filename to avoid confusion on how to interpret the filename. While this is common practice in other file formats the specification for .obj doesn’t mention quoting filenames and says specifically:
Blank space and blank lines can be freely added to the file to aid in formatting and readability.
Which can be interpreted as blanks in filenames can be stored as is, which is precisely what Blender does. Unfortunately Blender’s importer doesn’t expect the quotation marks in the filename therefore misinterpreting the correct filepath. This results in the aforementioned error in your question.
The Fix
Open the .obj file in a text editor of your choice an remove the quotes and save. It should look like this:
#
mtllib tree stump1 original model.mtl
usemtl tree_stump1_original_model
v 4.136163 -1.200306 -10.798826 0.113725 0.152941 0.141176
The file can now be imported by Blender.
Nvm this thread, it’s all solved.
@Stan`
tent_arab.dae (Didnt make any changes to the dae file)
Spoiler
+— Collada Import parameters——
| input file : C:UsersrichieDesktoptent_arab.dae
| use units : no
| autoconnect : no
+— Armature Import parameters —-
| find bone chains: no
| min chain len : 0
| fix orientation : no
| keep bind info : no
Schema validation (Error): Critical error: ERROR_XML_PARSER_ERROR Additional: Start tag expected, ‘<‘ not found
The Collada import has been forced to stop.
Please fix the reported error and then try again.+———————————-
| Collada Import : FAIL
+———————————-
Your plugin also seems to give a warning
Spoiler
Warning: class IMPORT_SCENE_OT_xml contains a property which should be an annotation!
E:Blender FoundationBlender 2.912.91scriptsaddonsio_scene_pyrogenesis__init__.py:72
assign as a type annotation: IMPORT_SCENE_OT_xml.filter_glob
assign as a type annotation: IMPORT_SCENE_OT_xml.import_props
assign as a type annotation: IMPORT_SCENE_OT_xml.import_textures
assign as a type annotation: IMPORT_SCENE_OT_xml.import_depth
Edited March 3, 2021 by Grapjas
System Information
Operating system:Windows 10
Graphics card: NVidia gforce GTX660
Blender Version
2.79
Short description of error
It is a common error, when trying to upload an object to Second-life or Opensim, to be unable to upload a model,created in Blender, due to a «DAE parsing issue»
This object is one that is effected.
Exact steps for others to reproduce the error
Export as .DAE file and upload to Opensim or Second-life
Event Timeline
Comment Actions
This particular «DAE parsing issue» is caused by negative object scaling which the importers to SL and OpenSim seem to reject (see error logs in the Viewer). However negative Scales are actually not forbidden by the Collada specifications, so this is not an error in the Collada Exporter, but an error in the Model.
To make this i little bit more user friendly, we could add an option for «automatic apply scale» to the Blender exporter.
Comment Actions
Thank you for your input! Actually I found a solution that seems to be working! Somebody happened to tell me that it’s a bug and I should report it I probably should have tried a bit harder to research first!
Comment Actions
Uh Gaia, I have another object with a dae parsing issue that has a normal scale ( the transform scale all 1.1.1? Is this what you mean?) Do you know what issues are likely to be causing this? It’s hard to find recources on making models for Secondlifeand opensim :/
Comment Actions
There are many reasons for getting parsing errors with Collada. But really, this report system is for reporting errors related to Blender and not so much about importing issues into target engines. Unless a target engine complains about wrong Collada format, then we are back at work here. But then we also need to know what the complaints are exactly. And a demo blend file of course, as always
cheers,
Gaia
What do I do with this? I was trying to import a gtlf file to the Blender, but it always pops a traceback like this but I don’t know why it does this
Traceback (most recent call last):
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2__init__.py", line 900, in execute
return self.import_gltf2(context)
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2__init__.py", line 914, in import_gltf2
if self.unit_import(path, import_settings) == {'FINISHED'}:
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2__init__.py", line 924, in unit_import
from .blender.imp.gltf2_blender_gltf import BlenderGlTF
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2blenderimpgltf2_blender_gltf.py", line 17, in <module>
from .gltf2_blender_scene import BlenderScene
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2blenderimpgltf2_blender_scene.py", line 17, in <module>
from .gltf2_blender_node import BlenderNode
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2blenderimpgltf2_blender_node.py", line 18, in <module>
from .gltf2_blender_mesh import BlenderMesh
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2blenderimpgltf2_blender_mesh.py", line 19, in <module>
from .gltf2_blender_material import BlenderMaterial
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2blenderimpgltf2_blender_material.py", line 19, in <module>
from .gltf2_blender_KHR_materials_pbrSpecularGlossiness import pbr_specular_glossiness
ModuleNotFoundError: No module named 'io_scene_gltf2.blender.imp.gltf2_blender_KHR_materials_pbrSpecularGlossiness'
location: <unknown location>:-1
What do I do with this? I was trying to import a gtlf file to the Blender, but it always pops a traceback like this but I don’t know why it does this
Traceback (most recent call last):
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2__init__.py", line 900, in execute
return self.import_gltf2(context)
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2__init__.py", line 914, in import_gltf2
if self.unit_import(path, import_settings) == {'FINISHED'}:
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2__init__.py", line 924, in unit_import
from .blender.imp.gltf2_blender_gltf import BlenderGlTF
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2blenderimpgltf2_blender_gltf.py", line 17, in <module>
from .gltf2_blender_scene import BlenderScene
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2blenderimpgltf2_blender_scene.py", line 17, in <module>
from .gltf2_blender_node import BlenderNode
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2blenderimpgltf2_blender_node.py", line 18, in <module>
from .gltf2_blender_mesh import BlenderMesh
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2blenderimpgltf2_blender_mesh.py", line 19, in <module>
from .gltf2_blender_material import BlenderMaterial
File "D:Program Files (x86)SteamsteamappscommonACE COMBAT 7GameContentPaksmod creationsac7toolsblender-2.83.18-candidate+v283.5f156291cdcc-windows.amd64-release2.83scriptsaddonsio_scene_gltf2blenderimpgltf2_blender_material.py", line 19, in <module>
from .gltf2_blender_KHR_materials_pbrSpecularGlossiness import pbr_specular_glossiness
ModuleNotFoundError: No module named 'io_scene_gltf2.blender.imp.gltf2_blender_KHR_materials_pbrSpecularGlossiness'
location: <unknown location>:-1