What changed
1 fix0 additions1 change0 removals
fixedFixed an issue introduced in Patch 1.0.6 (the 50+ tenant rendering optimization).
changedThe issue occurred with the Dormitory, which spawns additional tenants when a special tenant appears. It checked whether an unrendered tenant was exactly the same as a rendered tenant (they weren't). Since they were not considered identical, the Dormitory kept spawning additional unrendered tenants, which were then checked against the rendered tenant again, resulting in an infinite loop. As a result, if a tenant spawned on a tile containing a Dormitory while 50 or more tenants were being rendered, the game application would crash.
RentPoly changes
fixedFixed an issue introduced in Patch 1.0.6 (the 50+ tenant rendering optimization).
changedThe issue occurred with the Dormitory, which spawns additional tenants when a special tenant appears. It checked whether an unrendered tenant was exactly the same as a rendered tenant (they weren't). Since they were not considered identical, the Dormitory kept spawning additional unrendered tenants, which were then checked against the rendered tenant again, resulting in an infinite loop. As a result, if a tenant spawned on a tile containing a Dormitory while 50 or more tenants were being rendered, the game application would crash.
Fixed an issue introduced in Patch 1.0.6 (the 50+ tenant rendering optimization).
The issue occurred with the Dormitory, which spawns additional tenants when a special tenant appears. It checked whether an unrendered tenant was exactly the same as a rendered tenant (they weren't). Since they were not considered identical, the Dormitory kept spawning additional unrendered tenants, which were then checked against the rendered tenant again, resulting in an infinite loop. As a result, if a tenant spawned on a tile containing a Dormitory while 50 or more tenants were being rendered, the game application would crash.
Apologies for the inconvenience, and thank you very much for your feedback in helping us identify and fix this issue!
