Jump to content
  • 1
Sign in to follow this  
zoomer

RW Cameras

Question

Cameras are still not working for me in 2017.
Can we recap that issue a bit from scratch to get information and find solutions ?

I try to sum up.

Cameras worked for me fairly well in VW 2014-2015 :
They worked fine even on Layers assigned to Story Heights.
I could do Screenshots nearly full view window, by using "crop frame"
Just 2 Problems occurred for me :
1.
Sometimes, geometry far behind (!) the camera had the potential that a camera view showed no more
lights when rendering, until that geometry was set to invisible.
2.
If a Z-value was assigned to camera (in OIP), like I tried in a Staircase, the camera tend to shift its position
arbitrarily. A known Bug.


VW 2016 :
Cameras got some new features.
We can create, save and assign all features to Cameras.
Maybe no problems if assigned to Viewports (?)
But we can't securely switch between these in drawing Window. In that case at one time :

1.
Cameras lost their Positions always, no matter if there was a Z-value assigned, a Story height or not.
New XYZ locations values where for either selective or all Axes :
nearly infinite like 1,00000000ß0000e200, origin 0,0,0 or the XYZ of another camera.
2.
Camera and Target height for me sometimes change from mostly 1,60 m to 1,599999 or even more
deviate values.
3.
Camera Aspect Ratio Borders (the blue corners) only use a small part of the view Window of my monitor
(about a third of the width) so no more sufficient resolution for screenshots.

I think one or all following points came with different following releases of Service Packs
4.
Activation Icons in Camera Lister at one point won't disappear again, the whole de/activation process
was killed from that point, even in OIP or Camera Settings, until VW restart.
Over time more and more Cameras will reach that state.
5.
Cameras started to arbitrarily activate the old "crop view" in file settings, which is totally unwanted for
standard 3D Views which will be effected too.
6.
Cameras started to switch to a Top Plan orthogonal View inside that old "view crop" when activated for the first time.
An UNDO brought the original Camera back some times and old "view crop" was deactivated again.
7.
And last behavior change I noted, Cameras behaved like Saved Views and allways changed Layer Visibility
by making their own Layer the Active Layer.
Trying to switch back to the former Active Layer made them go nuts.

 

VW 2017 :

I did not test so much so far.
For 2016 files converted using cameras already :

1.
Cameras lost sometime their Position when only activated.
2.
Cameras show even smaller area with blue corners when activated for the first time, while the perspective looks
reasonable though. After switching between Camers the blue corners switch back to Camera Aspect Ratio in a
 ⅓ of View Window only size as usual for me.
3.
Cameras active switch to a Top Plan orthogonal Perspective in View Window when I only activate the visibility
of their Class to be able to edit.
4.
Crop Frame Scale Editing inlfuences blue corners first, when switching back to 100% it has changed Focal Length (!?) 


That makes it a little difficult to convert running Projects into VW 2017 if I relay on the old Cameras:
(Same for Reflectance Channel Changes)


Creating Cameras in an empty File without using any File Templates works so far in first tests for me.
But I have not yet changed any of the cameras settings or moer than one Camera at one time that I would usually
need to do.
 

Edited by zoomer

Share this post


Link to post

6 answers to this question

Recommended Posts

  • 0

Please do not combine requests like this in the future. Existing ones are fine, but separate threads for each request is how we want to handle things going forward.

Share this post


Link to post
  • 0

I would also add to 2017, your #5 from 2016 - the conflict between a camera's crop and real VP crop - as this is still happening in 2017.

57 minutes ago, zoomer said:

Cameras started to arbitrarily activate the old "crop view" in file settings, which is totally unwanted for
standard 3D Views which will be effected too.

 

Edited by rDesign

Share this post


Link to post
  • 0

yes, I am not sure what's happening.
Do the blue corners just show the wrong area of the final image when being so tight on a large drawing window,
or do they show reall are and aspect ratio just that small ....

My first attempt in a clean 2017 file, when activating a fresh Camera for the first time, was the blue corners
appeared in Thumbnail Size on my Screen. I couldn't reproduce that for now anymore.
and a "Fit To Objects" will destroy you perspective when Camera activated  ?

Share this post


Link to post
  • 0

Jim, the requests have been already in created in many threads,
this Thread is thought as trouble shooting and I'm looking for some information
So I just listed what my trouble is.

- Information of how these Cameras are designed and meant to work with.
- What Cameras can do and/or where I do things not intended to do with these.
- If I am the only one, or others have the same problems too
- If there are things working different as designed, known and accepted as bugs that will be solved
at one time if there is any solution possible.
- And of course help to track things down.


Since beginning of VW 2016 I posted all issues with Cameras. Some may sound a bit grumpy, sorry for that.
But the last Info I got was in late 2015 that there is a bug with Cameras used on a Layer with Z-height.

Even a "we don't see any problems with cameras" would be a useful information.

 

Since we have powerful Export Options to C4D and FBX,
problems of Cameras or no comfortable way to save renders have a much lower priority.
But I still want to know if current state is just temporary, if there is anything I can do or
if I should better not use them at all.

 

Edited by zoomer

Share this post


Link to post
  • 0

Sorry, have to activate that again.

 

I saw that nice video and so tried to use Cameras as they were meant to be used,

by converting these to Viewports :

 

 

Realized this isn't bad.

As you can crank up DPI for OpenGL Mode to get finer HL, even for screenshots only, with their lower final resolution.

Also comfortable to manage visibility versions and render modes.

 

The problem is that this way (VP's),

Cameras are no more available for C4D Exports.

I now get the unwanted "edge calculation".
I can't publish Viewports selectively.

 

But most important, Cameras also loose their Positions in VP's.

As I have to go in Camera Modes to change Expsoure Settings for my VP Render,

from time to time a Camera jumps to an arbitrary position.

And against DL Cameras, there is no Undo.

 

(Clean new 2017 Cameras in a File converted from 2016. Also I use Custom Crop Frames which I move if necessary)

Share this post


Link to post
  • 0

VW 2019

 

1.
Cameras lost their Positions always, no matter if there was a Z-value assigned, a Story height or not.
New XYZ locations values where for either selective or all Axes :
nearly infinite like 1,00000000ß0000e200, origin 0,0,0 or the XYZ of another camera.
2.
Camera and Target height for me sometimes change from mostly 1,60 m to 1,599999 or even more
deviate values.
3.
Camera Aspect Ratio Borders (the blue corners) only use a small part of the view Window of my monitor
(about a third of the width) so no more sufficient resolution for screenshots.

 

 

Cameras still go crazy in their settings and they lose their positions

as they started to do in VW 2016

 

(Although, so far I was not able to provoke the "Active Camera" indicator

in Camera List to appear at more than 1 Camera at a time)

Edited by zoomer

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×
×
  • Create New...