COD Modding & Mapping Wiki - User contributions [en]

Call of duty 4: Import models

2011-06-24T12:05:52Z

Randallphillips:

{{Warning_forpro}}
''By NovemberDobby''

{{Note|This tutorial will show you the basics of importing a new weapon model into Cod4. Below is my example, which you will hopefully be able to use.}}
{{Warning_advanced}}

[[Image:shot0097.jpg|center|600px]]

''You will be needing:''

*Maya 7.0 or 8.5 (not the Personal Learning Edition)
*Maya 8.0 requires a little hack (see below)
*The Cod4\bin\maya folder from the mod tools
*Texture(s) for your model: The dimensions have to be a power of two. (256*256, 512*512, etc), and the file must be a .jpg, .tga, or .dds. TGA and DDS textures can both have alpha channels, and can both be natively edited using Paint.net. (www.getpaint.net)
*My example weapon model, from [http://www.modsonline.com/Downloads-full-4308.html HERE]

*In this tutorial, I will assume you know Maya's basic controls. Firstly, I recommend you follow this tutorial, written by mdS [http://www.modsonline.com/Downloads-full-4254.html HERE]

*It shows you how to export a rigid model from Maya, and get it into the game using Asset Manager. It also shows you the first two steps needed to set up Maya to use the plugins. As these two steps are necessary, I'll explain them here, courtesy of Infinity Ward's Wiki.

== Maya 8.0 Fix ==

You can use the Maya 8.5 plugins (xmodel, xanim) which come with the CoD4 Mod Tools, in Maya 8.0. Just open the two MLL files with a [http://mh-nexus.de/en/hxd/ hex-editor], do a text search for '850' and replace it with '800'.

<pre>
Change 850 (hex 38 35 30 )
To --> 800 (hex 38 30 30 )

Offsets:
XAnimExport.mll - 0x2B10B
XModelExport.mll - 0x350EC
</pre>

850 is the version number v8.50, the Maya version the plugins are designed for. Maya v8.00 won't accept them, but if you change the version requirement like described above it will load the plugins. The Maya scripting engines probably didn't change a lot, thus you shouldn't experience any problems with the hacked plugins.

==MAYA Setup==

Create a Maya.env file in: C:\Documents and Settings\My Documents\maya\
and add the two lines below into it.

MAYA_SCRIPT_PATH = C:\Program Files\Activision\Call of Duty 4 - Modern Warfare\bin\maya\tools
MAYA_PLUG_IN_PATH = C:\Program Files\Activision\Call of Duty 4 - Modern Warfare\bin\maya\tools

This folder location will be different if you have the Steam version, or have installed Cod4 somewhere else. You also need to make a file called usersetup.mel in C:\Documents and Settings\\My Documents\maya\\scripts\
and add the following three lines to it:

source CODToolsMenu;
CODStartup;
CODToolsMenu;

Lastly, you need to extract the corret plugins for your version of Maya. Go to Cod4\bin\maya\tools, and open up either Maya7_plugins.zip or Maya8_plugins.zip. Extract the two files from that zip into the Cod4\bin\maya\tools folder.

==In MAYA==

* Ok, start up Maya, and you should see a Call Of Duty 4 menu at the top. Open my example weapon, and then save it as a Maya file in a folder called Cod5\model_export\maya_ex. Maya_ex is the name of your model for now, it can be anything as long as there are no spaces in the name. You can save the actual Maya file under any filename. Also, copy the textures out of my example file into the same folder you saved this into.

* To view and edit the texturing in this model, you need to use Hypershade. In Maya, go to {{Color|Window > Rendering Editors > Hypershade|yellow}}. You will be presented with a dialog box which shows you the textures in use along with some other stuff. In the top dark section, you should see four textures. The one called {{Color|'demo_wep_skin'|orange}} is the one we're interested in, the other three are there by default and you cannot remove them. You may have to re-locate the actual .tga texture which is being used, so double click on the demo_wep_skin, and you should see the main right hand side panel change in Maya. There should be a 'file1' tab there now, click on it. About halfway down this new page, you should see 'Image name'. Click on the folder icon to browse to the skin image, demo_weapon_skin.tga, and open it.

* There is one step that you need to do for each model that you export, otherwise they will appear totally black in Radiant and the game. Go to {{Color|Edit > Select All|yellow}}, and then to {{Color|Color > Apply color|yellow}}, but don't click on the menu button; click the small box to the right of it. In the {{Color|'Color Value'|orange}} frame, click on the coloured box, and select a full white colour from the colour selector that comes up. Click {{Color|'Apply color'|orange}}, and you should see your model become marginally brighter in the 3D window. You need to do this for every new model, or again if you add geometry to an existing model.

* This model has already been rigged with the correct joints needed to work as a weapon in Cod4, so, navigate to the Call Of Duty 4 menu, and click on Model Exporter. When the dialog box comes up, click on the 'Add new Entry' button. Tick the checkbox called 'Entry1', and then choose where you will export your model. This should be in the same folder as your Maya model, and should have a similar (if not the same) name.

* Next, in Maya's menus, go to Edit>Select All. Back in the Cod4 dialog, click on Set Exports in Entry1. This has set the polygons and joints that you want to export to the Cod4 model, and it's very rare that you won't want to export everything.

==MAYA: Convert==

You're now ready to convert the model to a useable format. In the Cod5 Model Export Window, click 'Select Exports', and 'Export Selected Entries'. If all goes well, a progress bar should pop up and reach 100%. It won't work unless you have clicked 'Select Exports' (or selected everything in Maya).

''You sould now have a .xmodel_export file in your model's folder in Cod5\model_export. If you do, continue to the steps below.''

==Asset Manager==

*Close Maya, and open up Cod4\bin\asset_manager.exe. You will see several buttons in the top left corner, along with a list. Scroll down to 'xmodel', and click 'New Entry'. You now need to enter the name of the model that you will use to access it ingame, and in Radiant. It can't have any spaces, and try not to make it too generic, pick something which will definitely be unique, e.g. db_laser_cannon. You will see a list of options for your model appear on the right hand side now, select 'animated' from the first drop-down menu. In the 'filename' field, click the browse (three dots) button to the right. Use this to locate and open your xmodel_export file that you made before.

*Save your Asset Manager file in Cod4\model_export. Anywhere else and it won't convert, but it won't have any errors.

To convert the xmodel_export, you need to edit the export file. Go to Cod4\model_export\modelfolder\, and open up the .xmodel_export in a text editor like notepd. You will see 'VERSION 8', this needs changing to 'VERSION 6'. Save and close it.

*Go back to Asset Manager, and click on your entry in xmodel. Go to PC Convert>Current Asset Only, and if it works, you should see 'Conversion done, hit key to continue'.

In the left hand scroll list, go to 'material', and click new entry. This entry must be the same name as the weapon texture you used in Hypershade, in this example, 'demo_wep_skin'. Change these properties of the material:

Materialtype = world phong
surfacetype = none
sort = default*
usage = not in editor

*Click the three dots symbol next to the 'Color map' box, and navigate to your .tga skin. If you want the skins to have a specular map aswell, you have to create a texture for that and browse for it, using 'Specular color map'. Do not use a Normal Map on your texture, because it'll stop the specular from working properly, on scopes and reflections.

*Re-save the Asset Manager file, it will only convert entries that are in the saved version.

*Select your material from the list on the left, and go to PC Convert>Current Asset Only. If all goes well, a black box should appear, and it'll eventually read 'Conversion done, hit key to continue'. You've now converted the texture for use with your model.

*If both your texture and your model have converted properly, you can now package them in your mod. I'm assuming you can use .csv files and know how to make a basic mod.ff. All of the textures must go in the mod's IWD, and if it doesn't have one, it needs one. The file structure is: IWD\images\, and the converted iwi images can be found in Cod4\raw\images.

==Creating the weapon's file==

For this example, we'll mod a stock weaponfile. (rpg_mp)

<pre>
WEAPONFILE \weaponType\projectile\weaponClass\rocketlauncher\impactType\rocket_explode\guidedMissileType\None\inventoryType\item\maxSteeringAccel\3000\displayName\Laser thingy\AIOverlayDescription\\modeName\\playerAnimType\rocketlauncher\gunModel\db_laser_cannon\gunModel2\\gunModel3\\gunModel4\\gunModel5\\gunModel6\\gunModel7\\gunModel8\\gunModel9\\gunModel10\\gunModel11\\gunModel12\\gunModel13\\gunModel14\\gunModel15\\gunModel16\\handModel\viewmodel_base_viewhands\isHandModelOverridable\0\idleAnim\viewmodel_rpg_idle\emptyIdleAnim\viewmodel_rpg_idle_empty\fireAnim\viewmodel_rpg_fire\lastShotAnim\viewmodel_rpg_fire\meleeAnim\viewmodel_M4m203_knife_melee_1\meleeChargeAnim\viewmodel_M4m203_knife_melee_2\reloadAnim\viewmodel_rpg_reload\raiseAnim\viewmodel_rpg_pullout\dropAnim\viewmodel_rpg_putaway\firstRaiseAnim\viewmodel_rpg_pullout\altRaiseAnim\viewmodel_rpg_pullout\altDropAnim\viewmodel_rpg_putaway\quickRaiseAnim\viewmodel_rpg_pullout\quickDropAnim\viewmodel_rpg_putaway\emptyRaiseAnim\viewmodel_rpg_pullout\emptyDropAnim\viewmodel_rpg_putaway\sprintInAnim\viewmodel_rpg_sprint_in\sprintLoopAnim\viewmodel_rpg_sprint_loop\sprintOutAnim\viewmodel_rpg_sprint_out\nightVisionWearAnim\\nightVisionRemoveAnim\\adsFireAnim\viewmodel_rpg_fire\adsLastShotAnim\viewmodel_rpg_fire\adsUpAnim\viewmodel_rpg_ads_up\adsDownAnim\viewmodel_rpg_ads_down\moveSpeedScale\1\adsMoveSpeedScale\1\sprintDurationScale\1\lowAmmoWarningThreshold\0.33\damage\1000\meleeDamage\135\fireDelay\0\meleeDelay\0.13\meleeChargeDelay\0.16\fireTime\0.33\meleeTime\0.8\meleeChargeTime\1.16\reloadTime\3.292\reloadShowRocketTime\0.1\reloadAddTime\1.17\dropTime\0.467\raiseTime\0.73\altDropTime\0.467\altRaiseTime\0.733\quickDropTime\0.25\quickRaiseTime\0.75\firstRaiseTime\0.73\emptyDropTime\0.467\emptyRaiseTime\0.73\sprintInTime\0.3\sprintLoopTime\1\sprintOutTime\0.3\nightVisionWearTime\0\nightVisionWearTimeFadeOutEnd\0\nightVisionWearTimePowerUp\0\nightVisionRemoveTime\0\nightVisionRemoveTimePowerDown\0\nightVisionRemoveTimeFadeInStart\0\clipOnly\0\adsTransInTime\0.5\adsTransOutTime\0.5\adsZoomFov\55\adsZoomGunFov\40\adsZoomInFrac\0.5\adsZoomOutFrac\0.1\adsOverlayShader\\adsOverlayReticle\none\adsOverlayInterface\none\adsOverlayWidth\240\adsOverlayHeight\240\adsBobFactor\1\adsViewBobMult\0\hipSpreadStandMin\5\hipSpreadDuckedMin\3.5\hipSpreadProneMin\2\hipSpreadMax\6\hipSpreadDuckedMax\6\hipSpreadProneMax\6\hipSpreadDecayRate\2.5\hipSpreadFireAdd\0.4\hipSpreadTurnAdd\0\hipSpreadMoveAdd\2.3\hipSpreadDuckedDecay\1.375\hipSpreadProneDecay\1.6\hipReticleSidePos\0\adsSpread\1.7\adsIdleAmount\25\hipIdleAmount\80\hipIdleSpeed\1\adsIdleSpeed\1\idleCrouchFactor\0.5\idleProneFactor\0.15\gunMaxPitch\30\gunMaxYaw\30\adsAimPitch\0\adsCrosshairInFrac\1\adsCrosshairOutFrac\0.2\adsReloadTransTime\0.6\adsGunKickPitchMin\-30\adsGunKickPitchMax\-20\adsGunKickYawMin\-17\adsGunKickYawMax\17\adsGunKickAccel\250\adsGunKickSpeedMax\1000\adsGunKickSpeedDecay\10\adsGunKickStaticDecay\1\adsViewKickPitchMin\20\adsViewKickPitchMax\95\adsViewKickYawMin\-10\adsViewKickYawMax\30\adsViewKickCenterSpeed\2500\hipGunKickPitchMin\-5\hipGunKickPitchMax\-3\hipGunKickYawMin\-15\hipGunKickYawMax\15\hipGunKickAccel\250\hipGunKickSpeedMax\500\hipGunKickSpeedDecay\15\hipGunKickStaticDecay\1\hipViewKickPitchMin\100\hipViewKickPitchMax\150\hipViewKickYawMin\-50\hipViewKickYawMax\-80\hipViewKickCenterSpeed\1500\swayMaxAngle\30\swayLerpSpeed\6\swayPitchScale\0.1\swayYawScale\0.1\swayHorizScale\0.1\swayVertScale\0.1\swayShellShockScale\5\adsSwayMaxAngle\30\adsSwayLerpSpeed\6\adsSwayPitchScale\0.1\adsSwayYawScale\0.1\adsSwayHorizScale\0.1\adsSwayVertScale\0.1\hudIcon\hud_icon_rpg\killIcon\hud_icon_rpg\dpadIcon\hud_icon_rpg_dpad\ammoCounterIcon\hud_icon_rpg\hudIconRatio\4:1\killIconRatio\4:1\dpadIconRatio\1:1\ammoCounterIconRatio\4:1\ammoCounterClip\Rocket\flipKillIcon\1\worldModel\weapon_rpg7\worldModel2\\worldModel3\\worldModel4\\worldModel5\\worldModel6\\worldModel7\\worldModel8\\worldModel9\\worldModel10\\worldModel11\\worldModel12\\worldModel13\\worldModel14\\worldModel15\\worldModel16\\worldClipModel\\rocketModel\viewmodel_rpg7_rocket\knifeModel\viewmodel_knife\worldKnifeModel\weapon_parabolic_knife\ammoName\rpg\maxAmmo\2\startAmmo\2\clipName\rpg_mp\clipSize\1\dropAmmoMin\1\dropAmmoMax\2\viewFlashEffect\muzzleflashes/at4_flash\worldFlashEffect\muzzleflashes/at4_flash\shellEjectEffect\\lastShotEjectEffect\\worldClipDropEffect\\pickupSound\weap_pickup\pickupSoundPlayer\weap_pickup\ammoPickupSound\\ammoPickupSoundPlayer\\projectileSound\weap_rpg_loop\fireSound\weap_rpg_fire_npc\fireSoundPlayer\weap_rpg_fire_plr\lastShotSound\\lastShotSoundPlayer\\emptyFireSound\weap_dryfire_rifle_npc\emptyFireSoundPlayer\weap_dryfire_rifle_plr\meleeSwipeSound\melee_swing_ps_large\meleeSwipeSoundPlayer\melee_rpg_swing_plr\rechamberSound\\rechamberSoundPlayer\\reloadSound\\reloadSoundPlayer\\reloadEmptySound\\reloadEmptySoundPlayer\\reloadStartSound\\reloadStartSoundPlayer\\reloadEndSound\\reloadEndSoundPlayer\\altSwitchSound\\altSwitchSoundPlayer\\raiseSound\weap_rpg_raise_npc\raiseSoundPlayer\weap_rpg_raise_plr\firstRaiseSound\\firstRaiseSoundPlayer\\putawaySound\weap_rpg_drop_npc\putawaySoundPlayer\weap_rpg_drop_plr\bounceSound\\nightVisionWearSound\\nightVisionWearSoundPlayer\\nightVisionRemoveSound\\nightVisionRemoveSoundPlayer\\reticleCenter\reticle_flechette\reticleSide\\reticleCenterSize\32\reticleSideSize\24\reticleMinOfs\17\enemyCrosshairRange\1000\crosshairColorChange\1\altWeapon\\boltAction\0\aimDownSight\1\rechamberWhileAds\1\adsViewErrorMin\0\adsViewErrorMax\0\adsFire\1\noAdsWhenMagEmpty\0\avoidDropCleanup\0\cancelAutoHolsterWhenEmpty\0\suppressAmmoReserveDisplay\0\blocksProne\0\noPartialReload\0\reloadAmmoAdd\1\autoAimRange\0\aimAssistRange\1000\aimAssistRangeAds\1000\fightDist\720\maxDist\1400\aiVsAiAccuracyGraph\\aiVsPlayerAccuracyGraph\\standMoveF\0\standMoveR\0\standMoveU\-1.7\standRotP\0\standRotY\0\standRotR\0\duckedOfsF\-2\duckedOfsR\0.8\duckedOfsU\-0.2\duckedMoveF\-1\duckedMoveR\0\duckedMoveU\-1.7\duckedRotP\0\duckedRotY\0\duckedRotR\0\proneOfsF\-2\proneOfsR\1\proneOfsU\-1\proneMoveF\-160\proneMoveR\3\proneMoveU\-120\proneRotP\0\proneRotY\300\proneRotR\-300\posMoveRate\6\posProneMoveRate\25\standMoveMinSpeed\110\duckedMoveMinSpeed\60\proneMoveMinSpeed\0\posRotRate\6\posProneRotRate\30\standRotMinSpeed\110\duckedRotMinSpeed\60\proneRotMinSpeed\0\explosionRadius\300\explosionInnerDamage\160\explosionOuterDamage\30\damageConeAngle\180\projectileSpeed\1500\projectileSpeedUp\500\projectileActivateDist\0\projectileLifetime\5\projectileModel\projectile_rpg7\projExplosionType\rocket\projExplosionEffect\\projExplosionEffectForceNormalUp\0\projExplosionSound\\projDudEffect\\projDudSound\\projImpactExplode\1\projTrailEffect\smoke/smoke_geotrail_rpg\projectileDLight\200\projectileRed\0.75\projectileGreen\0.3\projectileBlue\1\projIgnitionDelay\0\projIgnitionEffect\\projIgnitionSound\\destabilizationRateTime\0.4\destabilizationCurvatureMax\10\destabilizeDistance\300\parallelDefaultBounce\0.5\parallelBarkBounce\0.5\parallelBrickBounce\0.5\parallelCarpetBounce\0.5\parallelClothBounce\0.5\parallelConcreteBounce\0.5\parallelDirtBounce\0.5\parallelFleshBounce\0.5\parallelFoliageBounce\0.5\parallelGlassBounce\0.5\parallelGrassBounce\0.5\parallelGravelBounce\0.5\parallelIceBounce\0.5\parallelMetalBounce\0.5\parallelMudBounce\0.5\parallelPaperBounce\0.5\parallelPlasterBounce\0.5\parallelRockBounce\0.5\parallelSandBounce\0.5\parallelSnowBounce\0.5\parallelWaterBounce\0.5\parallelWoodBounce\0.5\parallelAsphaltBounce\0.5\parallelCeramicBounce\0.5\parallelPlasticBounce\0.5\parallelRubberBounce\0.5\parallelCushionBounce\0.5\parallelFruitBounce\0.5\parallelPaintedMetalBounce\0.5\perpendicularDefaultBounce\0.5\perpendicularBarkBounce\0.5\perpendicularBrickBounce\0.5\perpendicularCarpetBounce\0.5\perpendicularClothBounce\0.5\perpendicularConcreteBounce\0.5\perpendicularDirtBounce\0.5\perpendicularFleshBounce\0.5\perpendicularFoliageBounce\0.5\perpendicularGlassBounce\0.5\perpendicularGrassBounce\0.5\perpendicularGravelBounce\0.5\perpendicularIceBounce\0.5\perpendicularMetalBounce\0.5\perpendicularMudBounce\0.5\perpendicularPaperBounce\0.5\perpendicularPlasterBounce\0.5\perpendicularRockBounce\0.5\perpendicularSandBounce\0.5\perpendicularSnowBounce\0.5\perpendicularWaterBounce\0.5\perpendicularWoodBounce\0.5\perpendicularAsphaltBounce\0.5\perpendicularCeramicBounce\0.5\perpendicularPlasticBounce\0.5\perpendicularRubberBounce\0.5\perpendicularCushionBounce\0.5\perpendicularFruitBounce\0.5\perpendicularPaintedMetalBounce\0.5\fireRumble\\meleeImpactRumble\\adsDofStart\0\adsDofEnd\0\requireLockonToFire\0\notetrackSoundMap\weap_rpg_raise_plr weap_rpg_raise_plr weap_rpg_drop_plr weap_rpg_drop_plr melee_knife_stab melee_knife_stab weap_rpg_lift_plr weap_rpg_lift_plr weap_rpg_insert_plr weap_rpg_insert_plr weap_rpg_twist_plr weap_rpg_twist_plr
</pre>

*I have changed the display name of the weapon, and it's viewmodel. It will look like your model in first person view, but will still be an rpg in other people's hands and thirdperson. For more info on modding weaponfiles, Shadowlance194 wrote a tutorial here: http://www.modsonline.com/Tutorials-read-466.html

*This weaponfile needs to go in the mod IWD\weapons\mp folder, and also needs to be referenced in the mod csv:

weapon,mp/rpg_mp

'''Outline of updating model process:'''

*Save model in Maya
*Open Cod4 export plugin, tick 'entry1' & Select Exports, Set Exports if the geometry has changed
*Edit version number in .xmodel_export
*Convert model & materials in Asset Manager
*Put textures in IWD, re-build fastfile

{{Warning|'''NOTES AND WARNINGS:'''}}
*This is quite complicated, with a lot of things that can go wrong.
*There is no way to reverse the conversion; you can't get an xmodel_export from an xmodel file. You also can't re-import the xmodel_export into Maya, like in old versions of Cod, so don't lose the source!
*You will find that the weapon model looks very small in thirdperson view, or if you are looking at someone else who has it. You need to create a separate worldmodel for it, because for some reason they are on different scales. On estimate, the worldmodel needs to be around twice as large.
*There are three joints on this model. The one at the front, tag_flash, defines where the muzzleflash effect will be.
*The actual position of the weapon in your hand is the position of the weapon model relative to 0,0,0 in Maya, none of the joints control it.
*If you only edit a stock weaponfile, you don't need to worry about precaching it. However, if it's not stock, you need to add a line in your mod scripts: PrecacheItem("weaponfile_name");

[http://customcollegeessays.com/index.php college essay]

[[Category:Call of Duty 4]]
[[Category:Call of Duty 5]]
[[Category:Modtools]]
[[Category:Radiant]]
[[Category:Advanced Editing]]
[[Category:Modelling]]
[[Category:Maya]]

Call of Duty 4: Gametypes

2011-06-24T12:05:32Z

Randallphillips:

''by Tally''

{{Note|Adding CTF/CTFB to your new map is easy. The only level requirement is that you must have SAB spawn points. (if you dont have SAB spawns, it can still be done)}}

Essentailly, I spawn a '''trigger_radius''' for each team's flag. I give each team's trigger_radius a '''targetname''' which the code in the CTF/CTFB gametypes looks for. It then dynamically spawns a flag model onto that trigger_radius.

All you have to do is copy the level GSC template below and use it for your own map:

*Here is the level GSC from mp_backlot used in AWE4 for CTF and CTFB:

<pre>main()
{
maps\mp\mp_backlot_fx::main();
maps\createart\mp_backlot_art::main();
maps\mp\_load::main();

maps\mp\_compass::setupMiniMap("compass_map_mp_backlot");

//setExpFog(500, 2200, 0.81, 0.75, 0.63, 0);
//VisionSetNaked( "mp_backlot" );
ambientPlay("ambient_backlot_ext");

game["allies"] = "marines";
game["axis"] = "opfor";
game["attackers"] = "axis";
game["defenders"] = "allies";
game["allies_soldiertype"] = "desert";
game["axis_soldiertype"] = "desert";

setdvar( "r_specularcolorscale", "1" );

setdvar("r_glowbloomintensity0",".25");
setdvar("r_glowbloomintensity1",".25");
setdvar("r_glowskybleedintensity0",".3");
setdvar("compassmaxrange","1800");

'''if( getDvar("g_gametype") == "ctf")'''
{
'''addobj('''"allied_flag", [color=yellow](-486, 1998, 64)[/color], (0, 0, 0));
'''addobj('''"axis_flag", [color=yellow](630, -2067, 64)[/color], (0, 0, 0));
}

'''if(getDvar("g_gametype") == "ctfb")'''
{
'''addobj('''"allied_flag", [color=yellow](-486, 1998, 64)[/color], (0, 0, 0));
'''addobj('''"axis_flag", [color=yellow](630, -2067, 64)[/color], (0, 0, 0));
}
}

