CompuServe Messages

Bruce, You have some good points about the "ironclad boilerplate" that Autodesk has on not discussing future projects, and inconsistencies with that. Here in the Product Support department, we must adhere to that rule without fail. "Autodesk does not talk about future …." is the policy of the company, and we follow that policy strictly. The problem is, not all other people follow that policy as strictly as Product Support does. This is not under our control, and it does, as you point out, occassionally lead to inconsistencies. It is these inconsistencies we are actually trying to avoid. If everyone followed the policy to the letter, they would not exist. But you are right, that would definitely make the company appear less human. Bottom line: Jonas, Nik, myself, and anyone else who logs in from Product Support will adhere to the non-discussion policy as strictly as we can. Others may be a little looser with information, but that is not under our control. -Brian P.S. Re: SGI. As this is a joint project with SGI and ourselves, we announced the intent to develop a joint product. Specific details still fall under the non-discussion rule. P.P.S. Re: AASTUDIO. ye, we appear to be discussing that heavily. This is because it was recently previewed at two trade shows, and has been in the public eye. We are only discussion things that have been previously made public at those trade shows. P.P.P.S <<The " Autodesk doesn't discuss . . . " corporate boilerplate you tag on to some of these replies is begining to sound kinda cold and fake. A simple "i don't know" or "i can't say" would be a lot warmer, and honest .>><< I had hoped it would inspire Jonas and company to respond to stuff they couldn't talk about with a more humane and conversational face and tone>> You are right, it is a boilerplate answer. If you can think of a nicer way to say the same thing, I am open for discussions. I at least always try to start with " I am sorry, but…". In the end, though, it is the same result. the person does not get an answer. (And if I said "I don't know", as you suggested, I would probably be lying.) -Brian