Mech Commander Omnitech is standalone game.
There is no need for Mech Commander 2 installation nor disk.
There is no need for XNA installation any more for Mission Editor.

MCO 304
Link: http://www.moddb.com/mods/mechcommander-omnitech/downloads/mech-commander-omnitech-304

277: bugfix on delete array in missionBriefingScreen and missiongui.
278: ExtentRadius changed to be bigger for larger mechs
279: Variables defining removed heap sizes removed from the code.
280: Debugwins and variables removed from the code
281: Autosave file "Before_mission" added.
282: Mechlab bug - removed components saved to inventory fixed.
283: Players mechs are facing direction of the mission drop mech (first player unit in mission file)
shadowcat texture fix.Old Zeus replaced with Zeus mk2 model. Zeus mk2 to be replaced with another mech.
Buildings.csv fix - all dropships moved to air units. x_2_4 mission changed - components salvage added.
284: Cahnges in radio to prevent memory alloc if zero packet.
285: Problem with destroyed gates and pathfinding for longer disatnces fixed.
286: Bugfix in move.cpp - fixed redefinition of array(30) - mustbe 40+.
287: Many changes in define MAX variables in move.h and .cpp and other modules.Maps 180+ no longer crush on second load in solo.
Many checks added on delete or free. Misions MW2_1_1 and MW2_1_2 changed.
288: MW2_4_1 fix.
289: Saved variant name can go up to 20 characters (14). Crab icon. MW2_7_1 fix. Before_mission autosave for solo missions disabled.
290: PPC turret - new model. Bugfix in damage transfer from mission to logistics. Message window position changed.
Pilot ready screen fixed overlaping mech-pilot stats.
291: Mechlistbox and MechPurchase screen rewritten, no more crushes. Animation redesign - Fafnir and Warhammer2c (Karl).
New texture Warhammer2c (Karl).
292: Options - unlimited purchase implemented (components only for now). Options screen changed. Options.cfg changed - line for unlimited purchase added.
Change in logistics resolution selection.
293: Nova lGun joint fix.
294: Logistics resolution changes - logistics uses the same resolutons as mission.
295: Hi res offsets for logistics resolutions. ini files for logistic screens added for 1680 and 1920 res.
296: Logistics screens are in detected best supported resolution. Positions are calculated per offsets from ini files and 1280 as refernce.
297: Scaling for mech models and roataing weapon models for hi-res fixed. Hard coded cover rect for in pilot ready area moved to other rects.
298: Repair truck deploy reset if mission failed.
299: Salvage component changed to support CompCount. New Warhammer2c shadow (Karl).
300: Error in goblin pilot file fixed. Editor recompiled, xna-arm removed from editor obj manager.
301: Pilot radio under airstrike enabled.
302: Mech selection boxes for 2nd and 3rd line for offsets fixed. Pilot attribute metters not showing because of new cover rect fixed.
303: Fix: ECM shut down for dead or disabled mech with ECM. Fix: BlackJack eror in CSV file.
304: Editor is free of XNA.

MCO 269
241 :More detail and water textures.
242 : Minor building fixes (Karl), cement2 to 7 (Starman)
243 :
Extent radius for large vehicles returned/set to 20 (Starman).
Hollander.csv new variant (Starman).
Timberwolf fix (Karl).
MAX_SENSORS increased to 200 (+50).
Editor: message for max units on save changed from 104 to 192.

244 :Mw4 Cougar fixed - error in tgl incorrect ase export (6 weapon nodes), new Cougar model (6 weapon nodes).
245 : MAX_MOVERS_PER_TEAM increased to 150 (was 120). Max units for one team must be less then 150 (usually enemy).
Number of units plus number of sensor towers must be less then 200.
246 : AblStackHeap set to 4Mb.,Mission mw2_8_1_Wolcot added to mw2mercs campaign
247 : No salvage if mech too deep under water, removed gos_free in terrtxm.cpp.
248 : New mech - Stalker 11 weapon nodes, Nova mech - Changed torso - original was unusable.
249 : Button layout for lowest resolutions fixed, Stalker and Mist Lynx icons, New salvage values in salvage screen, armor and internal damage reduce the price, Players disabled mech can be salvaged for 10% of the price.
250 : Mech salvaged through salavge screen after mission are not auto-repaired.
251 : Hollander2.csv fix.
252 : Mech icon - Crossbow, MistLynx fix (Karl).
253 : UniversalBrain.abl file updated, 2 new component warehouses (new textures), Destroyed Nova fix, CanHaveECM will not be listed as ECM in weapons listbox for mechs. It is listed as a component.
254 : Null overlay index (terrain type) redefinition from 41 to 1, Both Editor and MCO recompiled, New mech Crab.
255 : Fixed crush on exit after last mission in campaign (save dropweight), New vehicle ACV.
256 : New vehicle Bulldozer, New vehicle Hummer
257 : New Argus texture, new shadow model (Karl).
258 : New BloodKite texture and shadow model (Karl)
259 : New Fafnir texture and shadow model (Karl)
260 : Fafnir texture fix (Karl)
261 : Changes in several modules per Echalon9s PVS studio changes, MaxVisualRange = 400 (gamesys.fit)
262 : New Champion model (Karl), 5 new textures for Karls models.
263 : 2 bugfixes per Echelon
264 : New mech Firefly (Karl - model by Starman)
265 : Firefly icon (Karl), Compbas min ranges for some weapons added, LRM range decreased.
266 :
Component stacking in components inventory and purchase.
Number of components can be set in purchase file:
l Component3 = 156 //Laser
l CompCount3 = 10
Game can read both new and old purchase files and combination (if CompCount is not found CompCount=1)

Mech variant can be set in purchase file:
st Mech1 = "Jenner"
l MechVariant1 = 1
Game can read both new and old purchase files and combination (if MechVariant is not found MechVariant=0)

Files mcl_c$ and mcl_mc changed in art folder - new text box definition for component count.
267 : Change in Component Purchase screen because of previous modifications.
268 : Lupus redesign (Karl).
269 : Hellfire redesign and Lupus fix (Karl). Mech purchase screen changes.