'''addobj(name, origin, angles)
{
ent = spawn("trigger_radius", origin, 0, 48, 148);
ent.targetname = name;
ent.angles = angles;
}'''</pre>

*Use the code above for CTF and CTFB (not all of the level code, of course - just the relevant CTF, and CTFB bits. You dont want mp_backlot code in your map), and copy/paste it into your own map's GSC file.

*Notice the coordinates in yellow? You have to change them to suit your map.'''Here's how:'''

*Go into your map, and go to the point that you think the allied flag should go.

*Drop down console and type:

<pre>/viewpos</pre>

* Close

*Go to the next place, you think the axis flag should go, and do the same viewpos.

*Come out of your map.

*Look in the fs_game mod folder for the mp_console.log file, and open it.

*Find the viewpos coordinates you just did, and copy/paste them into the relevant teams code.

*Once in your map GSC file, '''subtract 60''' from the 'z' corodinate ( they are listed like this - (x, y, z)). This is because viewpos is taken from the players eye level, and floor level is 60 units less than the eye level.

{{Warning|''' Make sure the right coordinates go with the right team - remember: allies have the '''"allied_flag"''' targetname; axis the '''"axis_flag"''' targetname.}}

*You can now either compile your map's GSC file into your map's fast file, or simply include it in your map's IWD file.
 

CTF/CTFB is now included in most mods, such as AWE4, ACE and X4.

[[Category:Call of Duty 4]]
[[Category:Gametypes]]
[[Category:Modding]]
[[Category:AWE]]

[http://essaywritingservices.org/prices.php write my essay]

Call of Duty 4: HUD/Key description

2011-06-24T12:04:41Z

Randallphillips:

[[Image:call-of-duty-4-modern-warfare-3.jpg|center|800px]]
 
--[[User:Zeroy|Zeroy.]] 12:30, 27 April 2009 (UTC)

[[Category:Call of Duty 4]]

[http://essaywritingservices.org/prices.php write my paper]

Call of Duty 4: FastFile Format

2011-06-24T12:04:31Z

Randallphillips:

[[Image:Under Construction Small.png‎]] '''*** Article and investigation in early progress ***'''

== Preface ==

Be aware, FF files are little endian, so swap those bytes 'round!

The data block types (also called "index identifier") are written in big endian in this article, e.g. 00 00 00 1F is actually 1F 00 00 00 in ff, although ints and floats in the examples are kept little endian!

The global file layout starts with a header. After which you get a string list (model tag names, animation notetracks, maybe more; not always present). Followed by an index list. This list gives information about the rest of the file, which is a concatenation of compiled files (reinterpreted and linked data generated from source files like d3dbsp and stringtables, hereinafter referred to as data blocks).

* Header
* String list index
* String list
* Data block index
* Data blocks

Each file is separated by the separation key: 0xFFFFFFFF. But be aware, each file itself can also contain such a sequence which is not meant to be the separation key! So it is necessary to understand each data type in the FF file.

Edit: The latest research led to the assumption, that it's no real separation key but an address pointer (which is 0xFFFFFFFF if the data follows or 0x??????4? if the content is located elsewhere).

It seems to be 0xFFFFFFFF replaces pointers used during compilation, leading to the following data block structure in case of some data blocks (at least rawfile):

* Block header (containing one or more 0xFFFFFFFF pointers, size needs to be known to properly read files)
* Block data (one for each 0xFFFFFFFF data, can be anything from a string to raw binary data, possibly a 00 marks the end for strings?)

== Header ==

''(Note: not up to date and not generalized)''

*Byte 0-3: decompressed fastfile size minus 44 (0x2C)
*Byte 4-7: about the total size of referenced data, e.g. the required memory for IWI textures if material files are in the ff
*Byte 8-11: ''unknown'', might be a flag
*Byte 12-23: ''unknown''
*Byte 24-27: somehow related to ff size?
*Byte 28-43: ''unknown''
*Byte 44-47: equal to number of entries in "1st index" and amount of (model tag/joint/notetrack) strings (times 4 for index length)
*Byte 48-51: separator? (FF FF FF FF)
*Byte 52-55: number of records* ("2nd index", times 8 for index length)
*Byte 56-63: separator? (FF FF FF FF FF FF FF FF)
*Byte 64-x: string list (xmodelsurfs?) --> not always, depends on the content (required offsets are in the FF header)*

<nowiki>*</nowiki> under re-investigation 

=== Example: smallest possible fastfile (mod.ff) ===

<pre>
29 00 00 00 decompressed fastfile size minus 44
00 00 00 00
1C 00 00 00 unknown

00 00 00 00 00 00 00 00 00 00 00 00

0D 00 00 00 data size in memory (?)

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

01 00 00 00 one index entry

FF FF FF FF 1F 00 00 00 a rawfile

FF FF FF FF index end

FF FF FF FF start separator
00 00 00 00 rawfile length (empty, no errors occured during compilation)
FF FF FF FF separator
6D 6F 64 00 fastfile name as rawfile name
00 rawfile string (empty)
</pre>

=== Example: mp_backlot_load.ff ===

'''Contains:'''
*2x shaders
*3x materials
*(1x fastfile name)

Materials:
# $victorybackdrop - mile_high_victory_screen.iwi (699,092 bytes)
# $defeatbackdrop - (none)
# $levelbriefing - loadscreen_mp_backlot.iwi (524,316 bytes)

<pre>
----------- [start of file and header]

71 03 00 00 Decompressed file size - 44 (hex: 371 + 2C = 39D; dec: 881 + 44 = 925)

B8 AA 12 00 Size of both IWI's the materials in FF point to - 56 (2x28, 28 bytes = IWI header)
0x12AAB8 = 1,223,352
699,092 + 524,316 = 1,223,408
difference: 56

A4 00 00 00 Might be a flag

00 00 00 00 Unknown
00 00 00 00 Unknown
00 00 00 00 Unknown
E5 00 00 00 Size of fastfile in memory (that is at least without header and separators, and maybe more)
00 00 00 00 Unknown
00 00 00 00 Unknown
00 00 00 00 Unknown
00 00 00 00 Unknown

----------- [end of header] (44 bytes), [start of index]

00 00 00 00 Unknown, is sometimes FF FF FF FF

06 00 00 00 Number of records in index (6)

FF FF FF FF 05 00 00 00 1st: shader
FF FF FF FF 05 00 00 00 2nd: shader
FF FF FF FF 04 00 00 00 3rd: material
FF FF FF FF 04 00 00 00 4th: material
FF FF FF FF 04 00 00 00 5th: material
FF FF FF FF 1F 00 00 00 6th: rawfile

FF FF FF FF end separator (the following FF FF FF FF is the start seperator of the next data block!)

----------- [end of index]
</pre>

== Index ==

Starts with an int telling the number of dword couples. Such a couple is composed of 2 ints:

4 byte offset (FF FF FF FF = -1, meaning right after the previous block?) 
4 byte identifier (data block type)

Separator (FF FF FF FF) after last couple

=== Types ===

* xmodelpieces = 0,
* physpreset = 1,
* xanim = 2,
* xmodel = 3,
* material = 4,
* pixelshader = 5,
* techset = 6,
* image = 7,
* sndcurve = 8,
* loaded_sound = 9,
* col_map_sp = 0x0a,
* col_map_mp = 0x0b,
* com_map = 0x0c,
* game_map_sp = 0x0d,
* game_map_mp = 0x0e,
* map_ents = 0x0f,
* gfx_map = 0x10,
* lightdef = 0x11,
* ui_map = 0x12,
* font = 0x13,
* menufile = 0x14,
* menu = 0x15,
* localize = 0x16,
* weapon = 0x17,
* snddriverglobals = 0x18,
* impactfx = 0x19,
* aitype = 0x1a,
* mptype = 0x1b,
* character = 0x1c,
* xmodelalias = 0x1d,
* rawfile = 0x1f,
* stringtable = 0x20

== Content ==

Since there is a FF FF FF FF separator (respectively pointer) in front of every block and none at the very end (after last 1F-block), we can assume that each block has a start separation and no end separation. Thus, any FF FF FF FFs you find after data blocks are actually the start separators of the next block. This means the index end separator is rather FFFFFFFF than FFFFFFFFFFFFFFFF!

=== 00 00 00 04 (material) ===

<pre>
----------- [block start]

00 2B 01 01 First 4 bytes seem to be 4 (unsigned) char's.
1st byte is so far always 0x00 (perhaps it's a short together with the second byte).
2nd byte so far either 0x2B or 0x00, I think this is a length.
3rd byte so far 0x01, when 0x00 (all 4) the content is only a number of 0x00's, then the filename (0x00 termination)
4th byte either 0x00 or 0x01. Can be a length or a bool.
Then 0x10 bytes of more header.
FF FF FF FF Separator
00 When fourth byte is 01, there's a 0x00 following?
Then there's garbage (0xFF) and some shorts it looks of length in the second byte.
Then more information...
02 00 0E E0 Often ends with this

----------- [block end]
</pre>

=== 00 00 00 05 (shader) ===

A shader consists of 3 levels. One, the top level, consists of a header (with a name inside). Then the next level is a pack of shaders, it has a header, shaders and at the end a name. Then the bottom level is the shader itself, it has a header (containing a name of the source file and the length of the data) and the raw shader data.

<pre>
----------- [block start]

36 pointers (0x90 bytes) (bytes 0x19 up to 0x22 say if we get any content at all?)
?? ?? .. 00 Then techset file name (0x00 termination) if pointer is 0xFFFFFFFF?

----------- [start of shader pack]

pointer
1 dword of some character-length options / flags?
3 pointers
1 dword of some character-length sizes
FF FF FF FF Separator
0x64 bytes of some short length options / flags? If the second pointer above is 0xFFFFFFFF

----------- [start of shader]

pointer, if not 0xFFFFFFFF, no filename is further on
pointer, often 00 00 00 00
FF FF FF FF Separator
?? ?? 00 00 2 shorts, first short multiplied by 4 gives the length of the shader, second is a flag?
?? ?? .. 00 String if first pointer is 0xFFFFFFFF, 0x00 terminated (name of shader source file)
Raw shader file (except the first 4 bytes, which, in the shader file, denotes the length of the file)
FF FF 00 00 which ends with this (always?)

----------- [end of shader]

Can either have more shaders (go back to [start of shader]) or shaders have ended

Variable length of 'stuff' (technique commands?)
41 10 AB A0 which ends with this (always?)
?? ?? .. 00 String, 0x00 terminated (technique file name)

----------- [end of shader pack]

Can either have more shader packs (go back to [start of shader pack]) or shader packs have ended

----------- [block end]
</pre>

=== 00 00 00 06 (image) ===

Stores some information about the specified IWI in fastfile. Does not include the actual image data.
Length is 52 bytes + IWI name (+1 for string termination).

<pre>
----------- [block start]

03 00 00 00
FE FF FF FF separator?
00 00 00 00
00 00 00 00

70 55 01 00 IWI size minus 28 (0x1C)
70 55 01 00 same

00 01 00 01
01 00 03 00
FF FF FF FF separator?

73 70 .. 00 IWI name without file extension (string + termination, variable size)

00 00 00 01
00 01 01 00

44 58 54 35 00 00 00 00 fixed size char[] for type? (here: DXT5....)

----------- [block end]
</pre>

=== 00 00 00 13 (font) ===

See also [[Call of Duty: Font System]]. Implicitly adds shaders.

<pre>
----------- [block start] 216 byte + 2 strings
18 00 00 00 int font_size
BF 00 00 00 int number_of_records
FE FF FF FF ?
FE FF FF FF ?
FF FF FF FF separator
66 6F .. 00 string font_name (e.g. fonts/bigFont.)
FF FF FF FF separator
00 2B 01 01 ?
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
FF FF FF FF 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF 01 00 01 00 03 00
0D 00 00 40 pointer?
FF FF FF FF
00 00 00 00
FF FF FF FF
66 6F .. 00 string font_material (e.g. fonts/gamefonts_pc.)
41 10 AB A0 63 70 EB 00 ?

----------- [image block] 112 bytes + 1 string

FF FF FF FF start separator / pointer
03 00 00 00
FE FF FF FF separator?
00 00 01 00 ?
00 00 00 00
D0 AA 0A 00 IWI size minus 28 (0x1C)
D0 AA 0A 00 same
00 02 00 04
01 00 03 00 ?
FF FF FF FF separator
67 61 .. 00 IWI name
00 00 00 02
00 04 01 00 ?
44 58 54 35
00 00 00 00 compression (here: DXT5....)

----------- [unknown block] 168 bytes

65 91 28 19
02 00 0E E0 ?
FF FF FF FF separator?
00 04 01 01 ?
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
FF FF FF FF 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
01 00 01 00 03 00 ?
0D 00 00 40 pointer? (same as above)
FF FF FF FF separator?
00 00 00 00

----------- [font block] 48 bytes + 1 string + number_of_records * 24 bytes

FF FF FF FF separator/pointer
66 6F .. 00 font effect name? (e.g. fonts/gamefonts_pc_glow.)
41 10 AB A0
63 70 EB 00
95 06 00 40
25 91 28 19
02 00 0E E0 ?

?? ?? ?? ?? font file entries (24 bytes each)

----------- [block end]
</pre>

=== 00 00 00 16 (localized string asset) ===

A localized string asset consists of an alias name and a translated string. During compilation, it takes the given alias name (REFERENCE) from *.str file and prepands the *.str file's name in upper-case plus an underscore. Example:

'''example.str'''
<pre>VERSION "1"
CONFIG "C:\trees\cod3\cod3\bin\StringEd.cfg"
FILENOTES ""
//--------------------------------

REFERENCE MARINES_NAME
LANG_ENGLISH "US Airforce"

//--------------------------------
ENDMARKER</pre>

'''mod.ff'''
<pre>
ÿÿÿÿ
ÿÿÿÿ
EXAMPLE_MARINES_NAME.
US Airforce.
</pre>

Length is 8 bytes + string sizes (string count = 0-2, depends on the first two ints).

<pre>
----------- [block start]

FF FF FF FF either pointer or FFFFFFFF if the string wasn't used before
FF FF FF FF same. If two pointers are used here, then no strings will follow.
55 53 .. 00 alias name for the localized
53 54 .. 00 actual localized string

----------- [block end]
</pre>

=== 00 00 00 1F (rawfile) ===

A rawfile. Often a rawfile named right after the fastfile's name is implicitly added. It contains the errors thrown when it was compiling / linking.

<pre>
----------- [block start]

64 00 00 00 Length of the file's content (example: decimal 100; does not count the string termination!)

FF FF FF FF Separator

6D 6F 64 00 File name or if it's the last 1F-block FastFile name (example: mod.)
?? ?? .. 00 Plain text content of length above (string, terminated by 0x00)

----------- [block end OR even end of file]
</pre>

=== 00 00 00 20 (stringtable) ===

A compiled stringtable (comma separated list, *.csv). Even values are stored as strings.

<pre>
----------- [block start]

05 00 00 00 (int) columns
02 00 00 00 (int) rows

FF FF FF FF separator
?? ?? .. 00 filename (path/*.csv) + string termination (0x00)

----------- [table cell description]

?? ?? ?? ?? columns * rows integers (5 * 2 * 4 = 40 bytes in total, 5 * 2 = 10 cells)
FF FF FF FF - if the string wasn't used before and follows after the cell description
?? ?? ?? 4? - if an identical string was already used (in another csv). It is some kind of memory offset (pointer). Base address calculation not figured out yet (0x40000072 ?)

----------- [cell content / strings]

?? ?? .. 00 string + termination (0x00)
Number of strings = amount of FF FF FF FFs in table cell description

----------- [block end]
</pre>

--[[User:NTAuthority|NTAuthority]] 10:54, 3 June 2010 (UTC) (some tiny information)

--[[User:CoDEmanX|CoDEmanX]] 01:45, 8 December 2009 (UTC)

--[[User:Daevius|Daevius]] 23:00, 8 December 2009 (UTC)

[[Category:Call of Duty 4]]
[[Category:Technical Reference]]
[[Category:File formats]]



[http://cvresumewritingservices.org/ resume writing services]

Call of duty 4: Import models

2011-06-24T12:04:05Z

Randallphillips:

{{Warning_forpro}}
''By NovemberDobby''

{{Note|This tutorial will show you the basics of importing a new weapon model into Cod4. Below is my example, which you will hopefully be able to use.}}
{{Warning_advanced}}

[[Image:shot0097.jpg|center|600px]]

''You will be needing:''

*Maya 7.0 or 8.5 (not the Personal Learning Edition)
*Maya 8.0 requires a little hack (see below)
*The Cod4\bin\maya folder from the mod tools
*Texture(s) for your model: The dimensions have to be a power of two. (256*256, 512*512, etc), and the file must be a .jpg, .tga, or .dds. TGA and DDS textures can both have alpha channels, and can both be natively edited using Paint.net. (www.getpaint.net)
*My example weapon model, from [http://www.modsonline.com/Downloads-full-4308.html HERE]

*In this tutorial, I will assume you know Maya's basic controls. Firstly, I recommend you follow this tutorial, written by mdS [http://www.modsonline.com/Downloads-full-4254.html HERE]

*It shows you how to export a rigid model from Maya, and get it into the game using Asset Manager. It also shows you the first two steps needed to set up Maya to use the plugins. As these two steps are necessary, I'll explain them here, courtesy of Infinity Ward's Wiki.

== Maya 8.0 Fix ==

You can use the Maya 8.5 plugins (xmodel, xanim) which come with the CoD4 Mod Tools, in Maya 8.0. Just open the two MLL files with a [http://mh-nexus.de/en/hxd/ hex-editor], do a text search for '850' and replace it with '800'.

<pre>
Change 850 (hex 38 35 30 )
To --> 800 (hex 38 30 30 )

Offsets:
XAnimExport.mll - 0x2B10B
XModelExport.mll - 0x350EC
</pre>

850 is the version number v8.50, the Maya version the plugins are designed for. Maya v8.00 won't accept them, but if you change the version requirement like described above it will load the plugins. The Maya scripting engines probably didn't change a lot, thus you shouldn't experience any problems with the hacked plugins.

==MAYA Setup==

Create a Maya.env file in: C:\Documents and Settings\My Documents\maya\
and add the two lines below into it.

MAYA_SCRIPT_PATH = C:\Program Files\Activision\Call of Duty 4 - Modern Warfare\bin\maya\tools
MAYA_PLUG_IN_PATH = C:\Program Files\Activision\Call of Duty 4 - Modern Warfare\bin\maya\tools

This folder location will be different if you have the Steam version, or have installed Cod4 somewhere else. You also need to make a file called usersetup.mel in C:\Documents and Settings\\My Documents\maya\\scripts\
and add the following three lines to it:

source CODToolsMenu;
CODStartup;
CODToolsMenu;

Lastly, you need to extract the corret plugins for your version of Maya. Go to Cod4\bin\maya\tools, and open up either Maya7_plugins.zip or Maya8_plugins.zip. Extract the two files from that zip into the Cod4\bin\maya\tools folder.

==In MAYA==

* Ok, start up Maya, and you should see a Call Of Duty 4 menu at the top. Open my example weapon, and then save it as a Maya file in a folder called Cod5\model_export\maya_ex. Maya_ex is the name of your model for now, it can be anything as long as there are no spaces in the name. You can save the actual Maya file under any filename. Also, copy the textures out of my example file into the same folder you saved this into.

* To view and edit the texturing in this model, you need to use Hypershade. In Maya, go to {{Color|Window > Rendering Editors > Hypershade|yellow}}. You will be presented with a dialog box which shows you the textures in use along with some other stuff. In the top dark section, you should see four textures. The one called {{Color|'demo_wep_skin'|orange}} is the one we're interested in, the other three are there by default and you cannot remove them. You may have to re-locate the actual .tga texture which is being used, so double click on the demo_wep_skin, and you should see the main right hand side panel change in Maya. There should be a 'file1' tab there now, click on it. About halfway down this new page, you should see 'Image name'. Click on the folder icon to browse to the skin image, demo_weapon_skin.tga, and open it.

* There is one step that you need to do for each model that you export, otherwise they will appear totally black in Radiant and the game. Go to {{Color|Edit > Select All|yellow}}, and then to {{Color|Color > Apply color|yellow}}, but don't click on the menu button; click the small box to the right of it. In the {{Color|'Color Value'|orange}} frame, click on the coloured box, and select a full white colour from the colour selector that comes up. Click {{Color|'Apply color'|orange}}, and you should see your model become marginally brighter in the 3D window. You need to do this for every new model, or again if you add geometry to an existing model.

* This model has already been rigged with the correct joints needed to work as a weapon in Cod4, so, navigate to the Call Of Duty 4 menu, and click on Model Exporter. When the dialog box comes up, click on the 'Add new Entry' button. Tick the checkbox called 'Entry1', and then choose where you will export your model. This should be in the same folder as your Maya model, and should have a similar (if not the same) name.

* Next, in Maya's menus, go to Edit>Select All. Back in the Cod4 dialog, click on Set Exports in Entry1. This has set the polygons and joints that you want to export to the Cod4 model, and it's very rare that you won't want to export everything.

==MAYA: Convert==

You're now ready to convert the model to a useable format. In the Cod5 Model Export Window, click 'Select Exports', and 'Export Selected Entries'. If all goes well, a progress bar should pop up and reach 100%. It won't work unless you have clicked 'Select Exports' (or selected everything in Maya).

''You sould now have a .xmodel_export file in your model's folder in Cod5\model_export. If you do, continue to the steps below.''

==Asset Manager==

*Close Maya, and open up Cod4\bin\asset_manager.exe. You will see several buttons in the top left corner, along with a list. Scroll down to 'xmodel', and click 'New Entry'. You now need to enter the name of the model that you will use to access it ingame, and in Radiant. It can't have any spaces, and try not to make it too generic, pick something which will definitely be unique, e.g. db_laser_cannon. You will see a list of options for your model appear on the right hand side now, select 'animated' from the first drop-down menu. In the 'filename' field, click the browse (three dots) button to the right. Use this to locate and open your xmodel_export file that you made before.

*Save your Asset Manager file in Cod4\model_export. Anywhere else and it won't convert, but it won't have any errors.

To convert the xmodel_export, you need to edit the export file. Go to Cod4\model_export\modelfolder\, and open up the .xmodel_export in a text editor like notepd. You will see 'VERSION 8', this needs changing to 'VERSION 6'. Save and close it.

*Go back to Asset Manager, and click on your entry in xmodel. Go to PC Convert>Current Asset Only, and if it works, you should see 'Conversion done, hit key to continue'.

In the left hand scroll list, go to 'material', and click new entry. This entry must be the same name as the weapon texture you used in Hypershade, in this example, 'demo_wep_skin'. Change these properties of the material:

Materialtype = world phong
surfacetype = none
sort = default*
usage = not in editor

*Click the three dots symbol next to the 'Color map' box, and navigate to your .tga skin. If you want the skins to have a specular map aswell, you have to create a texture for that and browse for it, using 'Specular color map'. Do not use a Normal Map on your texture, because it'll stop the specular from working properly, on scopes and reflections.

*Re-save the Asset Manager file, it will only convert entries that are in the saved version.

*Select your material from the list on the left, and go to PC Convert>Current Asset Only. If all goes well, a black box should appear, and it'll eventually read 'Conversion done, hit key to continue'. You've now converted the texture for use with your model.

*If both your texture and your model have converted properly, you can now package them in your mod. I'm assuming you can use .csv files and know how to make a basic mod.ff. All of the textures must go in the mod's IWD, and if it doesn't have one, it needs one. The file structure is: IWD\images\, and the converted iwi images can be found in Cod4\raw\images.

==Creating the weapon's file==

For this example, we'll mod a stock weaponfile. (rpg_mp)

<pre>
WEAPONFILE \weaponType\projectile\weaponClass\rocketlauncher\impactType\rocket_explode\guidedMissileType\None\inventoryType\item\maxSteeringAccel\3000\displayName\Laser thingy\AIOverlayDescription\\modeName\\playerAnimType\rocketlauncher\gunModel\db_laser_cannon\gunModel2\\gunModel3\\gunModel4\\gunModel5\\gunModel6\\gunModel7\\gunModel8\\gunModel9\\gunModel10\\gunModel11\\gunModel12\\gunModel13\\gunModel14\\gunModel15\\gunModel16\\handModel\viewmodel_base_viewhands\isHandModelOverridable\0\idleAnim\viewmodel_rpg_idle\emptyIdleAnim\viewmodel_rpg_idle_empty\fireAnim\viewmodel_rpg_fire\lastShotAnim\viewmodel_rpg_fire\meleeAnim\viewmodel_M4m203_knife_melee_1\meleeChargeAnim\viewmodel_M4m203_knife_melee_2\reloadAnim\viewmodel_rpg_reload\raiseAnim\viewmodel_rpg_pullout\dropAnim\viewmodel_rpg_putaway\firstRaiseAnim\viewmodel_rpg_pullout\altRaiseAnim\viewmodel_rpg_pullout\altDropAnim\viewmodel_rpg_putaway\quickRaiseAnim\viewmodel_rpg_pullout\quickDropAnim\viewmodel_rpg_putaway\emptyRaiseAnim\viewmodel_rpg_pullout\emptyDropAnim\viewmodel_rpg_putaway\sprintInAnim\viewmodel_rpg_sprint_in\sprintLoopAnim\viewmodel_rpg_sprint_loop\sprintOutAnim\viewmodel_rpg_sprint_out\nightVisionWearAnim\\nightVisionRemoveAnim\\adsFireAnim\viewmodel_rpg_fire\adsLastShotAnim\viewmodel_rpg_fire\adsUpAnim\viewmodel_rpg_ads_up\adsDownAnim\viewmodel_rpg_ads_down\moveSpeedScale\1\adsMoveSpeedScale\1\sprintDurationScale\1\lowAmmoWarningThreshold\0.33\damage\1000\meleeDamage\135\fireDelay\0\meleeDelay\0.13\meleeChargeDelay\0.16\fireTime\0.33\meleeTime\0.8\meleeChargeTime\1.16\reloadTime\3.292\reloadShowRocketTime\0.1\reloadAddTime\1.17\dropTime\0.467\raiseTime\0.73\altDropTime\0.467\altRaiseTime\0.733\quickDropTime\0.25\quickRaiseTime\0.75\firstRaiseTime\0.73\emptyDropTime\0.467\emptyRaiseTime\0.73\sprintInTime\0.3\sprintLoopTime\1\sprintOutTime\0.3\nightVisionWearTime\0\nightVisionWearTimeFadeOutEnd\0\nightVisionWearTimePowerUp\0\nightVisionRemoveTime\0\nightVisionRemoveTimePowerDown\0\nightVisionRemoveTimeFadeInStart\0\clipOnly\0\adsTransInTime\0.5\adsTransOutTime\0.5\adsZoomFov\55\adsZoomGunFov\40\adsZoomInFrac\0.5\adsZoomOutFrac\0.1\adsOverlayShader\\adsOverlayReticle\none\adsOverlayInterface\none\adsOverlayWidth\240\adsOverlayHeight\240\adsBobFactor\1\adsViewBobMult\0\hipSpreadStandMin\5\hipSpreadDuckedMin\3.5\hipSpreadProneMin\2\hipSpreadMax\6\hipSpreadDuckedMax\6\hipSpreadProneMax\6\hipSpreadDecayRate\2.5\hipSpreadFireAdd\0.4\hipSpreadTurnAdd\0\hipSpreadMoveAdd\2.3\hipSpreadDuckedDecay\1.375\hipSpreadProneDecay\1.6\hipReticleSidePos\0\adsSpread\1.7\adsIdleAmount\25\hipIdleAmount\80\hipIdleSpeed\1\adsIdleSpeed\1\idleCrouchFactor\0.5\idleProneFactor\0.15\gunMaxPitch\30\gunMaxYaw\30\adsAimPitch\0\adsCrosshairInFrac\1\adsCrosshairOutFrac\0.2\adsReloadTransTime\0.6\adsGunKickPitchMin\-30\adsGunKickPitchMax\-20\adsGunKickYawMin\-17\adsGunKickYawMax\17\adsGunKickAccel\250\adsGunKickSpeedMax\1000\adsGunKickSpeedDecay\10\adsGunKickStaticDecay\1\adsViewKickPitchMin\20\adsViewKickPitchMax\95\adsViewKickYawMin\-10\adsViewKickYawMax\30\adsViewKickCenterSpeed\2500\hipGunKickPitchMin\-5\hipGunKickPitchMax\-3\hipGunKickYawMin\-15\hipGunKickYawMax\15\hipGunKickAccel\250\hipGunKickSpeedMax\500\hipGunKickSpeedDecay\15\hipGunKickStaticDecay\1\hipViewKickPitchMin\100\hipViewKickPitchMax\150\hipViewKickYawMin\-50\hipViewKickYawMax\-80\hipViewKickCenterSpeed\1500\swayMaxAngle\30\swayLerpSpeed\6\swayPitchScale\0.1\swayYawScale\0.1\swayHorizScale\0.1\swayVertScale\0.1\swayShellShockScale\5\adsSwayMaxAngle\30\adsSwayLerpSpeed\6\adsSwayPitchScale\0.1\adsSwayYawScale\0.1\adsSwayHorizScale\0.1\adsSwayVertScale\0.1\hudIcon\hud_icon_rpg\killIcon\hud_icon_rpg\dpadIcon\hud_icon_rpg_dpad\ammoCounterIcon\hud_icon_rpg\hudIconRatio\4:1\killIconRatio\4:1\dpadIconRatio\1:1\ammoCounterIconRatio\4:1\ammoCounterClip\Rocket\flipKillIcon\1\worldModel\weapon_rpg7\worldModel2\\worldModel3\\worldModel4\\worldModel5\\worldModel6\\worldModel7\\worldModel8\\worldModel9\\worldModel10\\worldModel11\\worldModel12\\worldModel13\\worldModel14\\worldModel15\\worldModel16\\worldClipModel\\rocketModel\viewmodel_rpg7_rocket\knifeModel\viewmodel_knife\worldKnifeModel\weapon_parabolic_knife\ammoName\rpg\maxAmmo\2\startAmmo\2\clipName\rpg_mp\clipSize\1\dropAmmoMin\1\dropAmmoMax\2\viewFlashEffect\muzzleflashes/at4_flash\worldFlashEffect\muzzleflashes/at4_flash\shellEjectEffect\\lastShotEjectEffect\\worldClipDropEffect\\pickupSound\weap_pickup\pickupSoundPlayer\weap_pickup\ammoPickupSound\\ammoPickupSoundPlayer\\projectileSound\weap_rpg_loop\fireSound\weap_rpg_fire_npc\fireSoundPlayer\weap_rpg_fire_plr\lastShotSound\\lastShotSoundPlayer\\emptyFireSound\weap_dryfire_rifle_npc\emptyFireSoundPlayer\weap_dryfire_rifle_plr\meleeSwipeSound\melee_swing_ps_large\meleeSwipeSoundPlayer\melee_rpg_swing_plr\rechamberSound\\rechamberSoundPlayer\\reloadSound\\reloadSoundPlayer\\reloadEmptySound\\reloadEmptySoundPlayer\\reloadStartSound\\reloadStartSoundPlayer\\reloadEndSound\\reloadEndSoundPlayer\\altSwitchSound\\altSwitchSoundPlayer\\raiseSound\weap_rpg_raise_npc\raiseSoundPlayer\weap_rpg_raise_plr\firstRaiseSound\\firstRaiseSoundPlayer\\putawaySound\weap_rpg_drop_npc\putawaySoundPlayer\weap_rpg_drop_plr\bounceSound\\nightVisionWearSound\\nightVisionWearSoundPlayer\\nightVisionRemoveSound\\nightVisionRemoveSoundPlayer\\reticleCenter\reticle_flechette\reticleSide\\reticleCenterSize\32\reticleSideSize\24\reticleMinOfs\17\enemyCrosshairRange\1000\crosshairColorChange\1\altWeapon\\boltAction\0\aimDownSight\1\rechamberWhileAds\1\adsViewErrorMin\0\adsViewErrorMax\0\adsFire\1\noAdsWhenMagEmpty\0\avoidDropCleanup\0\cancelAutoHolsterWhenEmpty\0\suppressAmmoReserveDisplay\0\blocksProne\0\noPartialReload\0\reloadAmmoAdd\1\autoAimRange\0\aimAssistRange\1000\aimAssistRangeAds\1000\fightDist\720\maxDist\1400\aiVsAiAccuracyGraph\\aiVsPlayerAccuracyGraph\\standMoveF\0\standMoveR\0\standMoveU\-1.7\standRotP\0\standRotY\0\standRotR\0\duckedOfsF\-2\duckedOfsR\0.8\duckedOfsU\-0.2\duckedMoveF\-1\duckedMoveR\0\duckedMoveU\-1.7\duckedRotP\0\duckedRotY\0\duckedRotR\0\proneOfsF\-2\proneOfsR\1\proneOfsU\-1\proneMoveF\-160\proneMoveR\3\proneMoveU\-120\proneRotP\0\proneRotY\300\proneRotR\-300\posMoveRate\6\posProneMoveRate\25\standMoveMinSpeed\110\duckedMoveMinSpeed\60\proneMoveMinSpeed\0\posRotRate\6\posProneRotRate\30\standRotMinSpeed\110\duckedRotMinSpeed\60\proneRotMinSpeed\0\explosionRadius\300\explosionInnerDamage\160\explosionOuterDamage\30\damageConeAngle\180\projectileSpeed\1500\projectileSpeedUp\500\projectileActivateDist\0\projectileLifetime\5\projectileModel\projectile_rpg7\projExplosionType\rocket\projExplosionEffect\\projExplosionEffectForceNormalUp\0\projExplosionSound\\projDudEffect\\projDudSound\\projImpactExplode\1\projTrailEffect\smoke/smoke_geotrail_rpg\projectileDLight\200\projectileRed\0.75\projectileGreen\0.3\projectileBlue\1\projIgnitionDelay\0\projIgnitionEffect\\projIgnitionSound\\destabilizationRateTime\0.4\destabilizationCurvatureMax\10\destabilizeDistance\300\parallelDefaultBounce\0.5\parallelBarkBounce\0.5\parallelBrickBounce\0.5\parallelCarpetBounce\0.5\parallelClothBounce\0.5\parallelConcreteBounce\0.5\parallelDirtBounce\0.5\parallelFleshBounce\0.5\parallelFoliageBounce\0.5\parallelGlassBounce\0.5\parallelGrassBounce\0.5\parallelGravelBounce\0.5\parallelIceBounce\0.5\parallelMetalBounce\0.5\parallelMudBounce\0.5\parallelPaperBounce\0.5\parallelPlasterBounce\0.5\parallelRockBounce\0.5\parallelSandBounce\0.5\parallelSnowBounce\0.5\parallelWaterBounce\0.5\parallelWoodBounce\0.5\parallelAsphaltBounce\0.5\parallelCeramicBounce\0.5\parallelPlasticBounce\0.5\parallelRubberBounce\0.5\parallelCushionBounce\0.5\parallelFruitBounce\0.5\parallelPaintedMetalBounce\0.5\perpendicularDefaultBounce\0.5\perpendicularBarkBounce\0.5\perpendicularBrickBounce\0.5\perpendicularCarpetBounce\0.5\perpendicularClothBounce\0.5\perpendicularConcreteBounce\0.5\perpendicularDirtBounce\0.5\perpendicularFleshBounce\0.5\perpendicularFoliageBounce\0.5\perpendicularGlassBounce\0.5\perpendicularGrassBounce\0.5\perpendicularGravelBounce\0.5\perpendicularIceBounce\0.5\perpendicularMetalBounce\0.5\perpendicularMudBounce\0.5\perpendicularPaperBounce\0.5\perpendicularPlasterBounce\0.5\perpendicularRockBounce\0.5\perpendicularSandBounce\0.5\perpendicularSnowBounce\0.5\perpendicularWaterBounce\0.5\perpendicularWoodBounce\0.5\perpendicularAsphaltBounce\0.5\perpendicularCeramicBounce\0.5\perpendicularPlasticBounce\0.5\perpendicularRubberBounce\0.5\perpendicularCushionBounce\0.5\perpendicularFruitBounce\0.5\perpendicularPaintedMetalBounce\0.5\fireRumble\\meleeImpactRumble\\adsDofStart\0\adsDofEnd\0\requireLockonToFire\0\notetrackSoundMap\weap_rpg_raise_plr weap_rpg_raise_plr weap_rpg_drop_plr weap_rpg_drop_plr melee_knife_stab melee_knife_stab weap_rpg_lift_plr weap_rpg_lift_plr weap_rpg_insert_plr weap_rpg_insert_plr weap_rpg_twist_plr weap_rpg_twist_plr
</pre>

*I have changed the display name of the weapon, and it's viewmodel. It will look like your model in first person view, but will still be an rpg in other people's hands and thirdperson. For more info on modding weaponfiles, Shadowlance194 wrote a tutorial here: http://www.modsonline.com/Tutorials-read-466.html

*This weaponfile needs to go in the mod IWD\weapons\mp folder, and also needs to be referenced in the mod csv:

weapon,mp/rpg_mp

'''Outline of updating model process:'''

*Save model in Maya
*Open Cod4 export plugin, tick 'entry1' & Select Exports, Set Exports if the geometry has changed
*Edit version number in .xmodel_export
*Convert model & materials in Asset Manager
*Put textures in IWD, re-build fastfile

{{Warning|'''NOTES AND WARNINGS:'''}}
*This is quite complicated, with a lot of things that can go wrong.
*There is no way to reverse the conversion; you can't get an xmodel_export from an xmodel file. You also can't re-import the xmodel_export into Maya, like in old versions of Cod, so don't lose the source!
*You will find that the weapon model looks very small in thirdperson view, or if you are looking at someone else who has it. You need to create a separate worldmodel for it, because for some reason they are on different scales. On estimate, the worldmodel needs to be around twice as large.
*There are three joints on this model. The one at the front, tag_flash, defines where the muzzleflash effect will be.
*The actual position of the weapon in your hand is the position of the weapon model relative to 0,0,0 in Maya, none of the joints control it.
*If you only edit a stock weaponfile, you don't need to worry about precaching it. However, if it's not stock, you need to add a line in your mod scripts: PrecacheItem("weaponfile_name");

[[Category:Call of Duty 4]]
[[Category:Call of Duty 5]]
[[Category:Modtools]]
[[Category:Radiant]]
[[Category:Advanced Editing]]
[[Category:Modelling]]
[[Category:Maya]]

[http://customcollegeessays.com/index.php college essay]

Call of Duty 4: Gameplay standards

2011-06-24T12:03:48Z

Randallphillips:

[[Category:Modtools]]
[[Category:Call of Duty 4]]
[[Category:Modding]]
[[Category:Radiant]]
[[Image:Nutshell.png]] Gameplay Standards are extremely important when mapping a level as they determine how the player will see the world but also how the gameplay will be affected. Building a doorway to small or a ledge too high might result in poor game flow...

== General ==

*1 COD World unit = 0.02778 yard
*1 COD World unit = 0.0254 meters

==Doorways and windows ==

Doorways = 56 units wide/96 units high

For high traffic areas it is sometime best to make it a double door.

Double door = 128 units wide/96 units high

Window Height = 32 units from floor to the bottom of the window frame.

Window Frame = minimum of 46 units wide 72 units high. (Inside diameter)

== Stairways ==

Interior = 8 high / 10 deep 64 unit min. width

== Mantles (Climbing) ==

The tallest distance a player will climb automatically is 18 units. However, while 18 is the limit, stairs and curbs should be around 8 units high.

The highest a player can mantle ("climb") is eye level (approx. 64 units). Of course, if the player jumps, their eye level goes higher and they can climb higher things - but they player won't see the mantle icon if their eye isn't above the ledge.

== Hallways ==

Hallways = 489 units wide

== Walls ==

Building wall/One story high = 128 units high

Wall thickness = 8 units

Columns = 32-48 units wide

A 32 unit wide column is barely enough to still offer valid cover for the player. And after the column_cover node animations have been added 32-48 units will also provide valid cover and firing angles from both sides of the column for AI as well.

== Streets ==

Large - Four car width = 600 units

Small - Two Tank width = 300 units

Alleyway – small street = 300 units wide

== Sidewalk ==

Small = 128 units wide

Medium = 192 units wide

Large = 256 units wide (this is more for Singleplayer levels)

== Cover ==

Standing cover height = 48 units high

Crouching = 32 units

Prone cover height = 16 units high

Prone crawling height clearance = 32 units high

== Engagement ranges ==

These would be the range at which a firefight takes place. These ranges make sure the player is shooting at a target that is a good size to hit and interact with. This will help keep the levels from getting too big and having pixel shooting distances.

There is a model in the game called mw_scale_soldier. It has two rings around him, one at 600 and one at 1024. Based off of COD2’s weapons settings, 512 was a good distance to shoot an SMG at a target and 1024 was a good distance for a rifle. These can be adjusted if the new weapons get changed drastically. You can drop the model in your level to make sure your geo is not getting too big.

== Player Models ==

Standing = 72 units

Crouch = 36 units

== Sources ==

[http://www.infinityward.com/wiki/index.php/Gameplay_standards IW Wiki]
[http://essaywritingservices.org/index.php essay writing service]

Call of Duty 4: Damage Charts

2011-06-24T11:41:23Z

Randallphillips:

[[Category:Call of Duty 4]]
[[Category:Weapons]]
[[Category:Technical Reference]]
== EXPLOSIVE DAMAGE RADIUS ==

[[Image:explosive.png]]

== VEHICLES/ DESTRUCTABLES ==

[[Image:Destructibles.png]]

== WEAPONS ==

[[Image:cod4gun.png]]

All sources [http://www.fpsbanana.com/tuts/games/605 Here]

[http://writing-help.org/ Writing help]

[http://essaywritingservices.org/prices.php write my paper]

Call of Duty 4: Demo Player

2011-06-24T11:41:10Z

Randallphillips:

[[Category:Call of Duty 4]]
[[Category:Tools]]
[[Category:Technical Reference]]
[[Image:Nutshell.png]] Tool for easy playing demos of game Call of Duty 4: Modern Warfare
You can use slowmotion, faster playing, freezing demo, toggle third person view and toggle view HUD info.

== Installation and run ==

1. Download file cod4player.zip (224 kB, cod4player.exe + readme.txt).
2. Just unzip file "cod4player.exe", but rather don't put it into the COD4 folder. Then simply run it.

== Controls ==

* In main screen click on the keybord to show info about controls.
* You can set association demos in Setup menu and then just click on demofile to playback.

[[Image:cod4player_1.jpg]]
[[Image:cod4player_3.jpg]]
[[Image:cod4player_2.jpg]]

== Restrictions ==

*If You have COD4 just as copy on HD (no info in registry), cod4player ask You for path to iw3mp.exe.
*Tested on Windows XP SP2 Czech version only (Windows Vista - not tested!)

BIG thanx to:
Player Rellik to idea "how to.." :)

== Download & Sources ==

[[Image:Data.png]] Download & Website [http://www.cybopat.net/vb_cod4player_eng.php HERE]

[http://writing-help.org/ essay writing help]

[http://customcollegeessays.com/index.php college essay]

Call of Duty 4: d3dbsp

2011-06-24T11:40:59Z

Randallphillips:

The .d3dbsp structure, Call of Duty 4's variant on the well-known BSP format, is rather difficult to decipher. Since it's a binary file you can't simply read it. A hexadecimal editor is the best tool in this case. I am still deciphering it myself, I will post anything I happen to get known of regarding the file format.

Be sure to read [http://www.geocities.com/cofrdrbob/bspformat.html here] and [http://en.wikipedia.org/wiki/BSP_(file_extension) here] before you even try to decipher it. Knowing what the technique is that BSP formatted maps use, could be handy as well. Also see [[Call of Duty 2: d3dbsp]] for more information.

Every number ending with an 'h' indicates its a number using the hexadecimal count system. For other numbers one can assume the decimal count system is used.

=Header & Lump index=
The file starts with 3 DWORDs: the header 'IBSP' indicating this is a BSP file originally designed by ID software. After these 4 initial bytes you find the BSP version number. CoD4 uses the version number 22 (16h), which is different from CoD2. The next 4 byte group is the amount of lumps in the current BSP. The number of lumps varies from 23 to 37. Without compiled light (test maps) you get 23 lumps or 24 with lights. Stock maps have usually 37.

After the first 12 header bytes is an array filled with DWORD pairs, indicating the lumps' '''IDs and lengths'''. No absolute offsets are stored in this so called lump index in contrast to previous CoD BSP versions (each lump is connected). One can determine offsets by taking the previous lump's offset + length (padded to a multiple of 4). The first lump's offset is <code>(3 + (number of lumps * 2)) * 4</code>. Nonetheless, the first data byte has the offset 0. Don't count the header and the lump index!

[[Image:Lightbulb.png]]'' Note: there can be a difference of number of lumps per map. If a map has a leak
(no solid skybox or not everything is IN the skybox) the bsp only has 24 lumps (or even 23 if light is not
compiled). The bsp description yet only supports the 37-lumps version (a valid map).''

==Variance==
Not all lumps are padded to a multiple of 4 in size. There are two exceptions:

*[[#Lump.5B0x07.5D_-_unknown|Lump[0x07] - unknown]], no padding
*[[#Lump.5B0x27.5D_-_Entities|Lump[0x27] - Entities]], no padding but +1 for c-string termination

==Example==
[[Image:D3DBSP_v22.png]]

Offset calculation of the first lump:
<pre>
00 00 00 00 | B0 C7 00 00
↓ | ↓ - Little Endian transfrom
00 00 00 00 | 00 00 C7 B0
↓ | ↓ - hex to dec
0 | 51120
Lump ID | Lump length

Start offset = Header length + Lump index length
= (3 + (39 * 2)) * 4
= 324

End offset = Start offset + Lump length
= 51120 + 324
= 51444

Start offset | End offset
324 | 51444
↓ | ↓ - dec to hex
144 | C8 F4
</pre>

=Lumps=

==Lump[0x00] - Materials==
''former texture filename + flags''

Texture information is 72 bytes long per texture. The first 64 bytes are used for the texture name. Then we have an DWORD for flags, and another DWORD for content flags.

==Lump[0x01] - Lightmaps==
3,145,728 bytes (3,072 kb) per entry.

==Lump[0x02] - Light Grid Points==
4 bytes per entry.

==Lump[0x03] - Light Grid Colors==
168 bytes per entry.

==Lump[0x04] - Planes==
16 bytes per entry.

==Lump[0x05] - Brush Sides==
8 bytes per entry.

==Lump[0x06] - unknown==
Equal to count of brush sides?

==Lump[0x07] - unknown==
 

==Lump[0x08] - Brushes==
4 bytes per entry.

==Lump[0x09] - Layered Tri Soups==
24 bytes per entry.

==Lump[0x0A] - Layered Verts==
''ID 0Ah = 10'', former Vertex Data 
68 bytes per entry.

==Lump[0x0B] - Layered Indexes==
''ID 0Bh = 11'' 
2 bytes per entry.

==[Lump[0x13] - Portal Verts==
''ID 13h = 19'' 
12 bytes per entry.

==Lump[0x18] - Layered AABB Trees==
''ID 18h = 24'' 
12 bytes per entry.

==Lump[0x19] - Cells==
''ID 19h = 25, former Bounding Box'' 
112 bytes per entry.

==Lump[0x1A] - Portals==
''ID 1Ah = 26'' 
16 bytes per entry.

==Lump[0x1B] - Nodes==
''ID 1Bh = 27'' 
36 bytes per entry.

==Lump[0x1C] - Leafs==
''ID 1Ch = 28'' 
24 bytes per entry.

==Lump[0x1D] - Leaf Brushes==
''ID 1Dh = 29'' 
4 bytes per entry.

==Lump[0x1F] - Collision Verts==
''ID 1Bh = 31, former assumed as nodes'' 
12 bytes per entry.

==Lump[0x20] - Collision Tris==
''ID 20h = 32''
6 bytes per entry.

==Lump[0x21] - Collision Edge Walk==
''ID 21h = 33'' 
Variable in length.

==Lump[0x22] - Collision Borders==
''ID 22h = 34'' 
28 bytes per entry.

==Lump[0x23] - Collision Parts==
''ID 23h = 35'' 
12 bytes per entry.

==Lump[0x24] - Collision AABBs==
''ID 24h = 36'' 
32 bytes per entry.

==Lump[0x25] - Models==
''ID 25h = 37'' 
48 bytes per entry.

==Lump[0x27] - Entities==
''ID 27h = 39, also known as EntData'' 
Varying bytes per entry depending on size of entity. Basically a char[] terminated by a binary zero (=string).
The entities lump is readable and stored almost the same way described in the [[Call_of_Duty_4:_.MAP_file_structure#Entity|.MAP file structure]].

==Lump[0x28] - Paths ==
''ID 28h = 40'' 
Variable in length.

==Lump[0x29] - Reflection Probes==
''ID 29h = 41'' 
131,140 bytes (128 kB) per entry.

==Lump[0x2A] - Layered Data==
''ID 2Ah = 42'' 
Variable in length.

==Lump[0x2B] - Primary Lights==
''ID 2Bh = 43'' 
128 bytes per entry.

==Lump[0x2C] - Light Grid Header==
''ID 2Ch = 44'' 
50 bytes per entry? (variable in length?)

==Lump[0x2D] - Light Grid Rows==
''ID 2Dh = 45'' 
16 bytes per entry? (variable in length?)

==Lump[0x2F] - Simple Tri Soups==
''ID 2Fh = 47'' 
24 bytes per entry.

==Lump[0x30] - Simple Verts==
''ID 30h = 48, former Vertex Data'' 
68 bytes per entry. - Redundancy??

==Lump[0x31] - Simple Indexes==
''ID 31h = 49'' 
2 bytes per entry.

==Lump[0x33] - Simple AABB Trees==
''ID 33h = 51'' 
12 bytes per entry.

==Lump[0x34] - Light Regions==
''ID 34h = 52'' 
1 byte per entry.

==Lump[0x35] - Light Region Hulls==
''ID 35h = 53'' 
76 bytes per entry.

==Lump[0x36] - Light Region Axes==
''ID 36h = 54'' 
20 bytes per entry.

==Unidentified lumps==
Predicted lump IDs in brackets:

*[0x1E] Leaf Surfaces
*[0x??] Visibility
*[0x??] Cull Groups
*[0x??] Cull Group Indexes

Note: If not listed, either missing or ID not in use.

=BSP data in FastFile=
Even though IW said the fastfiles were encrypted, in fact they are zlib-compressed memory dumps with a 12 byte header. Due to the process of building a fastfile, the linker loads all files (referenced in the csv) into memory. Assumedly, this happens in the same fashion like the game engine loads the data for later use into a large data structure (might be a database, have a look at the console messages). It seems that there is a pre-processing or a different way of storing the bsp data at runtime. Whether or not active changes are made, the data differs in any case. At this point it looks difficult to get all desired data, but the fastfile construction is still under investigation.

<pre>
(Almost) unchanged lumps: 2, 3, ? 7?, 31, 32, 33, 34, 36, 44, 45, 52
Partially changed: 0, 1, 19, 35, 37, 39, 53, 54
Not or hardly recognizable: 4, 5, 6?, 8, 9, 10, 11, 24, 25, 26, 27, 28, 29, 42, 43, 47, 48, 49, 51
</pre>

[[Image:Under Construction Small.png]]

@Daevius: I couldn't find Lump 41 (5,114,460 bytes) and wasn't able to clearly identify the 9th and 10th lump (in order of the index). Lengths look good, but offsets seem to be screwed. 605 bytes of entity data (29th lump) are at the end of the 28th, in the entity lump are 285 bytes data of the following lump in return.

--[[User:CoDEmanX|CoDEmanX]] 03:04, 28 March 2009 (UTC)

''Made by Daevius, CoDEmanX & Silicone_Milk''

[[Category:Call of Duty 4]]
[[Category:Technical Reference]]
[[Category:File formats]]

[http://cvresumewriters.com/ resume writers]

[http://essaywritingservices.org/prices.php write my essay]

Call of Duty 4: Custom Skyboxes

2011-06-24T11:40:53Z

Randallphillips:

[[Category:Call of Duty 4]]
[[Category:Modtools]]
[[Category:Radiant]]
[[Category:Advanced Editing]]
[[Category:Skybox]]
{{warning_forpro}}

[http://www.planetside.co.uk/terragen '''Terragen'''] is a freeware scenery generator which can be used to create 2D skyboxes. The freeware version has a limitation that effectively limits the texture dimensions of the skybox to 960, so it can only really be used for skies at 512x512. If Terragen is registered for $99 (US), the size limitation is removed, so skies at 1024x1024 could potentially be rendered.

This tutorial will explain how to use a scene in Terragen to create a 2D skybox that can be used in Cod4 Radiant.

Here is an example of what you can achieve (no land on this one)

[[Image:skyrender0001.jpg|400px]]

'''Creating the scene'''

Terragen can be downloaded [http://www.planetside.co.uk/terragen/win/downloadwin.shtml HERE]

Terragen takes a little bit of practice to get the hang of. There are many websites that can teach you the basics. Here are some good ones:

* [http://www.planetside.co.uk/terragen/guide/ ''The official guide'']
* [http://individual.utoronto.ca/edegiuli/TGtut/TerragenTutMain.html ''Terragen tutorial by E. DeGiuli'']

Create your scene and save it. The camera position doesn't matter for now. Terragen can render realistic land if you're very skilled however making terrain is not recommended for a 2D skybox.

'''Set up the script'''

The skybox requires six images to be rendered. This script will automate the creation of all six so you do not have to repeatedly come back to your computer and readjust the camera after each render.

Use Notepad to save the following script as skyboxscript.tgs. It can be saved anywhere.

<pre>
initanim "C:\skyrender", 1

;_ft
Zoom 1.0
CamH 0
CamP 0
CamB 0
frend

;_lf
Zoom 1.0
CamH 90
CamP 0
CamB 0
frend

;_up
Zoom 1.0
CamH 270
CamP 90
CamB 0
frend

;_bk
Zoom 1.0
CamH 180
CamP 0
CamB 0
frend

;_rt
Zoom 1.0
CamH 270
CamP 0
CamB 0
frend

;_dn
Zoom 1.0
CamH 270
CamP -90
CamB 0
frend
</pre>

'''Render the skybox'''

A. Now, in Terragen, uncheck both of the Fixed Height Above Surface boxes in the Rendering Control window. Place your Terragen camera where you want the viewpoint of the skybox to be. What's important here is the Camera Position. The Camera Orientation doesn't matter. Note that changing the height can affect the appearance of the clouds even though the horizon is always in the same location.

[[Image:Terrastep1.jpg]]

B. Set the detail all the way up in the Rendering Control window. Set the width and height both to 512. This is the best you can do with the freeware version. If you have registered Terragen, set them both to 1024.

[[Image:Terrastep2.jpg]]

C. You should double check that you did the first two steps right so you don't waste a lot of time. Now, choose Execute Script... from the Terragen menu, and choose the file skyboxscript.tgs that you created earlier. Now the rendering will commence. It may take a couple of hours or more.

D. When the rendering is complete, a dialog will pop up saying the script is complete. Quit Terragen.

'''Get the textures ready'''

Now, if you open up the C: drive, you'll see six new BMP files. Rename them as follows, where xxxx is whatever you want to name your sky:

<pre>Original filename Change to
skyrender0001.bmp xxxxft.bmp
skyrender0002.bmp xxxxlf.bmp
skyrender0003.bmp xxxxup.bmp
skyrender0004.bmp xxxxbk.bmp
skyrender0005.bmp xxxxrt.bmp
skyrender0006.bmp xxxxdn.bmp </pre>

Use Photoshop or PaintShopPro to save them as TGA files (dont resize them!)into ...''Call of Duty 4 - Modern Warfare\texture_assets\skybox''. Create the folder if you have to.

'''Create the Material Skybox using Asset Manager'''

A. Open up the IW Asset Manager 
B. Select ''Material'' from the list, click ''New Entry'' and inout a name like ''sky_xxxxx'' 
C. Refer to the picture below for Asset Manager Settings 

[[Image:assman.jpg]]

D. For the Color map note that the pic with _ft needs to be loaded 
E. Press F10 to convert the new Asset 

Everything going well you will see your new Skybox in the texture list of Cod4 Radiant ;D - Good Luck!

--[[User:Zeroy|Zeroy.]] 14:49, 15 October 2008 (UTC)

[http://cvresumewriters.com/ resume writer]

[http://essaywritingservices.org/index.php essay writing service]

Call of Duty 4: Custom Dvars

2011-06-24T11:40:26Z

Randallphillips:

''By Drofder2004''

{{Note|Someone mentioned they did not know how to do custom dvars, instead of answering in a post, here is a quick scripting tutorial}}

<pre>
if(getdvar("<dvar>") == "")
setdvar("<dvar>", "<default>");
</pre>

(Code above in pseudocode)

"If dvar <dvar> is equal to nothing (if it doesn't exist)... 
...create dvar with default value"

Thats the bare basics.

Next you can create minimum and maximum values (if the dvar is numeric)

<pre>
if(getDvar("<dvar>") == "")
setDvar("<dvar>", "<default>");

else if(getDvarInt("<dvar>") > 10)
setDvar("<dvar>", 10);

else if(getDvarInt("<dvar>") < 0)
setDvar("<dvar>", 0);
</pre>

Again, pseudocode, starting at line 3 (continued from above).

...else, if the dvar is greater than 10, set the dvar to 10, or 
...if the dvar is less than 0, set it to 0.

Make sure you get you note the usage of getDvar and getDvarInt (also, you can use getDvarFloat, to retrieve decimal values).

And finally, using the dvar in your script.
Now, there are many ways to use the dvar, but the main way is to use it as a variable.

<pre>
if(getDvar("<dvar>") == "")
setDvar("<dvar>", "<default>");

else if(getDvarInt("<dvar>") > 10)
setDvar("<dvar>", 10);

else if(getDvarInt("<dvar>") < 0)
setDvar("<dvar>", 0);

<variable> = getDvarInt("<dvar>");
</pre>

Remeber, use the correct 'getDvar', use...

*getDvar for TEXT based dvars (example: <code>getDvar("g_gametype");</code> )
*getDvarInt for INTEGERS (whole number, example: <code>getDvarInt("scr_forcerespawn");</code> )
*getDvarFloat for FLOATS (decimals, example: <code>getDvarFloat("scr_hq_timelimit");</code> )

{{Info|Another good use, is to use the dvar as a wait command}}

For example,

<pre>
main()
{
while(getDvar("wait") != 0)
{
wait 1;
}

iprintln("Wait dvar is equal to 0");
}</pre>

The <code>while()</code> in the above script will keep waiting 1 second, until the dvar is changed to 0, once changed, the main function will continue.

Now you know dvars!

==Sources==

[http://www.codjumper.com/forums/viewtopic.php?f=19&t=5388 CodJumper]

[[Category:Call of Duty 4]]
[[Category:Modding]]

[http://cvresumewritingservices.org/ resume services]

[http://cvresumewritingservices.org/ resume writing services]