I don't have time to commit to discussion right now as I'm studying for
final exams, but I thought I'd mention a few things:
1) As established earlier, custom topology operators are NOT officially
supported in the Softimage SDK. You might be able to create a custom
topology operator to work for a specific use case, but it is not supported
for the general case. So don't be surprised if you cannot solve certain
problems.
2) Try defining all your port connections explicitly as input or output,
don't mix n' match between explicit ports and the combined IOPort.
3) Make sure to define all your output ports before defining any input
ports.
4) Try defining fixed port index values for your connections, listing your
output ports first.
These may sound like splitting hairs, but when you're dealing with an
incomplete system, you must try all options. I've often found subtle
differences in implementations are often the difference between something
that works vs. something that doesn't. It can be a hair pulling experience,
but if you find a solution, then it's worth it.
Matt
Date: Fri, 9 Dec 2016 14:20:19 +0300
From: Andrew Prostrelov <prostre...@gmail.com>
Subject: Re: Preserve UV methods after PolygonMesh.Set()
To: softimage@listproc.autodesk.com
XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Dear Santa,
I've been good all year.
Most of the time.
Once in a while, never mind.
All year i spent my work and free time to make XSI modelling tools
more interactive and usable.
Somehow i manage to finish about 3 tools in this year and bunch of
small scripts&tools.
Its only two tools left and toolset would be finished and ready to
release.
First one of unfinished tools is Multicut. And, since i'am not a TD
or TA, it took me about
4 month of work to get to the stage where i am at now. And it's been
a month since i stuck and
have no progress or changes. And i'm afraid that this Multicut tool
will end up unreleased and unusable
only because there is native packet bug there(or limitations i'm not
sure how to call it).
So Santa for this Christmas all i want is to find some way, trick,
workaround, hook, anything
that force "always complete" XSI Clusters to receive new components
from PolygonMesh.Get&Set processing.
Oh, and the second one tool is about XSI Retopology.
Andrew.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Ok. End of jokes here.
All entry stuff you can get from dialog above that we have with Matt.
So, to be more object oriented here is test stuff (11MB):
https://www.dropbox.com/s/m9sfrn8v3ajgd1d/myTest.zip?dl=0
The test scene "myTestScene.scn":
Its a simple 3x3 grid.
The test VS2013 Project "myTest.sln":
This project already have compilated to "myTest.dll" in nt-x86-64
directory.
This plugin deliver CustomCommand "myTestStart" and CustomOperator
"myTest".
Now all that you should do is:
01. open myTestScene.scn
02. load plugin myTest.dll to XSI
03. select grid in object mode (there is no need to select components all
stuff is hardcoded)
04. apply myTestStart CustomCommand to this object
As result you end up with additional edge added to source grid, two
clusters (Point and Sample) and myTest Operator in modeling stack.
Now if you dig through this Operator connections you find that Operator
have next ports:
OUT polygon mesh
IN polygon mesh
IN&OUT components cluster
IN&OUT samples cluster
I connected this Operator ports a lot of ways - there is no difference. I
mean, Clusters are not updating anyway.
Now if you look to the ScriptEditor Log, clusters are "always complete".
But if you look to the Cluster components array through SDK_Explorer (or
simply by selecting them)
you can see that this both Clusters do not have new edge vertices and
samples.
Thats the problem ! That's what holds me up from finishing this Multicut
tool.
And here is a short video of all this test process:
https://youtu.be/5eAo5bD_bQM
No babbling speeches only music )
------
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with
"unsubscribe" in the subject, and reply to confirm.
