VOGONS


Mechwarrior 2 Decomp/Recomp

Topic actions

Reply 140 of 156, by mattrock1988

User metadata
Rank Member
Rank
Member

So I've been filing countless bug tickets in the github for the Mercs-port version of this game.

I'm going to be honest, this business of AI slopping games together really stinks. I mean this with no disrespect to the guy working on this, but either the tools being used are careless and don't actually understand intention behind fixes, or the bug reports being filed don't get playtested. It's sort of lazy and doesn't speak to quality.

I'll give an example of this. The buildings with windows have a shimmering bug, and each time I send over a request to get it fixed, I am told that they are sure *this* new build has it fixed. Nope. Tried it again, and although it gets a bit closer, it's still janky. There is too much blind trust in the tools and not enough critical thinking.

I thought serious progress was being made with all the fixes being made to the Mac version, then unexplainable issues show up in other versions, or when specific scenarios occur, and it makes the entire exercise of running this port more pain than it's worth.

I've decided to go back to playing in DOSBox. At least I know it's consistent.

Retro PC: Intel Celeron Mendocino @ 500 MHz, TYAN Tomahawk BX, 6 GB IDE Quantum Bigfoot, 256 MB SDRAM, DVD-ROM, 1.44 MB floppy, Nvidia GeForce MX 440 AGP, ESS AudioDrive 1868F ISA

Reply 141 of 156, by leileilol

User metadata
Rank l33t++
Rank
l33t++

^^ that's why I don't engage with such projects. I've already seen my feedback fed into a prompt with my words paraphrased as they were into a slopper's comments for one non-disclosed vibed project, so i'm better off not wasting my time, just mute everyone vibing and not give any feedback at all. I only look forward to new projects that declare out of the gate they're clean and reject AI issues/pulls/commits. DOSBox-Pure's nice these days, and can emulate the 3dfx Voodoo Graphics at a low level through an uprezzed OpenGL output (no wrapper DLL passthrough garbage) so that probably would scratch the graphics itch if one desired...

FUCK "AI". It is a tool of fascism. We do not need it. We do not use it.

Reply 142 of 156, by Mikeyy00

User metadata
Rank Newbie
Rank
Newbie
mattrock1988 wrote on Yesterday, 20:07:
So I've been filing countless bug tickets in the github for the Mercs-port version of this game. […]
Show full quote

So I've been filing countless bug tickets in the github for the Mercs-port version of this game.

I'm going to be honest, this business of AI slopping games together really stinks. I mean this with no disrespect to the guy working on this, but either the tools being used are careless and don't actually understand intention behind fixes, or the bug reports being filed don't get playtested. It's sort of lazy and doesn't speak to quality.

I'll give an example of this. The buildings with windows have a shimmering bug, and each time I send over a request to get it fixed, I am told that they are sure *this* new build has it fixed. Nope. Tried it again, and although it gets a bit closer, it's still janky. There is too much blind trust in the tools and not enough critical thinking.

I thought serious progress was being made with all the fixes being made to the Mac version, then unexplainable issues show up in other versions, or when specific scenarios occur, and it makes the entire exercise of running this port more pain than it's worth.

I've decided to go back to playing in DOSBox. At least I know it's consistent.

The Window bug is unique. Heres everything up to now trying to sus that out:

Summary
The window bands on the Instant Action office tower still flicker for the tester after four releases of fixes (v1.2.23, v1.2.26, v1.2.28, v1.2.30). Each fix removed the flicker in the case it targeted. The latest report says it now shows on a different side of the building. It has not been reproduced in a test render here, because the tower comes out unlit in every capture so far.
• Where: the "Office Building" target (model S_1SMTWR) in Instant Action's office1 area, seen in seed 13 at about (-94,600, -90,600).
• What: red window bands on the dark walls break up as the view moves. Sometimes a band vanishes in a diagonal, stair-stepped patch, which is what you see when two surfaces at almost the same depth fight for the same pixels.
• Status: open, and listed in KNOWN_ISSUES. The next step depends on the tester's mission, side and graphics settings.
The building
S_1SMTWR is a single object with 29 polygons: four walls, a roof and 24 window bands, six on each wall. The bands are not on the walls. They stand a small distance in front of them, and that distance is different on each pair of sides.

