Leaderboard

@kingsal I've uploaded a quick version of my mod with your footsteps inside a "Experimental" folder in the OP link. Let me know what you think. I've had to use the Amplify effect of Tenacity in all of your files with a Peak amplitude of 0.0 dB (without allowing clipping). Also created a "new" carpet version for the guards by reducing the files' pitch by 20%; might also want one for commoner females with a +20% pitch instead. If you would rather prefer these modifications to be done with your raw sound files I'll delete the sound files and let you handle it properly. I just uploaded them to show how my shader values would sound. I've also noticed many of your missions have a player_swim_burst01/02/03.ogg set that sound a lot better than the core files, but the credit is still attributed to STiFU.

testMason FM Released (Aug 24 Version) testMason.pk4 This FM shows the complete character set of the Mason font on a floor in-game. It is mainly to support our on-going /russian/ work (but can be used with /english/ as well). The screenshots show the Cyrillic font, when the user selects the Russian font setting. One shot shows the TDM 2.13 situation. Note in particular the clobbered ASCII characters around "D". The other shot shows some 2 dozen "phase1b" DAT corrections I've done, to improve existing characters. There's plenty more work to be done by me & kalinovka from 0x80 on, to replace missing or non-compliant glyphs with new stuff. The FM displays the characters set twice, as a "Stray Marks" test seen fully in the screenshots, and an adjacent "Spacing" test. The two tests show the same character subsets in each aligned row. The row headers are in hex for "Stray Marks", in decimal for "Spacing". See the FM briefing for more details.

Neonsstyle recently pointed out to me that my seamless mass teleportation script doesn't seem to work when the setup is rotated, and I realised that the version I linked to in this thread even relies on manually adjusting the script. It was also inefficient because it had two nearly identical script functions for each direction, and it only supported one teleportation setup per map. As this is an old script it was clearly time to rewrite it. To begin with, the purpose of the script is to enable seamless teleportation without the player noticing that it has happened, giving the illusion that two areas of the map are physically connected. There should be two identical-looking locations, preferrably an S-shaped corridor to limit how much the player can see in the moment he is teleported and thus how much needs to be duplicated. The locations should also be AI-free, since I expect their patrols will break after teleportation. There are two trigger brushes at either end: a narrow brush that initiates the teleportation procedure, and a larger "zone" trigger_touch brush around it that applies the teleportation to the player and all AIs and moveables in its volume. The narrow brushes are in slightly different positions at either location to avoid that the player gets stuck in an infinite teleportation loop. The teleportation vector is automatically calculated from the origins of the departure and destination zone entity, so it's important you keep this in the same relative position. The image above shows the setup: the arrow represents the player's expected direction of movement through each location; the narrow box represents the trigger brush which initiates the teleportation; the large box represents the teleportation zone from which everything that can move gets teleported; the red cross represents the origin of the teleportation zone used to calculate the teleportation vector. To setup, copy the script into your map script or add it to your /script folder. Copy a pair of altogether 4 trigger brushes to your 2 identical-looking locations and change the "zone_departure" and "zone_destination" spawnargs on each of the narrow trigger brushes to point to the trigger zone brushes. With this new version of the script, it should be possible to have as many mass teleportation setups in your map as you want, and rotation should be no problem given the fully automatic calculation of the teleportation vector. mass_teleport.scriptmass_teleport.map

Down