[Plugin] Universal Importer - v1.2.6 - 30 July 2024
-
@chalupsky said:
So grateful to find this!!
@chalupsky said:
The model materials do not map to the model [...]
You don't select materials? Can you elaborate on this?
@chalupsky said:
I'm asked the maximum height, (1800mm), I cancel, and the model comes in at about 1/18 the size.
It's a known issue: sizing doesn't work for all models
-
@ekon said:
Hello Samuel, first off, thank you so much for this superb tool!!
Hello Ekon! With pleasure
@samuel_t said:
[...] Your model had absolute paths to textures. That's not supported by plugin.
I converted absolute paths to relative paths with a text editor. It's OK now [...]@ekon said:
I have the same issue about textures. I just installed the plugin and imported and FBX file but it comes in without textures. My base model comes from Revit. How can I re-path the textures so that the plugin can read / load them into Sketchup? (Text editor, ok, but how?)
First, if you can, upgrade Revit to latest version to increase chances to have more export options.
Then, tell me what export options Revit offers to you. Some .x (DirectX) and .fbx files are text-encoded. All .mtl files are plain text. Open exported file with a text editor to see if textures paths are editable. -
Hi Samuel,
Thanks for making this plug in available. I am having the same issue as others when importing a model. The model itself imports fine but without textures. I have read your response to others about the absolute path but am not sure what to do. I have attached the model file below if you have a chance to take a look and advise. thanksthe file is here:
https://www.dropbox.com/t/cwZOdCb32a1BrBoZ -
@p11205 said:
Hi Samuel,
Thanks for making this plug in available.Hi Paul
@p11205 said:
I am having the same issue as others when importing a model. The model itself imports fine but without textures. I have read your response to others about the absolute path but am not sure what to do. I have attached the model file below if you have a chance to take a look and advise. thanks
the file is here:
https://www.dropbox.com/t/cwZOdCb32a1BrBoZI successfully imported model as is on SketchUp 2017. See screenshot below. I followed these steps:
- Extract whole archive.
- Import "12044_w_Rae_30k.OBJ" file.
- Cancel when plugin asks about "DefaultMaterial".
-
Hi Samuel,
Thanks for responding so quickly. I tried again as you outlined.after importing the 12044_w_Rae_30k.OBJ file I never got the message regarding default material from the plug in. The model again came in with no textures. Not sure how to proceed.
-
Hello Sam,
Is there a recommended way to get the most out of your model as you reduce its poly count, I mean I keep getting wild responses. I have tried 20/50/70% etc... and my models look like crap up, not at all like your deer example.
Should I break down the model into groups and reduce each group at the same settings??? I hope I am making sense!
Cheers Sam.
-
-
This plugin claims that it works with FBX files not it does not!
Every time I try to import an FBX file I ALWAYS get the following error message:
Universal importer failed to load file FBX-DOM unsupported format.Obviously this plugin CANNOT handle FBX files
This shocks me that Google has no information on that specific error message since it is EVERY FBX file that results in this error
this plugin obviously does NOT support FBX files
Please either fix this or remove the option to import FBX files because as it currently stands, Universal Importer does NOT support FBX files -
FBX file format can be Binary or ASCII. If your file is in a format the importer doesn't support it will throw errors.
Similar to how an FBX export from SketchUp cannot be opened in Blender.
Also older FBX versions can throw up some issues as well.
Many things can lead to an error. It may not be Samuel's lovely extension that is at fault.
-
@Moltres Rider
Obviously, you have NO LUCK
Universal Importer plugin works in most cases with recent versions of FBX format. Try to upgrade model with Autodesk FBX Converter then try again to import model... -
Awesome plugin, but it doesn't seem able to handle decimals on the model sizes.. i.e. I have a model that is 53.69mm tall, when importing and entering that value, I get the following error, both with a comma and a decimal point:
-
Maybe it expects 53.69 but is receiving 53,69 - so does your system use a . or a , as the decimal separator ?
What do you actually type in the input-box ??
Also it seems to expect an integer, rather than a float in any case ??? -
@tig said:
Maybe it expects 53.69 but is receiving 53,69 - so does your system use a . or a , as the decimal separator ?
What do you actually type in the input-box ??
Also it seems to expect an integer, rather than a float in any case ???I did type both 53.69 and 53,69 and both cause the error.
I ended up having to import it at 100x scale and scale it back down.. it's a workaround, but not really ideal. -
I suspect that the default scaling factor is set as an integer, so trying to use a decimal float will cause an error in the input-box.
The extension's author [samuel_t] should be able to re-code it to suit ??
-
I locked target height to an Integer. Since scaling is hacky in this plugin, I must test Float carefully
-
1.1.7 version allows you to import in SketchUp models exported from Blender 2.80 or newer at .blend format.
Expect better compatibility for many formats. Thanks again to Assimp's contributors who made this happen!Download latest Universal Importer plugin from SketchUcation PluginStore.
-
Found an issue with "small" models.
Example: I'm importing a functional model that is 95x46x75.45mm in size. The STL is 75.45 tall, however, in order for it to import semi-properly, I have to use the 46mm as height.
However, the model, when imported, is actually 99.12x47.99x78.72mm in size, so it's actually 104.3261% of the original size in all directions.
If I import it at a factor of 100 (telling it that the STL is 4600mm in height), then downscale it to 0.01 in Sketchup, the size is correct.
-
Hi Samuel,
I'm getting this error in 2017 Make (Pro trial). I've tried with a .DAE and .FBX file and get the same error. The extension is working as expected in my licensed SU 2021 version, but failing with 2017 only. Any suggestions? Thanks for all your hard work on this amazing free tool!
-
I see C:\ versus C:/ in paths in the error message ?
Is the path inside '...' or "..." - which will give different result ?
Best to force the paths to use all / ?? -
@tig said:
I see C:\ versus C:/ in paths in the error message ?
Best to force the paths to use all / ??I agree, it's better to normalize dir separator but I don't think EarthMover's issue come from this...
Advertisement