p20–p25
• The north bands are slightly twisted: two corners sit 1 cm out and two sit 2 cm out.
• The east and west walls (p26, p27) come after their bands in the polygon list. The north and south walls (p0, p1) come before theirs.
• DOS draws without a depth buffer, painting polygons in its own sorted order, so these tiny gaps never matter there. The port uses a GPU depth buffer, so a band only 1–7 cm in front of its wall is at risk of depth fighting with it.
• Model coordinates are as stored in the PRJ; the damaged (SA1SMTWR) and collapse (SCGSMTWR) variants are hidden until the building is hit and were checked as not involved.
What was changed, release by release
Each release fixed the case it was aimed at; the tester then found the flicker somewhere the fix did not reach.
Release
Report that prompted it
Change
Verified by
v1.2.30
Video: one band at eye height breaking up in a diagonal patch
The DOS look grows each lit polygon 3 px outward and lets its span walk trim it. Grown corners moved on screen but kept their old depth, which tilted the polygon's depth plane. Grown corners now stay on their triangle's plane, as textured corners already did.
Not visually: the tower rendered unlit. Three campaign scenes re-captured identical to before.
v1.2.28
Bands still cut in and out, video plus screenshots
The v1.2.23 and v1.2.26 lift only caught overlays within 2 cm of a face. This tower's east and west bands are 7 cm out, so they were never lifted. Polygons 2–60 cm proud of a face on its seen side now get the same treatment. Cockpit parts are excluded.
Seed 13 office area rendered at 1080x720 from the side: bands reach their ends.
v1.2.26
Windows still flicker at a distance
Added a depth bias in the world vertex shader for lifted overlays (clip z pulled forward by 1.5×10⁻⁶ × w per lift level, up to 16), and extended the lift to Titanium models.
Render checks of the tower at range.
v1.2.23
Building windows cut in and out
New coplanar-lift pass: polygons lying on a larger face are moved 4 cm toward the viewer's side of that face.
Render checks; caught the north and south bands only.
Two mistakes along the way, both caught before release:
• The first v1.2.23 lift pushed the bands into the wall instead of out of it. The lift direction was flipped to match the shader's backface convention.
• The first v1.2.28 build broke the cockpit render test, because the wider rule also lifted cockpit polygons. Cockpit parts were excluded.
Checked and ruled out
• Depth buffer precision. The renderer asks for a 24-bit depth buffer (32-bit float on Apple). At 30 m with a 60 cm near plane, a 1 cm gap is about 200 times the smallest depth step, so precision alone should not cause fighting.
• The lift missing some bands. Walked through the lift code against all 24 band polygons: every one finds its wall, including the twisted north bands and the east and west bands whose walls come later in the list.
• The damaged and collapse variants. SA1SMTWR and SCGSMTWR share the tower's position but stay hidden until it is damaged. Their geometry does not overlap the wall faces.
• Something else drawn over the tower. No particles, debris or moving parts are near it in seed 13.
• Regressions from the fixes. Each release passed make check, check-shell and check-campaign, and three campaign scenes (BET1, IVA1, MED1) re-captured after v1.2.30 matched their earlier DOSBox scores exactly.
Why it is hard to reproduce here
The tester sees a lit grey tower with bright red bands against a dusk sky. Every render here shows the tower almost black, with bands that cannot be told from the walls.
• Placement. The tower is in Instant Action seed 13's office1 area, placed at (−89,500, −89,500). Several start positions were tried; some faced away, one started on a 144 m rooftop and fell, and one finally put the tower in view at ground level.
• Lighting. Seed 13 starts at 07:00 game time (the day palette). Forcing dusk (17:30) and noon with MERCS_TEST_TOD_START still left the tower unlit, so the tester's lighting comes from something not matched here: a different seed, mission or game look.
• Headless runs. The test harness renders off screen through Vulkan's software driver. It cannot show the tester's exact window, and each 10-second render takes about 1.5 minutes.
• The video. Frames show the flicker at the crosshair's height on one band, in a stair-stepped diagonal. That is the clearest clue, and it is what the v1.2.30 change targeted.
Open theories and next steps
The likeliest remaining cause is in the DOS look's polygon growth and its span-walk trimming, not in depth precision. The latest report of a "different side" fits that: the two pairs of sides differ in gap (1 cm against 7 cm) and in polygon order.
Theories still open
1. Growth on textured polygons. v1.2.30 kept grown Gouraud corners on their plane. The textured path already did, but the walk can still discard different pixels on the band and the wall when both are near the screen edge or crossing it.
2. The 1 cm sides specifically. The north and south bands sit only 1–2 cm out. The lift adds 4 cm and the bias adds a little more, but a steep viewing angle shrinks the gap on screen. If the "different side" is north or south, that points here.
3. A non-DOS game look. If the tester plays with a 3D look, the DOS growth is not involved at all, and the 3D path's handling of the lift would be the place to look.

There's going to be weird shit converting a 30 year old game to modern code/graphics stack. You're absolutely right that Dosbox is the only way to play it 100% as you remember.

For what it's worth, I appreciate the reports as I don't (currently) have the time to play the game start to finish every time something is pushed.

In Claudes defence, when it does a bug fix. it very may well cause other regressions. Could I tell it not to do that? Yes, but the rub is it'll take ~4 hours for it to do a full sweep of the game and compare frame by frame vs a copy it has in Dosbox. 2-3 of these full sweeps exhausts my work Claudes ($170 CAD plan) weekly limit. So I'm a bit limited on busting its balls.

