[Video Tutorial] Mission Director Basics

[killerog]

Very good idea Ketraar, and very nice of you to take the time to do it. Should be a good refresher for me when I come back to AP modding with out me having to nag you every 5mins

[Alan Phipps]

Thank you also, MD coding was always a complete mystery to me before. I think this thread already deserves a big mention in the Tutorials and Resources listings and even a place as a forum Sticky.

[Ketraar]

Thanks for the feedback

@Alan
You mean you want to hide this topic by making it a sticky?


But yeah, it should be listed in Tutorials, I'll poke a S&M Mod next time I'll catch one.

Ok so next vid will be about cue structure. As in use of parent/child cue (aka sub-cue), their priority, maybe how to cancel and rest cue, respectively what happens when you do. Might be some stuff on the side as usual

MFG

Ketraar

[EmperorJon]

To clarify on apricotslice's part; subroutines = functions, procedures, code reusability, parameter passing, etc.

Anyway, very nice tutorials!

[kurush]

Very nice! I noticed that you use some cheat sheet with {player.name} and other variables that are available in MD. Is it something you can give us a link for?

[Ketraar]

You can extract the director files (that one included) from the catalogue files (cat/dat) using doubleshadows X3Editor 2. mentioned it at the very beginning of the 1st video.

MFG

Ketraar

[kurush]

You can extract the director files (that one included) from the catalogue files (cat/dat) using doubleshadows X3Editor 2. mentioned it at the very beginning of the 1st video.

I actually did, just missed that particular file And of course I thought I can skip the first part of the video Thanks for the tutorial! I can't believe I wrote some MD code without that reference,

[Ketraar]

One more Tutorial uploaded.

Things addressed in this one are, cue structure, do_if, do_choose and variable usage, among some generic coding stuff.

This one is a bit more advanced than the previous ones, in case some things are not clear, please let me know.

MFG

Ketraar

PS.: The files I'm using in the tutorials are for AP but the procedure apply to TC as well, just that AP has some more commands and variables to use.

[LordGaara]

OT:
Ok, I can't stand it anymore.. seriously..

What is MFG, Ketraar?!

ICG
Martin

[Ketraar]

Mit Freundlichen Grüssen (with kind regards in German)

MFG

Ketraar

[Argonaught.]

Have watched all vids now, really appreciate the time your taking to make them


Argo.

[Ketraar]

My pleasure.

Though would be good to have feedback as to if they are of any help and somewhat understandable. Cant really improve if I don't know what I'm doing wrong or what can be done better. So let me know.

MFG

Ketraar

[Argonaught.]

Sp far it's all been pretty good, explanations are all good also.

I learned a few things i didn't know like the use of naming and how names can be global or local...didn't know any of that before to be honest. I still wonder how i managed to do my MD stuff and have it work lol.

The way your setting it out though is really good ie: walking through making a MD structure instead of just showing parts of it.

All good so far, if i can think of anything i'll be sure to ask though.

What really has me boggled is Library files and params etc...I have no idea how those are used at all...but carry on as you are.

Note: I think the reason no one has questions is because you've explained it really well.

Whats next with MD tutorial?

Argo.

[Ketraar]

Whats next with MD tutorial?

I've not thought of what to do next yet, I could address the libraries I guess, that includes the use of params too so it might be more than two parts. Also doing one on briefings and conversations, includes the use of actors.

So that should be OK for the next few I guess.

If I have time tomorrow I'll do one then, other wise on weekend.

MFG

Ketraar

PS.: also noticed some odd whistling sound that seams to originate from microphone, maybe some sort of echo, will try to get rid of that.

[Argonaught.]

No rush on making them...one a week would be cool, no need to do one every day/few days.

Yea conversations and actors, i haven't gone near them either.

I'm not sure what way it would go but i imagine, in terms of easy to hard, it'd be actors, conversations and then libraries and params...although it may be the other way around

Argo.

[DrBullwinkle]

would be good to have feedback as to if they are of any help and somewhat understandable.

I am finding the series extremely helpful.

Before: I had no clue where to begin; even after reading the manual.

After watching your videos: I can begin to write a simple mission. Also, I understand more of other people's scripts that I try to read.