MCO 240
- Redesigned mission GUI - MC1 style,
- Damage transfer from mission to logistics,
- Repair buttons added to mechbay and mechlab.
- Every weapon has its own weapon range - new ranges calculation, simple math instead of predefined tables in mc2,
- ECM works as ECM umbrella now, all friendly mechs under ECM range are invisible for sensors, can be purchased and added to the mech in mechlab.
- New simple math calculations for LOS, increased LOS for high ground,
- New Beagle probe, increase sensor range and can detect shutdown mechs, can be purchased and added to the mech.
- max unit textures are now up to 512x512,
- max game detail textures... can go up to 1024x1024,
- new detail textures fixed that ugly looking terrain,
- new building textures, redesign of existing textures.
- redesigned old overlays and over 100 new overlays, cement, grass, terrain...
- additional ammo bins for all weapons,
- player can hire local mercs in mission if allowed by mission designer. Full control of those merc mech and vehicles for the duration of the mission,
- New Paved Road texture,
- High res damage icons are used for logistics and will show damage in logistics.
- Orange is added to damage colors.
- New MCO purchase file editor by Karl,
- New Arrow IV turret - model by Starman, texture by Karl.
- Quick load/save fix.
- New feature Resource points for the mission are now visible in mechbay, player can icrease or decrease the number just like the drop weight.
- Left click and drag disabled in mechbay and mechlab.
- Component salvage like in MC1
- new button design for mission gui.
- new button for repair truck - recharge your repair truck with one click (cost RPs).

ABL Commands:
NEW
- teleporttopoint(PartID, position),
- setbrain(PartID, brainFileName),
- togglesensorstrike;
- toggleartillerypiece;
- toggleairstrike;

Fixed/activated:
- setobjectivetype(objectiveID, type)
- checkobjectivetype(objectiveID)

Mechs:
Redesigned
- Summoner - magic.
- Timberwolf - Karl.
- Mad Dog - Karl.

EDITOR
NEW:
- Objective Action for Mission Editor - Add Component salvage (add a components FIT file containing number of salvage components and component list)

Bugfixes:
- Error when loading mission with destroyed building as first after start.
- Bugfix for MakenewtechnologyAvailable, Playwav and PlayBik
- Bugfix incorrect entry for additional purchase files.


MCO 156
I am sorry for problem with corrupted textures, it is fixed.

MCO 155
- K_lightgate fix

MCO 154
- left, right, up, down animations disabled in menus.
- tileHeap, tileRAMHeap eliminated.

MCO version 152
One new mech and 27 new buildings.
- New mech - Omen (Karl)
- Kurita building set - (Heavy, Medium, Light) Gate, Wall, Post and Kurita Turret Control (Karl)
- Petrol Station (Karl - model by Starman)
- MC1/G building set - CranePA (animated), Elemental Barracks, Farmhouse, Field Storage, Hanger, 6 Kurita Houses, 5 Office Buildings Variants (Karl)

MCO version 151
- exodus x_2_5 mission fix (mission was impossible because of new feature, indirect fire without LOS).
- 1 bug and 3 possible problems fixed.
- folders missions and textures cleanup.
- Flyer units movement changes reversed. This should fix many problems in released 3rd party campaigns.

MCO version 148
More then 50 problems, bugs and fixed limits in the code fixed.
Improved stability.
Crushes for large maps (200) fixed.

MCO version 143
- Object2 changed files for all my buildings (impassablewhendestroyed)
- Long Tom projectile speed doubled.
- bug - invalid normal fixed (crush in base aries mission and possibly more missions. Function with two arguments with the second argument defaulted to NULL if omitted. At one place in the function value is assigned to second argument without checking its existence.)

MCO version 141
- textureCacheHeap and textureStringHeap eliminated
- colorMapHeap and colorMapRAMHeap eliminated
- craterPosHeap, cratershpHeap and craterList heap eliminated
- mapData heap eliminated
- Indirect fire weapons can fire if target is in range (no need for LOS)
- Crater texture loaded as separate var.
- Flyer units dynamics fixes.
- impassableWhenDestroyed for buildings activated. Set to False in building.fit file and destroyed building will be passable in game.
- impassableWhenDestroyed changed in all fit files for buildings in MCO objects folder.

MCO version 133
Mechs are free of mc2res.dll for logistics.

MCO version 132
REmodeled buildings: Barracks, Chemical Plant, Dome, HQ, Hangar,
Industrial complex, Liquid Storage - (Karl - models Hades)
Popup MRM Turrets anim fix (karl)
New buildings: Factory, Dome (karl)
New Salamander Armor as mech (karl - model by ThorC).
REmodeled buildings: 2StoryCivLiving (karl)
Fixed: Elemental (new animation - karl), Factory, Dome (Karl).
New Building: Windmill Port Arthur variant (karl)
Editor buiding groups fix.
Exodus and MW2 missions fixes - l modelID = ... must be new objnum for mechs,
vehicles and new buildings, or the edit0r crush on show object in objectives.
x_2_5 fix: Truck moved out of danger.
Repair Bay dynamics changed.
New building: Field Repair Bay
New Building: Portable Repair Bay
New Vehicle: Armored Supply Truck
Old Repair bay with new anims for new repbay dynamics

4 new abl commands:
1)
addresourcepoints(pointsToAdd);
pointsToAdd - number of Resource points, can be + or -.
Effect: Add resource points for the mission.
2)
addmoney(pointsToAdd);
pointsToAdd - amount of money, can be + or -.
Effect: In mission add money.
3)
togglerepairtruck;
Effect: Enable/Disable repair truck in support for the mission.
4)
togglesalvagecraft;
Effect: Enable/Disable salvage craft in support for the mission.

Chance to fall under heavy fire (hit by heavy weapons).
Auto detect closest supported resolution to players desktop resolution.

NEW ABL command:
settxtbuildingname(BuildingID, "BuildingName");

BuildingID - number from the editor for building.
"BuildingName" = "New text building name"

Effect: Display "BuildingName" text as building name in mission.
Works for Buildings, Turrets amd Gates

Building does not need entry in mc2res.dll. All is set in Building.fit:
st Name="Building Name" - text for in mission display
l BuildingName=0 - must be zero

Buildings dont need entrys in mc2res.dll for the editor.
In buildings.csv type "Building Name" instead of "Name ID Number"
Mechs and vehicles also dont need entrys in mc2res.dll.
For vehicles it is (vehicle.fit file): st Name ="Ambulance".
For mechs it is (mech.csv file): MechName,Anihilator.

