Jump to content


Sammy Stallion

Member Since 08 Dec 2016
Offline Last Active Jul 02 2018 07:24 PM

Posts I've Made

In Topic: MO 3.3 // Game Bugs

02 July 2018 - 07:24 PM

Actually, you can still attempt to run Chitzkoi to it. The trigger should only checks for his position on the landing pad, not proximity to the Irkalla.


Ok, but if the Irkalla is destroyed, does that fail me? If so, this is still a game-breaking bug, as the thing starts attacking my forces long before they've conquered enough territory to get Chitzkoi to the landing pad.

In Topic: MO 3.3 // Game Bugs

30 June 2018 - 10:35 AM

Yes; I have a save file that it keeps happening on.

Exactly what is happening to wake up the fortress, besides my units being nearby, I'm not sure--and they can be nearby for a long time with no apparent effect on the fortress, then suddenly it attacks.

If it helps, I set up the Stalin's Fist nearby and built some TIGRs with it; perhaps these were supposed to hold their fire against the fortress but don't. That's just a theory, though, and I don't think I've ever seen them shoot at the fortress without an order.

 

Edit: Is there a way to identify which save file is the one I made right before the issue occurs?  Looking at the Saved Games folder, it seems that only some of them have references to the mission names, which I'm assuming are the starting files.  I'd like to find and upload a file from later in that mission.


In Topic: MO 3.3 // Game Bugs

30 June 2018 - 08:57 AM

1) The game spontaneously minimizes a lot for me. That sure beats outright crashes (of which I've only had a few), and it's easy to maximize again, but it's still a bit irritating. Does anyone else have this issue?


Probably one of your background programs is the offender here. What is usually running there while you're playing?

Unless you mean a process not even listed in the task bar, often none besides the folder and launcher.

Also, I notice that in the Soviet Mission, Meltdown, Yuri's Flying Fortress suddenly starts attacking my units and leaving its landing pad to do so. Is that a bug? It certainly seems like something that could make the mission impossible, since it would force you to either kill it or get killed by it.

In Topic: MO 3.3 // Feedback & Suggestions (Balance, New Features, Modifications etc.)

24 June 2018 - 06:42 AM

This is strictly a lore issue, so spoilers: in Heatwork, why are you given Quilin tanks? Since the plot is that you're a Russian task force sent to shut down some unauthorized Chinese skunkworks, shouldn't they be rhinos instead?

In Topic: MO 3.3 // Game Bugs

17 June 2018 - 08:30 PM

I don't know whether these are bugs, but

1) The game spontaneously minimizes a lot for me. That sure beats outright crashes (of which I've only had a few), and it's easy to maximize again, but it's still a bit irritating. Does anyone else have this issue?

2) In the Epsilon mission, Singularity, messages saying to destroy the robot center in South Korea and field HQ in North Korea keep appearing, even after they've been destroyed. Also, no messages appeared indicating that the Iron Curtain must be destroyed.