[Goober5000]

So just do
when
--is-key-pressed
----ESC
--unset-cutscene-bars
--[clean-up-cutscene-stuff]

ESC is a reserved key, though, so it should be tied to something else.  Maybe 'Q'.

[karajorma]

I think you missed the point Goober.  What I meant is that when the mission is supposed to start a cinematic scene it would be nice if the black bars slowly slide in and out of view like in homeworld (which from his post appears to be how WMC has implemented it) but when the user wants to skip out of a cutscene the black bars should dissappear instantly rather than slowly retracting.

Oh and you can't use Q either. That's the equalise shields button

[Goober5000]

I don't think you understand.  If the key is going to be tied to the key-pressed sexp, it has to be one of the keys recognized by the game.  ESC doesn't work because it shows the "Quit Mission" screen.  I thought of Spacebar, but that fires missiles.  Q for Quit (or perhaps S for Skip) are the least-invasive of any of the key-pressed keys that could be plausibly used.  (Unless you want to say "To skip this cutscene, press '1'".)

[WMCoolmon]

New stuff:

fade-out
-- milliseconds to fade out
-- color to fade out to(Implemented but not working properly, may need lowlevel function editing)

fade-in
-- milliseconds to fade in

[karajorma]

Originally posted by Goober5000
I don't think you understand.  If the key is going to be tied to the key-pressed sexp, it has to be one of the keys recognized by the game.  ESC doesn't work because it shows the "Quit Mission" screen.  I thought of Spacebar, but that fires missiles.  Q for Quit (or perhaps S for Skip) are the least-invasive of any of the key-pressed keys that could be plausibly used.  (Unless you want to say "To skip this cutscene, press '1'".)

Ah. Fair enough. I suppose Q isn't bad. 1 would be a bad choice cause a lot of people use that for other things. Can't think of too many times when a player wouldn't want to equalise his shields straight after a cutscene

[WMCoolmon]

Planned camera stuff (Partially implemented):

set-camera-position
-- x point
-- y point
-- z point

set-camera-facing
-- x point
-- y point
-- z point

set-camera-rotation
-- x degrees
-- y degrees
-- z degrees

set-camera-facing-object
-- object name

(Not implemented)
setting-text
-- text
-- lines from bottom of screen

This would draw out text for giving a setting or time 1 letter at a time, as is done in many movies (I think it's done in Apollo 13)

Edit: Goob, are SEXPs calculated before game_render_frame_setup? That's where (ideally) the camera movement code would go. If not, where are they called from in game_frame?

[Trivial Psychic]

Originally posted by WMCoolmon
set-camera-rotation
-- x degrees
-- y degrees
-- z degrees

Would this basically constitute a pan?  Do you plan on adding a time factor so you can adjust the pan rate?  If this is pan, why to you have x, y, & z?  A vector only requires 2 variables.  Am I wrong on my assumption that this is a pan function?

[WMCoolmon]

No; I'm not quite sure how I'll do pans yet, but that would be a change on the y axis. Hopefully I'll be able to peg an optional variable onto the end of the set-camera-* sexps, which will be the time it takes to complete whatever you asked it to do.

So, to do a pan 45 degrees to the left, you'd say something like:
set-camera-rotation
-- 0
-- 45
-- 0
-- 5000

With the two 0s being replaced by the current camera x and z rotations.

Another possibility would be change-camera-rotation, which would rotate the camera from its current position by however many degrees you specify (relative rather than absolute, in other words).

[Flaser]

Originally posted by Trivial Psychic


Would this basically constitute a pan?  Do you plan on adding a time factor so you can adjust the pan rate?  If this is pan, why to you have x, y, & z?  A vector only requires 2 variables.  Am I wrong on my assumption that this is a pan function?

A two dimensional vector takes 2 arguments - 3D takes 3.
Though if you used polar cordinates then you'd need a radius, an azimuth and iclination angle. If we make all vectors a "unit" long than you can get away with only 2 angles.

[phreak]

i think a good idea for a pan is to have the cam_x, cam_y, and cam_z values stored as variables in fred, then use an every-time sexp to move it:

Code: [Select]


 everytime
  =
   
   1
  set-camera-pos
   
   
   
  modify_variable
 
   +
   
   
etc.


tweak dx,dy,dz as necessary

[Goober5000]

Originally posted by WMCoolmon
Edit: Goob, are SEXPs calculated before game_render_frame_setup? That's where (ideally) the camera movement code would go. If not, where are they called from in game_frame?

Yep.  Immediately before, practically.  Here's the game_frame excerpt:

Code: [Select]


[b]game_simulation_frame(); [/b]

// if not actually in a game play state, then return.  This condition could only be true in
// a multiplayer game.
if (!actually_playing ) {
Assert( Game_mode & GM_MULTIPLAYER );
return;
}

}

if (!Pre_player_entry) {
if (! (Game_mode & GM_STANDALONE_SERVER)) {
clear_time1 = timer_get_fixed_seconds();
// clear the screen to black
gr_reset_clip();
if ( (Game_detail_flags & DETAIL_FLAG_CLEAR) ) {
gr_clear();
}

clear_time2 = timer_get_fixed_seconds();
render3_time1 = timer_get_fixed_seconds();
[b]game_render_frame_setup(&eye_pos, &eye_orient);[/b]
game_render_frame( &eye_pos, &eye_orient );The sexp stuff (among other things) is handled in game_simulation_frame().

[WMCoolmon]

Awesome. Thanks Goob.

Now implemented, the stuff I said in the first post. No gradual movement SEXPs yet, unfortunately.

http://www.hard-light.net/forums/index.php/topic,29763.msg607952.html#msg607952

[Lynx]

What about subtitles? Are they possible there?

[WMCoolmon]

show-subtitle
-- subtitle text
-- image/animation to display to left of text (optional; default is none)
-- fade in time (optional; default is 0)
-- text redness (optional; default is 255)
-- text greenness (optional; default is 255)
-- text blueness (optional; default is 255)
-- text alpha (optional; default is 255)
-- x position (optional; default is centered)
-- y position (optional; default is at the bottom of the screen)

clear-subtitle
-- fade out time (optional; default is 0)

Would that be good?

[Lynx]

Better than I've ever hoped:D

[WMCoolmon]

*goes off to implement it*

[Cobra]

this sounds great for Willy_principal's "Battle of Beta Aquilae" demo.

now, make a new D3D version of FRED2 3.6.5 and i could have some fun with it.