Attempting to use a window at your native resolution instead of fullscreen (1920x1080 for me) causes the game to flip an error message at next launch, which says:



And then the game starts up in a tiny window.

Also, possibly related, when selecting my native resolution the 1X, 2X, Fullscreen button will not work properly.

It is possible for two dropships to spawn in the exact same place. This happened when three players (me + two bots) were attacking Rayvord Tundra. My brain dropship in the same place with another brain dropship and both crashed. We both lost our brains and the third player won right away.

EDIT: I tried to attack the map again so I scanned it first. (I had already scanned the map before but I forgot that.) After the scan finished, I pressed "space to finish" but nothing happened. I am using default controls.

This happens to me sometimes whilst digging down in dirt. To replicate (does not happen often) look straight down with a digger on hand, try to make your brainbot look left and right whilst digging and try to keep that angle directly down, as he drops the glass head dome seems to clip into dirt and remove it- when my brainbot decides to spaz though the ground it goes on a diagonal of about 45degrees down and leaves body shaped holes with the head part being most noticeable.

Making a pre-set with 200+ items in and later selecting it causes my game to slow and crash to desktop on my slower pc but not my new faster-ish one, still pauses for about 5ish seconds when I try to however over and select it.

- mouse smoothing issue on full screen (both pc's).. I discovered this one has been a problem for a few years

Unresponsive mouse. Controls bound to the mouse (not clicking, only things that involve moving the mouse e.g: looking around, aiming, placing bunker modules etc.) often fail to pick up on mouse movements. This does not happen on any other game, only CC. I'm not sure If this is a bug to do with CC or if it's my fault somehow, but it still makes CC very difficult to play and enjoy.

One time I scanned a location where the enemy already had a base. While I was scanning, the enemy brain robot was for some reason outside of the enemy base. The enemy started shooting their own brain bot and killed it. I exited the scan and when I went to attack the base I won instantly.

I was playing against two AI however, perhaps when I scanned it automatically filled the level with enemy A troops from those new troop spawn locations and killed the brain robot from enemy B that was also on the surface from having won a previous round.

On one level, my brain placement tool flipped out when I attempted to place it in my base.

I'm approving your post since you're a human being, but please clarify this report.

I occasionally gain the ability to control 2+ units at once, with their actions and movement mapped to the unit I currently am using. It happens after I build a base, and I am attacked by an enemy AI. It disables selection for the units that I can additionally control. Happens during a campaign with 1 Human and 3 AI.

Although this might not be a bug. It could be a feature that I have yet to figure out to make happen.

I had it happen again, I scanned the world only to find yellow and blue forces fighting each other. The planet was previously owned by blue. A brain died in the battle and when the skirmish faze came about I instantly claimed the site, no skirmish at all. Later, someone chose to attack me at that site. When the skirmish began I dropped down from the sky as a brain bot (no ship) into a pile of enemies on both sides.

I've had this too, the brain placement dots keep swapping from left to right (I think, it's hard to tell), and the screen, in lieu of a better word, spazzes out like crazy, similarly swapping from left to right and in some cases panning at very high speeds. It stops when you move the brain away from that spot and starts back when you move it back there.
I've had it or something like it happen a couple times in B26 so it's not an entirely new problem. I think it's a scene wrapping problem but of course I can't say that with any surety.

Saving Gibs in the Gibbing Editor has it generate the ini as:



When it should be:



Note that it saves it as "PresetName" and not as "CopyOf". It will give off an error when it loads, but due to a similar loading bug, it will not have an error show this. The game will just crash instead

Yes. This happens to me too, Im a browncoat, the A.I's a ronin, and lo and behold, My brainbot comes out with a AK-47.

Did not see this reported here, but plenty other places.

If you are playing a modded tech like (Unitec or my own (private) mod) sometimes when you allocate founds to auto build a base and press end turn (when the base is sopposed to be built) it just crashes with no error.

If I edit out custom brain actors it seems to work fine.

Edit: it crashes with normal brain too.

For some reason it won't let me edit the settings, so I am forced to play the game in 640x480 and not being able to edit post proccesing post pixel glow and delta time

Sounds like the game is in program files and/or you're not the admin.

The scene editor is too ♥♥♥♥ up for any quick synopsis:

Brainbots tend to get treated very very weirdly in a scene after a save/load. Their health is still present, but their team marker is not, and they cannot be manipulated using any scene making tool. Upon attempting to test the scene, the brainbot will vanish, and going back to the editor shows that it is, in fact, gone this time.

While making scenes, I noticed any number of small weird glitches, such as when trying to place actors and opening the Imperatus tab, it opens the coalition one instead. You then have to open the Imperatus tab again separately. This has happened on numerous occasions, so I know it's not just me missing the tab by accident.

Also occurring was an odd glitch where part of the scene I was making, on the far right, would be drawn on the screen if you were on the top left part. Moving away from that part of the screen put things back to normal.

In short, the scene editor is stupid.