MTM2.com

Ladies and gentleman, I present to you, Community Patch #2 - Bear Foot Unchained, HD Trucks and Cowpod 1.0.1!

But first thing is first:

This patch is provided as is. TRI and Microsoft have nothing to do with it and will offer no support. If it doesn't work please post in here but my knowledge of troubleshooting problems is limited. And please BACK UP YOUR ORIGINAL FILES!!!! I can't stress this enough.

A big thank you to Cale for creating an alternate HD pack. These trucks are made in the spirit of the original stock trucks but with a better body design and a much better texture work. Both the original stock trucks and the HD versions can be selected and they are clearly labeled as the HD trucks can create some lag under certain circumstances.

Bear Foot has finally been set free. From now on, in multiplayer games, the default truck that gets selected when you don't have the opponent's truck is Boogey Van!!!

And in further good news. Cowpod has been updated and it is compatible with Community Patch #2. At least in terms of supporting the correct number of pods. It cannot be used for fixing MTM2's registry but it's on the ToDo list.

Before and After Gallery: Click on the pictures to see full size.











How to install:

Unpack the files from within this archive (rar or zip) to your main MTM2 folder overwriting the original files. Please BACK-UP the original files in case something goes wrong.

Download links:

http://www.mtm2.com/MTM2/Utilities/Comm ... Patch2.rar (rar file - 80mb)
http://www.mtm2.com/MTM2/Utilities/Comm ... Patch2.zip (zip file - 95mb)

MTM2 Community Patch webpage
Cowpod homepage - Updated

Known Issues:

- The following resolutions do not work:
-- 1360x768 - new bug. Will look into it.
-- 1366x768 - new bug. Will look into it.
-- 1440x900 - patchy on Windows 10. You might be lucky and it works.
-- 1536x864 - Directx5-7 doesn't support it. Will consider removing the option.
- Dashboard doesn't work. If you want to use first person view please use non-dashboard camera.
- Software Renderer resolutions are unreliable. While most of them work there are specific tracks where it randomly decides to crash. Decreasing visual distance fixes the problem.
- Zoon Kitchen 2 animations are still wonky when using an increased draw distnce. Have not been able to crash the game but it hasn't been extensively tested.
- The menu bar won't go away in Windows 8 and Windows 10 when racing. Please use nGlide or dgVoodoo to get around the problem.
- Using snow and increased visual distance lags the game. Please either avoid snow or decrease visual distance. This is a game engine issue and until it's ported to DirectX9 it won't be fixed.

How to correctly use the patch:

- After every resolution change YOU MUST quit the game and restart it. Otherwise the game either won't work or will work very weirdly. (for Windows 10 the game might linger for a few seconds in taskbar under background process. Either manually use End Task or wait for it to go away)
- The 3dfx compatible resolutions (for those using nGlide or dgVoodoo2) are clearly labeled with 3dFX. Do NOT attempt to try a different resolution, the game will crash. If you want to use 3dFX wide screen please select 856x480 and in nGlide 1.05 (mandatory 1.05) use the "fit to screen" option.
- fixmore.pod is still needed!
- If in Windows 10 the game refuses to go into full screen using Direct3D when using compatible resolutions (like 1920x1080 for example) try to run the game in compatibility mode using Windows XP SP2. I've had this issue and running with compatibility mode fixed it.
- If using Windows 8/8.1 you will most likely have to use nGlide/dgVoodoo as the new resolutions have terrible performance on this OS. This is strictly a DirectX5/7 and Win8 incompatibility and there is nothing that can be done to fix this.
- To ensure maximum compatibility with any of the tracks, custom or stock, please go to Options>Graphics>Hardware Options and turn off the following options: Reflections and Truck Reflections.



