Arguments for procedural texture files not supported for MTL when importing WaveFront OBJ files #46459
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#46459
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Windows 7 Ultimate 64-bit
32.0GB RAM, Intel Core i7-3770k CPU @ 3.50GHz
GFX: GeForce GTX 980 Ti (Driver 355.82)
Blender Version
Broken: 2.75a c27589e
Short description of error
The specification for MTL files states that texture maps can support optional arguments before the file name allowing the imported material to be manipulated such as texture size (http://paulbourke.net/dataformats/mtl/). When importing a WaveFront OBJ with a linked MTL file, these optional arguments are parsed as part of the filename and therefore end up producing a material with an invalid image linked.
Exact steps for others to reproduce the error
The expected result here would be that all the materials applied to the meshes have a size manipulation of 1, -1, 1. However, instead the arguments provided to the texture map are included in the material file names, which prevent them from working at all.
stables.zip
Changed status to: 'Open'
Added subscriber: @Kruithne
Added subscriber: @sindra1961
I think that it is full specifications of the .mtl format.
The content that Wavefront OBJ Import/Export supports is written here .
I think that the specifications are not included.
Added subscriber: @tetha.z
Added subscriber: @mont29
Well… one thing for sure, it should not break texture filepaths. ;)
Supporting those options is more a TODO really, but will try to add at least basic ones too, since I’m at it…
This issue was referenced by
ecdc7c03ec
Changed status from 'Open' to: 'Resolved'
Fixed in
ecdc7c03ec
@mont29:
There is an option elsewhere, but they do not seem to be excluded.
Alias/WaveFront Material (.mtl) File Format
@mont29:
I'm sorry, it seems to extract only a thing to use.