Jump to content
🛡️FORUMS ARE IN READ-ONLY MODE Read more... ×
Sign in to follow this  
Dark-Knight-Dragon

Camera Planning help

Recommended Posts

Greetings,

Well I kinda already asked the question in the Title and Description. But to make it clear. I already understand the basis of camera scripting with OFP. But I do not understand how to make the scene appear when the camera is aimed at the scene. If I still need to clarify the question just ask. I'll then just try to explain what I want to do exactly biggrin_o.gif.

Greetings, Dark Knight Dragon

Share this post


Link to post
Share on other sites

Do it the other way around.    Create your scene first.    Use camera.sqs to watch it (read messiah's tute over at www.OFPEC.com if you're not familiar with it) and obviously have an eye to the shots you're going to use, but get the whole thing up and running first.  

When you're happy with the scene, start shooting it.    Use camera.sqs and Blanco's logiccam script (also at OFPEC) to get the shots you want.   Use variables to communicate between the action on the ground and the camera script to keep things coordinated.  

For example you might have a chopper flying from A to B.   Place a trigger over area C, somewhere in the middle.  The trigger detects chopper present (group the trigger to the chopper) and when the trigger is fired it sets a variable to true.

The camera script, meanwhile, is sitting on a

@myVariable

command, waiting for the chopper.  

Use time delays to get the basic timings right by all means, but the not for shots where timing is critical.

Share this post


Link to post
Share on other sites

Read my camera scripting tutorial.

Quote[/b] ]

I have seen many horrible camera scripting tutorials out there. Some that are just plain confusing,

and some that take too much time.

I assure you, after you read this, you WILL be scripting cameras like you never have before.

Well, for beginners at least.

OK, lets et started.

------------------------------------------------------------------------------------------

----------------------------

-The very first thing we need to do, is go inside the editor, and open up ANY map of your choosing.

-Now what we want to do is create a unit, and place him anywhere you want on the map.

-In the units "Init" field, type in

this exec "camera.sqs"

-click on preview (trust me "camera.sqs" is a BUILT IN camera tool in the OFP Mission editor)

-You should see crosshairs, and you should be able to move around and stuff.

The buttons are simple. Q and Z is to move up and down, and the arrows are to move forward,

and the numbers to the right side of your keyboard do even more USEFUL movements.

OK good, we now understand how to access the built in camera mode in the editor.

Now, to start scripting.

-First, If you want, focus the camera on your unit.

-Press the Ctrl button ONCE. What this will do, is it will copy ALL the COORDINATES of your camera

setup,and will create a handy dandy file in your OFP directory.

-Now move the camera elsewhere, press the Ctrl button again.

Good Good. Say we want the camera to MOVE from one point to the other, this is so simple,

You are going to laugh.

-First of all, save your map as......cameratest or something.

-Alt+Tab OUT of OFP and look for something called CLIPBOARD

it can be found HERE-- C:\Program Files\OperationFlashpoint--

-Look for a TEXT document name CLIPBOARD

-Open it up

-DING DING! WE HAVE A WINNER! CONGRATULATIONS!

Now leave all of that be for now.

There is a common error that I have found. BEFORE you copy paste these camera movements ANYWHERE,

you need a specific TEXT document. This happens depending on what file you use to look at stuff.

The "OPEN WITH" option is what I'm talking about.

EXAMPLE: Notepad, Wordpad, Textpad, or whatever.

MAKE SURE YOU USE THE CORRECT TEXT DOCUMENT TO MAKE YOUR SQS FILE!

OK, now lets go to OFP/USERS/MISSIONS/YOUR MISSION and open that mission up.

CREATE a new text document, and name it "thecamera.sqs."

Now, before you copy paste all the camera coordinates, there is something

you ALWAYS NEED before you use the clipboard.

This is VERY important, and can be often forgotten many times.

I would hope you copy paste this line somewhere for safe keeping.

titlecut ["","black in",10]

_camera = "camera" camcreate [0,0,0]

_camera cameraeffect ["internal","back"]

that ENTIRE line, keep somewhere safe. At the beginning of ANY camera scripts file,

you WILL need that.

Now open up "thecamera.sqs" and copy paste

titlecut ["","black in",10]

_camera = "camera" camcreate [0,0,0]

_camera cameraeffect ["internal","back"]

at the very top. This can only be placed at the TOP of ANY CAMERA SCRIPT

Now, open up your CLIPBOARD and copy paste all that random crap in your "thecamera.sqs"

OK, all set. The camera SCRIPT is now in your mission directory.

Now we need to tell the editor.

Save your camera script, and go back to the editor.

In the PLAYER init field, type in,

this exec "thecamera.sqs"

Now, it is not done yet.

One more thing, and you are home free.

Look at this line,

;=== 13:47:55

_camera camSetTarget [9861.44,103973.64,27.16]

_camera camSetPos [9861.44,3973.64,2.00]

_camera camSetFOV 0.700

_camera camCommit 0

@camCommitted _camera

look familiar?

Open up your "thecamera.sqs" file ONCE MORE,

and change the

_camera camCommit 0

to

_camera camCommit 5

what the 5 does, it will take the camera 5 seconds, to move from one camera,

to the other camera.

NOW YOU ARE DONE!!!!!!!

YOU CAN NOW SCRIPT CAMERAS!

Experiment a little. You might learn stuff I havent found yet.

Preview your mission, and watch your camera move SCRIPTED STYLE!

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×