Your English is excellent. Better than some Americans.

Given the nature of the content, and your extemporaneous style, your explanations are very clear. The only way to improve would be to use a script and to edit the output -- which would be quite a bit more work. So I would say that you have found a perfect balance of high "technology transfer" with a modest "investment".

The only suggestion that I have is to reduce your screen resolution before making the capture. That would make everything larger and easier to read. When you render your capture, be sure to use one of YouTube's default resolutions, which they list on their Suggested resolutions and bitrates page.

[apricotslice]

Another suggestion for you, once you have done all the basics, is to do a set of How-to themes and the most wanted topics. How to make a mission that runs from a character on a station. How to make a series of missions that run like a plot does and start whenever the player wants to. How to make an MD to just add things into the universe based on some sort of timing. How to make a MD to check that your own-plot station or character still exists and add them back in if they are not.

Another thought, is about characters. Why not make an MD that uses all the available characters and just have that vid introduce themselves ? It would show people which ones are existing and you can include the details of how to use each one within the "introduction". "Hello, I'm default Argon 1. You use me by .......". "Hello, I'm Ban Danna from X2, and you can still use me as an older Argon character by .......", assuming we can.

Stuff like the characters available for vid use is something I've not seen anywhere, so a vid on what is available to use would be good.

Also, perhaps a vid on the different ways of delivering messages to the player. Email type Message vs bottom screen vs player log, verses talking head. Which do you use in what situation. How to code each, so people can see the differences in the coding. (So same example message, but delivered all the different ways.)

[Ketraar]

Ok great input thanks, will take all into account.

As for the resolution, I can define the area which is captured, but MD code can get quite long (wide?) so I was not sure. As for the output I use a default output option that the program has, its called Youtube widescreen 720p, so hope that's the right one

Aro is right, maybe do actors and conversations (also combine apricotslice's suggestion for all messages delivery methods) first, do libraries later. Also think one of the next ones would be like a recap video, where a small mission/code is done using all stuff addressed so far.

MFG

Ketraar

[DrBullwinkle]

As for the resolution, I can define the area which is captured, but MD code can get quite long (wide?) so I was not sure. As for the output I use a default output option that the program has, its called Youtube widescreen 720p, so hope that's the right one

I was suggesting actually changing your screen resolution before capturing the screen. (Unless your native screen resolution is *exactly* 1280x720.)

Since you capture your entire screen and viewers display it in a window, everything gets shrunk slightly. Since Flash video is "lossy", the display is slightly fuzzy. Smaller and slightly fuzzy makes it more difficult to see. I *can* read what you do, so your vids are probably good enough.

However, if you want to experiment, I capture in 800x600 and render at 960x720 (using Camtasia). The default Camtasia output for YouTube HD did not give me the best quality. I get higher quality by rendering to .mp4, then uploading that to YouTube.

Since you are concerned with screen width, you could capture in a wide-screen format and render in same.

To summarize:

• - Try setting screen resolution to 1280x720 (if that is not its normal resolution).
  - Render to .mp4 in 1280x720 resolution.
  - Upload to YouTube

In my experience, I got much higher quality videos this way.

• (Note: 960x720 is a native resolution for YouTube, but I do not recall where I found it. Not on the page that I linked for you, apparently. )

[Ketraar]

I do render to mp4, but that gives me files sizes in the 2+ GB, thats not feasible for me to upload it would take me 8 or more hours for a single upload, so I have to compress it to get file sizes my connection can handle.

Also not very keen on changing my screen resolution tbh, both at work and at home I'm used to 1600's resolutions and dont see how any one can live with working on any program using lower ones. I do have a 17" monitor that I can use as secondary monitor and "clone" my screen and capture on that, but I guess that wont work. Its worth a try though.

An other option would be to render in 1080p if that does help I can do that.

The problem with MD coding and low resolutions is that it would need lots of scrolling. Even with this high res we will have to scroll a lot once we get to the bigger stuff.

So if its readable I'd rather keep things as they are (or increase output res to 1080p) for a balance between people being able to read stuff properly and me not having to go through low res working.

MFG

Ketraar