Elemental and Salamander jump fix (karl)
Huntsman and IceFerret - better mech models (karl)
Mech CSVs fix for new armor.
New armor allocation - more armor types.
My missions RPtruck fix.

Mech speed display extended

New Hi-res menus. 3 resolutions: standard 800x600 plus 1280x1024 and 1440x900

Mission briefing screen and pilot ready area added to new menus.
Mech purchase fix, compnent purchase fix.

mech purchase screen added to new menus.

Fixed bad load for feet0000.tga
Added folder detail with some detail textures to textures folder.

New logistic res change

new menus component purchase screen added.
new building - Generator (karl)

auto resolutions change - change resolution only if desktop res is
different then logistic res.

mission heap eliminated
appearance heap eliminated
terrain heap eliminated (200 crushes on first loaod after game start)
radio and msgheap heap eliminated
soundheap heap eliminated
system heap eliminated
gui heap eliminated - it was not used?
tgl heap eliminated.


gamesys.fit (f MaxVisualRange = 500 //300)
mechlab art for mechs - Karl
ase2tgl mem error fixed.

MCO version 102
Editor fixed: no more crushes on exit under win7, no more crushes in unit settings dialog.
Repair vehicle recharge completed.
Quick save/load fixed, no more crushes after quick load.
Game will recalculate paths for destroyed buildings.

MCO version 092
- Quicksave bug fix - more then 10 weapon nodes - another fixed limit.
- Better Kodiak mech model - 10 weapon nodes.

MCO version 091
- Quick load bug fix - another fixed limit.
- Repair truck can be deployed only once.

MCO version 089
Whats new:
- Mouse wheel incorporated in all MCO list boxes.
- Many mech fixes from Karl.
- New mech - Warhammer 2c (Karl)
- Improved mach models (magic):
Warhawk (model changed, 10 weapon nodes),
CauldronBorn (model changed, 12 weapon nodes),
Orion (better model, 9 weapon nodes, better animation),
Orion2c (better model, 9 weapon nodes, better animation),
Awesome (better model, 9 weapon nodes, better animation),
Centurion (better model, 6 weapon nodes, better animation),
Intruder (9 weapon nodes),
Grizzly (8 weapon nodes),
Nova (better model, 7 weapon nodes, better animation).
- New mech Zeus MK2 - 9 weapon nodes (magic).
- 4 new tanks: JEdgar, Saracen, Savannah, Striker (karl)
- Bug fixed - vehicle weapon nodes only 2 active, if created more then 2 in ASE/TGL, wehicle fire only first salvo and never again. All 4 nodes are now active and OK.
- new Elemental as mech (Karl, model by Thorc).
- 2 types of Forest-walls added to the game (karl).
- new building - Solar Collector (magic).
- max waypoints changed to 32 (magic).
- Repair Truck can recharge from resource buildings and resource vehicles.
- Repir Bay is not destroyed when empty.

===============================================================================
OK here is the first release of MCO:
(full game installer package - 400 Mb)

(http://www.moddb.com/downloads/start/30109) - no longer available.

===============================================================================
THE SECOND MCO RELEASE
(full game installer package - 430 Mb)
http://www.moddb.com/mods/mechcommander-omnitech

We wish to thank all the people who downloaded and played MCO's first release. Special thanks to all of you that playtested and reported bugs and other problems. Many of the problems and bugs found in the first release were fixed and there are many new features in the current build. We are very happy about receiving so much positive feedback and the interest you people still show into that yewel of a game.

===============================================================================
We would like to outline 4 very big changes in this new build :
===============================================================================

- Texture resolution for in game objects (mechs, vehicles, buildings) and terrain detail texture is now 256x256 (was 128x128) (To clarify : It's now possible, but not changed everywhere already )
- Memory allocation for game and Editor is changed and that fixed many issues.
- New maps 140x140, 160x160, 180x180 and 200x200
- 15 (!!!) new mechs added to the game
===============================================================================

PROGRAM REQUIREMENTS
This is a stand alone game: install this in its own folder. Also, you will need Microsoft Visual C++ 2010 (x86) redistributable which can be obtained from Microsoft directly at:
(http://www.microsoft.com/downloads/details.aspx?familyid=A7B7A05E-6DE6-4D3A-A423-37BF0912DB84)
and
If you want to use the editor, you will have to also install the XNA build for the editor (extract xna build and don't dbl click XNABuildSetup.exe. Dbl click XNA Build System.msi. It will install and report an error in the end about something missing. Just finish the install and it will be OK.
(http://www.microsoft.com/downloads/en/details.aspx?familyid=868fe562-5ded-4bb1-8648-708d3481bda3&displaylang=en)


What's new in Mech Commander Omnitech?

- Components inventory is back, just like in old MCG.
- No more unlimited purchase for mechs.
- Mission is too difficult and you have a lot of cbills, no problem, buy additional drop weight (5t - 10000cb), as much as you can afford.
- New save game file format.
- Component purchase.
- Component purchase screen.
- Sensor and jumping skills added to pilots like in mcg.
- Pilot promotion screen and pilot review area changed.
- Pilots get experience for those skills.
- New calc system for ranks.
- Sensor message when pilot has new sensor contact.
- Jump facing jump direction fixed.
- Skill try for sensors and jumping based on current sensor and jumping skill value.
- Fall when failed jump skill.
- New resolution 1920x1080.
- Sensor specialty skill and Jump specialty skill are now obsolete.
- 4 existing sensor levels are based on sensor skill value.
- Jump distance reduced for heavier mechs, more tons - lesser jump distance.
- Unit roster is no longer sorted; you can change as you wish. That way you can shift damaged units back in formation and put undamaged in front.
- 6 formations available for now. Formation key is "K", press to cycle through formations.
- Mechs are free of object2.pak (object numbers start is at 1200).
- Number of polygons limit tripled.
- A modification of rollins message box implemented.
- All vehicles are free from object2.pak (object numbers start is at 2000).
- All buildings can be free from object2 (object numbers start is at 2500, original buildings will be left in object2)
- Set of Rollins buildings.
- Starman's Mech Hangar.
- 5 new mechs (Fafnir and Lupus by Karl, Intruder and Thug by magic and MadCat MkII by MCO team).
- Number of potential abl commands doubled (was 256, now 512).
- Modified rollins message box added and accessible as abl command (for use in main mission abl file):

setTextMsg(0,"PROBE",10);

first parameter can be 0 or 1.
0 - instant message for the duration of number of seconds (10),
1 - rollins message box with press enter to continue, in this case third parameter should be 0.

Second parameter is text message. It should have no limit because it passes a pointer to string to underlying function.

Third is a number of seconds to display a message in case first is set to 0.

- Modified Mech purchase screen. New mech purchase simplified to the maximum, no memory consumption at all.

-changed objectchangesides abl command for use in mission.abl

syntax:
objectchangesides(PartID, teamID);

PartID - number from the editor for buildings, part id for mover (getunitmates(squadID)) from squad ID.
teamID - (0,2 player; 1,3,... enemy)

effect: change object side.
works for MECHS, VEHICLES and BUILDINGS

- NEW ABL command:
addmovertoplayer(PartID, teamID, commanderID);

PartID - part id for mover (getunitmates(squadID)) from squad ID.
teamID - (0,2 player; 1,3,... enemy)
commanderID = 0, player is 0 for Single player. Here for possible future multiplayer.

Effect: switch enemy mech or vehicle to player and add that unit to player roster.

- Changed the way of loading pilot icons.
- 6 NEW (not replacement NEW) pilots from MCG: Vixen, Scarab, Hunter, Beast, Mystique, Hitman. Thanks to ThorC.
- Activated ALL 4 weapon nodes for turrets.
- Max object texture resolution changed to 256x256.
- 3 wide resolutions supported; 1920x1200, 1680x1050 and 1440x900.
- reduced number of buildings and trees that can be rendered by the distance from camera.
- shadows will not render if distance from camera is too long.

What's NEW in editor:
- Fixed many errors: dynamic memory allocation version conflict.
- New load for mechs, vehicles and buildings. It will load old MC2 way as well.
- Rollins resize bug fix implemented.
- Fixed 600 objects limit for buildings.
- Max number of pilots doubled to 128.

===============================================================================
Whats new in second release:
===============================================================================
===============================================================================
- Texture resolution for in game objects (mechs, vehicles, buildings) is now 256x256 (was 128x128)
- Memory allocation for game and Editor is changed and that fixed many issues.
- New maps 140x140, 160x160, 180x180 and 200x200
- Activated ALL 4 weapon nodes for turrets.
- Max object texture resolution changed to 256x256.
- 3 wide resolutions supported; 1920x1200, 1680x1050 and 1440x900.
- reduced number of buildings and trees that can be rendered by the distance from camera (to prevent crashings or polygon overload).
- shadows will not render if distance from camera is too long.
- New maps 140x140, 160x160, 180x180 and 200x200
- Turrets and gates are free of object2
- Starmans Autocannon, LargeLaser, LRM and Calliope turrets included.
- Memory alloc fixed. Maps 180 and 200 are not crushing on exit now.
- All MC1 pilots are in MCO (by ThorC).
- New mechs Grizzly, Cicada, Crossbow, Ranger (by Magic)
- New Mechs Sunder, Hellfire, Redesigned Mist Lynx, Blood Kite, Naga and Mad Cat Mk3 (by Karl),
- New mechs Uziel, Argus, Thanatos, Owens (by Karl, models by Starman)
- New mech Champion (by Karl - model by RavenIIC)
- Mobile Turret Control vehicle and Mobile AC Turet (by Starman)
- New MRM turret, MRM popup and camo turets and LRM camo turrets (by Karl).
- New/fixed ABL and brain file functions (check the moddb download description for more details on this issue)


What's NEW in editor:
- Max number of pilots doubled to 128.
- More skys added to editor up to 36.
- Editor mem alloc changed.

===============================================================================

magic

Excellent, going to download straight away. Thanks Magic, Starman, Rollin and all others who worked on this.

______________________________________

I'm not retreating, I'm just fighting in another direction.

Still playing....installation went perfectly. Thanks tons for your effort!

1. See this on HLP
2. Look confused
3. ????
4. Download with rapturous expression!

Great work guys!

- New resolution 1920x1080

Humm...where to set? I don't see this in Options. Only see 1280x1024x32....

Is this an auto detect? I know my card and monitor support this resolution. Thought I'd give it a try.

Oscar, yes its on autodetect.

i can only get 1600 res, how do i get 1920x1080?
its set to 7 in the cfg file but i cant see a list of the res number.

Also, does it not auto salvage mechs? it seems to skip over the salvage screen after a mission

Thanks

I'm not sure what campaign you're playing, but if it's Exodus, many missions do not allow you to pick up after mission salvage. That campaign is about making the best with initially limited resources, and often there simply isn't time to go pick up salvage.

Congratulations on this release Magic!

Magic, I will try to get the final draft wrapped up shortly and send it to you. January 2011 was probably one of the most demanding work months I've ever had (lots of 85-90 hour work weeks), so needless to say, my time for other stuff was limited. February is quite busy too so far, but as close as I am on the story... I know I can get it wrapped up relatively quickly.

Magic, just a quick update. I'm nearly done with my revisions on the Exodus campaign manuscript, and should be sending the final draft to you this weekend.

Cheers,
Marceror

OK, thank you.

VERY Close now, but it's late and I'm going to call it a night. I'll do one more pass of proof reading, and probably have it to you within the next day or two.

First off I want to thank everyone involved with making this awesome mod.

I would like to say that some of the flavor text is mispelled. Unfortunately, I don't have specific references for you at this time.

I am still in my first play through and am stumped on one of the missions. I am in MW2_4_2 New Ivaarson. After crossing the bridge my mission always seems to fail no matter what I attempt to accomplish. What am I doing wrong?

Kappa Delta

hi there, this sounds great and would love to play it, but i keep getting MCOsetup.exe is not a valid win32 application, if anyone has a suggestion would love to hear it D

hi thx magic, i had allready tried that to no avail, so i tryed it again and it worked ! thx, i loved your exodus campaign and cant wait to get stuck into your new mw2 mercs camp, wolfmans camps always get to hard after a while so thx alot and good day, keep up the good work

I cannot get the program working due to the following error:

"The program can't start because MSVCR100.dll is missing from your computer. Try reinstalling the program to fix this problem."

Do I need the "Microsoft Visual C++ 2010 redistributable" to get the dll or is this another issue???

I read the download instructions as the above file was required for the editor so please do not think I am a total slug!

GAB

"Microsoft Visual C++ 2010 redistributable" is necessary to run the game. The error comes up, because you haven't installed that one.

The second download is for the XNA build, which you need only ADDITIONAL if you want to use the editor.

Hope that helps.

Cheers
Starman

"Microsoft Visual C++ 2010 redistributable x86" is required to run.

MCO is x86 application, so "Microsoft Visual C++ 2010 redistributable x64" will not work.

NEWS UPDATE 08022011

- All 4 weapon nodes for turrets are now active (it was only 1 (of 4) in the original).

Greetings,
It seems that i encountered a bug with the Mission Killdeer from the Carver 5 Campaign.
I kept crashing time and again a few minutes into the mission with the error:
Object moved off map

Finally i found a slow flying Hellcat II from west to east, which btw doesn`t show up on Radar, and as soon as it hits the east map edge -> Crash.
I do not know if this is intended, i just wanted to let you know since i couldn`t find this error when i did a search on this forum.

Is it normal that you can`t choose any saved Configs anymore? At least i don`t have that dropdown arrow besides the Mechnames anymore in Mechlab. Pita
And anyone else noticed that you don`t always can buy stuff eventhough you did capture the corresponding Weapon Facility in a mission? ( Clan Laser, Swarm LRM and Clan Gauss for me ). Played those missions a few times to see if i made a mistake somewhere, but still couldn`t buy them afterwards. Yet other Wep Fac that i captured i could buy said stuff before the next mission.

Nice day

Can you reach the hellcat in time to destroy it ?

Also, which mission is this please ? Liao or Davion Campaign ? I will then take a look into it.

Sorry about the mech configs and the not working purchase stuff. First one is a real bug, second is because the purchase files are also far from being good balanced. Will be fixed in later releases

Mission Intercept: Killdeer from the Liao Campaign ( 1 of 3 choice Missions ).

Yeah it is reachable, but unless you pay close attention and know it is flying there you can easily overlook or not notice it.

When i played the mission the first few times ( and kept getting that error ) i used 3 Mechs ( Lao Hu, Summoner and Cauldron Born ) and had the Lao head east to the Resource Building with the other 2 Mechs northwards to the Resource Building in the small City just north.
When the Lao killed the Tank defender at the eastern RB and took it over i would let it head back to my other 2 Mechs who by then would engage the 2 Mechs coming in from the Hillrange to the east of the northern City.
If you would follow the Lao´s run back then he would make, most likely, visual contact with the Plane. But as said before it doesn`t show up on radar ( just like infantry doesn`t ) and you are most likely occupied with the fight in the northern City with your 2 Mechs vs the 2 Light Mechs from the East you wouldn`t notice it`s even there.
Hope that describes the problem good.

Thanks for the response and the Info on the other 2 things.

Certainly a very neat mod for sure. Though i guess some of the new mechs are in the Exodus Campaign ( Dire Wolf, Faffy, etc? ) or are those soley for Multiplayer games?
Well time to get my ass whooped in Exodus.

Just those 5 mechs from the latest news are completly new and mostly likely not in any campaign. Everything else, that was already included in Magics MC2.5 is also in OT

I take a look at the mission. Thanks for the bugreport

* I warn you now - this is a detailed, BOOK, on Magic’s Addition, let the reader beware *

I, first off, want to congratulate you, Magic, on the additions you have made to this game. As an avid fan of the series since it came out, I was in adoration to see Mechs from all across MW universe pumped into your variant of the game (especially the Marauder IIc - Thanks a billion!!) The Mech designs are not only for the most part accurate, but are fluently and flushly adapted to the skins. (Ive seen customized games where a character moves a certain way and their arm and body have "chasms" in between). I downloaded both sets, the Omnitech game you put out, as well as the mech pack for the original MC2, and in doing so, actually decided to register here to offer my congratulations as well as a few constructive "outsider views" if they would be appreciated. ~~ All of the data I perceive will be from my local machine - Vista x32 - so if Windows 7 is any different I apologize. Also, I will be noting EVERYTHING, if it seems trivial, its not directed to be nitpicky, its just for information, PLEASE REMEMBER - I LOVE THIS ADDITION and if you need a tester for future variants/additions I'd love to participate ~~


*Before I go into my observations, I want everyone to understand my playability standards*

Recruit - Can breeze through a Lvl with insignificant damage w/o repairing (great for lvl testing/or stacking future lvls with easily acquired enemy mechs, aka cheating)

Regular - Missions can be finished w/o repairing, usually without losing any mechs if played properly, some mechs may sustain considerable damage during battle.

Veteran - If a repair truck/bay is not used you WILL lose several to all of your mechs, most mechs will sustain considerable damage throughout battle.

Elite - God has tagteamed with Satan, and sent the hordes of hell after you... What would you like on your tombstone??


1) - DIFFICULTY - Being a lover of a real challenge, I tested the first three missions on each difficulty, and it seems the survivability of player mechs, might be a little high (at least up to Veteran, as per Elite is F'ing ridiculous and will be the mainstay of my future gameplay)... Playing even the second mission of the Carver V campaign on VETERAN, I was able to not only beat the entire mission with only a Jenner, I did it without repairing, without using turret support, and without hiding behind Objects/Buildings to survive volleys. A slight tweak of harder difficulty, maybe another 25%, would make this setting perfect for a good gamer.
- - I then proceeded to do the same mission on REGULAR, rushing directly through the main gate of the bases without capping turret controls, thus taking fire from all vehicles, Mechs, and enemy turrets, and actually beat the mission with "zero" visible color damage to my Jenner?!? Regular could use about a 40% increase in enemy accuracy/damage.
- - As far as ELITE goes, I tried a Jenner vs. the "Flea"; face to face confrontation w/ little to no evasive techniques, and got ravaged - I LOVED every second of it

If there is a way I can either increase the Weapon Damage or Accuracy rate of Enemy Mechs, myself, (and not just pilot skill level eg: reg,vet,elite) would you be willing to provide that information? If I enter into battle with 1 mech against 5 mechs in Veteran, I want to be raped, not come out victorious


2) - Range/Vehicle Speed - This is a two part 'alert', several of the vehicles/Mechs I have noticed, seem to be relying on an incorrect speed/range table, as I have had some LRM trucks that move faster than Centipedes and Centipedes that are apparently unable to fire at me unless they were at long range, as they would just continue to drive away from me infinitely, I could keep them at medium range and they would refuse to attack me (most Mechwarriors would find unhostile enemies a blessing I find it sad they dont want to play ). In addition several of the mechs, instead of having evasive firefight styles, just rush up, literally point blank range and just hump my mech while firing at me... I understand it if they have melee battletech weaponry, but I swear this Javelin pilot is just straight up retarded. I have had LRM trucks that do this as well, instead of firing at me, just drive up to me and follow me around... I was actually using them as exploding puppies to deter the Javelins away


3) - Line of Sight - I have noticed the Line of sight is affected by placeable objects but not some of the terrain in your addition. Not a big deal as a lot of MMO's actually have this issue as well, but playing on Elite and using level change to protect my arse, will not work so well when they can PPC me right through the bloodstained hill. (I will do some more testing if you wish to find more accurately what "angle" of terrain is most affected)


4) - Pilot Avatars - The Pilot "videos" you have incorporated are the basic MC1 Style ones - which is GREAT!! MC2 had a tendency to play them at retarded times, or not at all. I play with them turned off usually, b/c that yellow box highlighter is enough visual warning for me, but I did notice the first couple missions I ran... If TWITCH for example would see something on radar, his pic/vid would initiate, but if FLASH caught it on radar too, TWITCH’s picture would stay active until the chain of announcements would end. I had one chain of 6 sensor acquisitions, then being attacked by 7 different targets for one of my mechs, and LONGSHOT’s pic/vid ran for almost 23 seconds, even though obviously not all the *.wav’s were her. For the sake of battle, and seeing our damage, shortening them a tad might even be a worthwhile investment. Just long enough to see who said it is really all that’s needed.


5) - MechLab/Weapon Component - THANK YOU FOR BRINGING THIS BACK!!! REALLY!!! UNLIMITED WAS FOR NOOBS ANYWAYS - Please, submit these as my main requests above all else - if you could find a way to let weapons stack, provide more “standard weps for customizing” like lasers(I’m sure command would be willing to pitch the C-bills to grant more than 1 laser, and 1 SRM per lvl, and yes I know u can just buy mechs, strip them and sell them back, but that defeats the purpose of limited components ), that would be the best improvement on to your entire addition, that and maybe incorporating the Component merchant into the MechLab to save having to go back and forth. As you already know the variant drop down menu is also removed. Other than that… Spectacular job bringing the best component of MC1 into MC2++.


6) - STRICTLY A COMPLIMENT - THANK YOU FOR FIXING TARGET ACQUISTION <PERIOD>. MC2 had this stupid habit of locking an entire force group on one target and trying to chase him down while I just had my 7 other mechs “lock-on to headshot” and chase them around picking them off one by one for perfect salvages of the entire group while I just ran around with my decoy. Your Enemies at least switch targets when my decoy leaves their “happy range”. Bravo to you sir .


