VOGONS


Mechwarrior 2 Decomp/Recomp

Topic actions

Reply 120 of 132, by Mikeyy00

User metadata
Rank Newbie
Rank
Newbie
Mikeyy00 wrote on 2026-11-18, 04:09:

1.1.32 Mech2 comes with a viewer exe now. Barebones, it'll need some work.

Edit: I'll bake an export option in on the next release for images (png) and 3D stuff to a blender compatible format.

1.1.33 has an export option.

Full disclosure, I won't be giving the map editor/export whatever much attention until MW2/GBL/Mercs are done with. Kind of best effort as I have free time.

Reply 121 of 132, by myne

User metadata
Rank l33t
Rank
l33t

I wouldn't bother with a re-importer.
Fairly likely to be a headache.
I'd add a reader for the new formats.

I built:
Convert old ASUS ASC boardviews to KICAD PCB!
Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.
Dos+Windows 3.11+tcp+vbe_svga auto-install iso template
Script to backup Win9x\ME drivers from a working install
Re: The thing no one asked for: KICAD 440bx reference schematic

Reply 122 of 132, by Deffnator

User metadata
Rank Member
Rank
Member

would be nice to keep contact with mech2.org dudes for more Q&A

Reply 124 of 132, by Mikeyy00

User metadata
Rank Newbie
Rank
Newbie
KHORG wrote on Yesterday, 09:34:
I'm getting a single virustotal result from the 1.1.33 exe: https://www.virustotal.com/gui/file/a34b28032 … c112a5e640794db […]
Show full quote

I'm getting a single virustotal result from the 1.1.33 exe:
https://www.virustotal.com/gui/file/a34b28032 … c112a5e640794db

1.1.28 comes back fine:
https://www.virustotal.com/gui/file/d1a3e9820 … bbbb260e58b3f04

Likely something the map viewer/exporter editor.. no, no malware put in there by me. Will see whats going on.

Edit: some debug data was left in the exe.. may have tripped it. Try 1.1.34.

Reply 125 of 132, by KHORG

User metadata
Rank Newbie
Rank
Newbie

Virustotal is happy with 1.1.34 now.

I've gone back and re-checked these on 1.1.34, there are a few bugs from this list still present.

KHORG wrote on 2026-11-15, 02:50:
I've just fired up the MW2 recomp, some things I've noticed when comparing it to the DOS 1.1 version which I have running throug […]
Show full quote

