Problems moving from one snapped shot to another

[treehaus1]

Hallo Folks,

am having trouble moving from one snapped shot to the next when I have the beam splitter camera active. This only happens when changing from shots stored both on the SAME, 50ft by 50ft SET (Interior). What happens is the camera appears in the right position on the flooplan, but the green camera axes lines and the blue sp line are those from the PREVIOUS camera position. The camera preview window labeled beam splitter also shows the view from the PREVIOUS camera position. (Theres a coupla screenshots here, so you can see what I mean....)

The only workaround I have found is to make plan view active and to delete the bem splitter camera from the set, then to UNDO delete, replacing the camera, which them refreshes the correct view in the camera preview window.

Is may grafic card not good enough?

I am running FF3.0.3.2 (3D) on my iMac 2.4GHz Intel Core 2 Duo, 4GB 800MHz Memory, OS X 10.5.8, ATI Radeon HD 2400.

Best,

Simon Sieverts

[jamesw]

My guess is that this is more likely to be a FrameForge bug than a graphic card problem. It would help us to replicate the problem if you could upload a file in which it happens. You might want to make a copy of the file and delete and purge irrelevant shots and sets, to reduce the size of the file to be uploaded.

By the way, the current Mac version is 3.0.3.3, but I don't think any of the latest changes would be relevant.

[jamesw]

P.S. If you do upload a file, post again and tell us the name of the file.

[treehaus1]

Hi,

I uploaded. The name of the file is Test_Bar_Ab_8mm.previz

Best,

Simon

[jamesw]

Thanks. I will try to fix it next week (right now we are closed for the U.S. Thanksgiving holiday). It would be a little easier to work with this file if you could provide the missing objects in "00 FEKO Modelle Kopie" and textures in "00 FÉKO Textures".

[treehaus1]

Hallo,

yes, both files are now on your ftp server, named

00 FEKO Modelle Kopie.zip
and
00 FÉKO Textures.zip


Best,

Simon Sieverts

[jamesw]

An update to Mac version 3.0.3.6 is now available. Please get that update and let me know if that fixes the problem being discussed here.