Patch History:
Community Patch #2 changes:
- Cale’s HD trucks have been added to the game as an alternative to the original stock trucks. Both versions can be used. Just careful as the HD trucks can create lag on certain tracks and with the increased draw distance.
- Truck appearing black in Driver’s Circle when you first start the game has been fixed.
- The extra green line in the joystick/wheel calibration page has been removed.
- Multiplayer latency has been fixed. It now displays correctly.
- Increased maximum pod count to 200. (likewise, maximum track count is now 200 and maximum truck count is now 200).
- Bonus fix: Cowpod has been made compatible with comm patch 2.
- The patch should now work with any windows xp version and possibly erlier versions.
- IMPORTANT FOR ONLINE PLAY: Boogey Van has been made the default truck. Bearfoot no longer gets selected as the default truck when you don’t have a custom truck podded. Please note this down. From now on Bearfoot can be freely used for online play (and Boogey Van has become the truck-non-grata).
- The program files (86) issue for online play might have been fixed but I have not verified. Still, I don’t recommend people to go out of their way to test this.
- Game now correctly alerts users in multiplayer that people are using a different game version. Gameplay is still possible and shouldn’t pose an issues (just like MTM2 patched and non-patched were able to work with each other).
- Updated game version to 2.00.50

Beta 0.37 changes:
- fixed trucks unable to drive over ground when terrain height set to 0 (rumbles like Sand Castle for example).
- Instant Replay page finally 100% fixed.

Beta 0.35 changes:
- Increased draw distance to 120 tiles! To put this into perspective, the original game had a max of 20. The CommPatch1 has a max of 50. This has a max of 120!!! Considering this setting is a radius (120 starting from the truck) it means that the diagram is 240. The game map is 256, so it basically loads about 95% of the map at any given time!
- The visual distance setting in the graphic option now displays exactly the number of tiles you want to set it at instead of percentage.
- Increased vertices and vertex limits to go with the increase in visual distance (certain tracks crashed because of it).
- Fixed the checkpoint finder! It now works correctly on all resolutions!
- Fixed the instant replay page. I have no idea at which point I screwed this up or how but there was a problem in the way the .POD was built.