7) - ENCYCLOPEDIA - For both the Omnitech, and the Mech pack, half of the mechs (the ones with the BT Variant names - "Jenner JR7-D" or "Anihilator ANH-1A", etc) show up in the vehicle section of the Encyclopedia, and I was curious if there was any way to change this, so that all of them are together in the Mechs section. (In the mech pack, several of the vehicles actually appear in the mech section as well which I will be detailing in Part 8)


8) - MISSING FILES - I noticed only one file missing for Omnitech, but I have a feeling that was because I accidentally stole it with ‘Cut and Paste’ to my Mech pack for MC2 original as opposed to Copy and Paste, but I will Include it just in case… (for everyone who found MechPack not to work properly - you can copy paste these files from the Omnitech download to the respective folders in your mechpack/MC2original if you want to access them in your Original MC2 Encyclopedia).

These are the vehicles that also show up as Mechs in the Encyclopedia

<MC2\Data\Objects>
- Missing from Omnitech - may have been user error
Cargodropship2.CSV

- Missing from Mechpack :
Cargodropship2.CSV
Gotha.CSV
Hellcat.CSV
Jfbroadsword
Leopard.CSV
Lucifer.CSV
Rapier.CSV
Sabutai.CSV
Sholagar.CSV

<MC2\Data\TGL>

All files respective to the ones missing above: (example for Gotha.CSV below: repeat for each CSV)

Gotha.agl
Gotha.ini
Gotha.tgl
Gothadam.tgl
Gothafallbackward.agl
Gothafallbackwarddam.tgl
Gothafallforward.agl
Gothafallforwarddam.tgl
Gothahitback.agl
Gothahitfront.agl
Gothahitleft.agl
Gothahitright.agl
Gothaidle.agl
Gothaparktostand.agl
Gotharntowk.agl
Gotharun.agl
Gothastandtopark.agl
Gothasttowk.agl
Gothawalk.agl
Gothawktorn.agl
Gothawktost.agl
Gothax.tgl


To wrap things up… Omnitech plays better on my Vista system than the original did, has a farther draw distance than the original did, and overall more exciting due to the dramatic increase in mech chassis. Great ‘expansion’ and we look forward to more things from you soon!!


PS - If you could email me the details on putting the MechPack chassis’ into the Original MC2 Purchase file that would be awesome… keep up the good work!!

Shayashi,

Thank you very much for your response. It is appreciated.

Some answers:

1. Difficulty. I completely agree with you in every detail. Most trouble I had form the first release of my first expansion pack was difficulty. About 90% of complaints were that its too difficult, so I went a little to easy for this one.
You can change the way you want in data/missions/gamesys.FIT.