Im confident even slop coded, it'll get sorted eventually. Heck, it's only been going on less than two months and the game is mostly the way there (in my opinion).

Reply 143 of 156, by mattrock1988

User metadata
Rank Member
Rank
Member
leileilol wrote on Yesterday, 21:31:

^^ that's why I don't engage with such projects. I've already seen my feedback fed into a prompt with my words paraphrased as they were into a slopper's comments for one non-disclosed vibed project, so i'm better off not wasting my time, just mute everyone vibing and not give any feedback at all. I only look forward to new projects that declare out of the gate they're clean and reject AI issues/pulls/commits. DOSBox-Pure's nice these days, and can emulate the 3dfx Voodoo Graphics at a low level through an uprezzed OpenGL output (no wrapper DLL passthrough garbage) so that probably would scratch the graphics itch if one desired...

Honestly, I tried giving this a fair shake and keeping an open mind, but I’ve noticed that if the person doing the decomp is not a programmer themselves, it’s a true exercise in frustration.

By comparison, there is another project called the Mechwarrior 3 Remake by Telltale Atheist that is actually good, since it’s not just slopped together. The dude himself has programming experience and, more importantly, has a plan that he executes. Just a week or so in and his port is rock solid enough that I can recommend it to my friends. The few bug reports that get filed also seem to deal with more meaningful issues instead of “I see this random anomaly - fix this - blah blah blah”

I’m not an AI hater, per se. Heck, I think AI tools can really make certain workloads much easier and enhance planning and process. Yet I have immense respect for projects that try to do the hard work properly, and sometimes even forego the AI tools entirely if possible, especially for code generation. Most of the code coming out of Claude is questionable at best.

Last edited by mattrock1988 on 2026-11-22, 06:19. Edited 1 time in total.

Retro PC: Intel Celeron Mendocino @ 500 MHz, TYAN Tomahawk BX, 6 GB IDE Quantum Bigfoot, 256 MB SDRAM, DVD-ROM, 1.44 MB floppy, Nvidia GeForce MX 440 AGP, ESS AudioDrive 1868F ISA

Reply 144 of 156, by mattrock1988

User metadata
Rank Member
Rank
Member
Mikeyy00 wrote on Yesterday, 21:48:
The Window bug is unique. Heres everything up to now trying to sus that out: […]
Show full quote
mattrock1988 wrote on Yesterday, 20:07:
So I've been filing countless bug tickets in the github for the Mercs-port version of this game. […]
Show full quote

So I've been filing countless bug tickets in the github for the Mercs-port version of this game.

I'm going to be honest, this business of AI slopping games together really stinks. I mean this with no disrespect to the guy working on this, but either the tools being used are careless and don't actually understand intention behind fixes, or the bug reports being filed don't get playtested. It's sort of lazy and doesn't speak to quality.

I'll give an example of this. The buildings with windows have a shimmering bug, and each time I send over a request to get it fixed, I am told that they are sure *this* new build has it fixed. Nope. Tried it again, and although it gets a bit closer, it's still janky. There is too much blind trust in the tools and not enough critical thinking.

I thought serious progress was being made with all the fixes being made to the Mac version, then unexplainable issues show up in other versions, or when specific scenarios occur, and it makes the entire exercise of running this port more pain than it's worth.

I've decided to go back to playing in DOSBox. At least I know it's consistent.

The Window bug is unique. Heres everything up to now trying to sus that out:

Summary
The window bands on the Instant Action office tower still flicker for the tester after four releases of fixes (v1.2.23, v1.2.26, v1.2.28, v1.2.30). Each fix removed the flicker in the case it targeted. The latest report says it now shows on a different side of the building. It has not been reproduced in a test render here, because the tower comes out unlit in every capture so far.
• Where: the "Office Building" target (model S_1SMTWR) in Instant Action's office1 area, seen in seed 13 at about (-94,600, -90,600).
• What: red window bands on the dark walls break up as the view moves. Sometimes a band vanishes in a diagonal, stair-stepped patch, which is what you see when two surfaces at almost the same depth fight for the same pixels.
• Status: open, and listed in KNOWN_ISSUES. The next step depends on the tester's mission, side and graphics settings.
The building
S_1SMTWR is a single object with 29 polygons: four walls, a roof and 24 window bands, six on each wall. The bands are not on the walls. They stand a small distance in front of them, and that distance is different on each pair of sides.

