![]() ![]() I used a spotlight object as my light source. The zip file does correctly have the textures in it.Ī quick browse of the obj/mtl files suggests that the correct textures are being referenced.Īhh, that makes a lot of sense actually. everything else is either solid colours, or whatever colours/textures the object had when I used it. I believe I’ve only used one texture, and thats for the flooring. So for any texture I’ve used, I append the # after the name? - is this the same case for colours? My apologies, I must not have read the readme fully. Thanks for the reply, adizanni - you are most welcome. I’m thinking to an elegant way to manage this, but I do not want to force the usage of the plugin (ex to name the light objects with a special tag and to disable shadowing for them). For half sphere lamps the shadow works well but for other light objects this might not work. If the center of the box falls inside the object and the object is solid, the object will shadow the light and no beam will get out of it. The behaviour of the lighr is really unpredictable because the pointlight is placed at the center of the box containing the light object. Related to lights and the shadow parameter you are right. json add a version URL query to them in order to be sure you are not picking an old cached version of the files (ex home.obj → home.obj?ver=1 and subsequent numbers for each new version of the file) In order to debug the plugin and understand the problem with the texture, I would need the sh3d file of your model.Īlso please whenever you reference a new version of the files. Please download the last version of the plugin: If you are not using the # as explained in the plugin README, there is something wrong elsewhere. ![]() With the help of another contributor we managed to debug the material generator but only when using the # character at the end of the name of the object. Thanks for encouragement and thanks for the feedback: it is this kind of comments that allow a constant improvement especially knowing that I develop in my spare time and I do not have a lot of that. mtl files generated from the plugin, I lost all textures. Setting the “Object list JSON” to the JSON file generated from the plugin correctly listed the much more usable object id’s in the “Object id” dropdown. Removing this grouping correctly resulted in a zip file being created. Luckily, I only had one group, so that was easy to remedy. Then saw a previous poster mention that it was to do with object groups. Initially, this didnt do anything for me. I did not manage to get a light entity to interact with the 3D plan. I understand that this is due to the way SweetHome 3D labels it’s objects (Why it can’t use the name I’ve given it in the software is beyond me). Trying to select a light in the 3D view to turn on from my entity is a bit of a nightmare however. ![]() From what I’ve been able to achieve so far is awesome! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |