Blendigo for v1.1.5
-
- Posts: 155
- Joined: Wed Jul 12, 2006 5:26 pm
Hi SmartDen,
First of all thanks for the updated script.
I downloaded the last versions and tried with some previous scenes and I got an "abnormal termination error".
After checking the exported file using the 111 and 115 version of blendigo, I observed that with the 111 version, the size was 180 mb and with the 115 version 450 mb (!?).
Hope this may be helpful
First of all thanks for the updated script.
I downloaded the last versions and tried with some previous scenes and I got an "abnormal termination error".
After checking the exported file using the 111 and 115 version of blendigo, I observed that with the 111 version, the size was 180 mb and with the 115 version 450 mb (!?).
Hope this may be helpful
- afecelis
- Posts: 749
- Joined: Tue Aug 01, 2006 4:14 am
- Location: Colombia
- 3D Software: Blender
- Contact:
Hi Smartden,
Thanks for your continuous efforts to keep blendigo up to date with Ono's latest releases and new things that get implemented.
However (and please excuse my ignorance if I'm about to say/ask anything obvious or stupid), I must agree that things are beginning to get a bit complicated, specially for non-power users (like myself ), yet I understand these "complications" are not on blendigo's behalf but due to the new features implemented in Indigo.
I then have some questions about the screenshot you posted on the 1st page:
-Is it compulsory to create UV texture layers for materials?
-Is it compulsory to create the two always (one for diffuse, one for bump)?
-Is it compulsory to name them that way? (albedo/bump) or as long as they match the name in blendigo, anything goes?
-What about materials with no UV layers, like glass, or NK materials, that in older versions required no UV mapping? Do we still need to create UV layers for them?
-In the case of a diffuse material with no bump in it, should we erase "bump" or "uv" (by default) and leave the name on this field blank?
I'm still trying to understand why all these changes and how they will benefit users. If things get too complicated I'll revert to "good old and trusty" 1.09
regards,
Alvaro
Thanks for your continuous efforts to keep blendigo up to date with Ono's latest releases and new things that get implemented.
However (and please excuse my ignorance if I'm about to say/ask anything obvious or stupid), I must agree that things are beginning to get a bit complicated, specially for non-power users (like myself ), yet I understand these "complications" are not on blendigo's behalf but due to the new features implemented in Indigo.
I then have some questions about the screenshot you posted on the 1st page:
-Is it compulsory to create UV texture layers for materials?
-Is it compulsory to create the two always (one for diffuse, one for bump)?
-Is it compulsory to name them that way? (albedo/bump) or as long as they match the name in blendigo, anything goes?
-What about materials with no UV layers, like glass, or NK materials, that in older versions required no UV mapping? Do we still need to create UV layers for them?
-In the case of a diffuse material with no bump in it, should we erase "bump" or "uv" (by default) and leave the name on this field blank?
I'm still trying to understand why all these changes and how they will benefit users. If things get too complicated I'll revert to "good old and trusty" 1.09
regards,
Alvaro
AMD Ryzen 7 1800 @3.6ghz, 32GB ddr4 3200 mhz Ram, Nvidia RTX 3060 12GB, Win10, Blender/Sketchup/Modo/Cinema4d
There is problem when using external pigm's and igm's.
If I try to use igm Indigo gives me error:
"IndigoDriverExcep:SceneLoaderExcep: The Mesh 'Cylinder' tried to use the material 'Material2', which have not been defined."
when pigm:
"IndigoDriverExcep:SceneLoaderExcep: Failed to load XML doc from path'..\materials\wood\old_parquet.pigm': Error document empty. Line 0, column 0.
Anybody had the same experience?
If I try to use igm Indigo gives me error:
"IndigoDriverExcep:SceneLoaderExcep: The Mesh 'Cylinder' tried to use the material 'Material2', which have not been defined."
when pigm:
"IndigoDriverExcep:SceneLoaderExcep: Failed to load XML doc from path'..\materials\wood\old_parquet.pigm': Error document empty. Line 0, column 0.
Anybody had the same experience?
A bit of patience...
Every time he same story: when a new version of software come out...PANIC!!!!
But, after a few time, the use become normal. Example, in Blender the UV face select is missed, but SmartDen is guilty for this? I think no!!! He made a BIG WORK for all the Blender-Indigo people, don't forget.
I think the only way to solve problems is EXERCISE and USE of a software, and non tedious philosophy about program functions, or other...
Use of 1.1.5 is difficult? Try another version, if you have a short time for a job!!!!
Personally i solved the use-problem in UV set, the only problem is a black parts in smoothed solid, but I'm try with different subdivision, etc.
Excuse for my poor English, and I hope is clear the sense of my post.
Mario
But, after a few time, the use become normal. Example, in Blender the UV face select is missed, but SmartDen is guilty for this? I think no!!! He made a BIG WORK for all the Blender-Indigo people, don't forget.
I think the only way to solve problems is EXERCISE and USE of a software, and non tedious philosophy about program functions, or other...
Use of 1.1.5 is difficult? Try another version, if you have a short time for a job!!!!
Personally i solved the use-problem in UV set, the only problem is a black parts in smoothed solid, but I'm try with different subdivision, etc.
Excuse for my poor English, and I hope is clear the sense of my post.
Mario
if you use external materials you should know, the material name in the pigm and in the blender/blendo have to be the same!Woodie wrote:There is problem when using external pigm's and igm's.
If I try to use igm Indigo gives me error:
"IndigoDriverExcep:SceneLoaderExcep: The Mesh 'Cylinder' tried to use the material 'Material2', which have not been defined."
when pigm:
"IndigoDriverExcep:SceneLoaderExcep: Failed to load XML doc from path'..\materials\wood\old_parquet.pigm': Error document empty. Line 0, column 0.
Anybody had the same experience?
Check normals, dude!
I did not intend to claim that this is somebody's fault. I just thought that it works like nk files (names do not have to match), and I found a bug. Thank you for explanation, it worked with igs materials (BTW it is casesensitive), but I tried that with pigms and it does not work. I of course checked name in XML file. Is the some more extensive explanation?
I use windows vista.
And mario - chill out man. No one says that this is Smarts fault. I think we are all greatfull for all his hard work. But the process of improving cannot continue without extensive testing. I tried to new feature and for whatever reason it does not work for me. Either it is my fault (most likely) or indigo or blendigo.
Anyway I also spotted a place for improvement (I don't know if this is possible). When I want to change external material browser takes me always into file folder not to the folder where the previously used igs/pigm is located.
I use windows vista.
And mario - chill out man. No one says that this is Smarts fault. I think we are all greatfull for all his hard work. But the process of improving cannot continue without extensive testing. I tried to new feature and for whatever reason it does not work for me. Either it is my fault (most likely) or indigo or blendigo.
Anyway I also spotted a place for improvement (I don't know if this is possible). When I want to change external material browser takes me always into file folder not to the folder where the previously used igs/pigm is located.
- Borgleader
- Posts: 2149
- Joined: Mon Jun 16, 2008 10:48 am
- Borgleader
- Posts: 2149
- Joined: Mon Jun 16, 2008 10:48 am
Ok so I re-read this thread twice already and found no mention o the error I got (or maybe I just missed something here or elsewhere).
So...I tried re-installing blender (twice) I tried re-installing Blendigo (and indigo) v1.1.5 2-3 times each, and I'm still having problems. Here's a picture.
(Sorry for the size. but I find resizing image screws up the text so I left it as it is so you could read it properly.)
So...I tried re-installing blender (twice) I tried re-installing Blendigo (and indigo) v1.1.5 2-3 times each, and I'm still having problems. Here's a picture.
(Sorry for the size. but I find resizing image screws up the text so I left it as it is so you could read it properly.)
- Attachments
-
- Hmm yeah...I dont even get why I have this error
- WTF_Indigo.jpg (577.83 KiB) Viewed 4406 times
Borgleader... You're not paying attention to the "\.." after the "\preview" directory. It's bumping you up one level. In other words, it's not looking it the textures directory in previews. It's up one level in the Indigo directory.
If you create your own textures folder there and add the file, it should work. That's how I fixed it.
A more permanent solution may be to edit the path in the IMPmatdb.igs file, but I haven't tried that.
If you create your own textures folder there and add the file, it should work. That's how I fixed it.
A more permanent solution may be to edit the path in the IMPmatdb.igs file, but I haven't tried that.
-
- Posts: 155
- Joined: Wed Jul 12, 2006 5:26 pm
It seems that nobody else got this problem !?enricocerica wrote:Hi SmartDen,
First of all thanks for the updated script.
I downloaded the last versions and tried with some previous scenes and I got an "abnormal termination error".
After checking the exported file using the 111 and 115 version of blendigo, I observed that with the 111 version, the size was 180 mb and with the 115 version 450 mb (!?).
Hope this may be helpful
How could it be explained, this is a huge size difference and it probably explains that Indigo crashes.
Any idea how to solve it ?
Thanks
Who is online
Users browsing this forum: No registered users and 52 guests