So, after three weeks of vacation in Venice, Florence, Tuscany, Rome, and Paris, I’m back. Here’s a few pics from my trip, all taken with my iPod Touch, which was a great little travel companion.
You want to save a scene (a .scn file) to a folder that is not part of project. For example, you may want to save a copy of scene to a temporary working folder where a batch processing job can pick up the scene, and you don’t want to have to create a Softimage project.
Softimage scenes must be saved to a valid project location.
A valid project location is any folder that contains a system folder, with a dsprojectinfo file in that folder.
To create a minimal project location, you can simply copy the system folder from an existing project. You can then save the scene in that location (you don’t even have to create a Scenes subfolder).
It’s getting to be that time of year when people start asking about the next version…
You can probably get a pretty good idea of when to expect Softimage 2014 by looking backwards. So, here’s the dates that previous versions were announced and released (data gathered via google).
|2013||27 March 2012||12 April 2012|
|2012||01 March 2011||07 April 2011|
|2011||15 March 2010||06 April 2010|
|2010||03 August 2009||14 Sept 2009|
|7.5||23 Feb 2008||23 Feb 2008|
Display debug per-object attribute on distant point cloud
by Fabricio Chamon
Moving cached geometry
by Alok Gandhi
Turbulize Null position
The WordPress.com stats helper monkeys prepared a 2012 annual report for this blog.
Here’s an excerpt:
About 55,000 tourists visit Liechtenstein every year. This blog was viewed about 290,000 times in 2012. If it were Liechtenstein, it would take about 5 years for that many people to see it. Your blog had more visits than a small country in Europe!
In 2012, there were 374 new posts, growing the total archive of this blog to 1,123 posts. There were 810 pictures uploaded, taking up a total of 186 MB. That’s about 2 pictures per day.
The busiest day of the year was August 31st with 1,893 views. The most popular post that day was Friday Flashback #85.
Early this week, I posted a script that did a random shuffle of a collection of objects. That script used tuple assignment to swap elements in a list; here’s a simpler example, with the tuple assignment (line 9) highlighted:
import random v = [o for o in Application.Selection] print [o.Name for o in v] # random shuffle for i in range( len(v) ): j = random.randint( i, len(v)-1 ) v[i], v[j] = v[j], v[i] print [o.Name for o in v] # [u'cube', u'cube1', u'cube2', u'cube3', u'cube4', u'cube5', u'cube6', u'cube7', u'cube8'] # [u'cube5', u'cube4', u'cube7', u'cube2', u'cube1', u'cube3', u'cube', u'cube8', u'cube6']
Looking at that line, you might wonder why you don’t end up assigning the same value to both a[i] and a[j] (eg, how does that line not do a[i] = a[j] and then a[j] = a[i] ?).
In tuple assignment, the right-hand side is considered a tuple of values. So the right-hand side is evaluated first, and then the resulting values are pairwise assigned to the tuple on the left hand side. For example, consider this-rather-more-concrete snippet:
a = 2 b = 8 a,b = b-a,b+a print a print b # 6 # 10
The right-hand side “b-a,b+a” is first evaluated, giving the tuple 6, 10, so you effectively have this:
a,b = 6,10
After my stay at Autodesk ended seven weeks ago, I never got to say anything like “I’ll be back”, because I never really went away. Posting here continued more or less as normal. But now, I’m back at work: today is my first day at Solid Angle SL as one of the Solids, as they’re [apparently] sometimes called
I’ll be working from my home office, with occasional visits to Madrid.