Subject:
|
Re: Multiple instances of CAMERA.DAT and LOOK_AT.DAT
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Fri, 5 Dec 2008 19:42:11 GMT
|
Viewed:
|
6270 times
|
| |
|
|
In lugnet.cad, Michael Horvath wrote:
> L3PAO currently supports CAMERA.DAT and LOOK_AT.DAT for determining camera
> information. I'd like to see more programs support them.
>
> However, I'm wondering how best to handle cases where multiple sets of the files
> are defined? There's no way I know of at the moment to syntactically pair them
> into groups. One option might be to hide the ones that are inactive. Another
> option might be to make it necessary to store them in separate submodels, and
> then activate one of the submodels depending on which pair you want to use.
>
> What are your opinions?
If there were a real camera dat file that included facing information,
look_at.dat would then be unnecessary, and the pairing problem would go away.
--Travis
|
|
Message has 1 Reply:
 | | Re: Multiple instances of CAMERA.DAT and LOOK_AT.DAT
|
| (...) Knowing where the look_at point is actually located is necessary with certain camera types and if you want to do things like add focal blur. Also, it would be needlessly difficult for users to have to try and calculate the proper rotation (...) (16 years ago, 7-Dec-08, to lugnet.cad)
|
Message is in Reply To:
| | Multiple instances of CAMERA.DAT and LOOK_AT.DAT
|
| L3PAO currently supports CAMERA.DAT and LOOK_AT.DAT for determining camera information. I'd like to see more programs support them. However, I'm wondering how best to handle cases where multiple sets of the files are defined? There's no way I know (...) (16 years ago, 5-Dec-08, to lugnet.cad)
|
3 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
