Call of Duty 5: Loadscreen Creation Alternate - Revision history

CoDEmanX at 14:52, 7 February 2012

2012-02-07T14:52:38Z

← Older revision		Revision as of 14:52, 7 February 2012
Line 109:		Line 109:
	[[Category:Call of Duty 5]]		[[Category:Call of Duty 5]]
	[[Category:Modtools]]		[[Category:Modtools]]
	[[Category:~~Loadscreen~~]]		[[Category:Loadscreens]]
	[[Category:Mapping]]		[[Category:Mapping]]

Zeroy: /* WORK-AROUND */

2009-10-07T10:03:45Z

WORK-AROUND

← Older revision		Revision as of 10:03, 7 October 2009
Line 25:		Line 25:
	Here is a download for a test map loadscreen I did:		Here is a download for a test map loadscreen I did:

	[http://~~tallys-world~~.com/~~downloads~~/loadscreen_workaround.zip DOWNLOAD EXAMPLE]		[[File:data.png]][http://wiki.modsrepository.com/codww_files/loadscreen_workaround.zip DOWNLOAD EXAMPLE]

	Inside the .ZIP file you will find all the necessary files you will need to make your own loadscreen. Just use them as a guide. Pay close attention to both their setup and their syntax and wording.		Inside the .ZIP file you will find all the necessary files you will need to make your own loadscreen. Just use them as a guide. Pay close attention to both their setup and their syntax and wording.

	[[Image:Information.png]] You will need to rename the map used in these example files, to match your own map. Otherwise, you wont have a loadscreen that works with your map. Please pay attention to the instructions given in this tutorial		[[Image:Information.png]] You will need to rename the map used in these example files, to match your own map. Otherwise, you wont have a loadscreen that works with your map. Please pay attention to the instructions given in this tutorial


	== SETUP ==		== SETUP ==

Zeroy: /* RUNNING YOUR MP MAP */

2009-03-04T18:25:53Z

RUNNING YOUR MP MAP

New page

[[Image:Nutshell.png]] As many maps are now nearly ready for release, I thought it the right time to release my work-around for the loadscreen problem.

== CAUSES OF THE PROBLEM ==

Essentially, there are 3 causes to the problem:

*Launcher wont let you make a loadscreen at all, because the .DLL file for AssetManager is the one for COD4 and doesnt work with the SQL .DLL for the COD5 tools. It therefore returns an error of a .DLL file mismatch;

*There are missing CSV files that Launcher looks for. These are assetlist CSV files, which the game is told to ignore on load. However, when the compiler cant find them, it returns a series of errors which are enough to make it abort notwithstanding the .DLL error mismatch of 1.

*The Treyarch Wiki gives wrong info in building the level.GDT file. The correct settings are these:

You will notice that the materials files for victoryBackdrop and defeatBackdrop are '''not''' the ones you are told to use in the Treyarch Wiki. If you try to use the ones on the Wiki, when you try and run your map, the game will crash with an error saying that it cannot load image mile_high_victory_screen.

No matter what you do, it will refuse to load that image. However, if you use the settings above, all will be fine.

== WORK-AROUND ==

Ok, so how to overcome this? Simple: dont use Launcher to build your loadscreen at all. Use a .BAT file and a mp_map_load.csv file.

Here is a download for a test map loadscreen I did:

[http://tallys-world.com/downloads/loadscreen_workaround.zip DOWNLOAD EXAMPLE]

Inside the .ZIP file you will find all the necessary files you will need to make your own loadscreen. Just use them as a guide. Pay close attention to both their setup and their syntax and wording.

[[Image:Information.png]] You will need to rename the map used in these example files, to match your own map. Otherwise, you wont have a loadscreen that works with your map. Please pay attention to the instructions given in this tutorial

== SETUP ==

*Place the folder 'compiler' inside the 'mods' folder in your root game install. That is by default:

C:\Program Files\Activision\Call of Duty - World at War\mods

Rename the example CSV file mp_gap_load.csv to match the name of your map.

Go into the CSV file, and rename the map referenced inside. that is, edit this line:

ui_map,maps/mp_yourmap.csv

Edit the .BAT file. You need to change every instance of mp_gap_load. That is, you have to edit to this:

copy /Y mp_yourmap_load.csv ..\..\zone_source
cd ..\..\bin
linker_pc.exe -language english -compress -cleanup mp_yourmap_load
cd ..\mods\compiler
copy ..\..\zone\english\mp_yourmap_load.ff
pause

*Place the files inside the enclosed 'zone_source' folder inside your game's 'zone_source' folder.

The assetlist CSVs go in the 'english' folder. The game needs these although it will be told to ignore them.

The example mp_gap_load.csv goes just inside 'zone_source'. Rename the file itself to the name of your map.

Open the CSV file, and rename the loadscreen to match your map's name.

*Place the contents of the enclosed 'raw' folder in their respective folders in your game's tools 'raw' folder. Obviously, you cant actually use the materials and image files, but use them as a guide to where you place your map's ones.

That is, your maps' loadscreen IWI file and materials go in their respective folders inside the 'raw' folder.

== BUILDING LOADSCREEN FAST FILE ==

Go back to mods/compiler, and double-click the .BAT file. This will run linker_pc.exe and return a .FF file.

If you've followed everything correctly, the tools should return a load .FF file named after your map.

''This is one I built for a "Jump" map by _DanTheMan_, named mp_gap (the example used):''

[[Image:mp_gap.jpg|center]]

I have created about 5 such loadscreens for different mappers using this method.

== RUNNING YOUR MP MAP ==

1. As we all know, COD5 uses the local Application Data directory to run maps and mods. What isnt clear at the moment is that Treyarch have reverted us back to the COD4 pre-1.5 patch method, where all map IWDs go inside a mod folder.

[[Image:warning.png]] You cannot run your map IWD inside the 'usermaps' folder.

2. So, to set up your map, place everything but the IWD file in:

Inside the 'usermaps' folder, create another folder named after your map (just like you did for COD4). So, the directory root will now be:

3. Place your 3 fast files:

*mp_mapname.ff
*localized_mp_mapname.ff
*mp_mapname_load.ff

4. Next, choose a mod to run your map from. There is a default mod named mp_usermaps. Place your map's IWD, with its loadscreen IWI and minimap IWI, inside it.

Have fun!

''By Tally''

[[Category:Call of Duty 5]]
[[Category:Modtools]]
[[Category:Loadscreen]]
[[Category:Mapping]]

Zeroy: /* RUNNING YOUR MP MAP */

2008-12-15T17:51:36Z

RUNNING YOUR MP MAP

← Older revision		Revision as of 17:51, 15 December 2008
Line 100:		Line 100:

	Have fun!		Have fun!

			''By Tally''

			[[Category:Call of Duty 5]]
			[[Category:Modtools]]
			[[Category:Loadscreen]]
			[[Category:Mapping]]

Zeroy: /* BUILDING LOADSCREEN FAST FILE */

2008-12-15T17:50:38Z

BUILDING LOADSCREEN FAST FILE

← Older revision		Revision as of 17:50, 15 December 2008
Line 68:		Line 68:
	If you've followed everything correctly, the tools should return a load .FF file named after your map.		If you've followed everything correctly, the tools should return a load .FF file named after your map.

	This is one I built for a "Jump" map by _DanTheMan_, named mp_gap (the example used):		''This is one I built for a "Jump" map by _DanTheMan_, named mp_gap (the example used):''


Line 75:		Line 75:

	I have created about 5 such loadscreens for different mappers using this method.		I have created about 5 such loadscreens for different mappers using this method.


	== RUNNING YOUR MP MAP ==		== RUNNING YOUR MP MAP ==

Zeroy: /* SETUP */

2008-12-15T17:50:18Z

SETUP

← Older revision		Revision as of 17:50, 15 December 2008
Line 35:		Line 35:


	1. Place the folder 'compiler' inside the 'mods' folder in your root game install. That is by default:		*Place the folder 'compiler' inside the 'mods' folder in your root game install. That is by default:

	C:\Program Files\Activision\Call of Duty - World at War\mods		C:\Program Files\Activision\Call of Duty - World at War\mods
Line 49:		Line 49:


	2. Place the files inside the enclosed 'zone_source' folder inside your game's 'zone_source' folder.		*Place the files inside the enclosed 'zone_source' folder inside your game's 'zone_source' folder.

	The assetlist CSVs go in the 'english' folder. The game needs these although it will be told to ignore them.		The assetlist CSVs go in the 'english' folder. The game needs these although it will be told to ignore them.
Line 57:		Line 57:
	Open the CSV file, and rename the loadscreen to match your map's name.		Open the CSV file, and rename the loadscreen to match your map's name.

	3. Place the contents of the enclosed 'raw' folder in their respective folders in your game's tools 'raw' folder. Obviously, you cant actually use the materials and image files, but use them as a guide to where you place your map's ones.		*Place the contents of the enclosed 'raw' folder in their respective folders in your game's tools 'raw' folder. Obviously, you cant actually use the materials and image files, but use them as a guide to where you place your map's ones.

	That is, your maps' loadscreen IWI file and materials go in their respective folders inside the 'raw' folder.		That is, your maps' loadscreen IWI file and materials go in their respective folders inside the 'raw' folder.


	== BUILDING LOADSCREEN FAST FILE ==		== BUILDING LOADSCREEN FAST FILE ==

Zeroy: /* CAUSES OF THE PROBLEM */

2008-12-15T17:50:01Z

CAUSES OF THE PROBLEM

← Older revision		Revision as of 17:50, 15 December 2008
Line 3:		Line 3:

	== CAUSES OF THE PROBLEM ==		== CAUSES OF THE PROBLEM ==


	Essentially, there are 3 causes to the problem:		Essentially, there are 3 causes to the problem:

	1. Launcher wont let you make a loadscreen at all, because the .DLL file for AssetManager is the one for COD4 and doesnt work with the SQL .DLL for the COD5 tools. It therefore returns an error of a .DLL file mismatch;		*Launcher wont let you make a loadscreen at all, because the .DLL file for AssetManager is the one for COD4 and doesnt work with the SQL .DLL for the COD5 tools. It therefore returns an error of a .DLL file mismatch;

	2. There are missing CSV files that Launcher looks for. These are assetlist CSV files, which the game is told to ignore on load. However, when the compiler cant find them, it returns a series of errors which are enough to make it abort notwithstanding the .DLL error mismatch of 1.		*There are missing CSV files that Launcher looks for. These are assetlist CSV files, which the game is told to ignore on load. However, when the compiler cant find them, it returns a series of errors which are enough to make it abort notwithstanding the .DLL error mismatch of 1.

	3. The Treyarch Wiki gives wrong info in building the level.GDT file. The correct settings are these:		*The Treyarch Wiki gives wrong info in building the level.GDT file. The correct settings are these:



	You will notice that the materials files for victoryBackdrop and defeatBackdrop are ~~[U]~~not~~[/U]~~ the ones you are told to use in the Treyarch Wiki. If you try to use the ones on the Wiki, when you try and run your map, the game will crash with an error saying that it cannot load image mile_high_victory_screen.		You will notice that the materials files for victoryBackdrop and defeatBackdrop are '''not''' the ones you are told to use in the Treyarch Wiki. If you try to use the ones on the Wiki, when you try and run your map, the game will crash with an error saying that it cannot load image mile_high_victory_screen.

	No matter what you do, it will refuse to load that image. However, if you use the settings above, all will be fine.		No matter what you do, it will refuse to load that image. However, if you use the settings above, all will be fine.


	== WORK-AROUND ==		== WORK-AROUND ==

Zeroy: New page: Image:Nutshell.png As many maps are now nearly ready for release, I thought it the right time to release my work-around for the loadscreen problem. == CAUSES OF THE PROBLEM == Esse...

2008-12-13T19:45:43Z

New page: Image:Nutshell.png As many maps are now nearly ready for release, I thought it the right time to release my work-around for the loadscreen problem. == CAUSES OF THE PROBLEM == Esse...

New page

[[Image:Nutshell.png]] As many maps are now nearly ready for release, I thought it the right time to release my work-around for the loadscreen problem.

== CAUSES OF THE PROBLEM ==

Essentially, there are 3 causes to the problem:

1. Launcher wont let you make a loadscreen at all, because the .DLL file for AssetManager is the one for COD4 and doesnt work with the SQL .DLL for the COD5 tools. It therefore returns an error of a .DLL file mismatch;

2. There are missing CSV files that Launcher looks for. These are assetlist CSV files, which the game is told to ignore on load. However, when the compiler cant find them, it returns a series of errors which are enough to make it abort notwithstanding the .DLL error mismatch of 1.

3. The Treyarch Wiki gives wrong info in building the level.GDT file. The correct settings are these:

You will notice that the materials files for victoryBackdrop and defeatBackdrop are [U]not[/U] the ones you are told to use in the Treyarch Wiki. If you try to use the ones on the Wiki, when you try and run your map, the game will crash with an error saying that it cannot load image mile_high_victory_screen.

No matter what you do, it will refuse to load that image. However, if you use the settings above, all will be fine.

== WORK-AROUND ==

Ok, so how to overcome this? Simple: dont use Launcher to build your loadscreen at all. Use a .BAT file and a mp_map_load.csv file.

Here is a download for a test map loadscreen I did:

[http://tallys-world.com/downloads/loadscreen_workaround.zip DOWNLOAD EXAMPLE]

Inside the .ZIP file you will find all the necessary files you will need to make your own loadscreen. Just use them as a guide. Pay close attention to both their setup and their syntax and wording.

[[Image:Information.png]] You will need to rename the map used in these example files, to match your own map. Otherwise, you wont have a loadscreen that works with your map. Please pay attention to the instructions given in this tutorial

== SETUP ==

1. Place the folder 'compiler' inside the 'mods' folder in your root game install. That is by default:

C:\Program Files\Activision\Call of Duty - World at War\mods

Rename the example CSV file mp_gap_load.csv to match the name of your map.

Go into the CSV file, and rename the map referenced inside. that is, edit this line:

Edit the .BAT file. You need to change every instance of mp_gap_load. That is, you have to edit this:

2. Place the files inside the enclosed 'zone_source' folder inside your game's 'zone_source' folder.

The assetlist CSVs go in the 'english' folder. The game needs these although it will be told to ignore them.

The example mp_gap_load.csv goes just inside 'zone_source'. Rename the file itself to the name of your map.

Open the CSV file, and rename the loadscreen to match your map's name.

3. Place the contents of the enclosed 'raw' folder in their respective folders in your game's tools 'raw' folder. Obviously, you cant actually use the materials and image files, but use them as a guide to where you place your map's ones.

That is, your maps' loadscreen IWI file and materials go in their respective folders inside the 'raw' folder.

== BUILDING LOADSCREEN FAST FILE ==

Go back to mods/compiler, and double-click the .BAT file. This will run linker_pc.exe and return a .FF file.

If you've followed everything correctly, the tools should return a load .FF file named after your map.

This is one I built for a "Jump" map by _DanTheMan_, named mp_gap (the example used):

[[Image:mp_gap.jpg|center]]

I have created about 5 such loadscreens for different mappers using this method.

== RUNNING YOUR MP MAP ==

1. As we all know, COD5 uses the local Application Data directory to run maps and mods. What isnt clear at the moment is that Treyarch have reverted us back to the COD4 pre-1.5 patch method, where all map IWDs go inside a mod folder.

[[Image:Information.png]] You cannot run your map IWD inside the 'usermaps' folder.[/B][/color]

2. So, to set up your map, place everything but the IWD file in:

Inside the 'usermaps' folder, create another folder named after your map (just like you did for COD4). So, the directory root will now be:

3. Place your 3 fast files:

*mp_mapname.ff
*localized_mp_mapname.ff
*mp_mapname_load.ff

4. Next, choose a mod to run your map from. There is a default mod named mp_usermaps. Place your map's IWD, with its loadscreen IWI and minimap IWI, inside it.

Have fun!