p20–p25
• The north bands are slightly twisted: two corners sit 1 cm out and two sit 2 cm out.
• The east and west walls (p26, p27) come after their bands in the polygon list. The north and south walls (p0, p1) come before theirs.
• DOS draws without a depth buffer, painting polygons in its own sorted order, so these tiny gaps never matter there. The port uses a GPU depth buffer, so a band only 1–7 cm in front of its wall is at risk of depth fighting with it.
• Model coordinates are as stored in the PRJ; the damaged (SA1SMTWR) and collapse (SCGSMTWR) variants are hidden until the building is hit and were checked as not involved.
What was changed, release by release
Each release fixed the case it was aimed at; the tester then found the flicker somewhere the fix did not reach.
Release
Report that prompted it
Change
Verified by
v1.2.30
Video: one band at eye height breaking up in a diagonal patch
The DOS look grows each lit polygon 3 px outward and lets its span walk trim it. Grown corners moved on screen but kept their old depth, which tilted the polygon's depth plane. Grown corners now stay on their triangle's plane, as textured corners already did.
Not visually: the tower rendered unlit. Three campaign scenes re-captured identical to before.
v1.2.28
Bands still cut in and out, video plus screenshots
The v1.2.23 and v1.2.26 lift only caught overlays within 2 cm of a face. This tower's east and west bands are 7 cm out, so they were never lifted. Polygons 2–60 cm proud of a face on its seen side now get the same treatment. Cockpit parts are excluded.
Seed 13 office area rendered at 1080x720 from the side: bands reach their ends.
v1.2.26
Windows still flicker at a distance
Added a depth bias in the world vertex shader for lifted overlays (clip z pulled forward by 1.5×10⁻⁶ × w per lift level, up to 16), and extended the lift to Titanium models.
Render checks of the tower at range.
v1.2.23
Building windows cut in and out
New coplanar-lift pass: polygons lying on a larger face are moved 4 cm toward the viewer's side of that face.
Render checks; caught the north and south bands only.
Two mistakes along the way, both caught before release:
• The first v1.2.23 lift pushed the bands into the wall instead of out of it. The lift direction was flipped to match the shader's backface convention.
• The first v1.2.28 build broke the cockpit render test, because the wider rule also lifted cockpit polygons. Cockpit parts were excluded.
Checked and ruled out
• Depth buffer precision. The renderer asks for a 24-bit depth buffer (32-bit float on Apple). At 30 m with a 60 cm near plane, a 1 cm gap is about 200 times the smallest depth step, so precision alone should not cause fighting.
• The lift missing some bands. Walked through the lift code against all 24 band polygons: every one finds its wall, including the twisted north bands and the east and west bands whose walls come later in the list.
• The damaged and collapse variants. SA1SMTWR and SCGSMTWR share the tower's position but stay hidden until it is damaged. Their geometry does not overlap the wall faces.
• Something else drawn over the tower. No particles, debris or moving parts are near it in seed 13.
• Regressions from the fixes. Each release passed make check, check-shell and check-campaign, and three campaign scenes (BET1, IVA1, MED1) re-captured after v1.2.30 matched their earlier DOSBox scores exactly.
Why it is hard to reproduce here
The tester sees a lit grey tower with bright red bands against a dusk sky. Every render here shows the tower almost black, with bands that cannot be told from the walls.
• Placement. The tower is in Instant Action seed 13's office1 area, placed at (−89,500, −89,500). Several start positions were tried; some faced away, one started on a 144 m rooftop and fell, and one finally put the tower in view at ground level.
• Lighting. Seed 13 starts at 07:00 game time (the day palette). Forcing dusk (17:30) and noon with MERCS_TEST_TOD_START still left the tower unlit, so the tester's lighting comes from something not matched here: a different seed, mission or game look.
• Headless runs. The test harness renders off screen through Vulkan's software driver. It cannot show the tester's exact window, and each 10-second render takes about 1.5 minutes.
• The video. Frames show the flicker at the crosshair's height on one band, in a stair-stepped diagonal. That is the clearest clue, and it is what the v1.2.30 change targeted.
Open theories and next steps
The likeliest remaining cause is in the DOS look's polygon growth and its span-walk trimming, not in depth precision. The latest report of a "different side" fits that: the two pairs of sides differ in gap (1 cm against 7 cm) and in polygon order.
Theories still open
1. Growth on textured polygons. v1.2.30 kept grown Gouraud corners on their plane. The textured path already did, but the walk can still discard different pixels on the band and the wall when both are near the screen edge or crossing it.
2. The 1 cm sides specifically. The north and south bands sit only 1–2 cm out. The lift adds 4 cm and the bias adds a little more, but a steep viewing angle shrinks the gap on screen. If the "different side" is north or south, that points here.
3. A non-DOS game look. If the tester plays with a 3D look, the DOS growth is not involved at all, and the 3D path's handling of the lift would be the place to look.

There's going to be weird shit converting a 30 year old game to modern code/graphics stack. You're absolutely right that Dosbox is the only way to play it 100% as you remember.

For what it's worth, I appreciate the reports as I don't (currently) have the time to play the game start to finish every time something is pushed.

