Yitzi's unofficial SMAX patch 2.2e

[ete]

I'm getting the editing unit (monolith) bug, and a likely related issue with not being able to view which units are occupying a square (along the bottom) while in scenario editor.

To reproduce: Make a scenario, place a unit, right click and click edit unit. For the other part, just click the unit and you'll see it does not show up on the bottom display. The bottom display not working bug persists even if you save the game as a .SAV and reload.

[Yitzi]

I'm getting the editing unit (monolith) bug, and a likely related issue with not being able to view which units are occupying a square (along the bottom) while in scenario editor.

To reproduce: Make a scenario, place a unit, right click and click edit unit. For the other part, just click the unit and you'll see it does not show up on the bottom display. The bottom display not working bug persists even if you save the game as a .SAV and reload.

Ok, I've investigated a bit, and found that the same bugs show up in Kyrub's version.  The editing unit (whatever) bug isn't specifically "monolith"; if you start with an empty map it's "monolith", but starting the scenario editor from a game (via ctrl-k or the menu) can give other possibilities.

The "bottom display not working" bug could be quite difficult to fix without a version of the game where it works properly (which Kyrub's does not fulfill), but as a workaround you can start a normal game, activate the scenario editor from there, clear the map, and then the bottom display seems to work properly.

[ete]

Thanks for investigating. I also came across editing unit (Green) after posting. I have a version (scient's old one I think, though it could have been another version) where the bottom display worked properly, could you work from that?

And that workaround may make it work. I'll see if it works with loading custom map files.

[Yitzi]

I just tested, and scient's also has the same bug.

[ete]

ah, that's strange.. I don't remember having that issue while making my previous scenario.

no.. on testing, I don't have it on my previous scenario. Which is odd because I think I used the same steps for both, and I do get it on this new map.

That one's probably just been in the game all along then, I'll try and isolate the cause tomorrow.

Edit: Your workaround solves the second issue, and both seems to be happening in the scient version. My apologies for assuming it was caused by your patch, I had just not run into/noticed them before. Also, it came up with editing unit (Gaia's Landing) everywhere in my last test.

[Buster's Uncle]

Do either of you keep clean and/or only officially patched versions of the game for testing purposes?

[Yitzi]

Do either of you keep clean and/or only officially patched versions of the game for testing purposes?

I have such a version, but I don't use it because it won't work with my current alphax.  (Scient's patch did enough that I can modify it to use alphaxb instead, and then have alphaxb be the original version, but with the original I can't do seem to do that.)

[Darsnan]

Ok, so that explains it.  You made something that wasn't supposed to be possible, and therefore it's not working properly.

If you want, once I start taking requests you can put in a request to make probejets work properly, but I consider it a mod-enabling change rather than a bugfix and will prioritize it accordingly.

Understood. Another bug with Probe NJ are that once the Probe Jets MC a Carrier, the Probe NJ automatically lands on the Carrier it just subverted.

D