Re: Single frame subregion parameter for batch render.
If you can script, you can do this using a script and xsibatch. the script is simply setting the subregion before xsibatch renders the image. You can pass arguments for the passe.CropWindowWidth, passe.CropWindowHeight, passe.CropWindowOffsetX and passe.CropWindowOffsetY and renaming you output image. there's a reference on how to call the command here at the bottom of the page, the "Using Scripts to Set Renderer Specific Options" section. http://softimage.wiki.softimage.com/xsidocs/rendering_BatchRenderingBasicsXSIR.htm On Wed, Apr 2, 2014 at 11:34 AM, Robert Cole wrote: > I need to render individual tiles of a very high resolution image (and > stitch them together after, most likely w/ Photoshop). I can no longer find > the documentation on Image Resolution>subregion parameter for batch > rendering..anybody have a hint? And, if anybody would like to chime in on > another, possibly less tedious way of rendering out and saving individual > tiles , I would be very grateful. (The requested image is to go on a 20' > wall...) > > Thank you, > -Robert > > >
Shotgun join Autodesk
Here we go again... http://inthefold.autodesk.com/in_the_fold/2014/06/going-faster-shotgun-joins-autodesk.html Hans
Re: Softimage crash on startup
might be obvious, but has not been mentioned... did you remove the softimage in you home, then retart Soft? i.e C:\Users\[user]\Autodesk\Softimage_2014_SP2 Hans On Wed, Jul 23, 2014 at 9:39 AM, todd peleg wrote: > Stephen.. > > I followed those videos you did about the process manager.. and a tutorial > about running a script with xsibatch..no errors at all.. > > it did what it was supposed to do (echoed "hello") > > I never had mcafee or norton or any of the like on this machine.. and like > i said.. until recently.. it worked fine.. > > i am fairly confident there is a conflict (obviously) but i cant pinpoint > it at all.. which puts it just outside my wheelhouse... > > > ill run the process manager again.. and isolate the data you indicate in > your tutorial and send it to you... thank you so much for the offer. > > > todd > > > On Wed, Jul 23, 2014 at 5:42 AM, Stephen Blair > wrote: > >> If you want, send me the Process Monitor log and I'll take a look. >> >> You could try using msconfig to do a selective startup, but you'll need >> to enable the right services to keep your licensing. >> >> Did you try to run a script with xsibatch? >> >> http://xsisupport.com/2012/12/12/the-case-of-mcafee-antivirus-vbscript-and-the-softimage-startup-crash/ >> >> >> On Tue, Jul 22, 2014 at 10:20 PM, todd peleg >> wrote: >> >>> Hi all.. >>> >>> I have a machine that softimage has worked on consistently for YEARS. >>> >>> today... it decided to open up with this error: >>> "Failed to save scene before system failure" >>> >>> then its gone. >>> >>> ive tried a ton of the troubleshooting ive found thru google searches >>> with no success.. >>> >>> can anyone point me to any other options? >>> >>> >>> things ive tried thus far (not in this order): >>> >>> - checked the registry for issues related to jscript and vbscript >>> (nothing found) >>> - uninstalled any newly added software >>> - renamed the user preferences >>> - double checked graphics driver issues by >>> a) editing the layout file to open with the explorer rather than the >>> view manager >>> b) reinstalled an approved graphics driver >>> - installed 2 new clean versions of softimage (2014 and 2014 sp2) >>> - runonce.bat (all all versions) - nothing showed up that i saw >>> - launched xsibatch.. it worked >>> >>> i also tried the process manager... but.. i couldnt find anything >>> outstanding.. though i admit at a certain point.. i got confused..and >>> stopped reading thru it. >>> >>> thanks for anyone that can help. >>> >>> >>> todd >>> >> >> >
Re: Splitting a still render into multiple frames (addon?)
This was my answer in a previous thread: "If you can script, you can do this using a script and xsibatch. the script is simply setting the subregion before xsibatch renders the image. You can pass arguments for the passe.CropWindowWidth, passe.CropWindowHeight, passe.CropWindowOffsetX and passe.CropWindowOffsetY and renaming your output image accordingly. There's a reference on how to call the command here at the bottom of the page, the "Using Scripts to Set Renderer Specific Options" section. http://softimage.wiki.softimage.com/xsidocs/rendering_BatchRenderingBasicsXSIR.htm " As far as qube, there's a way to feed the job's package with values for these paremeters for every work. then your job type uses these values and feed them to your xsibatch command line. You can then merge all the tiles easily into Nuke. On Wed, Aug 20, 2014 at 2:32 PM, Steven Caron wrote: > deadline uses the crop window.. alan, you guys using arnold still? if so, > arnold supports the crop window just like mental ray. > > in deadline's submission dialog you can just choose the number of tiles in > x and y. it computes the number of tasks and on load of the scene sets the > pass crop before arnold starts rendering. > > > On Wed, Aug 20, 2014 at 11:26 AM, Matt Lind > wrote: > >> It would help greatly if you mentioned which renderer you’re using as >> that more than anything will dictate your options. >> >> >> >> >> >> Matt >> >> >> >> >> >> >> >> *From:* softimage-boun...@listproc.autodesk.com [mailto: >> softimage-boun...@listproc.autodesk.com] *On Behalf Of *Alan Fregtman >> *Sent:* Wednesday, August 20, 2014 11:20 AM >> *To:* XSI Mailing List >> *Subject:* Re: Splitting a still render into multiple frames (addon?) >> >> >> >> I have neither, but how does it work with those? >> >> >> >> My employer uses "Qube" by PipelineFX. >> >> >> >>
SP2
Please someone explain, How does naming a release SP2 compare to SP1 has a version number increment of 0.0.03? 2014 SP1 = 12.1.94 2014 SP2 = 12.1.99 Should itnot have been at least 12.2.xx? You can blame my code but I always have relied on point version to differenciate versions.In this case they both return 12.1. It has always been consistent at least since 2010. Why different now? Hans
Re: SP2
0.0.05 rather On Mon, Jul 29, 2013 at 4:36 PM, Hans Payer wrote: > Please someone explain, > > How does naming a release SP2 compare to SP1 has a version number > increment of 0.0.03? > > 2014 SP1 = 12.1.94 > 2014 SP2 = 12.1.99 > > Should itnot have been at least 12.2.xx? > > You can blame my code but I always have relied on point version to > differenciate versions.In this case they both return 12.1. > > It has always been consistent at least since 2010. Why different now? > > Hans >
Re: SP2
Same here. new compiled plugins loads in SP2 but not in SP1. On Mon, Jul 29, 2013 at 7:58 PM, Nicolas Burtnyk wrote: > 2014 SP2 *does* have API changes, even to the extent that plugins compiled > against 2014 SP1 are not loadable in 2014 SP2. > > Our installer got broken by the weirdness in version numbers. In all > versions back to 2011 (and probably before that), the "minor" version > referred to the SP#, i.e. 2011 SP2 is 9.2.. The SAPs start at minor > version 5, with a similar +1 on the minor for SPs, e.g. 2011 SAP SP1 is > 9.6.. > > So I agree that the version number is "wrong" for 2014 SP2. > > > > > On Mon, Jul 29, 2013 at 3:41 PM, Luc-Eric Rousseau wrote: > >> looks alright to me. >> >> the build number change tell me SP2 is indistinguishable from SP1 >> except it's got some code change that caused 5 builds but dont affect >> API or scene file. However, if SP1 is indeed a 11.1 instead of 11.0, >> then there must have been API change or something that affects the >> version of the scene file. >> >> you can see other examples of build numbers here.. >> http://xsisupport.com/2012/07/18/softimage-build-versions >> >> 2011 SP2 changed persistence. goddamn shader persistance bug and the >> only time we've done a SP2 at ADSK >> >> >> On Mon, Jul 29, 2013 at 4:37 PM, Hans Payer wrote: >> > 0.0.05 rather >> > >> > >> > On Mon, Jul 29, 2013 at 4:36 PM, Hans Payer >> wrote: >> >> >> >> Please someone explain, >> >> >> >> How does naming a release SP2 compare to SP1 has a version number >> >> increment of 0.0.03? >> >> >> >> 2014 SP1 = 12.1.94 >> >> 2014 SP2 = 12.1.99 >> >> >> >> Should itnot have been at least 12.2.xx? >> >> >> >> You can blame my code but I always have relied on point version to >> >> differenciate versions.In this case they both return 12.1. >> >> >> >> It has always been consistent at least since 2010. Why different now? >> > >
siutils.py changes in 2013? why?
Hello, The si shortcut in siutils return a method object in 2013 instead of the XSI.application object in 2012. So to get the same result as in 2012 you have to add parentheses() when calling si in 2013 in order my old plugins to work. Seems like no big deal, I will change siutils.py so it behaves as in 2012. But why change it? Is there a good reason? It's a bit annoying. Now I'm afraid others will start writing code with si() and I'll have to find a clever way to support both at the same time. Thanks Hans
Re: siutils.py changes in 2013? why?
Thanks On Thu, Apr 26, 2012 at 3:57 PM, Steven Caron wrote: > there was a 'memory leak'. i logged an issue about this mentioning they > should have provided a way to avoid the leak but maintain compatibility > with client code. i suggest you do the same so it will get some more > attention. > > i wouldn't change siutils.py but instead put a try catch in your code > until its resolved. > > s > > > On Thu, Apr 26, 2012 at 12:53 PM, Hans Payer wrote: > >> Hello, >> >> The si shortcut in siutils return a method object in 2013 instead of the >> XSI.application object in 2012. So to get the same result as in 2012 you >> have to add parentheses() when calling si in 2013 in order my old plugins >> to work. Seems like no big deal, I will change siutils.py so it behaves as >> in 2012. But why change it? Is there a good reason? It's a bit annoying. >> Now I'm afraid others will start writing code with si() and I'll have to >> find a clever way to support both at the same time. >> >> Thanks >> >> Hans >> > >
Re: AFX Cameras to XSI
I don't if it still works with CS6. Haven't played with for a while. try this: http://www.motience.com/index.php/mtools/documentation/16-import-ae-transform Hans On Tue, May 22, 2012 at 8:00 PM, Marc Brinkley wrote: > I know this has come up a few times sorry for more noise. > > > > Anyone have a way to get AfterFX CS6 cameras out to Softimage? We needed > to track some footage in the new CS6 version of AFX and it would be great > to get that info into Softimage. > > > > TIA! >
Re: SaveCopyAs
There is no equivalent of a savecopyscene in Softimage. I think copying an already saved scene to another location is the way to go. Any scripting language can do that without the need of the sdk, except for getting the current scene path. I know the workflow is different with Max but f.y.i. Softimage will not allow anybody to overwrite a scene once it's pick up by a node on the farm. In that case, the user has to change his scene file name if he want to save his scene. On Thu, Jan 3, 2013 at 7:52 PM, James Vecore wrote: > Hello Everyone, > > ** ** > > I’m new to the mailing list. My company (Pluto Post) is getting started > with Softimage and ICE. My first task was to setup a custom Qube render job > for V-Ray for Softimage. The issue I have run into is that there seems to > be no way to save a scene and NOT change the current scene’s save location. > 3dsmax has a very simple maxscript command to do this and we used it in our > custom max submit. The reason we use SaveCopyAs is that we like to save a > copy of current scene at submission time as a snapshot of the scene in the > output folder. This way we always have a copy of the scene exactly as it > was when the render was submitted and the user is free to continue to > save/version his current scene at his or her discretion without messing > with the render job. > > ** ** > > I could not find a way to do this in softimage without double saving > (which I want to avoid, especially with 1GB+ files). I only see two command > related to saving: SaveScene and SaveSceneAs. I also searched the C++ sdk > for anything that would let me achieve what I want and I could not find > anything. My current solution is to save the current scene to the current > path and copy the scene file to the destination. This is not ideal since > the user may not always want to overwrite their scene save before render > (especially our artists that use to the existing 3dsmax workflow). I could > also force a version up save, but that is also not ideal and will generate > many more save versions that necessary. > > ** ** > > Obviously it is not a deal breaker if SaveCopyAs is not possible, but it > would help ease our transition if anyone has any idea how to accomplish it. > > > ** ** > > Thanks, > > ** ** > > -James >
