[0.75.3] Faction Erased?

[Guy]

I have encountered a bug where my squad is not visible on the map, in the squad selection menus, and I'm able to move the camera completely freely from one corner of the map to the other.


Image of UI during bug


I started a new game because my previous games are from 8 months and wanted to try out the new starts and the new race. I settled in to a start, got equipment and a competent starting character, got a faction rolling, made an outpost, realized that I should find a spot with better resources, moved there and started construction.

I have some creature nests near my base and decided to build walls around my base for shelter. When I have my engineer get to the entrance close to one of the nests wolves come in, a fight breaks out as the wolves charge at him.

My fighter squad either attacks them immediately, or locks up in place (no change to combat animations even when ordered to attack) until they're attacked so much that they are nudged out of their glitched position.

Once they clean up the wolves I move my engineer back in and everyone is locked into their places like before. With no enemies left to attack them and nudge them I just quick-saved and reloaded. When I reloaded there were no wolf bodies, no squad members in the world, and no icons of the squad members in the UI (the actual squads for the fighters and non-fighters existed, just not populated with anyone).

I clicked around thinking that maybe the icons for the characters were there but transparent (has happened before), but no stats displayed on the status screen in the lower left. The final nail in the coffin was when I could move the camera anywhere on the world map with no leash distance to characters. I went from one corner to another over a few minutes just kinda admiring a glitch I had never seen/heard of before and enjoying being able to scout out potential base locations in remote areas. I reloaded with reset squad positions; same thing happened. Imported the save with and without reset squad positions set; same thing happened. I loaded the autosave that occurred a bit after the quick-save, same issue.

Luckily the previous autosave prior to the quick-save is safe to load.

Attached is the crash dump, I also have the quick save uploaded to dropbox in the link below.

Quick save link