RE: Command used within Python Module causes memory leak?
Hi Eric, Is it reproducible if you use internal Python? Which Python version are you using? It would be helpful to investigate if you could provide some sample codes. Thanks, Songqiong Yang -Original Message- From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Eric Thivierge Sent: Saturday, November 01, 2014 4:32 AM To: softimage@listproc.autodesk.com Cc: Matt Lind Subject: Re: Command used within Python Module causes memory leak? I'm using external Python and am on 2014 SP2 with a QFE. Yeah not sure here. Eric T. On Friday, October 31, 2014 4:29:55 PM, Matt Lind wrote: what version of Softimage are you using? I have been experiencing memory leaks with C++ operators written in 2013 SP1. Same operator compiled for other versions seems to work fine. I’m tempted to say there is a known issue with memory leaks with Python in past versions, but I cannot say for sure. Might also be limited to the Python supplied with the factory installation. Matt attachment: winmail.dat
RE: Softimage 2015 SDK help not working
Can you open this link http://docs.autodesk.com/SI/2015/ENU/Softimage-Developer-Help/ ? It works in my site. Thanks, Joany From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Nuno Conceicao Sent: Wednesday, July 02, 2014 2:09 AM To: No name Subject: Softimage 2015 SDK help not working Is it just me or the online sdk help for Softimage 2015 is not working? attachment: winmail.dat
Re: Render tree crash with SI 2013
It was known issue logged as SOFT-5858:[CER]: Random crash when opening ICETree or RenderTree on certain scenes. and fixed in Softimage 2014. Thanks, Joany Original message From: olivier jeannel Date:15/05/2014 00:38 (GMT+08:00) To: softimage@listproc.autodesk.com Subject: Re: Render tree crash with SI 2013 Ok, thank you all for your solution. Opening the rendertree first, seems to solve the problem ! Now, what we be a good way to investigate on this ? I had the feeling that something is off on that particular workstation, since on other projects it has also some unstability. Thank's a lot. Olivier Le 14/05/2014 16:03, Tim Borgmann a écrit : I once had a similar problem while working on location at a company. The only work around solution was to open the rendertree first (in a clean scene) and than load the scene. I thought it maybe was caused by issues with the workgroups as it seems the crash was related to the rendertree loading some shader/rt_compounds when opened first. But I didn't had the time to investigate the problem in detail. So the workflow was open SI, hit 7 and than load the scene. Cheers Tim I'm still having crashes on one particular machine using SI 2013. on one particular scene, a big 500Mo object from cad, as soon as I hit 7, XSI crashes. I have a Quadro 4000 I already updated the drivers last month. Now I wonder if there are some settings I should tweak. This doesn't happen on other machines. It opens fine on a quadro 1800 machine. Anything to check ? any settings files to delete ? Would greatly apreciate advices. attachment: winmail.dat
RE: siComboBox
Notice the error message : “UI Items should be specified as a 1D array of String/Value pairs.” It should be 1d array of label/value pairs. So try to modify below codes as : MatTypes = [“Mat1”, Mat1, Mat2, Mat2, Mat3,Mat3] Thanks, Joany From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of philipp seis Sent: Wednesday, April 23, 2014 5:52 PM To: softimage@listproc.autodesk.com Subject: siComboBox Dear listers, i hope someone has a hint for me here, cause me = lost. I want to make a layout using siComboBox. It gives me an error claiming: python\Lib\site-packages\win32com\client\dynamic.py, line 258, in _ApplyTypes- Can i do something about that ? And then it says i shoud use a 1D Array, which i guess i have...,so ??? - this is what i'm running: --- xsi = Application lm = xsi.logmessage from win32com.client import constants as c from win32com.client import Dispatch as d oRoot = xsi.ActiveSceneRoot oRsCP = oRoot.AddProperty(CustomProperty,False,'RedShiftMaterial') MatTypes = [Mat1, Mat2, Mat3] RsLayout = oRsCP.PPGLayout # evil line throwing the error : RsLayout.AddEnumControl(ChooseMaterial, MatTypes, Type, c.siControlCombo) xsi.InspectObj(oRsCP) -- Log: # ERROR : 2229 - Traceback (most recent call last): # File Script Block , line 18, in module # RsLayout.AddEnumControl(ChooseMaterial, MatTypesCombo, Type, c.siControlCombo) # File COMObject unknown, line 3, in AddEnumControl # File C:\Program Files\Autodesk\Softimage 2013 SP1\Application\python\Lib\site-packages\win32com\client\dynamic.py, line 258, in _ApplyTypes_ # result = self._oleobj_.InvokeTypes(*(dispid, LCID, wFlags, retType, argTypes) + args) # COM Error: Invalid argument. UI Items should be specified as a 1D array of String/Value pairs. - [line 18] kind regards, philipp attachment: winmail.dat
RE: undocumented flag for Command.SetFlag()
Yes, you are right. By default, this flat is internally set to true for all custom commands. In this case, invoke Cmd.SetFlag( 262144, false ) to make the command be not undoable. Thanks, Joany -Original Message- From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Matt Lind Sent: Wednesday, September 04, 2013 1:30 AM To: softimage@listproc.autodesk.com Subject: RE: undocumented flag for Command.SetFlag() Interesting. I thought all self installing commands were undoable. How is setting this flag different? Thanks, Matt -Original Message- From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Songqiong Yang Sent: Sunday, September 01, 2013 7:48 PM To: softimage@listproc.autodesk.com Subject: RE: undocumented flag for Command.SetFlag() 262144 is an internal flag that is used to set as undoable. Thanks, Joany -Original Message- From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Sebastian Kowalski Sent: Saturday, August 31, 2013 6:59 PM To: softimage@listproc.autodesk.com Subject: Re: undocumented flag for Command.SetFlag() There is NO thing like weekend in the industry . . . Am 30.08.2013 um 21:42 schrieb Chris Chia chris.c...@autodesk.com: I will forward that to dev. It's already weekend for us. Will get back to you asap. Regards, Chris On 31 Aug, 2013, at 2:38 AM, Matt Lind ml...@carbinestudios.commailto:ml...@carbinestudios.com wrote: Edit: C:\Program Files (x86)\Autodesk\Softimage 2013 SP1\Application\Commands\GlobalVarPlugin.js From: softimage-boun...@listproc.autodesk.commailto:softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Matt Lind Sent: Friday, August 30, 2013 11:33 AM To: softimage@listproc.autodesk.commailto:softimage@listproc.autodesk.com Subject: undocumented flag for Command.SetFlag() Can anybody with inside information explain this one? I am looking at GlobalVariable.js which is the plugin for the SetGlobal(), SetGlobalObject(), and GetGlobal() commands. In the _Init() of each command there is a line that looks like this: Cmd.SetFlag( 262144, false ); Normally you'd see Cmd.SetFlag( siNoLogging, true ), or something like that, to define behavior of the command's execution environment. Upon looking in the SDK docs for Command.SetFlag(), there is no combination of enums that individually or bitwise combined that resolve to 262144 as shown above. So what does this flag do? Thanks, Matt winmail.dat attachment: winmail.dat
RE: InspectPreference
Try InspectPreferences(Camera);.It's required to pass a category name. In the preferences window, click the Preferences root folder, you can see all preference categories. Camera is one of category. Thanks, Joany -Original Message- From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Eugen Sares Sent: Thursday, August 29, 2013 3:10 PM To: softimage@listproc.autodesk.com Subject: InspectPreference Hi, it is possible to open the preferences of a certain category via script, like InspectPreferences(General); How do I open the prefs of, say, Camera? It's under a folder. InspectPreferences(Tools.Camera); does not work. Thanks! Eugen attachment: winmail.dat
RE: 'find' command not respecting current partition
Hi all, It's fixed in Softimage 2014. Check the following topic in user guide: Interface and Tools Windows and Views The Explorer Displaying Selected Elements Under the Current Pass in the Explorer Thanks, Joany From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Peter Agg Sent: Friday, June 14, 2013 1:23 AM To: softimage@listproc.autodesk.com Subject: Re: 'find' command not respecting current partition It's only slightly more annoying than when the Explorer is sure you want to find the object in a random group rather than in the hierarchy. On 13 June 2013 18:19, Simon van de Lagemaat si...@theembassyvfx.commailto:si...@theembassyvfx.com wrote: Dooohhh... ya pass not partition sorry. On Thu, Jun 13, 2013 at 10:15 AM, Gareth Bell gareth.b...@primefocusworld.commailto:gareth.b...@primefocusworld.com wrote: Do mean current pass? If that's the case, I find hitting U for current pass and then hitting F works. From: softimage-boun...@listproc.autodesk.commailto:softimage-boun...@listproc.autodesk.com [softimage-boun...@listproc.autodesk.commailto:softimage-boun...@listproc.autodesk.com] on behalf of Simon van de Lagemaat [si...@theembassyvfx.commailto:si...@theembassyvfx.com] Sent: 13 June 2013 18:11 To: softimage@listproc.autodesk.commailto:softimage@listproc.autodesk.com Subject: 'find' command not respecting current partition Does this drive anyone else up the damn wall? You have an object selected and when you hit F to find it in the partitions in explorer it takes you to an inactive partition? HAIR PULLING Sorry for the rant. attachment: winmail.dat
Re: custom operators and changing topology
Try to use CComAPIHandler, to call APIs provided by Object Model. More info pls refer to sdk manual about CComAPIHandler class. Thanks, Joany Original message From: ran sariel ran.sar...@gmail.com Date: To: softimage softimage@listproc.autodesk.com Subject: Re: custom operators and changing topology so does that mean that there's no way to write a custom operator changing topology in 2012??, On Wed, May 22, 2013 at 9:22 PM, Songqiong Yang songqiong.y...@autodesk.commailto:songqiong.y...@autodesk.com wrote: Hi Matt, Thanks for your comments. We will work with doc team to see what’s going on if there are sdk changes in SP. Normally, in SP release, SDK wouldn’t be changed except the bug fixing (But support backward-compatibility). This is very particular/rare case that happened in 2013 SP1. Back to this question, you may try to use CComAPIHandler, to call APIs provided by Object Model. Thanks, Joany From: Matt Lind [mailto:ml...@carbinestudios.commailto:ml...@carbinestudios.com] Sent: Thursday, May 23, 2013 8:45 AM To: Songqiong Yang; softimage@listproc.autodesk.commailto:softimage@listproc.autodesk.com Subject: RE: custom operators and changing topology For the record, SDK updates like this are pretty important. I would like to request the docs be updated with reach release whether it be a main release, service pack, or subscription advantage pack. In this particular scenario, if I had to write the custom topology operator, I would be following the 2013 SP1 documentation only to encounter errors from improper use (because SDK doesn’t match the manuals), or would pull out hair wondering why my operator is behaving in a flakey manner. It’s important the documentation be matched with the software we’re using. Thank you. Matt From: softimage-boun...@listproc.autodesk.commailto:softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.commailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Songqiong Yang Sent: Wednesday, May 22, 2013 5:21 PM To: softimage@listproc.autodesk.commailto:softimage@listproc.autodesk.com Subject: RE: custom operators and changing topology Hi Matt, We didn't update docs for service pack release. You can see their introduced version is v11.1(2013) in 2014 sdk manual. 11.1 means 2013 SP1. Thanks, Joany Original message From: Matt Lind ml...@carbinestudios.commailto:ml...@carbinestudios.commailto:ml...@carbinestudios.commailto:ml...@carbinestudios.com Date: To: softimage@listproc.autodesk.commailto:softimage@listproc.autodesk.commailto:softimage@listproc.autodesk.commailto:softimage@listproc.autodesk.com Subject: RE: custom operators and changing topology I’m on 2013 SP1, but those new methods are not shown in the SDK manuals. I think they were added in 2014. Matt From: softimage-boun...@listproc.autodesk.commailto:softimage-boun...@listproc.autodesk.commailto:softimage-boun...@listproc.autodesk.commailto:softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.commailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Songqiong Yang Sent: Tuesday, May 21, 2013 10:12 PM To: softimage@listproc.autodesk.commailto:softimage@listproc.autodesk.commailto:softimage@listproc.autodesk.commailto:softimage@listproc.autodesk.com Subject: RE: custom operators and changing topology Hi Ran, Which Softimage version are you using? Since 2013 SP1, there’re two new C++ APIs introduced, to allow the creation of paramdef with a specified classification. 1. Factory::CreateParamDef CreateParamDefhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1Factory.html#a3badfe123fc78a4353347e7c2de0d270 (const CStringhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CString.html in_scriptname, CValue::DataTypehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html#ad8ed01ff3ff3d8e19db4d2818bb6 in_type, siParamClassificationhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/namespaceXSI.html#a8f0a8fe3a0669ff112ec8be6075c9f92 in_classification, INT in_capabilities, const CStringhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CString.htmlin_name, const CStringhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CString.html in_description, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_default, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_min, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_max, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html
RE: custom operators and changing topology
Hi Matt, We didn't update docs for service pack release. You can see their introduced version is v11.1(2013) in 2014 sdk manual. 11.1 means 2013 SP1. Thanks, Joany Original message From: Matt Lind ml...@carbinestudios.com Date: To: softimage@listproc.autodesk.com Subject: RE: custom operators and changing topology I’m on 2013 SP1, but those new methods are not shown in the SDK manuals. I think they were added in 2014. Matt From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Songqiong Yang Sent: Tuesday, May 21, 2013 10:12 PM To: softimage@listproc.autodesk.com Subject: RE: custom operators and changing topology Hi Ran, Which Softimage version are you using? Since 2013 SP1, there’re two new C++ APIs introduced, to allow the creation of paramdef with a specified classification. 1. Factory::CreateParamDef CreateParamDefhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1Factory.html#a3badfe123fc78a4353347e7c2de0d270 (const CStringhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CString.html in_scriptname, CValue::DataTypehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html#ad8ed01ff3ff3d8e19db4d2818bb6 in_type, siParamClassificationhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/namespaceXSI.html#a8f0a8fe3a0669ff112ec8be6075c9f92 in_classification, INT in_capabilities, const CStringhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CString.htmlin_name, const CStringhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CString.html in_description, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_default, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_min, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_max, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_suggestedmin, constCValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_suggestedmax, CStatushttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CStatus.html *pst=0) 2. CustomProperty::AddParameter AddParameterhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CustomProperty.html#a3cd8cb29aea12aad508cfc2d623dc836 (const CStringhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CString.html in_scriptname, CValue::DataTypehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html#ad8ed01ff3ff3d8e19db4d2818bb6 in_type, siParamClassificationhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/namespaceXSI.html#a8f0a8fe3a0669ff112ec8be6075c9f92 in_classification, INT in_capabilities, constCStringhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CString.html in_name, const CStringhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CString.html in_description, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_default, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_min, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_max, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.htmlin_suggestedmin, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_suggestedmax, Parameterhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1Parameter.html io_parameter) Thanks, Joany From: softimage-boun...@listproc.autodesk.commailto:softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Ahmidou Lyazidi Sent: Wednesday, May 22, 2013 8:00 AM To: softimage@listproc.autodesk.commailto:softimage@listproc.autodesk.com Subject: Re: custom operators and changing topology what is your debuger saying? --- Ahmidou Lyazidi Director | TD | CG artist http://vimeo.com/ahmidou/videos 2013/5/22 Matt Lind ml...@carbinestudios.commailto:ml...@carbinestudios.com Scripting and C++ are not 1:1. It might not be necessary to set parameter classification to ‘siClassifTopo’ in C++. I don’t know the answer
RE: custom operators and changing topology
Hi Ran, Which Softimage version are you using? Since 2013 SP1, there're two new C++ APIs introduced, to allow the creation of paramdef with a specified classification. 1. Factory::CreateParamDef CreateParamDefhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1Factory.html#a3badfe123fc78a4353347e7c2de0d270 (const CStringhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CString.html in_scriptname, CValue::DataTypehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html#ad8ed01ff3ff3d8e19db4d2818bb6 in_type, siParamClassificationhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/namespaceXSI.html#a8f0a8fe3a0669ff112ec8be6075c9f92 in_classification, INT in_capabilities, const CStringhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CString.htmlin_name, const CStringhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CString.html in_description, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_default, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_min, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_max, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_suggestedmin, constCValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_suggestedmax, CStatushttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CStatus.html *pst=0) 2. CustomProperty::AddParameter AddParameterhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CustomProperty.html#a3cd8cb29aea12aad508cfc2d623dc836 (const CStringhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CString.html in_scriptname, CValue::DataTypehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html#ad8ed01ff3ff3d8e19db4d2818bb6 in_type, siParamClassificationhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/namespaceXSI.html#a8f0a8fe3a0669ff112ec8be6075c9f92 in_classification, INT in_capabilities, constCStringhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CString.html in_name, const CStringhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CString.html in_description, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_default, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_min, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_max, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.htmlin_suggestedmin, const CValuehttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1CValue.html in_suggestedmax, Parameterhttp://download.autodesk.com/global/docs/softimage2014/en_us/sdkguide/si_cpp/classXSI_1_1Parameter.html io_parameter) Thanks, Joany From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Ahmidou Lyazidi Sent: Wednesday, May 22, 2013 8:00 AM To: softimage@listproc.autodesk.com Subject: Re: custom operators and changing topology what is your debuger saying? --- Ahmidou Lyazidi Director | TD | CG artist http://vimeo.com/ahmidou/videos 2013/5/22 Matt Lind ml...@carbinestudios.commailto:ml...@carbinestudios.com Scripting and C++ are not 1:1. It might not be necessary to set parameter classification to 'siClassifTopo' in C++. I don't know the answer. Matt From: softimage-boun...@listproc.autodesk.commailto:softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.commailto:softimage-boun...@listproc.autodesk.com] On Behalf Of ran sariel Sent: Tuesday, May 21, 2013 3:21 PM To: softimage Subject: Re: custom operators and changing topology Thank you Matt the issue is not defining the data type, the problem I'm facing is trying to let softimage treat my customOperator as one that is changing topology. one of the advice I found online was defining the first parameters on that operator as siClassIfTopo, that method is valid for the object model but not in the c++ signature. Ran On Tue, May 21, 2013 at 2:49 PM, Matt Lind ml...@carbinestudios.commailto:ml...@carbinestudios.com wrote:
RE: Loop playback in animation sequencer
Hi Ronald, It's not supported in Camera Sequencer. Thanks, Joany -Original Message- From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Toonafish Sent: Friday, April 19, 2013 11:04 PM To: softimage@listproc.autodesk.com Subject: Loop playback in animation sequencer Is the playback loop setting broken in the shiny new Camera Sequence Editor in 2014 ? It does not seem to matter if I toggle it on or off in the Playback Options. Thanks, - Ronald attachment: winmail.dat