In Claudes defence, when it does a bug fix. it very may well cause other regressions. Could I tell it not to do that? Yes, but the rub is it'll take ~4 hours for it to do a full sweep of the game and compare frame by frame vs a copy it has in Dosbox. 2-3 of these full sweeps exhausts my work Claudes ($170 CAD plan) weekly limit. So I'm a bit limited on busting its balls.

Im confident even slop coded, it'll get sorted eventually. Heck, it's only been going on less than two months and the game is mostly the way there (in my opinion).

Hey sorry if my rant was rather negative. I just want to feel like some progress was happening instead of taking a step forward and two steps back.

I wish you well and perhaps it does eventually get solid as a rock, but at this stage I’ve given enough of my time to reports and I’m hoping others in the community pick up the slack.

Retro PC: Intel Celeron Mendocino @ 500 MHz, TYAN Tomahawk BX, 6 GB IDE Quantum Bigfoot, 256 MB SDRAM, DVD-ROM, 1.44 MB floppy, Nvidia GeForce MX 440 AGP, ESS AudioDrive 1868F ISA

Reply 145 of 156, by KHORG

User metadata
Rank Newbie
Rank
Newbie

From testing on 1.1.42:

re-tested on 1.1.45

  • The NPC vehicle on Blade Splint now has a headlight 'projection' rendered in front of it, but it's being dithered into the road texture. It should lie flat on the road texture.
  • The helicopter on Blade Splint has it searchlight (which is projected onto the ground) fixed underneath the helicopter when it should appear in front of it.
  • The red/green lights on the Blade Splint helicopter are partially fixed. The red/green light nearest the player is extruded correctly but the furthest is sunk into the heli. These then swap depending on facing between the player and the helicopter.
  • The large boundary walls of the various Wolf Trial arenas in the original game appear grey if viewed perpendicular, but appear black if viewed on an acute angle. Rightly or wrongly this is the behaviour in DOS and in the new decomp version so should probably be continued until we decide to alter it. However, the decomp version has now picked up an issue where there is massive flickering on these walls.
  • On Cold Crescent, the Falcon Monorail should have small red flashing lights, two at the front and two at the rear.
  • On Cold Crescent, the gate to the Teraformer complex should open when it recognises your IFF, but it doesn't open.
  • On Cold Crescent, the monorail structure itself (which is a non-targettable structure) has a flickering problem when it is rendered.
  • On Cold Crescent, the "nuke" explosion which occurs on a delay after the Teraformer is destroyed is never played. So enemy mechs close to the Teraformer are never destroyed and the player doesn't see the white-light effect on their screen.
  • On Cold Crescent the Teraformer gate seems to be playing a mech-powerup sound whenever you go near it.
  • On Cold Crescent, the Falcon Monorail is coloured red/blue in the left targetting MFD (in wireframe mode) when it should be appearing entirely blue.

Not sure if this one got missed from a few bug reports back:

  • 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.

That problem with the Windows being rendered on Buildings in Mercs, it looks like the engine isn't sure which is meant to be in front, so is dithering the windows based on viewing angle of the player.

Do we know how the windows are handled on the 3D objects? Are they faces cut into the 3D object and then textured? Or are they decals applied to the outside?

Last edited by KHORG on 2026-11-22, 06:55. Edited 8 times in total.

Reply 146 of 156, by myne

User metadata
Rank l33t
Rank
l33t

The original game was buggy. It is practically the first generation of 3d and it ran ok on a 486-66 8mb.

Everything about it was barely working in the first place.
But it was fun, and we were young.

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 147 of 156, by mattrock1988

User metadata
Rank Member
Rank
Member
myne wrote on Yesterday, 23:51:

The original game was buggy. It is practically the first generation of 3d and it ran ok on a 486-66 8mb.

Everything about it was barely working in the first place.
But it was fun, and we were young.

You're not wrong. But the new decomped port seems to add additional bugs and makes usability iffy.

Anyway, I'll give this effort another few weeks or months and check back in on it later.

Retro PC: Intel Celeron Mendocino @ 500 MHz, TYAN Tomahawk BX, 6 GB IDE Quantum Bigfoot, 256 MB SDRAM, DVD-ROM, 1.44 MB floppy, Nvidia GeForce MX 440 AGP, ESS AudioDrive 1868F ISA

Reply 148 of 156, by myne

User metadata
Rank l33t
Rank
l33t

If you just want to play OG windows versions as faithfully as possible, see sig.

And chill. This will mature in time.

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 149 of 156, by Deffnator

User metadata
Rank Member
Rank
Member

I was going to say something about the mentally ill clown above with the attw signature using a word he doesn't understand and sugests garbage like DSpure, but i rather restrain myself.
also myne is right.

MW1-Port 0.0.3 (pc 98) (DOS)