Look for:


l<4> PlayerSkills = 100,100,100,100
l<4> EnemySkills = 40,60,80,100
l<4> PlayerWeapons = 160,140,120,100
l<4> EnemyWeapons = 40,60,80,100

Enemy weapons will be back to 100% for all difficulty levels. for the next release.

2. I increased weapon ranges compared to the original and all weapons there have min fire range, like Large Lasers, they cant fire if mech or vehicle is too close. Will consider lowering those min fire ranges.

As for the movement I havent changed anything. Its old MC2 pathfinding algorithm.

3. That is leftover from MC2 as well.

4. Im not sure but I think all those videos are 23s or so long. We will have to reduce all pilot videos to 5-6 sec.

5. There will be mechcommander office from where he/she can access mech and weapons purchase. Once commander accept the mission or mini campaign (several linked missions) he/she will be in the field with no purchase.

6. That was fixed in my first expansion, and you are welcome.

7. I dont have time and I dont plan to spend a second on encyclopedia, sorry. This can be fixed...

8. ...?

NEWS 16022011

Max object texture is now 256x256 (was 128x128) supported by the game and the editor.

Sweet... made my own personal adjustments, to tweak my preferences.. but i ran upon this... and was curious if this was correct, or possibly the reason for the dramatic difference in difficulty between VETERAN to ELITE

