Hi Scrubs just trying this out and I'm getting a Python Script error in Blender v2.78b

bpy.context.space_data.bookmarks_active = 0
bpy.context.space_data.recent_folders_active = 0
bpy.ops.text.run_script()
Python script fail, look in the console for now...

Works OK here.
Are you using filmic?
In the latest version, you need to click "Run Script" right after importing the model. You do not need to append the parts to the Model object (all parts need to remain selected).
Other than that I am not sure. Does it fail with every model? I am still with Blender 2.77 but I doubt it would make a difference.

I just tried it in v2.77a and it works just fine.
In my v2.78b I have switched over to filmic (by means of replacing the colormanagement folder) and just forgot to change the line in replace.py : P Now it's working perfectly.

No worries. I like to know that everything is ok 😉

Version 1.8.9 available. Older versions do not work anymore due to Collada exporter modifications.
Empty your browser cache before exporting.

There is a small bug in the collada exporter. It can happen that the export will fail. I will fix it when I'll be back home in a few hours. For now, if it fails, just include a decorated part in your scene. You can delete the piece in Blender later.

Issue fixed. Clear your browser cache.

Hi Scrubs, thanks for making such an awesome program! One question I do have though-- in the new version of the template, I noticed that when I import into Blender, the model itself no longer generates directly on the ground layer. Instead, it is floating rather high up. Even though when I export from MecaBricks workshop, the model is sitting on the ground. Is there a reason for this, or a way to have the model import so it is sitting properly? I never had this problem with the older version of the template. Similarly, new renders since the old template came out seem to have much more noticeable lines between individual parts as well, along with a generally cloudier look to the bricks as well.

Thanks!

I just tried but everything imports correctly for me. When you import in Collada before running the script is everything ok?
Regarding the materials, I did not change really change anything for the last few update of the script.

Thanks for the answer! Regarding the importing, I tried exporting a few other models just to test. Some generated on the "ground" layer in Blender as they should have, but others just randomly generated either floating quite a bit above or below the "ground" layer. As far as I know, I'm doing the export process correctly (export -> Collada -> Group by Geometry -> Add LEGO Logo), so not sure what is going on there.

For the rendering differences though, after the new update the normal import rendering process has yielded different results. I have not modified any of the script, and I'm not getting any errors or anything. Simply just opening up the Blender Lite Template, deleting the bricks that are already there (like you do in the tutorial video), and then importing and positioning the model. I'm using the same HDR file (Studio 032) as well. The end result in the new template creates edges between the bricks that are very bold, as well as a different, more cloudy look to the shadows and transparent pieces. I did a test render using the new version of Blender and the new Template to show the difference from a render I did back in January:

Blender 2.77, Template 1.8.5: http://i.imgur.com/XW6eJPO.png

Blender 2.78, Template 1.8.9: http://i.imgur.com/jgTv6J8.png

For both, I just imported the Collada file, ran the script at the appropriate time, resized & positioned the model, added the HDR Studio 032 file, and rendered. I know a handful of friends as well who have noticed this problem.

Thanks again for taking the time to check this out!

Hi Scrubs,

I am facing the same problems as Legosim posted above. I have tried a clean reinstall (due to a laggy interface, but that can be solved pretty easily), but that did not solve the problem. I really like the program, and it can certainly look very pretty.

The first one is from late January, using Blender 2.77 and template 1.8.4
http://i.imgur.com/XpmiYqC.png

This one is from yesterday, and is a similar model, but one can see the difference in quality. (Blender 2.78, Template 1.8.9)
http://i.imgur.com/7z2rU7y.png

Both were ran using the same settings (HDR 032, transparant background) following the standard instructions.

Thanks in advance!

For the cloudy thing it looks like a round edge shader issue. Let me look into that one.
@Legosim for the position thing, do you have an example of a public model where you have an issue so that I can try it out?

Just tried with Blender 2.77 and 1.8.9. No problem. Round edge shader behaves as it is supposed to.
I guess I will have to install Blender 2.78 tonight to see if I get the same as on you renders.

Scrubs, the one model I was consistently having trouble with on the positioning was this guy: http://mecabricks.com/en/models/PKbjQNZRvdG

Again, very much appreciate your help with this!

I tried it but I don't have any issue. Again with Blender 2.77
Here is a side view of before and after hitting the "Run Script" button.

Scrubs, interesting. I uninstalled 2.78c and reinstalled 2.77; the model imported directly onto the ground layer. Maybe it's just a difference between the two versions of blender? Anywho, I'll try out a render using Blender 2.77 and the 1.8.9 Template as well, and see if the shader effect is still there. Thanks!

EDIT: Actually, I tried to use the 1.9.8 Template with Blender 2.77 and the program crashed about 20 minutes into the render. Have had that happen a few times now. Uh oh.

Are you on windows? It looks like 2.77 windows doesn't like SSS with a cubic falloff. Gaussian works fine though.

I just installed Blender 2.79c on MacOs. The tank is importing at the good location. No issues... Did you try to re-download the script to start fresh?
Same for renders. I tried with a little model and both images where rendered exactly the same. So it is confusing. Are you sure you don't scale your model after running the script?

It looks like it was scaled to me. Scaling causes weird things to happen, and it looks exactly like what the examples were. 😉

I have tried rendering it twice now, and one of the times, it crashed after a while, the other one ran fine. I made sure to scale and position the model before I ran the script, yet the (partial) result that I first got was as clouded as the previous ones and the new one. I'll list my steps so you can determine if I am doing something wrong.
First I removed the bricks from the template and adjusted the camera. Then I imported the model and scaled and positioned it correctly. After that, I selected a HDR, ran the script (after which the program lags a bit and says it doesn't respond), before I rendered it.
If I recall correctly, scaling the model never affected the outcome of the previous renders, so I find it peculiar that it would suddenly become a problem.