Announcement

Collapse
No announcement yet.

mascript and VrayPhysCam

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • mascript and VrayPhysCam

    If you assign a target object with the code:

    a = $vrayphyscam01.target

    b = box()
    b.target = a

    if you play with the "targeted" setting on the modifier panel the object may disappear. Worse though, on toggling the setting, the physcam will generate targets at the target distance which are not the real target. If you move the camera about you will get a trail of targetobjects. Moving the targetobjects has no effect on the camera.

    The camera will eventually crash as will vray. Max remains ok. If you delete the camera before vray crashes you can get things back, but eventually Vray will give an error something like:
    "you must have a valid object selected"

    if you save the file after this warning, the file now contains the brain dead camera and will not render. It will load, but not render. You can merge objects from it though

    Probably bad programming on my part as the MAXSCRIPT manual specifically warns against using this to target objects (Though every light or controller has this particular rotation controller as part of its animation stack).

    Still trying to work out how to set a lookat_controller with a script generated look_at object

    Raj
Working...
X