PC98
-Menu sound still has issues
-Movement feels off compared to PC-98, speed issues were fixed but movement feels strange, i think mostly because how this as the x68k port is compared to the original DOS release, the former also had better sounds and 3d interludes.
-Ingame text also feels off but i believe is due to the translation and text size
-Menu also feels wonky with speed issues mostly because of the intro when you skip when using mouseclick or enter and goes into 2 or 3 windows at once

DOS
-Menu has some sluggish issues as skipping the check
-Sound issues just like the DOS release when running on dosbox where the game wouldn't play any single sound
-Keyboard commands doesn't work in battle outside movement.
-Mouse menu speed issues

As for a suggestion for the future if possible, the game uses keyboard only for torso twist as aiming movement, it was clunky even at that time since M and N were aim up and down and < > were torso twist, and at that time mech 1 had analog controller support out of the box, if its possible to remap that to use mouse or modern controlers, it would be nice.

Also, i said earlier that i will await for the sharp x68k support, because it is strange that the pc98 had 3d support but Victor and Activision never ported the 3d overlord interlude to it when traveling from one planet to another.
they really lost a good chance of shipping this game with Mech 2 as a bonus

Reply 150 of 156, by Mikeyy00

User metadata
Rank Newbie
Rank
Newbie
Deffnator wrote on Today, 01:02:
I was going to say something about the mentally ill clown above with the attw signature using a word he doesn't understand and s […]
Show full quote

I was going to say something about the mentally ill clown above with the attw signature using a word he doesn't understand and sugests garbage like DSpure, but i rather restrain myself.
also myne is right.

MW1-Port 0.0.3 (pc 98) (DOS)

PC98
-Menu sound still has issues
-Movement feels off compared to PC-98, speed issues were fixed but movement feels strange, i think mostly because how this as the x68k port is compared to the original DOS release, the former also had better sounds and 3d interludes.
-Ingame text also feels off but i believe is due to the translation and text size
-Menu also feels wonky with speed issues mostly because of the intro when you skip when using mouseclick or enter and goes into 2 or 3 windows at once

DOS
-Menu has some sluggish issues as skipping the check
-Sound issues just like the DOS release when running on dosbox where the game wouldn't play any single sound
-Keyboard commands doesn't work in battle outside movement.
-Mouse menu speed issues

As for a suggestion for the future if possible, the game uses keyboard only for torso twist as aiming movement, it was clunky even at that time since M and N were aim up and down and < > were torso twist, and at that time mech 1 had analog controller support out of the box, if its possible to remap that to use mouse or modern controlers, it would be nice.

Also, i said earlier that i will await for the sharp x68k support, because it is strange that the pc98 had 3d support but Victor and Activision never ported the 3d overlord interlude to it when traveling from one planet to another.
they really lost a good chance of shipping this game with Mech 2 as a bonus

I've got it chewing on the x68k.. bit more work there as it's not x86.. how do we want this though? 3 ways to play? DOS/PC98/X68k? or do we want an amalgamation of the 3 into one?

Reply 151 of 156, by Deffnator

User metadata
Rank Member
Rank
Member
Mikeyy00 wrote on Today, 01:24:
Deffnator wrote on Today, 01:02:
I was going to say something about the mentally ill clown above with the attw signature using a word he doesn't understand and s […]
Show full quote

I was going to say something about the mentally ill clown above with the attw signature using a word he doesn't understand and sugests garbage like DSpure, but i rather restrain myself.
also myne is right.

MW1-Port 0.0.3 (pc 98) (DOS)

PC98
-Menu sound still has issues
-Movement feels off compared to PC-98, speed issues were fixed but movement feels strange, i think mostly because how this as the x68k port is compared to the original DOS release, the former also had better sounds and 3d interludes.
-Ingame text also feels off but i believe is due to the translation and text size
-Menu also feels wonky with speed issues mostly because of the intro when you skip when using mouseclick or enter and goes into 2 or 3 windows at once

DOS
-Menu has some sluggish issues as skipping the check
-Sound issues just like the DOS release when running on dosbox where the game wouldn't play any single sound
-Keyboard commands doesn't work in battle outside movement.
-Mouse menu speed issues

As for a suggestion for the future if possible, the game uses keyboard only for torso twist as aiming movement, it was clunky even at that time since M and N were aim up and down and < > were torso twist, and at that time mech 1 had analog controller support out of the box, if its possible to remap that to use mouse or modern controlers, it would be nice.

Also, i said earlier that i will await for the sharp x68k support, because it is strange that the pc98 had 3d support but Victor and Activision never ported the 3d overlord interlude to it when traveling from one planet to another.
they really lost a good chance of shipping this game with Mech 2 as a bonus

I've got it chewing on the x68k.. bit more work there as it's not x86.. how do we want this though? 3 ways to play? DOS/PC98/X68k? or do we want an amalgamation of the 3 into one?

