We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Ok, I Agree

Change params for cameras

Home › Forums › Bug Reports and Feature Requests › Change params for cameras

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • 2021-08-23 at 3:32 pm #43920
    NaxosCG
    Customer

    Hello,
    It would be nice to be able to change cameras parameters, like :
    – movable / fixed
    – change zoom factor (min & max) when the camera has been moved (zoomed or twinned to another location
    – fov
    – clipping…

    But most of it, the movable / fixed would help a lot :
    scenario : turn around an object, then click to focus / zoom to a detail, with fixed cam, then come back to main cam free to move.

    Once a good fellow explained me how to do that using fake cameras, and stuff, did not really get it. simply being able to set the current cam to “fixed”, then “free”, or to be able to change min / max rotations would be nice.

    Regards.

    "1+1=3... for large values of 1"

    2021-08-24 at 12:43 am #43934
    Avier3D
    Customer

    Hi,
    This has been requested before and some of it can be driven with puzzles, but I’m also on your boat.

    scenario : turn around an object, then click to focus / zoom to a detail, with fixed cam, then come back to main cam free to move.

    You can do this by placing locators on every set location, where your camera needs to be and where to look, and then also puzzle those state changes. It is sometimes not as smooth but still works well.

    But I agree that the UX tooling in regards camera is an area that defintiely will help users create better experiences.

    2021-08-24 at 3:11 pm #43962
    web
    Customer

    You can control pretty much when using javascript directly instead of the puzzles. Like that for example:

    appInstance.controls.enableZoom = true;
appInstance.controls.enablePan = true;
appInstance.controls.enableRotate = true;
appInstance.controls.minDistance = 10;
appInstance.controls.maxDistance = 700;
appInstance.controls.autoRotateSpeed = 0.5;
appInstance.controls.enableKeys = false;
    2021-08-25 at 9:21 am #43979
    NaxosCG
    Customer
    web wrote:

    You can control pretty much when using javascript directly instead of the puzzles. Like that for example:

    appInstance.controls.enableZoom = true;
appInstance.controls.enablePan = true;
appInstance.controls.enableRotate = true;
appInstance.controls.minDistance = 10;
appInstance.controls.maxDistance = 700;
appInstance.controls.autoRotateSpeed = 0.5;
appInstance.controls.enableKeys = false;

    Thanks, but as i’m more a graphist than a coder, i’d rather prefer verge3D to have camera-params puzzles, anyway i can give a try.
    Regards.

    "1+1=3... for large values of 1"

    2021-08-25 at 9:25 am #43980
    NaxosCG
    Customer

    I’ve tried to put “appInstance.controls.enableRotate = false;”, after camera zoom-in, it works as the camera can’t move anymore, nice.
    But then it seams that nothing can be clicked anymore, so i can’t click to zoom-out again…

    Attachments:
    You must be logged in to view attached files.

    "1+1=3... for large values of 1"

    2021-08-27 at 9:59 pm #44049
    jdhutchinson
    Customer

    Where is maxDistance in the documentation and API? I don’t see it anywhere?

    2021-09-09 at 3:00 pm #44469
    web
    Customer

    @NaxosCG
    Sry dont know why this bug is occuring. I had zero problems with it, but I’m also using no puzzles just pure javascript. But this shouldnt make a difference.


    @jdhutchinson
    I think there are many items missing in the documentation. But you can see the current settings when you just do a console.log(appInstance.controls)

    2021-09-09 at 5:06 pm #44477
    jdhutchinson
    Customer

    That’s true you can print currently instanced objects and stuff. But kinda need to be able to see the alternative methods and their correct names :wacko:

    I did get a reply from Ivan regarding dampingFactor for example, because the actual method name needed was a) different to the documentation and b) different to threejs too. So I didn’t really know how to derive the logic for getting the correct methodproperty name. I don’t if it just needs updating, or if it’s an enterprise feature to be able to know the right names of stuff?

    Maybe Yuri et. Al can shed some light on it.

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.