f<4> WarriorRankScale = // Based upon weighted average of skills
45.0, // Green
56.0, // Regular
66.0, // Veteran
999.0 // Elite <--- possibly meant to be 99.0?

Possible, will take a look...

Ive been going through as many of the files as I can but I cant seem to find the Weapon Component files that specify each weapons damage/range/rate of fire, ID information etc, if you dont mind sharing. I did find them individually specified for each mech within their individual specs files, and I'm going to assume each needs to be manually changed for the ones that are equipped for each mech as well??

Look for file compbas.scv.

All weapons are there. Be careful when edit, it has external dependances, and is comma delimited. I recommend notepad for editing.

Plus for every mech every weapon must be set in mech.csv file.
Weapon specs are not important in mech file weaponID is.

Much appreciated!! Thank you

(And yes I've been using three files for modding, aka making three copies, Excel to copy/paste from, .xlr to organize, and Notepad to do the actual modding once I tweak it the way I want it - seems like extra work, but color coding in .xlr makes it 10 times easier to just data drop for me)



Is BR in your compbas just a Base Value Rating? I noticed it is usually one tenth of your compprice - so wasnt sure if this was an actual stat or just a formula result you used to determine your prices.

Just for reference, from the MC2 Editor Documentation:

"Map sizes correlate approximately as follows: 60 x 60 = 29 x 29 tiles; 80 x 80 = 39 x 39 tiles; 100 x 100 = 49 x 49 tiles; and 120 x 120 = 59 x 59 tiles."

"Tiles - Terrain is mapped in tiles each equal to 25 by 25 meters in the “real world,” equivalent to 128 x or y world units. Map coordinates are measured in world units."

So, a 120x120 pixel map is 59 tiles square, with each tile equal to 25m square. Total map size, in meters, is 1475m x 1475m (ie. 1.5km approx.).

Long range weapons have a default setting of 300m (IIRC), or, fully 20.3% of the distance along any edge of the map on flat terrain.

Is there ANY future possibility of expanding the map sizes to 240x240 or maybe even 480x480 - memory constraints not withstanding?

This additional 'playgroud' would make a huge difference in playability for MCO. As it is right now, we MechCommanders are limited somewhat to 'quick and dirty', 'instant action' single lance actions and can't explore other tactical considerations like multi-lance operations without everone walking all over themselves.

Thanks for MCO. I'm enjoying the Alpha and looking forward to future release versions as things progress.

Hi,

i was wondering if your calculations and data is correct.
The mapsizes 60x60 or 120x120 are in tiles. When you open the editor and measuere the distance from one side to the other in meters using the "distance to last click" feature you are told that the 120x120 map is around 16000 m wide. These measures are in contradiction to what you posted. The long range weapons reach not such far on a 120x120 map either. Please explain your logic and calculation to make me understand your post better .

I agree nevertheless with the drive to larger maps. I work on this for a while for other reasasons you mentioned, agree to the need
Thank you for more explanations

check out wolfman's missions and wolfman's forum at
http://s2.invisionfree.com/wolfman_x_forum/index.php

Hey Wolfman,

I was just quoting what I found in the Editor Manual and a basis for the calculations.

I am however confused by the usage of the terms and the relationship of/to "real world", "world unit" and "Map Corordinates".

(quote)"Tiles - Terrain is mapped in tiles each equal to 25 by 25 meters in the “real world,” equivalent to 128 x or y world units. Map coordinates are measured in world units."(/quote)

What is the "size" of a "world unit"? If a tile is 128 "world units" square, and (BIG) IF a world unit is 25m then I could see the likelyhood of 16000m. Actually, (59x(128x25m)) = 188800m though, which is greater than your 16000m by a long shot and definitely larger that 16000m. 58x128 (if you assume 128 = meters) only accounts for 7552m, which comes up a bit short of your 16000m as well. Very confusing.

Then there are the textures as well with all their different sizes representing regular and detail terrain levels.

Its all rather confusing, but it works. A formula would surely be nice - no doubt. It would be nice to be able to know for sure the exact map sizes and how there are arrived at in a meaningful way. It would be great to know this than for no other reason that to calculate the total memory requirement for a 'future' map and just exactly how big that map could be and no larger. As a programmer friend of mine is often fond of saying "...its in the code, man."

In any event, maps that are/could be double or triple their current size "would" be a great update to the game; which is were this whole idea/thought/request started. If Magic and Starman and yourself can find a way to do this then I would be a very happy camper.

you could always go barebones with it and do a manual "range test" to correlate the size of a map... very simply actually...
set up a bunch of buildings, or objects in a row, now across the way from them do the same thing, but at varying distances... keep track of how many "tiles and/or cubits" you are setting the buildings apart, and then use either long range, or midrange range weapons to determine with the firing range, the approximate distance between the buildings and thus their tiles... it wont be one hundred percent accurate, but using that, at least u know what the formula needs to add up to when u sub in the co-ordinates of the buildings as variables. (in case that was too wordy, its along the lines of a firing range)


Building A - - - - - - - - - - Building B

X - - - - - - - - - - - - - - - - - - - O <- 7.0 Tiles Apart
X - - - - - - - - - - - - - - - - - - O <- 6.8 Tiles Apart
X - - - - - - - - - - - - - - - - - O <- 6.6 Tiles Apart
X - - - - - - - - - - - - - - - - O <- 6.4 Tiles Apart
X - - - - - - - - - - - - - - - O <- 6.2 Tiles Apart

etc. etc.

Again, I know it seems really primative, but when I map and adjust my settings in game, there is no better judge of result, than the actual result itself

Wolfman, I see in your MC2X Rev15 that you have included a 160x160 map. How did that change go - I haven't tried it yet?

Not working yet. It crashes after a it shows the taxmap correctly.
I work on it since some time 160, 200,240.
I guess it is amemory allocation issue. The bigger maps just disappear with out error mesage nor tacmap. 160 does somethin

check out wolfman's missions and wolfman's forum at
http://s2.invisionfree.com/wolfman_x_forum/index.php

Correction: Delete the entire section on WORLD COORDINATES above. Its wrong - at least it is with what you see in the editor. But, I will figure it out.

Please forgive my stupidity. I have errored in the map size calculation. The following measurements are now corrected:

PIXEL SIZE

Using the 60x60 map size as an example:

The map is represented as 29x29 tiles with each tile being measured at 25m x 25m square.

In the MC2 3D world, a map of 29x29 tiles is represented by a grid, where the grid squares are at a 45deg angle to the side of the map - not perpendicular to the edge.

The right angle edges of this 29x29 tile area are diamonded because of the orthographic representation.

The tiles must be measured, not from the corners A, B, C, D, but from the opposing corners A-C and B-D in order to arrive the correct width of the map area.

Given a right triangle where the corners are A, B, and C with sides represented as a, b, c, and using the formula for a right triangle, (sin A = opp/hyp = a/c and cos A = adj/hyp = b/c), where a=25 and b=25 and C=90 deg angle, the length of c (or the distance between A and B) is 35.36.

So,

A 60x60 map is actually 29x29 tiles, an overall map size of 1025.44 meters by 1025.44 meters
A 80x60 map is actually 39x39 tiles, an overall map size of 1379.04 meters by 1379.04 meters
A 100x100 map is actually 49x49 tiles, an overall map size of 1732.64 meters by 1732.64 meters
A 120x120 map is actually 59x59 tiles, an overall map size of 2086.24 meters by 2086.24 meters

If we extrapolate this forward to larger maps, then:

A 140x140 map is actually 69x69 tiles, an overall map size of 2439.84 meters by 2439.84 meters
A 160x160 map is actually 79x79 tiles, an overall map size of 2793.44 meters by 2793.44 meters
A 180x180 map is actually 89x89 tiles, an overall map size of 3147.04 meters by 3147.04 meters
A 200x200 map is actually 99x99 tiles, an overall map size of 3500.64 meters by 3500.64 meters
A 220x220 map is actually 109x109 tiles, an overall map size of 3854.24 meters by 3854.24 meters
A 240x240 map is actually 119x119 tiles, an overall map size of 4207.84 meters by 4207.84 meters

Given the size of the map in our example (60x60) is now determined, we can compute the pixel size by dividing the side length (1025.44m) by 60 which gives us a pixel size of 17.090666666666666666666666666667 or 17.09 meters per pixel.

Given a map size of 240x240, we can compute the pixel size by dividing the side length (4207.84 m) by 240 which gives us a pixel size of 17.532666666666666666666666666667 or 17.53 meters per pixel.

Sometimes its hard to see the forest for the trees...... A little simple geomotry can solve any problem when used correctly.

NEWS 20022011

- 3 (new for MCO) wide resolutions supported; 1920x1200, 1680x1050 and 1440x900.
- reduced number of buildings and trees that can be rendered by the distance from camera.
- shadows will not render if distance from camera is too long.

Is this update available for download?

Not yet, sorry. We are polishing it a bit and including some more stuff in it But it shouldn't take too long.

Rgr! Thanks for the work! Haven't touched MC2 for at least 4 years but last weekend I looked for my install media and grabbed the old dropshipcommand url in my browers and there is this awesome thing here. My eyes are hurting in 1024x768 though.

NEWS UPDATE 24012011

4 New maps (in testing):
140x140
160x160
work fine in the editor: create new, save, load. And in game load, play, finish, failed.

180x180
200x200
work fine in the editor: create new, save, load. And in game load and play. Finish an failed are crushing the game - memory allocation issue.

More thorough object placement is yet to be tested.

This is excellent news and progress...thanks!

Hey all

I joined for the sole reason of congratulating the MCO team for the great effort and sharing some of my observations with the alpha release.

First of all, I find it a great that there is now a survival motive (no more unlimited purchase of mechs/guns, limited number of pilots) included in the game, the new pilot skills (jump, sensors) add realism.

I have, however been experiencing game crashes, that mostly happened during my fiddling with the new component/mech purchase screen. (the game exits with the usual suspect exit message) and the other time is when i try to quick load the game.

Since MC is a fairly easy game, I have started to notice these things when I upped the difficulty level to elite, hence the need for quickload gets more frequent. (Quickload will randomly not work on Win XP PRO SP3 x86/Win 7 Ultimate x64 SP1, even tried it VIA Virtualbox OSE 4.04; ALL OSes were fully patched using the newest drivers)

Has anyone else been having the same problems?

Besides the above mentioned nuisance the game rocks.

Best regards

Ulric Bekker

\o/

Welcome to the board

Sorry for the inconvinience with the purchase system. This will be eradicated somewhere in the future because Magic is recoding it completly, though that might take a while (I'm just saying this, because when I say something takes long, then usually he suprises me the next day with "Look what I have done" )

I also noticed the not working quickloads with my XP Home, SP3(not always, but often).

The game will become more stable in the future

haha, yeah the mechlab is the main place I experience my glitches too... I try and avoid it for the most part during the campaign, using pieces I salvage off other mechs and what not... my main glitch with vista, I tend to notice if I run solo mission... in the mech purchasing, if I buy something like an Atlas or another mech, then change my mind and sell it back, for some reason - it turns into a different mech in the mechlab buy screen (usually a cougar, but not always) thus if I change my mind AGAIN and DO want to buy it, I'm SOL that little "Quit Game" button has become my best friend, bc reloading the game seems to be the only way to fix this, as just going to the main screen and reloading the mission - reloads it with the mechlab condition it was in before (minus whatever mech I sold, and the random mech added)...

I'm still trying to find a way to hack the mechlab/component purchasing tabs - to change it from "1 purchase of each item" to maybe 2 or 3 (for instance reg. lasers)

*I played the original MC2 campaign on Elite, only using razorbacks, and the last two missions I think I switched to Sha Yu's - kinda want to attempt the same for MC2.5/3.0*

If you want more than one component or mech in stock, it must be placed 2x times in the purchase file, simply create two lines with the same entry, just raise the rolling number by 1

What I noticed in the purchase screen, is that it swichtes through the variants. Each time you load the game, the next variant from mech.csv is loaded One it reaches the end of the file, one or two times the mech won't load at all