Community Patch #1 changes:
- version number changed to 2.0.44 (multiplayer is compatible with people using the original version, 2.0.42).
- Increased visual distance from max 20 units to max 50 units.
- Visual distance is fully controllable from within the game.
- Increased maximum verts limit (less crashes).
- Maximum number of objects limit increased (stops tracks from crashing with the new visual distance).
- Box count has been increased - groundbroxes shouldn't crash the game anymore.
- Added a multitude of more modern resolutions.
- Added new UI to go with the new resolutions.
- Video clips are working again (for those of you who it didn't work for anymore).
- All 4 truck tires leave track marks.
- Tire track life span increased.
- Game should not crash if somehow wrong resolutions are selected (the resolution doesn't match the prefereddisplay in monster.ini). If resolution doesn't match it defaults to 640x480.
- Added a BLIMP button in graphics option. Now you have full control of whether you want the blimp to appear or not (can help stop certain tracks from crashing).

Beta 0.31 changes:
- Lowered the position of the lap time info so as to not be covered by the bloody menu. (Win 8 and Win 10 issue).
- Compiled against DirectX7 headers (at least I think so, can't find a reliable way to test this out. MSI afterburner only says DirectDraw but does not give the version number.
- Increased some vertices limits.
- Disabled a keyframe AV. This keyframe error has a connection with ZooN Kitchen 2.

Beta 0.30 changes:
- "too many vertices" error should have been fixed. I have doubled the vertices limit. Am curious if it's going to be hit.
- Pitch black hall-of-mirror bug has been fixed.
- Removed obsolete resolutions (320x200). Now the game defaults to 640x480 as the lowest. Also removed 2560x1440 as it doesn't work with Directx5.
- Improved the fail safe mechanism in case a wrong resolution is chosen. The game should default to 640x480.
- The checkpoint finder has been improved... somewhat. It's not a garbled mess anymore. It's not great but it's functional at least.

Beta 0.27 changes:
- Multiplayer should be fixed now.
- Monster.exe should work in Windows XP now as well.
- Bumped up maximum render distance from 20 to 50 units.
- The maximum render distance is now fully customizable from within the game.
- Max Verts increased from 800 to 1200 (same as render patch).
- Maximum number of objects increased from 256 to 512 (same as render patch #2. this initially caused crashes on tracks like duality and razzle dazzle).
- Mark finally increased the box count - or otherwise known the infamous ground box error. Limit increased from 600 to 800. Tracks like Razzle Dazzle can now be completed with 8 running trucks.
- 3dfx 16:9 has been added.

What to expect in the future:
- Increase in the object limitations (models, textures etc).
- A fix to remove the menu bar during gameplay in Win8/10.
- Maybe further bump up the pod limit.
- Workaround fix for snow issue (most likely removal of snow texture but increased number of snow flakes falling).

Long Term Plans:
These will take forever to do as it requires a more advanced coding knowledge but ultimately I want it done.
- Port the game to DirectX9 to fix many of the compatibility issues/crashes and allow even higher resolutions (2560x1440 etc.
- Port the game to OpenGL - same reason.
- Re-introduce Drag system from MTM1.
- Extra options in the .trk file, namely a second set of axle bars and different front and rear tires.
- Make it read more than the first 8 letters of a sit file name to be the tracks ID.
- Accept Axis Z for controllers. (this one will be looked at only after game is finally ported to DX9).
- Incorporating an ingame FPS limiter (not quite Vsync but rather a manual box where you can the maximum limit to whatever you want).
- Decoupling the physics from the FPS count. Right now the game physics (and AI behaviour) is dependent on the frames per second count. This means, the higher the FPS the more different the game behaves. Ideally physics will work the same whether it's 20fps or 100fps.
- Fix dashboard.

Credits:
- Thanks to Cale for supplying the bulk of the pictures used in the patch and for creating the HD truck pack.
- Thanks to Gamer121 for supplying HD artwork used in the patch.
- The fine folks at TRI that made a game that has stood the test of time for so long and turns out to be very modable.

Game crashes:
- Certain tracks like ZooN's Kitchen 2 or Toys in the Attic are very predisposed to crashes. Either decrease the visual distance and/or deselect the blimp in Graphic Options.

NOTES:
- Please remember to backup your original files. Rename monster.exe to monster.exebk, trid3d.dll to trid3d.dllbk, triglide.dll to triglide.dllbk, cockpit.pod to cockpit.podbk, STARTUP.POD to STARTUP.PODbk, UI.pod to UI.podbk, TRUCK2.pod to TRUCK2.podbk, extras.ini to extras.inibk and also make a copy and backup of monster.ini before editing it. Then rename the backup to monster.inibk
- The patch has been tested and works 90% of the time flawlessly on all tracks with 8 stock trucks racing.
- Highly detailed custom trucks may give performance issues on certain object heavy tracks like Alpine's Certifiably Crazy. There is no work-around for this. It is a game engine limitation. The only solution is to either not use a highly detailed custom truck or to revert back to a regular draw distance. However most of the tracks out there will not have a problem handling 2 or 3 highly detailed custom trucks.

Dude. These trucks are Bad@$$ to the Bone. I TOTALLY call "B R O Racing".

So, interesting, I finally got the shine-through issue with this patch in DirectX mode. Not there using nGlide. Don't know what changed between the two patches, but there you go.

I just saw this, great way to end a bad day. Can't wait until my desktop decides to work again to test it out! I'm gonna run some tests on it to see if the windows 10 compatibility has improved on it too. I'll let you know what I find out.

For a while I didn't have the shine-through either then with the last two patches (0.35 and 0.37) I started getting it. I believe it's the way the compiler handles the DirectX 5-7 code (and then how Windows interprets it). Which is why 3dfx doesn't have the issue as it uses a different set of code instruction.

In other news, I have been looking through Winterkill's dashboard information and I decided I want to fix the dashboards for the next patch. This will take a long time but other than that, are there any good dashboard pictures people can recommend? (obviously the higher resolution the better especially for 1920x1200 and 1920x1080).

So, after 3 fresh installs on my windows 10 machine, I finally got to try it out. For some reason, after I mount around 30 pods, the game gives the missing files error. I have no idea what to do about that. Also, the game crashes if I try to use custom trucks and crashes at the driver check in until I unmount the pod.

:/

I have no idea how to go about fixing that. I have been testing on both my desktop and my laptop, both on Windows 10 and neither have had any troubles so far. Have even used the laptop to play online and to me it felt like the game is more stable than before.

Do you have the game installed in program files(x86)? The betas had a weird issue with crashing online if it was installed in program files (but it was fine anywhere else).

I used to have the game crashing at driver check in while I was building the new UI (it somehow tied to specific trucks for a weird reason despite it being not the truck's fault) but never had the issue after the final version.

Are you installing the game from your own disc or from a download from this website?

Maybe the installation files have gotten corrupted and something is up? Just for a test, download the game from here http://www.mtm2.com/~mtmg/mtm2.html and just copy the mtm2 folder from inside to let's say C:\MTM_Testing or D:\MTM_Testing (preferably D: because Win 10 is an overprotective nasty OS). Then without running setup.exe just copy the community patch #2 files, overwriting as required. Then go to SYSTEM and right click on monster.ini and disable the "read-only" box (otherwise it won't save when you change video settings). Do the same for pod.ini otherwise it won't allow you to modify the file. (remember to maybe use windows xp sp2 compatibility settings with monster.exe).

Then try and run the game as is a few races and then gradually add your pods and see if something changes.

I know it's a pain in the ass but I'm trying to figure out what's going on and the only way I can do that without seeing your screen is through such baby steps.

I just did that on my laptop as a test and that's all I needed to do to make it work. Tested with 160 mounted pods.

An idea, how hard would it be to fix the weird 11khz 8bit mono wav file limitation? Would it be possible to allow external links to music?
Also, would it be possible to fix the CB radio to be allowed to use more bandwidth and maybe sound like something?
Also, could you increase the rate that truck position updates are sent to other players?

I will look into it for the future. The .wav shouldn't be a problem. For the CB radio and the truck updates I'm not sure as I don't know how tied they are into the DirectX5-7 network code (what i wanna say by that is I don't know if it's a limit from directx or from tri themselves. Will look for it when I go back home).

Cool. That could breed new life into multiplayer.

Hahahahahaha, you know that made me laugh really hard...Actually I think it might be because of the UDP protocol the game uses for online play lmao, which is really funny because I've kinda known that for years. Pretty sure the TCP ports (like 47624) and tcp 2300-2400 are required for launching the game and that everyone gets in, but when you're actually playing and rumbling on the cube it's most likely in control of the UDP protocol, which is funny as hell, and probably why it's so laggy and people can jump and ghost around all over the place. Looool. I dunno why I find that so funny I just do. That's what makes this game what it is man, lag shots and stuff.

Ok, in that order:

1. it's not, I made sure to install it in a separate directory.
2. For me it only seems to crash with high very trucks. Cales hd trucks work perfectly, but my trucks will load in driver check in, but crash if I try to use it in game. After that, it crashes at the driver check in until I remove the pod.
3: I'm using a downloaded install. I start with a fresh download each time and I've used the one from here and vales with the same results. I'll try modifying the settings like you said tho.
4: it works up until I add somewhere between 25 and 30 pods, but evendors unmounting the extra pods won't even help at that point.

I'm out aND about today but I'll try it when I get back home

With any of your trucks? lemme download about 20 and see what happens

So I had 120 pods mounted. 31 pods were your trucks (starting in 2017 and going down in chronological order). I used Khaos and I ran 6 consecutive races with 7 AI trucks, all randomly selected from your trucks. Other than achieving a grand average of 4fps, I haven't had any other issue.

I did 1 race on SLO Motion and then 5 on Soda 1 because it was impossible to try and play with 4 fps. lol

The fact you got them to work tells me it's something on my end. May be something with my video drivers, who knows. And lol at 4fps. I'm trying out new stuff with textures and shading so I can use fewer verts. I'd like to try my hand at one or two of Cale's super stock trucks eventually too, we'll see later when work dies down.

Just for the sake of it, next time you reinstall or you try the steps I mentioned above, redownload MTM2 first. Over time files get corrupted and it can happen that a small byte gets corrupted somewhere that doesn't stop the installation from happening but it gives you problems running the game.

It's a long shot but we can't rule out anything.

Will do. I'll try it if I'm not busy tonight

Great job on this patch!

Is this normal after a rumble?