CompuServe Thread

Autodesk Software Forum · General

#IPAS questions, cont.

7 messages in this thread

#63207From: David C. ThompsonOct 25, 1993 3:21 AM

I haven't been getting any response from Autodesk on IPAS questions. I wonder if you can refer me to a specific person there. We are having a strange problem with R3 with an AXP. It works in any viewport in R2 but in a camera viewport in R3 we get no particles, any other viewport works. The program has start and end frame parameters and the camera viewport works up to that point. As soon as the start frame is reached, and the particles are triggered, nothing. Finally, is there any means of preventing particles from elongating in an AXP if the ratio of the bounding box sides are not 1:1:1?

#63219From: Nik Grant [adesk]Oct 25, 1993 8:26 AM

Support for IPAS questions breaks down into a couple of categories. If you've got IPAS developer questions, you're asking in the correct forum. Usually Jonas Riukus will answer them. He's new at Autodesk and is coming up to speed on developer issues exceptionally well, I think. If you've got a question about a specific purchased IPAS routine, then the developer of that routine offers support. In the case of the YOST Boutique (what a name!) then you can ask your IPAS questions here too. Jonas was ill last week but should be back soon…

#63292From: Jonas Ruikis [ADESK]Oct 25, 1993 3:37 PM

Hi David, Is this a routine that you've written? Jonas[ADESK]

#63298From: David C. ThompsonOct 25, 1993 4:44 PM

Hi Jonas, Yes, I wrote it. Any thoughts on the two probelms? DCT

#63481From: David C. ThompsonOct 26, 1993 1:25 PM

Here's a little more information about the AXP. First, the compiler I'm using is Watcom 9.01 Rev E. Applying Yost's ipasfix has no effect on the problem. Second, the problem only appears in 3DSr3 in a camera or spotlight viewport, no particles are rendered. They appear as expected in r2 in either viewport. Hope to hear from you soon.

#63486From: Yost GroupOct 26, 1993 1:31 PM

IPASFIX.EXE will only fix maxdata problems with the Watcom compiler. There are a slew of other problems that the Watcom can generate, and you're looking at one of them. My recommendation is to just bite the bullet and get HighC. It'll pay for itself in debugging time saved in the long run.

#63495From: David C. ThompsonOct 26, 1993 1:58 PM

I'm glad you answered. Guess you're right, time to bite the bullet. I didn't think the maxdata problem had any effect in this case but it was worth a try.