#Another Vapor ???
7 messages in this thread
I've got another Vapor.axp strangeness. I've setup a default axpbox (center
emitter), to simulate steam-like vapor coming out of a spaceship engine before
it fires. I render the animation on my P90 (128mb ram), it turns out ok. I
send the same critter to another P90 (128mb ram, same 3ds.set) over my
Lantastic 6.0 network and it renders the vapor at right angles (from the top
view) to the animation rendered on my P90. Have I forgotten some obscure, or
maybe obvious, network parameter?
If all is configured correctly, sending out a vapor animation to a network
ought to be completely transparent. Unfortunately, without spending some time
with your network (physically), I can't even begin to comment on what might be
happening.
– G
Gary,
This network has just undergone a major upgrade and I know I'm going to have to
go through it with a fine tooth comb. I'll keep plugging away. Thanks for
trying anyway.
Paul G
Paul, do you have seperate, discreet local process directories for each of your
slaves? If not, you might try that…
FWIW,
-Alan
Alan,
<<do you have seperate, discreet local process directories for each of your
slaves?>>
I do. I have also double checked my 3ds.set and 3dsnet.set files for all
machines. All the relevant parameters in both files are correct and
consistent. Also, I rendered the scene I was having trouble with on a P90
slave on a 486/DX266 with the same result. The P90 editing workstation gives
me the result I expect. I'm going check, recheck and test some more. Thanks.
Paul G
Whew, Paul, sounds like a wild one.
I think the next thing I would try is just the opposite: Force all slaves to
access one common directory for all processes (you might have to make them
read-only files to get this to work) and see if that makes any difference.
I hope you can find the problem.
Best of luck,
-Alan
Alan,
Will do. Sounds like a next logical step.
-Paul G