I've used it a decent amount as the guys at the foundation of our studio
all use it, but I really dislike it (I used it years ago too before xsi) it
is so dis-organised and slow, I think it breeds sloppy workflow with messy
scenes in terms of scene organisation naming etc. XSI has explorer
I had posted a replicable and verified bug regarding the fact that a
few--and likely many--commands do not iterate over multiple deltas attached
to a reference model. While I have no idea if that bug is a low enough
hanging fruit to fix before all of us lose support in 2016, I also have no
idea
What I suggest you do is a ingest process workflow.
1 - Ingest - Use the object load to spit your objects onto the parts you want,
make sure you put some nicely name nulls (these will be your hooks) and if you
are very tidy add a red material in your object level. Also this is the point
in
Did anyone else, other then me, go the direction of max/vray? I was pseudo
forced as it seemed to be the software of choice in smaller commercial
shops here in Toronto. There's no ICE like architecture in there but for
look Dev I've found it really good! I found the material slate editor nicer
Hello,
Was wondering if there is a way to have a self installing property
survive a New Scene call. Typically I attach it to the Scene Root but
that won't survive a New Scene call.
I have a UI that I would like to save the state of over a new scene call.
Anyone have a trick for this?
Eric
to select an object in your scene, right click your item (in the explorer) and
and choose select in scene
was all I needed to hear.
...
ahhahaahhahaha
On Mon, Mar 23, 2015 at 3:51 PM, Andi Farhall hack...@outlook.com wrote:
to select an object in your scene, right click your item (in the
explorer) and and choose select in scene
was all I needed to hear.
On Mon, Mar 23, 2015 at 9:09 AM, Simon Reeves si...@simonreeves.com wrote:
I've used it a decent amount as the guys at the foundation of our studio all
use it, but I really dislike it (I used it years ago too before xsi) it is
so dis-organised and slow, I think it breeds sloppy workflow with
I never got it to work, but you can try this.
http://download.autodesk.com/global/docs/softimage2013/en_us/sdkguide/si_cmds/SetGlobal.html
On 23-Mar-15 11:07, Eric Thivierge wrote:
Hello,
Was wondering if there is a way to have a self installing property
survive a New Scene call. Typically I
Personally I'm not changing stuff (partly because you can't change the
things I would want tot change in Houdini)
For me this is a pretty big commitment. I plan to go full-Houdini, so I
will probably change my Maya and Soft, to work like Houdini, if I change
anything.
It is hard enough to learn
I think the old XSIMan by graphicprimitves was the closest you could get to
a prman bridge, sadly the product was discontinued a long time ago.. I
tested it quite a bit when it came out, nice little plugin but the
implementation was rather basic in a way, no render-region support etc.
there is
Add the creation of the property to a NewScene event, maybe?
Greetz
Leendert
--
Leendert A. Hartog AKA Hirazi Blue
Administrator NOT the owner of si-community.com
If I do this, I lose the selected values in the property. :\
On 3/23/2015 12:04 PM, Leendert A. Hartog wrote:
Add the creation of the property to a NewScene event, maybe?
Greetz
Leendert
Not exactly what I was looking for. I want to attach my Property to
something in the application so the UI stays open and valid when
creating a new scene. Not just values.
Thanks though,
Eric T.
On 3/23/2015 11:59 AM, Francois Lord wrote:
I never got it to work, but you can try this.
Hey Eric,
here's what I would try: (brainstorming alert - I've never done this myself
this way... :) )
Inside your custom property implementation I'd implement an onChanged()
callback that collects all relevant parameter values, serializes them into
a json string and stores this string outside
A custom user preference page are the only solution. Everything else
will get flushed.
On Mon, Mar 23, 2015 at 12:05 PM, Eric Thivierge ethivie...@hybride.com wrote:
Not exactly what I was looking for. I want to attach my Property to
something in the application so the UI stays open and valid
SetGlobals is definitely a good solution. I have worked with this successfully
before. But it only to retrieve and set single boolean value.
In your case I would rather have json save out running on each scene close
event and retrieve on scene open event.
Sent from my iPhone
On 23-Mar-2015,
If you implement your UI in Netview, it will survive a new scene call.
Other options include using custom preferences, or dumping your UI state to
storage such as a file on the hard drive or as data in memory where a
onBeginNewScene event can access the data.
Another option is plugin
Luc-Eric is right on the money with this one. We have several of these in
our pipeline to have data persist even between closing and opening a session
On Mon, Mar 23, 2015 at 11:11 AM, Luc-Eric Rousseau luceri...@gmail.com
wrote:
A custom user preference page are the only solution. Everything
I guess it depends on one’s choice of workflow. It’s much more convenient to
use takes for overrides when materials are at the object level. If you’ve set
up bundles, it’s basically just a select objects from bundles, set the take and
assign new materials, done. It’s much more involved to do
you can use old tutorials, the nodes are the same, the interface might look
a Little bit different, but the nodes have the same functionality. we still
look at some old tutorials from version 8 =). Sesi just keep adding new
nodes. but you will find that every one use mostly the
Just received notice from Pixar that Renderman free for non-commercial use
is now available.
Does anybody have used Renderman before with Softimage and is their a
bridge between Softimage and Renderman available?
(yes, I have Maya too, so I can use it with Maya but I would like to test
Renderman
3delight exports rib files...
Greetz
Leendert
--
Leendert A. Hartog AKA Hirazi Blue
Administrator NOT the owner of si-community.com
cmd line renderman is available but not sure how you would make a rib
with all the new shader parameters etc straight outa softimage :(
On 23 March 2015 at 21:32, Daniel Brassard dbrassar...@gmail.com wrote:
Just received notice from Pixar that Renderman free for non-commercial use
is now
for playing around with it, sure, but if you use softimage I don't think
prman is a serious alternative for commercial projects these days. 3delight
will export ribs sure, but to actually get those to render in prman is a
different thing, getting shaders to work etc.
On Tue, Mar 24, 2015 at 10:59
Saving a preset of the property in a siOnCloseScene event and reloading
in a NewScene event?
Can't test this ATM, not near Softimage. But it's inelegant even if it
works...
I'll shut up now... ;)
Greetz
Leendert
--
Leendert A. Hartog AKA Hirazi Blue
Administrator NOT the owner of
Yeah not something I really want to do for saving the state and I can
just deal with it for now. Guess this is why doing a QT Window UI that
is attached to the application would be best.
Thanks,
Eric T.
On Monday, March 23, 2015 12:59:40 PM, Leendert A. Hartog wrote:
Saving a preset of the
27 matches
Mail list logo