I say work with it so it is possible to do a better all in one source port, as of now semi emulated, but it would be nice to learn more, mainly for future external file mods like translated menu files and title screen.
i would also suggest a CRT shader based on the NEC monitors of its time but in my opinion this is secondary compared to make the game work 100%

since irl as other stuff is taking my time rn, i am not committed to test more, even the mw4 projects are not in my agenda rn.

in any case, i rather see all 3 versions of mech 1 playable on windows than ever setup neko II or dosbox again.
or deal with the terrible snes port is mechwarrior only in name.

Reply 152 of 156, by Mikeyy00

User metadata
Rank Newbie
Rank
Newbie
KHORG wrote on Yesterday, 22:35:
From testing on 1.1.42: […]
Show full quote

From testing on 1.1.42:

  • The NPC vehicle on Blade Splint now has a headlight 'projection' rendered in front of it, but it's being dithered into the road texture. It should lie flat on the road texture.
  • The helicopter on Blade Splint has it searchlight (which is projected onto the ground) fixed underneath the helicopter when it should appear in front of it.
  • The red/green lights on the Blade Splint helicopter are partially fixed. The red/green light nearest the player is extruded correctly but the furthest is sunk into the heli. These then swap depending on facing between the player and the helicopter.
  • The large boundary walls of the various Wolf Trial arenas in the original game appear grey if viewed perpendicular, but appear black if viewed on an acute angle. Rightly or wrongly this is the behaviour in DOS and in the new decomp version so should probably be continued until we decide to alter it. However, the decomp version has now picked up an issue where there is massive flickering on these walls.
  • On Cold Crescent, the Falcon Monorail should have small red flashing lights, two at the front and two at the rear.
  • On Cold Crescent, the gate to the Teraformer complex should open when it recognises your IFF, but it doesn't open.
  • On Cold Crescent, the monorail structure itself (which is a non-targettable structure) has a flickering problem when it is rendered.
  • On Cold Crescent, the "nuke" explosion which occurs on a delay after the Teraformer is destroyed is never played. So enemy mechs close to the Teraformer are never destroyed and the player doesn't see the white-light effect on their screen.
  • On Cold Crescent the Teraformer gate seems to be playing a mech-powerup sound whenever you go near it.
  • On Cold Crescent, the Falcon Monorail is coloured red/blue in the left targetting MFD (in wireframe mode) when it should be appearing entirely blue.

Not sure if this one got missed from a few bug reports back:

  • 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.

That problem with the Windows being rendered on Buildings in Mercs, it looks like the engine isn't sure which is meant to be in front, so is dithering the windows based on viewing angle of the player.

Do we know how the windows are handled on the 3D objects? Are they faces cut into the 3D object and then textured? Or are they decals applied to the outside?

Few of these should be banged out in 1.1.45

Reply 153 of 156, by mattrock1988

User metadata
Rank Member
Rank
Member
myne wrote on Today, 00:19:

If you just want to play OG windows versions as faithfully as possible, see sig.

And chill. This will mature in time.

Thanks for the suggestion on the OG versions for Windows link. I'll check that out.

Also, I'm sure someone will have this ironed out in time. If not this specific port, perhaps OpenMercs, which is another MW2 Mercs decomp effort I've been following fairly closely.

Retro PC: Intel Celeron Mendocino @ 500 MHz, TYAN Tomahawk BX, 6 GB IDE Quantum Bigfoot, 256 MB SDRAM, DVD-ROM, 1.44 MB floppy, Nvidia GeForce MX 440 AGP, ESS AudioDrive 1868F ISA

Reply 154 of 156, by KHORG

User metadata
Rank Newbie
Rank
Newbie

On 1.1.45, re-tested on 1.1.50, haven't yet tried fully completing Velvet Hammer yet.

  • All of the MFD camera views (Down, Rear, Weapon and Target-Camera, but not Target-Wireframe) appear to be creating a small invisible inset window in the top left of your primary first person view. If you select an enemy target (but not a building or nav point), it will incorrectly display an additional much larger red target bracket within this invisible inset window.
  • When the left MFD is changed from target-wireframe to target-camera, it should only display the target (mech or building) and the background behind it should be black. Currently it's incorrectly rendering the terrain/sky behind the target in this inset window also.
  • On the left MFD, when it is in target-wireframe mode, it has the correctly displayed bounding box around the edge of the MFD, but when in target-camera, it has a slightly incorrectly offset bounding box.
  • Also, the target-camera MFD view should be displaying enemy mechs or objects using their highest LOD, the same as the target-wireframe does.
  • Powered-down friendly and enemy mechs/vehicles show not be shown on Satellite View. This particularly affects Velvet Hammer.
  • Also powered-up mechs/vehicles which are inside buildings should not be shown on Satellite View. E.g. the HoverLimo on Velvet Hammer, or your own mech when it starts inside the Mech Hangar on this map.
  • Velvet Hammer can't be completed. If you succeed at all primary/secondary goals and return to Nav Pi, the mission doesn't end.
  • Velvet Hammer has several white trapezoidal shapes appearing in the middle of the map when in Satellite View. These are probably part of the Dome overhead and should not be shown in Satellite View.
  • The Falcon Nova and Mad Dog which power up on Velvet Hammer should have scripting telling them to attack the "None" objects in front of them, but they are not doing so, resulting in them being trapped inside buildings.
  • The "None" objects on Velvet Hammer should not be shown in Satellite View.
