You already have the polygon node ids. You can drill down into the triangles collection of the polygonmesh object to get access to the triangulated mesh. From there, just sum the triangles for each polygon as the node ids will match the triangle index ids. You can alternately ignore node indices and iterate via polygon index property on each triangle.
Matt --- Original Message --- From: softimage-requ...@listproc.autodesk.com Sent: March 14, 2016 12:00 PM To: softimage@listproc.autodesk.com Subject: Softimage Digest, Vol 88, Issue 56 Send Softimage mailing list submissions to softimage@listproc.autodesk.com To subscribe or unsubscribe via the World Wide Web, visit http://listproc.autodesk.com/mailman/listinfo/softimage or, via email, send a message with subject or body 'help' to softimage-requ...@listproc.autodesk.com You can reach the person managing the list at softimage-ow...@listproc.autodesk.com When replying, please edit your Subject line so it is more specific than "Re: Contents of Softimage digest..." Today's Topics: 1. Re: XSI and Window 10, the bright future (Luc-Eric Rousseau) 2. polygon area sum for normalizing texel density (Fabian Schnuer Gohde) ---------------------------------------------------------------------- Message: 1 Date: Mon, 14 Mar 2016 11:21:36 -0400 From: Luc-Eric Rousseau <luceri...@gmail.com> Subject: Re: XSI and Window 10, the bright future To: "softimage@listproc.autodesk.com" <softimage@listproc.autodesk.com> Message-ID: <cap7dfks-ghsz-y97rj6jljkayv4atvq3qijpdudtaesxq6-...@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 If you're the kind of person that's using "Classic Shell" you should probably not upgrade to windows 10. Just leave that machine on windows 7 until it dies, and you'll get windows 10 on the next PC. There is a way, however, you can keep your "free windows 10" option open forever and not worry about the end date. I have done this myself, twice. To do that, you need to upgrade your windows 7 to windows 10, check that it's activated, and then downgrade back to windows 7. Your BIOS will then be activated for both 7 and 10, and you can re-install windows 10 at any time in the future. That's also the way to do a "clean install" of windows 10: you upgrade, wipe, and then install windows 10 from the downloaded .iso At this point, it would be best if you cloned your boot disk, which I did on one PC with the free software that comes with SSD drives. It's a perfect time to upgrade to SSD if you haven't done so, and then you can leave your unused windows 7 drive for safe-keeping. After you install windows 10, you have 30 days to revert to windows 7, it's a button in the control panel. (http://windows.microsoft.com/en-ca/windows-10/going-back-to-windows-7-or-windows-81) This works, although in my experience some things messed up in the upgrade/downgrade process, so it's best to clone the drive. XSI and Adobe survive the process just fine, however. Personally, I have two HP computer that broke in some ways (realtek audio not working, not waking up sleep) with windows 10. You can install something called "GWX Control Panel" to block all the nagging messages and automatic downloads of windows 10. On 13 March 2016 at 13:47, Fabian Schnuer Gohde <list....@gohde.no> wrote: > Hi, > I've got machines with Win 8.1 Pro at the moment and with the free upgrade > "deadline" approaching I'm thinking wether not not to take the plunge to > Win10 during the summer. > > My main concern apart from privacy issues is that given the fact that there > will now be continuous rolling windows upgrades that XSI will cease to > function one fine morning. Much the same way that some programs stop working > with MacOSX updates. And no-one will provide updates to fix that. > > I'm mostly happy with Win8.1+ClassicShell but the fact that M$ and Intel > want upcoming hardware to require new Windows is perhaps a reason to update. > I'm still looking to use XSi for another 3-5 years. > > Does anyone with more knowledge of Windows internals and XSI dependencies > have an opinion on the likelyhood of M$ messing with something that XSI > needs? > > Thank you, > Fabian > ------------------------------ Message: 2 Date: Mon, 14 Mar 2016 19:04:15 +0100 From: Fabian Schnuer Gohde <list....@gohde.no> Subject: polygon area sum for normalizing texel density To: softimage@listproc.autodesk.com Message-ID: <CABetkv6ZS3OS4=bigpczvfff4g2vhtxf_najl49r1olnxaa...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi, I'm setting up some texture baking and before re-inventing the wheel (and I'm running out of time on this project) I was wondering if there is a quick way (or if someone has a snippet of code) to quickly calculate the area of polygons in a mesh to set up the map resolution accordingly. Unwrapping will be via UniqueUVs. just need an even texel density accross all objects. Thank you, Fabian -------------- next part -------------- An HTML attachment was scrubbed... URL: http://listproc.autodesk.com/pipermail/softimage/attachments/20160314/ace49b9a/attachment.html ------------------------------ _______________________________________________ Softimage mailing list Softimage@listproc.autodesk.com http://listproc.autodesk.com/mailman/listinfo/softimage End of Softimage Digest, Vol 88, Issue 56 ***************************************** ------ Softimage Mailing List. To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.