Hello everyone.

As the title of the thread states, this is a tutorial for custom cinematics for World of Warcraft 3.3.5.

Without further ado here we go...


Part I. Getting started...


You need to download a bunch of programs if you don't already have them...


* MyDbcEditor (viewtopic.php?f=59&t=782)
* Microsoft Visual Studio (https://www.visualstudio.com/en-us/down ... io-vs.aspx)
* MPQ Editor (http://www.hiveworkshop.com/forums/tool ... bit-249562)


Once you have all the programs you need collect a bunch of files... The files you'll need are:


*CinematicCamera.dbc
*CinematicSequences.dbc




Any camera skin file as they are all the same (E.g. FlyByDwarf00.skin) these can be found in Common-2.mpq / Cameras.




Then you need to C++ program that generates the .m2 file which can be downloaded from Stoneharry's Github: https://github.com/stoneharry/Misc-WoW- ... camera.cpp



Part II. Editing the DBC's.


Open up CinematicCamera.dbc, it should look something like this:




Now insert a new line and give it your own ID.





Now change the name to what you want to name your .m2 file later, I've chosen Test.mdx...


Then you need to go ingame and get the coords for where you want the camera to end because the camera will use these coords as the "root coords".


You can read about the different columns here: https://wowdev.wiki/DB/CinematicCamera




Once you've set up the CinematicCamera.dbc you need to open up CinematicSequences.dbc


Read about the different columns here: https://wowdev.wiki/DB/CinematicSequences


You only need to insert a row where you specify a sequence ID and bind it to your cinematic ID, my cinematic ID was 300 and I've set the sequence ID to 200.






Part III. Visual Studio...


Open up Microsoft Visual Studio and create a new Win32 Console Application.

[imghttp://puu.sh/o3e9h/62f876e3f6.png[/img]


You can remove the information that is generated in the file except for #include "stdafx.h"




Then open up the camera.cpp from Stoneharry's github and put the information in the project.


Now for the actual editing of the vectors... This is the tricky part.


AnimationLength = The length of course...


TimeStamp = When the camera triggers based on the AnimationLength...


Position = DBC file coords +/- Vector (E.g. if set to 3920 in DBC and you do -5 in the vector it will do 3920 - 5...)
( Example: fake9.stamp = 0000; fake9.data.d[0] = 0.00f; fake9.data.d[1] = 150.00f; fake9.data.d[2] = 14.00f); )

The structure of the vectors are: TimeStamp; X; Y; Z...




Target = DBC file Z +/- Vector (E.g. if set to 10 in dbc and you do -5 it will look down, and +5 makes it look up...)


For easy calculation I have done "RootX" - "NewX" = "OffsetX" (E.g. DbcX = 3920, NewX = 3940 then OffsetX = 3920-3940 = -20...)
This only applies to the position vectors, the target is a bit more complex then that and you will need to mess around with this to get it to work.


This is a very basic way to calculate the coords and it's a very complex system so you will need to do a lot of trial and error to get it the way you want...


You also need to set up where you want the .m2 file to generate to, (E.g. FILE* f = fopen("C:\Users\Kenny\Desktop\Kenny\World of Warcraft - 3.3.5a\Data\Patch-U.MPQ\Cameras\Test.m2", "w+")


This generates it straight into my patch folder and then I can just call it in-game without restarting the game (I have an unpacked MPQ folder...)


Once you have entered all your vectors and what-not it's time to compile the program.


Note: If you get an error saying something about _CRT_SECURE_NO_WARNINGS then go into Project -> Properties -> Configuration Properties -> C/C++ -> Preprocessors -> Preprocessor Definitions and add the line _CRT_SECURE_NO_WARNINGS...







Should look something like this when compiled:




Once that's done, go into the Release folder and run the console program, in my case it's C:UsersKennyDocumentsVisual Studio 2013ProjectsConsoleApplication5ReleaseConsoleApplication5.exe...


This will now generate the .m2 file to whereever you specified in the C++ file...




Part IIII. Getting your camera ingame...


As I meantioned I have an unpacked mpq folder meaning I don't need to shut down the game, open the mpq file and put in the new files... You can easily do this by creating a new folder in your en##/Data folder and naming it Patch-#.MPQ.


So when you have created your MPQ you create a folder inside it named Camera, here you place the .m2 file and .skin file...
Then go back to the root of the mpq and create another folder named DBFilesClient and in here you put the CinematicCamera.dbc and CinematicSequences.dbc...


Then go ingame and write .debug play cinematic #CinematicSequenceID




??
profit




Part V. FAQ
Do I need to use target vectors at all or can I comment them out? - You do not need to use these, you can comment them all out but if you are doing a camera that starts higher up than the DBC Z you will need to set the target Z to a negative value to make the camera look down, else it will look straight ahead.


My camera is looking straight up into the sky / straight down in the ground. - Make sure that the first timestamp is set to 0000, else the camera won't know which coords to load (E.g. if you set the first one to 5000 it will look straight up into the sky until after the 5 seconds have passed and it loads the target.)


I'm getting a WoWError when trying to play my cinematic. - Make sure you have the .m2 and .skin files set up correctly, and that the dbc's are set up correctly. The skin file needs to be named *filename*00.skin. Also make sure that you set the name of the file to *filename*.mdx in the CinematicCamera.dbc.




Part VI. Credits
Schlumpf for creating the C++ program to generate the .m2
Stoneharry for helping me setting up my first camera.
Myself for creating the guide.

Hey, i've been looking around in trinitycores files, lua files, xml files, m2 files and blp files in order to try and pinpoint where the glow of DK eyes is defined, and I started thinking I would like a function on the character customization screen where you can change the eye color of dk's.

I mean changing the eye color as part of the customization and not just modifying the blp file, according to the bloodelf female m2 model it says that the texture is Hardcoded, see screenshot below.

http://puu.sh/hEYpn/a7f9e90fa5.png

I'm curious if anyone would know how to find a workaround for this or including more textures (blp files) in order to be able to change it as part of the customization?

I would also like to point out that it's for patch 3.3.5.

That is all.

Or you could just copy paste stuff from your database and remove all the overflowing text, convert it to a csv file, put in the new information which you got from the DB, then just convert it back to a dbc.