CompuServe Messages

Greetings! Hey, I got a 😉 out of you that time! I'm happy. I like to find from time to time that we're not bugging the heck out of you! As far as I can tell, LenzFX is the only IXP (or at least the only one I know anything about) that uses LIGHT location in 3DS.LOC as opposed to OBJECT location or image processing techniques (contrast edging, thresholding, et cetera). Thus, running the check with Disk #1 doesn't get us anything (they work just fine…) since those routines use I-P or object location info. I guess I was asking if you (Autodesk) had a general interest in nailing down whether the problem exists in LenzFX, Flame & Vapor, or in Studio 4 – with the implied larger question being: 'If it is a bug in Studio 4, is it going to get fixed?' I know y'all plan on a gradual transition, but I also know that things like the DS64PCI inviso-face-select bug aren't gonna get fixed because they'd require not only new Vibrant files, but an R4c3 as well. Thus, while it would be helpful to us to have information relating to global procedural faces + light location, it is not really important to us – from a product support point of view – unless the workaround DOES eventually change. Given that possibility, it would be worthwhile to suggest to the boss that she gin up the test IXP in case it's a Studio thing, in the hopes it'll get patched BEFORE it becomes an issue for our customers as well. I'm not trying to say that it is a Studio bug, just that IF it is, and IF it's important to you, than it would become important to us for find out. Am I making sense? Of course, another factor is that LenzFX 2 is due in a matter of weeks, and it may be educational to see if it does the same thing. Thanks for the suggestions… -Eric