Create FStorm Camera from View

[Sylk]

Hi, Karba.

Please, can you add a "Create FStorm Camera From View" option into the max "Create" menu?

Nor by adding a button "Get View Settings" in command panel (visible in Create mode / hidden in Modify mode) when we create FStormCamera ; Press this button fill parameter fields with active view parameters. Then a button "Create" add FStormCamera into the scene.

Something like that:

"Create FSCamera" button actions:
- If no view position collected, then add camera at 0,0,0 in scene
- If no view direction collected, then add camera pointing to north (front view)
- All other settings are defined by the FStormCamera settings

I think it could be pretty convenient.


Thanks a lot for your amazing works. Luv FStorm!

[Iskánder ivp87]

This is what i get, see pic. And it's exactly what your code ask ( FStormCamera pos:[0,0,0] ), so no error (for me an error is an error message), just bad coding. Also your "try catch" use makes no sense, its structure is not really logical. And it doesn't create camera if the view is camera.

So no, your script doesn't work and does absolutly not what my script do.

Try my script, and read how the code is simple and logical. And universal.

Your bad is the use of try and the (macros.run "Lights and Cameras" "Camera_CreateFromView") command which not exist in 2017. Never use menu commands.
Then the try test stop code don't execute this command, don't move the camera and just return "Do not works in ortographics views"... I'm in perspective view

ha!! YOU SEE! That's the error I was talking about!!! haha thank you man, the two pc I tried are running on 2015, where it seams this command still works

as I'm not a programmer putting everything inside try catch is kind of a very quick way of doing things without crashing max/maxscript/the pc, no exaggerating here, when trying to create area lights I managed to blue-screen the PC not one but twice!

[Sylk]

This is what i get, see pic. And it's exactly what your code ask ( FStormCamera pos:[0,0,0] ), so no error (for me an error is an error message), just bad coding. Also your "try catch" use makes no sense, its structure is not really logical. And it doesn't create camera if the view is camera.

So no, your script doesn't work and does absolutly not what my script do.

Try my script, and read how the code is simple and logical. And universal.

Your bad is the use of try and the (macros.run "Lights and Cameras" "Camera_CreateFromView") command which not exist in 2017. Never use menu commands.
Then the try test stop code don't execute this command, don't move the camera and just return "Do not works in ortographics views"... I'm in perspective view

[Iskánder ivp87]

No error, just bad coding. If for you, create camera from view is just put a camera to origin in the scene then yes it works. But for me it means create/move a camera to the view position, orientation and fov of the current view in the selected viewport, and this is what my script do.
Try my script and see.

that's exactly what my script do, I don't get what are you missing, is easy look, this is what I'm telling you, "my script always create a camera from view port" if I it only created a camera in the origin I wouldn't be telling you (multiple times by the way) that it works! I would be telling you: "please help me make it work, because it do not works!!"

so if the only thing my script do in your case is to create a standard camera in the origin, (0,0,0 ??) there have to be some error/s

now could you help me to understand what could be happening that in my case it works fine, and in your case it only creates a camera in the origin? have you tried and saw that this is the behavior or just read the code?

[Sylk]

No error, just bad coding. If for you, create camera from view is just put a camera to origin in the scene then yes it works. But for me it means create/move a camera to the view position, orientation and fov of the current view in the selected viewport, and this is what my script do.
Try my script and see.

[Iskánder ivp87]

No error, just not work as expected, as i said you.

man but if it not work as expected to you, and it works as expected to me, and tested in two different computers, there have to be some error

leaving aside the concordance between the name or the ''category:"DragAndDrop"' thing, any time I use it, it creates an Fstorm Camera from View, if it doesn't do it in your case, is clear it should be some error or am I wrong?

[Sylk]

No error, just not work as expected, as i said you.

[Iskánder ivp87]

Just curious why one would need this script? Max has 'create camera from view' built in already.

best,
O

well the one I uploaded create an fstorm camera by selecting a standard one, I have tryed to make it crash and have test it in two different pcs and it works fine but it seams that it give some kind of error to Sylk

[Sylk]

Just curious why one would need this script? Max has 'create camera from view' built in already.

best,
O

Many People request this.
The build-in doesn't create FStormCamera.

Also my script allows place selected/create new camera from view even if view is a camera, not the build-in.

[Oliver De La Rama]

Just curious why one would need this script? Max has 'create camera from view' built in already.

best,
O

[Sylk]

Here is FStormCameraFromView v1.

[Sylk]

I didn't categorized, as drag and drop, 3d max put it that way automatically, maybe because I dropped the script int to a toolbar?

No... category:"DragAndDrop"

[Iskánder ivp87]

It seams to work, in which scenario it doesn't convert a selected camera or create an fstorm camera from a perspective viewport?

I'm trying to make it fail because better now than when you least expect it, for example the other days I did a script to do a couple of relax phases and conversion to quad mesh and some stuff, I had to change the topology of a bunch of very similar objects, but in some worked and in others not, I later learned all was cause some objects had an edit poly modifier applied, but in those moments you can't open the code and try to analyze and "discover" what's happening, so in (at least halve the objects) I had to do it all by hand, yeah! haha when you don't know better it doesn't get that bad

[Iskánder ivp87]

No, the camera not placed from view. I did mine, more simple, proper and works in all cases. I'll share it later

About file, no reason to categorize it as DragAndDrop. I assume you based on the ThreeMarks' script but you must adapt this to script goal.

I didn't categorized, as drag and drop, 3d max put it that way automatically, maybe because I dropped the script int to a toolbar? any way do you know what could be happening, I just put it in another pc I use to vray net rendering, and it works fine too

what error does it gives to you?

[Sylk]

did I up load an incorrect file?

macroScript Macro15
category:"DragAndDrop"
toolTip:"Creating FStormCamera From View"

if it's not this tell me, I test it right now and it worked fine, all the options, to create a camera from view you have to be in a perspective view, not in an orthographic one

No, the camera not placed from view. I did mine, more simple, proper and works in all cases. I'll share it later

About file, no reason to categorize it as DragAndDrop. I assume you based on the ThreeMarks' script but you must adapt this to script goal.