Forum Moderators: wheatpenny, TheBryster
Vue F.A.Q (Last Updated: 2025 Jan 24 7:34 pm)
Okay. (1) The ones that do have Vue on them also have the rendercow, I hope? Vue itself will not function in that capacity, unless each iteration on the network has a different liscence and registration number (if I'm remembering correctly; it may be that Vue only functions as the network controller for the rendercow(s) ). (2)There needs to be a rendercow installed on the host, as Vue can't render when it is controlling a network. If the actual installs are correct, the next thing to try is to add the undetected boxes by -name-. Find out what they are named as in the network environment, and add them one at a time. If that fails, then look at any antivirus and firewall software you are running. XP has it's own, and may be blocking port 5000 by default. Those are the most common 'ooops' with the HyperVue setup. Beyond that, and it gets more technical...
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
Thought I would now have a go at animation with Vue. Have my 'Lonely planet' rendering now but having a problem setting up Rendercow. Half my computers don't seem to detect from HyperVue. Things that I have noticed are: 1. The ones that work straight away don't have Vue installed on them. 2. The ones that fail will not detect on the port 5000 setting. HyperVue will sit there forever with 'Scaning...'. I have to kill Vue to exit. If I change the port, it finds the PC straight away but doesn't add it to the list. Specs: All XP, All P4s. Thanks, Sacada.