Fast Travel Exploit

[Archmagexemnos]

While experimenting with the Shift + F12 menu, I found a way to utilize it to fast travel to anywhere on the map. While the menu is open, the limit on how far away you can move your camera from your squad is removed. Simply open the menu, move the camera to your desired location, and then quicksave. Next, load the save, making sure the "reset squad position" box is checked off. Now you can teleport anywhere you want on the map.

Keep in mind that if you have multiple squads, they will all be transported to the same spot. Just something interesting I wanted to share.

[Morkonan]

Originally posted by Archmagexemnos:

While experimenting with the Shift + F12 menu, I found a way to utilize it to fast travel to anywhere on the map. While the menu is open, the limit on how far away you can move your camera from your squad is removed. Simply open the menu, move the camera to your desired location, and then quicksave. Next, load the save, making sure the "reset squad position" box is checked off. Now you can teleport anywhere you want on the map.

Keep in mind that if you have multiple squads, they will all be transported to the same spot. Just something interesting I wanted to share.

Though others have suggested this tip, there's something it can be used for more importantly than just "fast travel."

A number of players, including myself, have experienced issues where it seems a certain region has something corrupted/bad loading in it that will crash the game when the player moves the camera to that Point of View, like when they double-click to focus the camera on a group in a different region.

If the game is forced to load the visual display of that area and something is borked up, the game will crash.

However, using your method, they can rescue their game from that by relocating the squads in a different area.

It's no different than choosing to do so while focused on the group-in-focus and then saving, exiting, and reloading with ""Reset Squad Position" ticked on. But, it is a different way to do it that might be helpful and doesn't require a group for the camera to be focused on.

Note: IIRC, if, for some reason I suppose, the game can't determine the current save's "camera focus," choosing to Reset Group Position will move the group(s) to The Hub. Anyone know if that's actually true? ie: A "Default Reset Position?"

[Archmagexemnos]

That's actually helpful to know, as i have had extensive issues with crashes when trying to load the 2nd floor of one of my buildings. It seems like something i should try.

[�[Dire_Venom]�]

Great advice above, helps a lot

[SnugSnug]

Originally posted by Morkonan:

Originally posted by Archmagexemnos:

NEW ISSUE: The game crashes whenever you go to a particular area of the map

It's caused by a corrupt file, go into \data\newland\land\overlaymaps\ and delete all the files named new_overlay.x.x.png. Then re-validate your files on steam or re-install.

This may also help fix a troubled region, taken from lo-fi forums known issue page.

0.22 has also introduced some new crashes related to loading of assets, this may be the cause of your topfloor issue. It may be worth checking your kenshi.log following a crash from that region, you may be able to track the issue, especially if its mod related.

[Morkonan]

Originally posted by SnugSnug:

...
0.22 has also introduced some new crashes related to loading of assets, this may be the cause of your topfloor issue. It may be worth checking your kenshi.log following a crash from that region, you may be able to track the issue, especially if its mod related.

From the dumps I could find when dissecting the cause of my crash, or trying to, since "uplad ur savecg games zomgz!" is not exactly a "fix," what I've seen are error reports on texture references, likely borked when the game's getting confused about exactly "where you are." Now, I don't know this for sure since there is no reason a log file can't also continually report errors that have long been fixed on the backend, somewhere, and the devs don't worry about fixing the error reports for those things. But, from what I could see, that's what was causing mine.

Once there is an error in a region it does not clean itself up and will insist on trying to do that "error" every time the region is "in focus." It only ever tries to re-reference/reload AFTER it has unloaded a region. That's good in that the player doesn't have to wait as long for that process to occur, but bad when it's using references that are allowed past any basic error checks.

[Hobo Misanthropus]

It's not really an exploit, it's the game editor. An editor would hardly be useful if you have to play the actual game to test your content and fixes.