I've just fired up the MW2 recomp, some things I've noticed when comparing it to the DOS 1.1 version which I have running through dosbox:

  • The grey MW2 menu cursor seems to have been replaced with a default windows cursor?
  • If you click on the Archive Holoprojector, it cuts to a zoomed-in view of the "projection" animation, then cuts back again to the normal view. Usually it just runs this animation in the distance of the hall, then cuts to the display.
  • There's some kind of slim vertical red line on enemy target brackets when selecting enemies.
  • Using Z to zoom in immediately causes the 3D cockpit outline to be culled by the renderer. It only re-appears when you shift-zoom all the way back to default.
  • Funnily CTRL-Z has carried over the buggy behaviour from the original game. It was meant to reset your zoom, but in original MW2 had a bad tendency to bounce the camera around.
  • The Satellite View doesn't show a top-down view of your own mech, it also incorrectly carries over enemy targetting brackets from first-person view and puts them in random places.
  • The floatiness of the original targetting reticle seems to be gone. Now if you let go of a key it immediately stops.
  • There's a big frame-rate drop when turning on or off light amplification. Image enhancement is fine.
  • The turrets on wolf level 2 don't seem to be able to turn. They just start blazing away in whatever direction they were originally pointing at.
  • There are various 3D hill objects missing from wolf mission 2. They should be visible as soon as you drop in.
  • When you arrive at a Nav point, two things should happen; 1) the unselected nav icon on your radar for that location should dim slightly (this works) 2) the text for "Nav Alpha" in the bottom left of the screen should also dim (and stay dimmed even if you change to a different waypoint then back) to indicate you've already been there, this doesn't occur.
  • Satellite View doesn't show enemy buildings in red outline (particularly on Wolf 3), it just shows them as black outline.
  • Satellite View also doesn't show the enemy fire in yellow. Usually you can see incoming PPCs, lasers and missiles.
  • On your targetting MFD, (bottom left display) the helicopter on wolf mission 3 should show as a blue fuselage and a red circle for the blade above it, but only the fuselage appears in the MFD view.
  • The NPC vehicle (automobile) driving around on wolf 3 isn't there.
  • On wolf mission 3, the red or green roof-lights on the taller building aren't there. Usually they should fade in and out, being either green or red.
  • In Satellite View, 2D sprites like fires should appear as little fire images, but currently they only show as a black line.
  • In original or recomp MW2, when you're shooting the ground, there is a black puff of dust. However in the original game there is a semi-bug when shooting buildings, static vehicles etc. In this case it should show a weapon splash effect, but it didn't always, sometimes the angle on the building/object would be wrong and you would instead see a black puff of dust and wonder if you were hitting it. However, in the recomp it only shows the black puff of dush when shooting buildings/objects, not the weapon splashes.
  • F5-F6-F7-F8 should act as alternates for the right MFD, e.g. if you press F8, you can press F5 to cycle back to the default mode. This doesn't work in the recomp, instead.... F5 and F6 are linked to each other, F7 and F8 are also linked, you need to press F8 again before you can get back to F5 and all sorts of UXUI that makes my head hurt.
  • If you look down (CTRL up/down) in the Mad Dog cockpit, you can see the backs of the Mad Dog legs, which you shouldn't be able to. I haven't checked all the other mechs for this.
  • Wolf Trial 1, the first two mechs don't move until you're looking down on them from a hill, they should be moving towards you at about the 10 second mark (which is a couple of seconds after you're fully online).
  • Wolf Trial 1 again, the second two mechs should start moving towards you as soon as you destroy the Engagement Sphere. Instead the first only moves towards you when attacked, and his starmate follows him around like an AI with no attack orders.
  • Some of the original 'flight sim' controls seem to have changed? In the original game, UP aimed down and CTRL-UP looked down. In the recomp, UP aims down and CTRL-DOWN (not CTRL-UP) looks down.
  • Sable Flame is all kinds of busted. The Sensor Array Dome is opaque when it should be transparent and you should be able to see into it and through it.
  • Also on Sable Flame, the 2nd Mech group should power up after you destroy the 1st, and the 3rd should power up after you destroy the 2nd. But the the 2nd and 3rd come online at the same time after the 1st is destroyed. Also weirdly the 1st group doesn't appear on radar after betty announces Enemy Powerup Detected.
  • Still on Sable Flame, the third group of mechs get distracted by a Wolf dropship which is flying around above them and instead run around shooting at that.
  • Still on Sable Flame, the Falcon dropships have a Wolf logo on the side (I checked in the original, it's definitely the Falcon logo there).
  • Dropships seem not to be able to turn/aim their turret on top, so like the current problem with static turrets, they just shoot straight forwards when they see something.
  • Still on Sable Flame, there is some weird switcheroo going on with which mechs are in which group, it should be 3-2-2. But instead it's 2-2-3? One of the Mad Dog's from the first star ends up in the last and I feel like the Stormcrow changed group also.

That said, various niche functionality does work, e.g. Ammo dumping is fine, as is Autopilot. The dusk effect that kicks in at the start of Wolf 3 is identical to the original game.

I'll have a further look. It would be nice to be able to get it to optionally use cd audio, rather than ripped tracks.

Separately on 1.1.34, re-tested on 1.1.37

  • The missing ambient sound in the Clan Hall has now been fixed, but this sound keeps playing when you go into the Ready Room, or you re-open the Register (aka pilot register). Ordinarily the sound should stop at these points.
  • The two Falcon dropships on Sable Flame can now turn their turrets, but they can't aim down. So they seem to perpetually shoot over your head. On DOS they can aim directly at you and really damage your mech.
  • The Clan Hall is being rendered with both vertical and horizontal black strips which the mouse can be moved behind (I'm using a 1920x1080 monitor). In-game, it renders without issue in fullscreen.
  • Mechs and turrets are trying to shoot your mech through indestructible terrain. This is particularly noticeable on Burning Chrome, where the Mad Dog and Summoner will damage themselves with their own LRMs when facing Ice Walls, and the single ledge-mounted turret will blast away at the Ice Wall nearest to it.
  • The Jade Falcon Clan Hall does have an ambient noise loop, a different one to that played in the Wolf Clan Hall.
  • I can't believe I missed this, but when you land on the Clan selection splash screen, if you select Falcon, Wolf or Trial of Grievance, the "fire" ambient noise from the splash screen keeps playing over the SMK intro video, into the Wolf/Falcon registers, or into the Trial of Grievance screen.
  • There are some buildings missing from Wolf Trial 1, possibly similar to the missing terrain from Flame Tongue mentioned earlier.
  • There is a red dot on your mech, which shouldn't be there, when you go into Satellite View and then lower the Satellite range.
  • On Scorching Sand, the enemy turrets are being rendered at the lower edge of the left targetting MFD. I haven't seen any other objects do this, usually everything else is rendering in the centre.
  • In DOS, the two Jenners that start on top of the Mesa on Scorching Sand will use their jumpjets to slow down after they jump off (you can see the JJ plumes). In the recomp, they don't so they hard land and both get red-damaged legs.

The LOD distances I mentioned earlier are still not correct, here are three screenshots, DOS was at a distance of 442M, recomp was at 445M.

The attachment MW20001.GIF is no longer available
The attachment mw2_recomp.png is no longer available

If you look at the combined picture, you can see the skinny arms, thighs and ankles on the recomp Mad Dog.

The attachment lod_distances.jpg is no longer available

It might be there is a bug in DOS MW2 with the range at which it actually switches to the low-poly LODs. It wouldn't be the first time, there were numerous bugs with listed-versus-actual weapon ranges in the original game.

Perhaps not bugs, but questions:

  1. Did you want the graphical issues on the radar display listed, or are you across those?
  2. Also, just looking at how the skyline is rendered in those screenshots, was changing from the stepped skyline colours to a more blended look intentional? I think.. this might be screwing with the Pre-dawn effect on Scorching Sand, it just makes everything look black there, rather than graduated.
  3. Are you able to get Claude to check if enemy Mechs should be trying to shoot you through destructible buildings or not? When testing in DOS... roughly 66% of them did not... but 33% of them did.... But that might just be bugginess in the original game.

Screenshots of Scorching Sand old-vs-new skyline while it's in the "Pre-dawn" phase. After 5 minutes it lights up to daylight.

The attachment MW20000.GIF is no longer available
The attachment ss_recomp.jpg is no longer available
Last edited by KHORG on 2026-11-20, 18:59. Edited 9 times in total.

Reply 126 of 132, by myne

User metadata
Rank l33t
Rank
l33t

That last one...
Not sure it's a "new" bug.
The AI was not exactly stellar.

I built:
Convert old ASUS ASC boardviews to KICAD PCB!
Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.
Dos+Windows 3.11+tcp+vbe_svga auto-install iso template
Script to backup Win9x\ME drivers from a working install
Re: The thing no one asked for: KICAD 440bx reference schematic

Reply 127 of 132, by Deffnator

User metadata
Rank Member
Rank
Member
myne wrote on Today, 08:37:

That last one...
Not sure it's a "new" bug.
The AI was not exactly stellar.

Activision had to use Dark Reign's Ai code for Battlezone because the mech 2 engine ai was terrible.

Reply 128 of 132, by Mikeyy00

User metadata
Rank Newbie
Rank
Newbie
KHORG wrote on Today, 08:31:
Virustotal is happy with 1.1.34 now. […]
Show full quote

Virustotal is happy with 1.1.34 now.

I've gone back and re-checked these on 1.1.34, there are a few bugs from this list still present.

KHORG wrote on 2026-11-15, 02:50:
I've just fired up the MW2 recomp, some things I've noticed when comparing it to the DOS 1.1 version which I have running throug […]
Show full quote

I've just fired up the MW2 recomp, some things I've noticed when comparing it to the DOS 1.1 version which I have running through dosbox:

  • The grey MW2 menu cursor seems to have been replaced with a default windows cursor?
  • If you click on the Archive Holoprojector, it cuts to a zoomed-in view of the "projection" animation, then cuts back again to the normal view. Usually it just runs this animation in the distance of the hall, then cuts to the display.
  • There's some kind of slim vertical red line on enemy target brackets when selecting enemies.
  • Using Z to zoom in immediately causes the 3D cockpit outline to be culled by the renderer. It only re-appears when you shift-zoom all the way back to default.
  • Funnily CTRL-Z has carried over the buggy behaviour from the original game. It was meant to reset your zoom, but in original MW2 had a bad tendency to bounce the camera around.
  • The Satellite View doesn't show a top-down view of your own mech, it also incorrectly carries over enemy targetting brackets from first-person view and puts them in random places.
  • The floatiness of the original targetting reticle seems to be gone. Now if you let go of a key it immediately stops.
  • There's a big frame-rate drop when turning on or off light amplification. Image enhancement is fine.
  • The turrets on wolf level 2 don't seem to be able to turn. They just start blazing away in whatever direction they were originally pointing at.
  • There are various 3D hill objects missing from wolf mission 2. They should be visible as soon as you drop in.
  • When you arrive at a Nav point, two things should happen; 1) the unselected nav icon on your radar for that location should dim slightly (this works) 2) the text for "Nav Alpha" in the bottom left of the screen should also dim (and stay dimmed even if you change to a different waypoint then back) to indicate you've already been there, this doesn't occur.
  • Satellite View doesn't show enemy buildings in red outline (particularly on Wolf 3), it just shows them as black outline.
  • Satellite View also doesn't show the enemy fire in yellow. Usually you can see incoming PPCs, lasers and missiles.
  • On your targetting MFD, (bottom left display) the helicopter on wolf mission 3 should show as a blue fuselage and a red circle for the blade above it, but only the fuselage appears in the MFD view.
  • The NPC vehicle (automobile) driving around on wolf 3 isn't there.
  • On wolf mission 3, the red or green roof-lights on the taller building aren't there. Usually they should fade in and out, being either green or red.
  • In Satellite View, 2D sprites like fires should appear as little fire images, but currently they only show as a black line.
  • In original or recomp MW2, when you're shooting the ground, there is a black puff of dust. However in the original game there is a semi-bug when shooting buildings, static vehicles etc. In this case it should show a weapon splash effect, but it didn't always, sometimes the angle on the building/object would be wrong and you would instead see a black puff of dust and wonder if you were hitting it. However, in the recomp it only shows the black puff of dush when shooting buildings/objects, not the weapon splashes.
  • F5-F6-F7-F8 should act as alternates for the right MFD, e.g. if you press F8, you can press F5 to cycle back to the default mode. This doesn't work in the recomp, instead.... F5 and F6 are linked to each other, F7 and F8 are also linked, you need to press F8 again before you can get back to F5 and all sorts of UXUI that makes my head hurt.
  • If you look down (CTRL up/down) in the Mad Dog cockpit, you can see the backs of the Mad Dog legs, which you shouldn't be able to. I haven't checked all the other mechs for this.
  • Wolf Trial 1, the first two mechs don't move until you're looking down on them from a hill, they should be moving towards you at about the 10 second mark (which is a couple of seconds after you're fully online).
  • Wolf Trial 1 again, the second two mechs should start moving towards you as soon as you destroy the Engagement Sphere. Instead the first only moves towards you when attacked, and his starmate follows him around like an AI with no attack orders.
  • Some of the original 'flight sim' controls seem to have changed? In the original game, UP aimed down and CTRL-UP looked down. In the recomp, UP aims down and CTRL-DOWN (not CTRL-UP) looks down.
  • Sable Flame is all kinds of busted. The Sensor Array Dome is opaque when it should be transparent and you should be able to see into it and through it.
  • Also on Sable Flame, the 2nd Mech group should power up after you destroy the 1st, and the 3rd should power up after you destroy the 2nd. But the the 2nd and 3rd come online at the same time after the 1st is destroyed. Also weirdly the 1st group doesn't appear on radar after betty announces Enemy Powerup Detected.
  • Still on Sable Flame, the third group of mechs get distracted by a Wolf dropship which is flying around above them and instead run around shooting at that.
  • Still on Sable Flame, the Falcon dropships have a Wolf logo on the side (I checked in the original, it's definitely the Falcon logo there).
  • Dropships seem not to be able to turn/aim their turret on top, so like the current problem with static turrets, they just shoot straight forwards when they see something.
  • Still on Sable Flame, there is some weird switcheroo going on with which mechs are in which group, it should be 3-2-2. But instead it's 2-2-3? One of the Mad Dog's from the first star ends up in the last and I feel like the Stormcrow changed group also.

That said, various niche functionality does work, e.g. Ammo dumping is fine, as is Autopilot. The dusk effect that kicks in at the start of Wolf 3 is identical to the original game.

I'll have a further look. It would be nice to be able to get it to optionally use cd audio, rather than ripped tracks.

Separately on 1.1.34:

  • The missing ambient sound in the Clan Hall has now been fixed, but this sound keeps playing when you go into the Ready Room, or you re-open the Register (aka pilot register). Ordinarily the sound should stop at these points.
  • The two Falcon dropships on Sable Flame can now turn their turrets, but they can't aim down. So they seem to perpetually shoot over your head. On DOS they can aim directly at you and really damage your mech.
  • The Clan Hall is being rendered with both vertical and horizontal black strips which the mouse can be moved behind (I'm using a 1920x1080 monitor). In-game, it renders without issue in fullscreen.
  • Mechs and turrets are trying to shoot your mech through indestructible terrain. This is particularly noticeable on Burning Chrome, where the Mad Dog and Summoner will damage themselves with their own LRMs when facing Ice Walls, and the single ledge-mounted turret will blast away at the Ice Wall nearest to it.
  • The Jade Falcon Clan Hall does have an ambient noise loop, a different one to that played in the Wolf Clan Hall.
  • I can't believe I missed this, but when you land on the Clan selection splash screen, if you select Falcon, Wolf or Trial of Grievance, the "fire" ambient noise from the splash screen keeps playing over the SMK intro video, into the Wolf/Falcon registers, or into the Trial of Grievance screen.
  • There are some buildings missing from Wolf Trial 1, possibly similar to the missing terrain from Flame Tongue mentioned earlier.
  • There is a red dot on your mech, which shouldn't be there, when you go into Satellite View and then lower the Satellite range.
  • On Scorching Sand, the enemy turrets are being rendered at the lower edge of the left targetting MFD. I haven't seen any other objects do this, usually everything else is rendering in the centre.
  • In DOS, the two Jenners that start on top of the Mesa on Scorching Sand will use their jumpjets to slow down after they jump off (you can see the JJ plumes). In the recomp, they don't so they hard land and both get red-damaged legs.

The LOD distances I mentioned earlier are still not correct, here are three screenshots, DOS was at a distance of 442M, recomp was at 445M.

The attachment MW20001.GIF is no longer available
The attachment mw2_recomp.png is no longer available

If you look at the combined picture, you can see the skinny arms, thighs and ankles on the recomp Mad Dog.

The attachment lod_distances.jpg is no longer available

It might be there is a bug in DOS MW2 with the range at which it actually switches to the low-poly LODs. It wouldn't be the first time, there were numerous bugs with listed-versus-actual weapon ranges in the original game.

Perhaps not bugs, but questions:

  1. Did you want the graphical issues on the radar display listed, or are you across those?
  2. Also, just looking at how the skyline is rendered in those screenshots, was changing from the stepped skyline colours to a more blended look intentional? I think.. this might be screwing with the Pre-dawn effect on Scorching Sand, it just makes everything look black there, rather than graduated.
  3. Are you able to get Claude to check if enemy Mechs should be trying to shoot you through destructible buildings or not? When testing in DOS... roughly 66% of them did not... but 33% of them did.... But that might just be bugginess in the original game.

Screenshots of Scorching Sand old-vs-new skyline while it's in the "Pre-dawn" phase. After 5 minutes it lights up to daylight.

The attachment MW20000.GIF is no longer available
The attachment ss_recomp.jpg is no longer available

Checking these.

Re your questions:
Sure, if there's issues list them.. I don't need screenshots unless its hard to describe
It's supposed to flip from stepped colors/blended if you choose dos smooth / dos dithered.. is it not on your end?
I'll ask.

Reply 129 of 132, by Mikeyy00

User metadata
Rank Newbie
Rank
Newbie

Claude Regarding AI (based off the decomped source):

Every AI pilot checks line of sight before firing. There’s a skill flag that would let weaker pilots skip the check, but it never takes effect, because the game limits pilot skill to a range where the check always runs.
The check is one straight line between the two mechs’ positions, and an AI fires when only its target is on that line. A mech partly behind a building, or behind one whose collision shape is smaller than its model, passes the check. Its shots then hit the building, which looks like shooting through it.
Your one-in-three result in DOS fits that, so it’s the original’s behaviour. The port already runs the same check for every AI, so I left it alone.

Reply 130 of 132, by Mikeyy00

User metadata
Rank Newbie
Rank
Newbie
KHORG wrote on Today, 08:31:
Virustotal is happy with 1.1.34 now. […]
Show full quote

Virustotal is happy with 1.1.34 now.

I've gone back and re-checked these on 1.1.34, there are a few bugs from this list still present.

KHORG wrote on 2026-11-15, 02:50:
I've just fired up the MW2 recomp, some things I've noticed when comparing it to the DOS 1.1 version which I have running throug […]
Show full quote

I've just fired up the MW2 recomp, some things I've noticed when comparing it to the DOS 1.1 version which I have running through dosbox:

  • The grey MW2 menu cursor seems to have been replaced with a default windows cursor?
  • If you click on the Archive Holoprojector, it cuts to a zoomed-in view of the "projection" animation, then cuts back again to the normal view. Usually it just runs this animation in the distance of the hall, then cuts to the display.
  • There's some kind of slim vertical red line on enemy target brackets when selecting enemies.
  • Using Z to zoom in immediately causes the 3D cockpit outline to be culled by the renderer. It only re-appears when you shift-zoom all the way back to default.
  • Funnily CTRL-Z has carried over the buggy behaviour from the original game. It was meant to reset your zoom, but in original MW2 had a bad tendency to bounce the camera around.
  • The Satellite View doesn't show a top-down view of your own mech, it also incorrectly carries over enemy targetting brackets from first-person view and puts them in random places.
  • The floatiness of the original targetting reticle seems to be gone. Now if you let go of a key it immediately stops.
  • There's a big frame-rate drop when turning on or off light amplification. Image enhancement is fine.
  • The turrets on wolf level 2 don't seem to be able to turn. They just start blazing away in whatever direction they were originally pointing at.
  • There are various 3D hill objects missing from wolf mission 2. They should be visible as soon as you drop in.
  • When you arrive at a Nav point, two things should happen; 1) the unselected nav icon on your radar for that location should dim slightly (this works) 2) the text for "Nav Alpha" in the bottom left of the screen should also dim (and stay dimmed even if you change to a different waypoint then back) to indicate you've already been there, this doesn't occur.
  • Satellite View doesn't show enemy buildings in red outline (particularly on Wolf 3), it just shows them as black outline.
  • Satellite View also doesn't show the enemy fire in yellow. Usually you can see incoming PPCs, lasers and missiles.
  • On your targetting MFD, (bottom left display) the helicopter on wolf mission 3 should show as a blue fuselage and a red circle for the blade above it, but only the fuselage appears in the MFD view.
  • The NPC vehicle (automobile) driving around on wolf 3 isn't there.
  • On wolf mission 3, the red or green roof-lights on the taller building aren't there. Usually they should fade in and out, being either green or red.
  • In Satellite View, 2D sprites like fires should appear as little fire images, but currently they only show as a black line.
  • In original or recomp MW2, when you're shooting the ground, there is a black puff of dust. However in the original game there is a semi-bug when shooting buildings, static vehicles etc. In this case it should show a weapon splash effect, but it didn't always, sometimes the angle on the building/object would be wrong and you would instead see a black puff of dust and wonder if you were hitting it. However, in the recomp it only shows the black puff of dush when shooting buildings/objects, not the weapon splashes.
  • F5-F6-F7-F8 should act as alternates for the right MFD, e.g. if you press F8, you can press F5 to cycle back to the default mode. This doesn't work in the recomp, instead.... F5 and F6 are linked to each other, F7 and F8 are also linked, you need to press F8 again before you can get back to F5 and all sorts of UXUI that makes my head hurt.
  • If you look down (CTRL up/down) in the Mad Dog cockpit, you can see the backs of the Mad Dog legs, which you shouldn't be able to. I haven't checked all the other mechs for this.
  • Wolf Trial 1, the first two mechs don't move until you're looking down on them from a hill, they should be moving towards you at about the 10 second mark (which is a couple of seconds after you're fully online).
  • Wolf Trial 1 again, the second two mechs should start moving towards you as soon as you destroy the Engagement Sphere. Instead the first only moves towards you when attacked, and his starmate follows him around like an AI with no attack orders.
  • Some of the original 'flight sim' controls seem to have changed? In the original game, UP aimed down and CTRL-UP looked down. In the recomp, UP aims down and CTRL-DOWN (not CTRL-UP) looks down.
  • Sable Flame is all kinds of busted. The Sensor Array Dome is opaque when it should be transparent and you should be able to see into it and through it.
  • Also on Sable Flame, the 2nd Mech group should power up after you destroy the 1st, and the 3rd should power up after you destroy the 2nd. But the the 2nd and 3rd come online at the same time after the 1st is destroyed. Also weirdly the 1st group doesn't appear on radar after betty announces Enemy Powerup Detected.
  • Still on Sable Flame, the third group of mechs get distracted by a Wolf dropship which is flying around above them and instead run around shooting at that.
  • Still on Sable Flame, the Falcon dropships have a Wolf logo on the side (I checked in the original, it's definitely the Falcon logo there).
  • Dropships seem not to be able to turn/aim their turret on top, so like the current problem with static turrets, they just shoot straight forwards when they see something.
  • Still on Sable Flame, there is some weird switcheroo going on with which mechs are in which group, it should be 3-2-2. But instead it's 2-2-3? One of the Mad Dog's from the first star ends up in the last and I feel like the Stormcrow changed group also.

That said, various niche functionality does work, e.g. Ammo dumping is fine, as is Autopilot. The dusk effect that kicks in at the start of Wolf 3 is identical to the original game.

I'll have a further look. It would be nice to be able to get it to optionally use cd audio, rather than ripped tracks.

Separately on 1.1.34:

  • The missing ambient sound in the Clan Hall has now been fixed, but this sound keeps playing when you go into the Ready Room, or you re-open the Register (aka pilot register). Ordinarily the sound should stop at these points.
  • The two Falcon dropships on Sable Flame can now turn their turrets, but they can't aim down. So they seem to perpetually shoot over your head. On DOS they can aim directly at you and really damage your mech.
  • The Clan Hall is being rendered with both vertical and horizontal black strips which the mouse can be moved behind (I'm using a 1920x1080 monitor). In-game, it renders without issue in fullscreen.
  • Mechs and turrets are trying to shoot your mech through indestructible terrain. This is particularly noticeable on Burning Chrome, where the Mad Dog and Summoner will damage themselves with their own LRMs when facing Ice Walls, and the single ledge-mounted turret will blast away at the Ice Wall nearest to it.
  • The Jade Falcon Clan Hall does have an ambient noise loop, a different one to that played in the Wolf Clan Hall.
  • I can't believe I missed this, but when you land on the Clan selection splash screen, if you select Falcon, Wolf or Trial of Grievance, the "fire" ambient noise from the splash screen keeps playing over the SMK intro video, into the Wolf/Falcon registers, or into the Trial of Grievance screen.
  • There are some buildings missing from Wolf Trial 1, possibly similar to the missing terrain from Flame Tongue mentioned earlier.
  • There is a red dot on your mech, which shouldn't be there, when you go into Satellite View and then lower the Satellite range.
  • On Scorching Sand, the enemy turrets are being rendered at the lower edge of the left targetting MFD. I haven't seen any other objects do this, usually everything else is rendering in the centre.
  • In DOS, the two Jenners that start on top of the Mesa on Scorching Sand will use their jumpjets to slow down after they jump off (you can see the JJ plumes). In the recomp, they don't so they hard land and both get red-damaged legs.

The LOD distances I mentioned earlier are still not correct, here are three screenshots, DOS was at a distance of 442M, recomp was at 445M.

The attachment MW20001.GIF is no longer available
The attachment mw2_recomp.png is no longer available

If you look at the combined picture, you can see the skinny arms, thighs and ankles on the recomp Mad Dog.

The attachment lod_distances.jpg is no longer available

It might be there is a bug in DOS MW2 with the range at which it actually switches to the low-poly LODs. It wouldn't be the first time, there were numerous bugs with listed-versus-actual weapon ranges in the original game.

Perhaps not bugs, but questions:

  1. Did you want the graphical issues on the radar display listed, or are you across those?
  2. Also, just looking at how the skyline is rendered in those screenshots, was changing from the stepped skyline colours to a more blended look intentional? I think.. this might be screwing with the Pre-dawn effect on Scorching Sand, it just makes everything look black there, rather than graduated.
  3. Are you able to get Claude to check if enemy Mechs should be trying to shoot you through destructible buildings or not? When testing in DOS... roughly 66% of them did not... but 33% of them did.... But that might just be bugginess in the original game.

Screenshots of Scorching Sand old-vs-new skyline while it's in the "Pre-dawn" phase. After 5 minutes it lights up to daylight.

The attachment MW20000.GIF is no longer available
The attachment ss_recomp.jpg is no longer available

Most (hopefully all) should be fixed in 1.1.36. Let me know what didn't.

I've confirmed a few are still there, working on those.. (there are a bunch that are fixed though).

Reply 131 of 132, by KHORG

User metadata
Rank Newbie
Rank
Newbie

On 1.1.37

  • The NPC vehicle (automobile) driving around on wolf 3 is now there, but is missing the white headlight projection effect it would display in front of it.
  • The NPC vehicle (automobile) driving around on wolf 3 is now there, but has a displey issue with it's two yellow headlamps, if you look at them from the wrong angle, one of them will merge into the vehicle itself.
  • On wolf mission 3, the red or green roof-lights on the taller building are now visible, but they are being rendered at all distances. So you can see the lights across the entire map before you can see the buildings.
  • On wolf mission 3, the red or green roof-lights on the taller building are now visible, but they are being shown as large square pixels, not as the smaller pinpricks of light as in the original game.
  • On Sable Flame, the Sensor Array Dome is being rendered as a red wireframe, when it should be a grey wireframe.
  • On Sable Flame, the two Falcon dropships can now aim down, but they are shooting at you with an offset, so perpetually miss either to the left or to the right. This happens on both Hard and Medium.
  • The radar Extent arms are not being rendered out to the radar circle, instead they are being cut short, leaving a gap between them and the radar circle.
  • Also the radar (both circle and arms) is initially loading in at a higher brightness while your mech is powering up, then is reducing to the correct brightness (both circle and arms, with the arms being correctly slightly dimmer) once your mech is online.
  • When you abort mission, the overhead-view spinning ejection effect doesn't play, instead it just fades to black. It does correctly play if you eject using ctrl-alt-e.
  • When the SMK videos play, the mouse cursor should disappear, and re-appear after the end of the video.

Also the Sensor Array Dome on Sable Flame is being rendered at 1.3KM+, when originally it popped in between 900-1km. Not sure if this was intentional around longer draw distances? Honestly it kind of works given the size of the dome.

Reply 132 of 132, by Mikeyy00

User metadata
Rank Newbie
Rank
Newbie
Deffnator wrote on 2026-11-11, 14:59:
Mikeyy00 wrote on 2026-11-10, 21:37:
Update on the tail end of the thread in case you didn't catch my first post edit. […]
Show full quote

Update on the tail end of the thread in case you didn't catch my first post edit.

Mech 2 and GBL are basically as done as I can get them. Any bugs you find, let me know.
Mercs is probably.. 80%? of the way there. I expect to have it basically done in the next week or so.

Heavy Gear 1 is probably ~50% ready. ETA end of Nov.
Heavy Gear 2 has been started, hoping for end of Nov too, but it's a totally different engine. I remember 2 being a bear to get running on newer OSes too.. so I figured why not.
When both are ready, I'll start a new thread for them.

Hope you look more unto Mech1 soon

New build up. Check the changelog. Let me know what issues you see.