robcat2075

I like the "art" look of that lightning. It's not realistic lightning, it's like what you might see in a stop-mo film.

Per the viideo, You leave those 2 seconds unused ( and unrendered, for now) so that a camera transition from the last segment to yours may be fashioned. We dnt' know what that will be untila ll the segments are in and an order has been chosen. It may be necessary to drag each object timeline separately, let me know if that works.

For Pixelplucker, the answer is "no", it looks the same in every possible view and zoom, right? This is why I'm not sure what we're talking about. V15 doesn't have retopology. Are we talking about transparency while retopology is being used or just transparency in general?

Here's a test of an object with transparent materials at 100%, 75%, 50%, 25%, 0% It seems to be all correct in shaded realtime mode TransparencyTest01.prj transp.mov

It's a strange mental frame-of-mind. I understand it but can't really explain it in words. I think a lot of it has to do with "What the cool kids are doing." I've noticed a big thing in Maya circles is the "How to Cheat with Maya" books, as if there's some super-secret thing that's being revealed. I feel like saying "You don't have to 'cheat' in A:M, the right way is also the easy way", but that's not as much fun as a "secret".

32-bit is just a download away!

I'm confused. I thought the problem was related to using retopology? If not, why are talking about coplanar patches?

You can dull the highlight by making spec size much larger and intensity weaker Instead of using real reflection you could use a reflection map material with a blurred reflection image. This would also probably render faster, too. A similar tactic might do well for the copper surfaces also.

Other ideas... try the 32-bit version of A:M, try Direct3D instead of OpenGL.

Is that the only way the resplining tool works? Does the transparency work any different in other views like birdseye, or in perspective vs. flat?

Are you modeling that in a chor?

You can probably grab all the keys in the PWS and slide them.

OK. The perspective was ambiguous and I thought maybe it was on something but casting no shadow.

Is that thing being drilled sitting on the surface below it or floating above it?

Displacement maps can have trouble in animation. I've found that rendering larger and scaling the image down can help a lot. Is doing it as a bump map much less effective?

That looks quite fetching. The grass might scintillate less if you had jitter on.

Possibly you have another group that is overriding the transparency?

AO working Props with is a recently fixed bug. Cool nodular landscape Will!

Occasionally that will happen with a Windows browser too. Usually the save dialog tells you what file type it intends to save a file as and that is an opportunity to correct it from ".txt" to "all file types" which will save whatever the original file name had.

Good looking parts. I'd suggest some ease as the first few parts fly in instead of having them hit a wall. Lighting is rather flat for my taste.

If that's a highly reflective or clear surface you wouldn't see shadows anyway.

I just tried it in v17 64-bit and it does work. Mention that too.

I get a crash also in 32-bit A:M. AMReport it and note that it works OK in v16.

Are other Mac users having this trouble? AMReport it with a screen capture and then go back to a previous beta until it's resolved.