Zarel commented

This is one of those situations where a screenshot would be REALLY useful.

truckspin uploaded file weirdborg.jpg (12.8 KiB)

looks the same when it is in the main window

Per commented

This happens only in multiplayer? Any pattern at all to when they are displayed incorrectly?

truckspin commented

I don't see any pattern at all. The only remarkable thing is that it never happened before beta 10, and now it happens about 50 % of the time.

truckspin commented

Some people claim that this happens with 7+ players, some claim it happens with 8, but most people think that there is no pattern at all.

truckspin commented

Also funny: "weird cyborgs" can't be selected with ctrl+a. That is when they look weird to the OWNER.

truckspin commented

More observations: The owner only pays for the propulsion. That makes even super cyborgs very cheap. They also produce very fast, which would indicate that they don't have the full HP, but that's hard to know for sure. (My speculation: The price and production time depends on whether the OWNER sees the weird version, and the HP depend on whether the KILLER sees the weird version.)

When some players can get scourge and flashlight cyborgs super fast to the unit maximum for 25 per unit, and others can't, it's really a game killer. I just kept getting attack waves of 100 cyborgs to a highly fortified position. Didn't cost much, and didn't take much time to get the next wave ready.

Change priority to blocker please. It's currently the biggest problem in beta 10 from the perspective of a player.

Per commented

When it happens, does it happen for all cyborgs owned by that player all the time, or does it only happen to the occasional cyborg?

truckspin commented

It's all or none. And it depends on two players: The owner and the one who sees it.

Zarel changed priority from minor to critical

Zarel commented

I trust acidjnk's judgment.

Buginator changed blockedby which not transferred by tractive

Buginator commented

Refs #1687

That ticket will hold the logs to track this issue down.

Per changed status from new to closed

Per set resolution to fixed

Per commented

Hopefully fixed in [10351] and [10352]