Last edited by KHORG on 2026-11-22, 19:31. Edited 1 time in total.

Reply 155 of 156, by Mikeyy00

User metadata
Rank Newbie
Rank
Newbie
KHORG wrote on Today, 06:36:
On 1.1.45 […]
Show full quote

On 1.1.45

  • All of the MFD camera views (Down, Rear, Weapon and Target-Camera, but not Target-Wireframe) appear to be creating a small invisible inset window in the top left of your primary first person view. If you select an enemy target (but not a building or nav point), it will incorrectly display an additional much larger red target bracket within this invisible inset window.
  • When the left MFD is changed from target-wireframe to target-camera, it should only display the target (mech or building) and the background behind it should be black. Currently it's incorrectly rendering the terrain/sky behind the target in this inset window also.
  • On the left MFD, when it is in target-wireframe mode, it has the correctly displayed bounding box around the edge of the MFD, but when in target-camera, it has a slightly incorrectly offset bounding box.
  • Also, the target-camera MFD view should be displaying enemy mechs or objects using their highest LOD, the same as the target-wireframe does.
  • Powered-down friendly and enemy mechs/vehicles show not be shown on Satellite View. This particularly affects Velvet Hammer.
  • Also powered-up mechs/vehicles which are inside buildings should not be shown on Satellite View. E.g. the HoverLimo on Velvet Hammer, or your own mech when it starts inside the Mech Hangar on this map.
  • Velvet Hammer can't be completed. If you succeed at all primary/secondary goals and return to Nav Pi, the mission doesn't end.
  • Velvet Hammer has several white trapezoidal shapes appearing in the middle of the map when in Satellite View. These are probably part of the Dome overhead and should not be shown in Satellite View.
  • The Falcon Nova and Mad Dog which power up on Velvet Hammer should have scripting telling them to attack the "None" objects in front of them, but they are not doing so, resulting in them being trapped inside buildings.
  • The "None" objects on Velvet Hammer should not be shown in Satellite View.

Some addressed in 1.1.46

**I'm trying another LLM to see if we can get some better fixes (ChatGPT 6.2).

Reply 156 of 156, by KHORG

User metadata
Rank Newbie
Rank
Newbie

Just want to check on these, these are unfixed issues from previous bug reports.

  • 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.
  • There's a big frame-rate drop when turning on or off light amplification. Image enhancement is fine.
  • 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 seen any other mechs do this so far.
  • On Blade Splint, directly ahead of you there is a crossroads, if you follow that to the right to the next crossroads, there is a misplaced flame sprite in the middle of this crossroads half embedded in the ground. Not sure where it should be, but not in that location.
  • Once a building is destroyed, it should only show as a black silhouette on Satellite View. It should not show as a red outline of the 3D rubble.
  • Selected buildings, whether enemy or NPC, should show entirely as blue wireframes (when in wireframe targetting mode) in the left MFD. For example the Chemical Plant on Silver Staff is being rendered as part Red, part Blue.
  • For some missions, the colour of the ground in Satellite View isn't matching the colour of the ground as seen from the cockpit. On Aquiline Fire it's Black when it should be Maroon. On Pyre Light it's Brown when it should be Sandy. Flame Tongue is correctly Olive Drab however.
  • Mechs should visibly darken their textures on their main 3D model as they get more damaged. This should happen on the specific limb/component that is turning yellow/red on their wireframe, but isn't currently occurring.
  • On Aquiline Fire, the crashed Wolf dropship should have a small flashing red light on it's one remaining wing which is protruding into the air.
  • On Aquiline Fire, the crashed Wolf dropship should have Wolf Clan decals on each side.
  • On Aquiline Fire, when destroyed, the crashed Wolf dropship should explode into about 5 medium sized particles and several smaller particles. However in the recomp it's only generating one large particle.

Also what was the story with the LOD's? You mentioned they'd been set to DOS thresholds of 160 m / 380 m / 1 km, but I put up screenshots on page 7 showing that this isn't what I see in my DOS 1.1 install. E.g. at 450m it still hasn't changed to the first low-poly LOD. When testing the levels, it's pretty noticeable with the mechs changing detail level.