Announcements, requests and support regarding the 3DS MAX exporter
-
Jan
- Posts: 19
- Joined: Sun Jul 02, 2006 10:21 pm
Post
by Jan » Fri Feb 09, 2007 5:17 am
Hi all. It's time to implement the indigo camera in max, and there are some different ways to do it so...what do you think? Vote the best option
I have a question about this: what shutter speed value takes indigo camera? I don't understand at all how works without this parameter (or a rotary shutter like a videocamera).
PD: image for second option (integrated into standard camera parameters):
Thanks in advance
Alejandro
-
suvakas

- Posts: 2613
- Joined: Mon Sep 04, 2006 11:08 pm
- Location: Estonia
-
Contact:
Post
by suvakas » Fri Feb 09, 2007 5:27 am
Yes, I've been wondering about the shutter speed too.
At the moment there seems to be no tag to controll that. (I think U3dreal just used linear tone maping to emulate ISO and Exposure. Correct me if i'm wrong?)
About the camera. How do you intend to implement a separate or extended Camera using script? As far as i know, then you can't use scripted plugins on Target Cameras (neither you can't extend a target camera rollout via script). Agan - correct me if i'm wrong =)
Suvakas
-
Jan
- Posts: 19
- Joined: Sun Jul 02, 2006 10:21 pm
Post
by Jan » Fri Feb 09, 2007 6:03 am
I'm not sure of understand you. As I know, target cameras are extended as any other, but I dont had investigate too much about this for now (at least until the end of the poll

)
Example code (only creation, no parameters):
Code: Select all
plugin Camera Indicam
name:"Indicam"
classID:#(0x28da14cf, 0x669b3c72)
category:"Jan_test"
extends:TargetCamera replaceUI:true
(
tool create
(
on mousePoint click do
case click of
(
1: nodeTM.translation = gridpoint
2: #stop
)
)
)
Hope this helps
Alejandro
-----EDIT----------
Suvakas, you have all the reason. When i try to replace UI with my own rollout, original rollouts remain unaltered. Anyway, I will maintain the option, since i think that it's possible to override this with extended free camera with a dummy as target.
Regards
-
suvakas

- Posts: 2613
- Joined: Mon Sep 04, 2006 11:08 pm
- Location: Estonia
-
Contact:
Post
by suvakas » Fri Feb 09, 2007 7:12 am
Ok. Great if it works !
This is what i was talking about before.
[taken from Maxscript help file]:
Code: Select all
Current limitations prevent certain plug-ins from being extended, in particular those with custom creation managers. These include target lights and cameras and all the System plug-ins. You can tell if a plug-in is not extendable if your new rollouts do not appear.
Maby that goes for something else. I havn't tested it myself yet, so i dont 100% know what i'm talking about
Suvakas
-
Jan
- Posts: 19
- Joined: Sun Jul 02, 2006 10:21 pm
Post
by Jan » Fri Feb 09, 2007 7:22 am
Direct extend of targetcamera doesn't work. The dummy as target on a extended free camera is a solution. Anyway, I must say that my favorite is the added rollout in both (target and free), because in this way the user is free to decide if targetcamera or freecamera. We will see the poll result
Alejandro
-
suvakas

- Posts: 2613
- Joined: Mon Sep 04, 2006 11:08 pm
- Location: Estonia
-
Contact:
Post
by suvakas » Fri Feb 09, 2007 7:33 am
Gotcha!.
I was thinking about the similar thing a while back. That maby using dummy as a target for free camera works.
But i was too lazy and didn't investigate it any further.
Suvakas
-
Jan
- Posts: 19
- Joined: Sun Jul 02, 2006 10:21 pm
Post
by Jan » Fri Feb 09, 2007 10:17 am
Works for sure, because I did the investigation some time ago for maxwell converter, when the camera target couldn't be created from maxscript. I use a not-rendereable teapot instead
Alejandro
-
Jan
- Posts: 19
- Joined: Sun Jul 02, 2006 10:21 pm
Post
by Jan » Tue Feb 13, 2007 6:11 am
Suvakas, if you can take a look to you private messages
Thanks
Alejandro
Who is online
Users browsing this forum: No registered users and 8 guests