You probably mean that the constrained object rotates about the point-at axis when you move the target. This is some sort of gimbal lock problem. To fix it you can usually do the following:

1. Point the constrained object (your cube) at the target (your sphere).

1. Move each rotate dial of the constrained object. One of the rotate dials won't work, i.e. it doesn't rotate the constrained object.

1. Set the nonworking rotate dial to -90 or 90. This has no visible effect on the orientation of the constrained object (see step 2).

1. Move the target. The constrained object should now follow without rotating about the point-at axis. If the -90 degrees setting doesn't work, try the 90 degrees setting.
    

Quote - Hi VK,

Yep. I'm still in the Alps. Went for a 3-day hike to a refuge at 3,000m last week.

As Ronald MacDonald would say "I'm still lovin' it!" - lol

mac

Hi mac,

Sounds great. Although I prefer to see these rocks from afar. lol

Hi bagginsbill,

I quoted you for agreement --cropping indeed solves the problem of tilted buildings. The following just points out that the result of a rise view option looks different, and that this option is useful for a CG camera if you need exactly the look of a real view camera. The renders are from ElectricImage.

Hi mac,

Yes, hope you're fine. Are you still in the Alps?

Attached Link: camorbit.pz3

There was another hack for the orbit center problem: 

Just add a second set of "translate" channels at the end of the channels list of main camera (and aux camera). Be sure to change the channel names and dial names of the new channels. Now you can use the "Dolly" dials for standard pan, or the new dials for framing pan. The new channels will pan the view, too, but the camera will always orbit the center of the image frame (unless you also set the Dolly dials).

This used to work in Poser 4. The attached zip contains an old .pz3 demonstrating the new camera dials. I don't know if it works in newer versions, I stopped using Poser at version 4.

To use the new camera channels in new documents, I included them in the "preferredState" and in the "camerasAndLights" script, IIRC.

Quote - Problem solved. No more tilted buildings.

The Rise/Fall option of a CG camera is still useful. Although you can increase the camera distance of a CG camera, the cropped and resampled image will look different (see picture). Why? Modifying the camera distance also changes the perspective distortion of the object --unless you also modify the focal length, which in turn leads to a different field of view.

The Rise View option will pan the view and at the same time preserve the field of view and the perspective distortion of a real perspective correction lens or a view camera.

Attached Link: falling water

Modeled in modo and rendered in EIAS.

Attached Link: http://sourceforge.net/projects/arbaro

I used 8 Macs in 20 years, basically one of each processor generation (Macintosh Plus, SE/30, LC II, Performa 475, Power Macintosh 7500/100, G3 beige, G4 @400, iMac G5), with a grand total of 2 hardware failures (1 harddisk, 1 power supply) and repair costs of about 300 $. I still have all of them, except for the LC II. *This is prolly why MCSEs (of all skill levels) average about $40k while the nix admins (ditto) average $70K+ in salary... we can do 3x the work in less time, and don't require as much hardware muscle to get the same jobs done. Basically, you only need 1/3 the staff and 4/5ths the hardware budget to do the same job if the staff is competent. Very interesting. I guess the "Win PCs are less expensive" legend exists because many people (even IT pros) buy a computer like a can of beer: A smaller number on the price tag means a cheaper product.

i just love the fact that my pc is cheaper to repair and upgrade....nuff said Let's see: I switched in 1986 and I'm using my computer on a regular basis, i.e. several hours each day, mainly to make money. We have a hybrid environment in our office, about 10 Win PC, 1 Linux PC, and 1 Mac. The average administration overhead for a Win PC versus a Mac has been at least 20 minutes a week in the past 20 years. Most of the overhead is directly or indirectly caused by malware protection. I never wasted any time or money on any kind of malware protection for my Mac. Assuming an additional administration overhead of only 20 minutes a week for a Win PC makes in 20 years about 340 hours. I charge 200-400 bucks for my business hour and I'm my own sysadmin. The bottom line is: I saved around 100.000 $ because I've been using a Mac instead of a Win PC in the past 20 years. If I consider the superior hardware quality and backward compatibility of my Mac, the calculation gets even worse for the Win PC. Of course, your bottom line might look different, for example when money doesn't matter or when you're selling anti-virus software.

Obviously, some Windows users get what they deserve :evil grin:

Yes, most of the video tutorials on the Mac are made with SnapZ Pro.

I hope so, considering the price tag ;)

Quote: Before Poser overwites ball.pzz, it saves a temporary file called pzSav_ball.pzz and deletes that one behind the scenes after it writes the new ball.pzz file... Poser applies the usual "safe write" method to safe modifications of existing files: First, it renames the existing file (with prefix "pzSav_"), second it writes a new file with the original name to the disk, third it deletes the old pzSav_* file from the disk. If the write operation fails, the safe command sequence is aborted, and the pzSav_* file is not deleted. Thereofore, pzSav_* is always the last saved version of the file. And the new version of the file is always written to new sectors on the disk.