Has anyone started working with the beta fix for Vue 4 Pro (update 266918)?

I have tried the update and it seems to have fixed several of the problems I was having. So far so good, but I have only tried it for one day.

I think I'll wait a bit and see if folks here have comments about it. I have the first update to Pro, and it has helped with some issues I was having.

Hmmm, gotta go see. Sharen

Shari,
I don't understand how you even got started. As soon as I start the patched Vue Pro up, the first layer is already locked. I cannot unlock it and cannot do anything.

So I had the extreme pleasure of uninstalling Vue Pro so that I could roll back to the first fix since the 'Cancel last update' did not work either. Just for fun, I tried installing it again, with the same results.

david

I tried The beta and really find it extra: The program is speedier, Mouse doesn't get captured by bottom slider of render window, textures on meshes can at last be resized so Vue4 scenes with mapped textures on meshes are all right now... etc... many improvments BTW davidryuen don't take notice of locked icons on obj browser : they are all mixed up: Locked icon:= visible hidden icon := locked hide from render icon := hidden Cheers Paul

With new upgrade I have finally got my plants to load. :o)

Yippee!!! my extra plants Work !!!!!! Haven't tired anything else but the plant thing was driving me nuts!

Well, it fixed a glitch I found in the plants after a couple of days; the textures would load, but couldn't be 'read'. I tried a test Cow render, and the app bombed. However, I didn't do a reboot before I tried the render, so that may have had something to do with it. Give it another spin tomorrow when I'm awake...

I had the rendercow to crash at end of a render also. :o(

I played with the update and found it fixed the problem of a camera inside something. Before it wouldn't render a camera inside a covered wagon looking out. Now it does. I was also getting a lot of crashes before, so far ~touch wood~ it's seems stable.

Importing Walk cycles and applying the Mover Wizard "Pedestrian" setting during path creation seems to work properly now...except for the fact that my program died during rendering.

Either way- progress is being made and I'm quite happy I purchased Vue Pro + Mover.

Regards,
JB

I am consistently crashing while attempting to do a network render. I will probably have to roll back again since I can't afford to do single-machine renders. A 2-machine Rendercow setup (XP Pro local, XP home client) which used to work no longer works on a simple 4 second animation render. Has anyone gotten network rendering to work on animations? At all?

I've been using it, and it seems to be fairly stable... What I found out is that one of my renderboxes is acting flakey (it's the temperamental one, so I shouldn't be surprised), and it was what caused my Vue Pro to bomb. I did a 595 frame render today with 4 of the 5 cows running. What you may want to try is to start your animation render with just the rendercow on the system with Vue on it. Once it is doing frame 0, then add the next box, and wait until that one is rendering a frame to add another one, etc. The HyperVue manager is touchy, and with Vue Pro is seems to be even touchier to things like packet collision. That seems to be the problem when you try and start all the Cows at the same time. The main Cow seems fine, as the textures are already on the local drive, but shoving the textures across a network to multiple cows simultaneously does seem to lead to 'kaboom'. Letting each Cow get set up with the resources before activating another one seems to be the workaround.

Dale,
I wish I knew how you got 4 cows to render - I can't even get 1 running. I did as you said, started one cow rendering and kaboom! Can't even do a one cow render through the HyperVue manager. I tried both ways: starting with the Vue install machine and that crashed, then starting with the client machine and that crashed.

david

Hmmm... After you ran the 4.51 beta, did the program automatically run the patch on the Cows? Apparently, what Vue Pro does in an update is place a seperate .exe file in the main Vue folder, and when it detects that HyperVue is active, should automatically run the Cow version of the patch on each detected Cow. If it didn't, you will bomb every time, as it apparently does a version check to ensure compatibility. You can copy that Rendercow Update onto a CD or across the network manually and run the updater on each renderbox that way (and as this is a beta, I'm assuming that you are running the 4.1 official release first on everything. I don't know if these are cumulative patches or last one has all fixes, but I'd assume the former, just for safety's sake). I'd also get in the habit of saving each upgrade updater for the Cows in a seperate folder, just so you don't have to futz with the full patches anytime the rendergarden units get flakey. If Vue itself is running stable, then I would try uninstalling the ProCows completely, including digging out every trace of them in the registry, run something like Norton WinDoctor, to make sure there isn't something else in the system that is causing trouble (Vue Pro has a -lot- more connections to the OS than Vue does). Reinstall the Cow from the CD, then run each successive patch manually. Ah. Another idea. Do you have PaintShop Pro 8? PSP 8 has its own Python engine and setup, and I found that installing Vue and the Cows over PSP 8 -sometimes- does flakey things to the python runtimes. I had to uninstall PSP 8, clean up the registry, and reinstall it -after- I had Vue Pro and Cows in place. That was just from the release install, and I can't reproduce it consistently by any means, but an unstable Python environment =will= crash the Cows, usually when it starts texture loading, and occasionally will take VuePro down with it. Of course the Benelli 9mm, 36" baseball bat, and the array of computer tools I keep lying about in plain sight of my computers may have something to do with it, too.... ;P

Thanks for all the details. However, I discovered after rolling back that I'm still crashing Vue when I use the Hypervue Manager. So it's not beta patch related. Just another way to crash Vue that the beta patch didn't fix.