Squad public testing что это
В Squad проходит тест обновления версии 2.0
Сегодня разработчики Squad анонсировали PlayTest крупного обновления.
Ниже можете ознакомиться с изменениями данного обновления:
V 2.0 Примечания к выпуску
v2.0 Известные ошибки и проблемы
• После запуска Squad в главном меню появляется 6-10-секундная задержка. Над этим ведется работа. А пока, пожалуйста, просто терпеливо ждите.
• Управление вертолетом в настоящее время не настроено должным образом из-за ошибки, которая заставляет большинство вертолетов игнорировать эффекты трения воздуха. Это будет исправлено в будущей сборке.
• По умолчанию при создании отряда или присоединении к нему не будет выбран ни один комплект. Обязательно выберите комплект или смените его в ящике с боеприпасами после спавна.
• Иногда значок ХАБа будет отображаться как не работающий спавн (красный), когда он на самом деле работает. Если это так, вы все равно можете спавниться на нем, выбрав его на карте.
• Существует потенциальная проблема производительности на Goose Bay, которая может повлиять на игроков в некоторых ситуациях. Если вы пострадали и у вас есть какая-либо конкретная информация по этому поводу, пожалуйста, сообщите нам об этом. Мы все еще занимаемся данным вопросом.
• Есть небольшая задержка, когда появятся транспортные средства. Это будет исправлено в будущей версии.
• Голосование по карте в настоящее время не работает. Голосование фракций отключено на большинстве карт.
• Браузер серверов находится на стадии разработки.
v2.0 Системные изменения
• Первая фаза капитального ремонта слоев карт.
• Оптимизация загрузки ресурсов и использование памяти.
• Голосование по картам/слоям/фракциям.
• Будущий потенциал для более разнообразных подгрупп в отношении состава транспортных средств/комплектов/развертываемых средств.
• Капитальный ремонт графических настроек.
• Загрузочные экраны карт.
• Новые инструменты админа для управления командными убийствами и наблюдения за проблемными игроками.
• Поддержка новых опций для стримеров.
v2.0 Игровой процесс
Задержка активации спавна на ХАБе.
• Эта новая функция для ХАБа включает в себя таймер задержки активации спавна до того, как точка спавна ХАБа будет использована.
• Время по умолчанию для этой задержки активации в данный момент установлено 10 секунд для всех сценариев. Это значение будет скорректировано в будущих обновлениях.
• Текст “спавн активируется» будет отображаться, когда задержка спавна начала отсчет и индикатор задержки будет виден на HUD.
• Эта задержка предназначена для изменения динамики спавна, окружающей ХАБ, для стимулирования большего планирования и уменьшения количества «телепортационных прыжков”, которые происходят с недавно построенными ХАБами.
• Это также предназначено для стимулирования защиты FOB/HAB, чтобы она была меньше связана с интенсивностью спавна и больше с стратегическим позиционированием и общим контролем района.
• Это делается для того, чтобы команды не злоупотребляли системой спавна путем мгновенного спавна на вновь созданном ХАБе, а также для того, чтобы побудить игроков защищать ХАБ в течение короткого периода времени после завершения постройки, чтобы гарантировать, что точка спавна станет активной.
• Эти изменения также дадут противникам немного передышки и времени, чтобы обезопасить область после переполнения ХАБа или частичного его уничтожения, не опасаясь того, что враги появятся снова в тот момент, когда ХАБ будет восстановлен до порога или когда достаточное количество игроков либо уйдет, либо будет убито в близости от переполненного ХАБа.
Улучшение полетов на вертолете.
• Смягчение эффекта «качелей» и уменьшение внезапного ускорения на низких скоростях за счет регулировки кривой ускорения по оси X.
• Улучшенное удержание энергии за счет высокоскоростного вращения.
• Поступательная подъемная сила и угол атаки: масштабируемая эффективность несущего винта в зависимости от условий полета. Мощность Ротора умножается до 1,3х при встрече с воздухом под большим углом наклона (J-повороты) или при движении на высоких скоростях (поступательная подъемная сила).
• Унифицированные расчеты ускорения для всех фаз полета. Управление должно быть более естественным и последовательным на протяжении всего полета.
• Переработан эффект «флюгера», чтобы вертолет всегда садился носом вперед.
• Исправлено странное поведение флюгера, вызванное расчетом инерции вертолета, не учитывающим изменение вращения между рамами.
• Снижение остаточной тяги при отключенном двигателе, вынуждающее к аварийным посадкам.
Механика возврата развертываемых средств.
• Возвращает 80% от размещенной развертываемой стоимости, если она была удалена без полного строительства после размещения. Эта механика предназначена для уменьшения штрафа за случайное плохое размещение развертываемых.
Механика возврата пехотных комплектов.
• Возврат 80% стоимости боеприпасов игроков при смене ролей в ящике с боеприпасами. Не следует возвращать патроны для оружия/магазинов, которые были израсходованы.
• Возвращает боеприпасы как ящикам FOB, так и транспортным средствам.
• Возвращает боеприпасы, когда игрок находится в транспортном средстве.
• Технически общее количество боеприпасов в источнике боеприпасов может увеличиться, если игрок переходит от высокой стоимости роли к недорогой роли.
v2.0 Новый контент.
Новые транспортные средства.
9 вариантов техники: ДШК, M2, БМП1, Mortar, UB32, ЗУ23, СПГ9, Logi, транспортные.
Squad public testing что это
We will be running a work in progress playtest build containing extensive new lighting and shadow changes on the Squad Public Testing App this weekend.
NOTE: The lighting/shadow changes you see in this build will not be coming in the V2.9 or the V2.10 update, this is a test phase for us to begin getting feedback, long before we implement these changes to the live version of Squad.
Currently in the live game, when players run with lower Shadows and lower Ambient Occlusion settings, this can allow for somewhat easier spotting of enemies in certain circumstances, while also greatly downgrading the game’s visual quality. Also, the current Far Shadows are not optimized, leading to performance degradation for most player setups when Far Shadows are enabled.
Al Basrah Awnings [imgsli.com]
Al Basrah Street [imgsli.com]
Chora [imgsli.com]
Gorodok Park [imgsli.com]
Gorodok Watertower [imgsli.com]
Logar [imgsli.com]
Mestia Tunnel [imgsli.com]
Mutaha Night [imgsli.com]
Narva [imgsli.com]
Sumari [imgsli.com]
Tallil Column [imgsli.com]
Yehorivka Gully [imgsli.com]
Here are the full details regarding the changes:
Setting Shadows to “Low” will retain most of the gameplay impact of shadows and Ambient Occlusion when they’re set to higher levels, but drastically reduce their quality. Currently in the live game, setting Shadows to “Low” removes shadows almost entirely.
Distant Field Ambient Occlusion will be enabled on all graphics quality settings, while having been optimized at lower quality settings. DFAO allows realistic dimming of enclosed spaces and areas of dense foliage. In combination with the extended shadow ranges, this will ensure that all players will have similar visibility when trying to spot targets.
Optimized Shadow Cascades, as well as increased maximum resolution for epic settings:
Note that for both Shadows and Ambient Occlusion, «Low» settings will be at lower resolutions than they are now to offset the performance cost of having more shadows on screen. “High” and “Epic” settings will render shadows at a higher resolution than before, achieving improved visual quality while performing better than Far Shadows do in the current live version of the game. This means that you may want to raise or lower your Shadows and Ambient Occlusion graphics settings from what you normally run in the live game.
Ambient Occlusion will be reworked for underground areas such as tunnels and bunkers to allow for more accurate shading, better gameplay and greatly improved atmosphere.
Lighting will be improved on all layers. Some layers will be completely overhauled with new HDR lighting. The rest will be incrementally upgraded, and will gradually receive their finishing touches in further patches.
Here are just a few examples of layers which received entirely new lighting. You will have to find the rest, yourself!
-Updated lighting to give more contrast, brighter highlights, and deeper shadows on most map layers.
-Overhauled the colour grading and post-processing on all map layers.
-Implemented Volumetric Lighting on all map layers.
-Reduced fog thickness on Tallil, Yehorivka, Gorodok, Lashkar, and Kohat. Adjustments of fog on many other layers.
-Removed Eye Adaptation from all layers to reduce exploits and allow for balanced gameplay in all areas of our maps.
-Removed Ambient Cubemaps from layers to reduce the washed out feeling across all maps.
-Most night layers are now brighter.
-Relit most underground tunnels with new lights and atmospheric effects, especially on Mestia.
-Adjusted layout and tooltips of the Graphics menu to improve clarity and user experience.
-Added localized volumetric fog for dusty areas such as tunnels.
-Fixed Ambient Occlusion artifacts on thousands of buildings, environment objects, and foliage assets.
-Fixed Ambient Occlusion artifacts where underground tunnels intersect with the landscape.
-Fixed incorrect PBR shading on several hundred environment assets.
-There are still some shading artifacts with some older assets on maps. We are continuing to address these.
-Fixed incorrect PBR shading on several landscapes, including Skorpo, Manic, Yehorivka, and Al Basrah.
-Improved palm tree shaders to have light scattering through the leaves.
-Fixed shiny road materials on many maps, including Al Basrah, Yehorivka, Belaya, and Goose Bay.
Reworked HAB Proximity Scaling. The distance at which a HAB can be proxied by enemies (i.e. the HAB is considered overrun and becomes unspawnable) will scale by the number of enemies in proximity to the HAB. For example:
3 soldiers can proximity disable a HAB if they are all positioned within 30m of it.
8 soldiers can proximity disable a HAB if they are all positioned within 80m of it.
A minimum of 3 players is now required to proxy a HAB (this was previously 2). The maximum proxy range now scales up to 80m (this was previously fixed at 30m).
Designer’s Note: This is intended to reward a cohesive Squad that works together with each other while attacking an enemy HAB. It is intended to give an advantage to a team which is organized and has a plan to execute decisive tactics. It’s intended to give less advantage to players who attack independently, without planning, and attack one by one.
This is also intended to incentivize FOB and HAB placement further from the frontlines, and to devalue and decrease the prevalence of the spawn-wave mentality.
The HAB proximity disable system is static in the live game, with 2+ players within a 30 meter radius disabling a HAB. It’s often observed that when a friendly is seen dying close to a HAB on the minimap, the expected & effective tactic is for the team to quickly spawn on the HAB with enemies just outside, with full knowledge of which direction they are coming from because they had just seen a friendly killed by them. Giving up and quickly respawning with the enemy right next to you is not a tactic that we want to incentivize or reward.
The mindset of “Give up, spawn at HAB” is something that has been noted in the existing meta that is often forced on both the attacking and defending teams as the optimal way to play. This is not intentional, and we believe it undermines our efforts to make Squad about Teamwork, Coordination, Communication, & Friendly Communities. We hope this new change will help to avoid needlessly rewarding players for moving recklessly and alone.
Welcome to the latest iteration of our UAT builds. The team has been busy working on the issues that you wonderful folks have been finding throughout our previous UAT builds.
Our current intention is to hold a playtest event this Sunday, 21st Feb 2021 (full details to be finalized in another post, keep an eye on our socials for info). We want to put this build through its paces and see if any critical issues would be detrimental to the release of v2.0.
If things are looking good, this will likely be the final UAT that we release, and V2 will release shortly after. Fingers crossed. We’d love you to join us on Sunday for the playtest to ensure we understand how this build runs on full servers, and we hope you are looking forward to a full release soon.
Read on to find out more on how to report any issues that you find and a complete list of changes and known issues so far with UAT #5
Help us playtest this release! If you encounter an issue, we truly appreciate players that write up bug reports and give feedback in our reporting channels on our Discord server. [discord.gg] Channels are: #v2-beta-feedback and #v2-beta-bug-reports.
Work on V 2.0 is still ongoing and as we reach the final stretches, we do need some more assistance from our amazing community of players to help us test this new build at full capacity.
On Tuesday 2nd Feb 2021, we will have a server running within the “Squad – Public Testing” app on Steam from 11am PST (7pm UTC) until 1pm PST (9pm UTC)
The server name will be:
REMINDER: Testing is taking place on the “Squad – Public Testing” application NOT the Squad main client. You will need to ensure you have downloaded Squad – Public Testing beforehand as the download and install size is that of a full game itself. (Around 60 GB). If you are unable to see it, try a text search in your game library.
Today we are releasing Update #3 to the UAT build of v2.0.
This will be the final update to the Public Testing app until 2021 but it comes with a slew of fixes and changes to put through its paces, with perhaps even a little festive treat you can find on the updated CAF map, Goose Bay, as part of the Layer Overhaul.
We’ll see you in the new year for a fresh start and getting V 2.0 live for all to play. Thank you for taking the time to help make V 2.0 even better.
Help us playtest this release! If you encounter an issue, we truly appreciate players that write up bug reports and give feedback in our reporting channels on our Discord server. [discord.gg] Channels are: #v2-beta-feedback and #v2-beta-bug-reports.
Today we are releasing an update to the UAT build of V 2.0 with some of the latest fixes from our development pipeline.
We aim to keep this application updated with continuous updates as we move forward with testing and fixing issues, as such, new issues may appear that may affect your performance or experience while playing in these playtests. This is to be expected. Reporting these will greatly benefit the team in eradicating these issues.
Help us playtest this release! If you encounter an issue, we truly appreciate players that write up bug reports and give feedback in our reporting channels on our Discord server. [discord.gg] Channels are: #v2-beta-feedback and #v2-beta-bug-reports.
Today marks the beginning of playtesting V 2.0 as part of our UAT phase.
We aim to keep this application updated with continuous updates as we move forward with testing and fixing issues, as such, new issues may appear that may affect your performance or experience while playing in these playtests. This is to be expected. Reporting these will greatly benefit the team in eradicating these issues.
We Want You! To help us playtest this release if you encounter an issue, we truly appreciate players that write up bug reports in our reporting channels in our Discord server. Channels are: #v2-beta-feedback [discord.gg] and #v2-beta-bug-reports. [discord.gg]
Today marks the end of UAT testing. We want to take this time to thank all of you who joined in the UAT sessions and helped to test out the next update.
A massive thanks are also due to the community server hosts who helped provide servers for the testing sessions and organized dedicated sessions.
Join us on Wednesday, 23rd September, when Squad will be moving to a 1.0 release with the Middle Eastern Alliance faction, our stunning new map, Fallujah and, 50v50 servers.
It’s been a long journey, but it’s not over yet. We still have plenty more plans for Squad and the future.
Thank you again to our superb, dedicated, and passionate community. You made this possible.
Today brings another UAT build with more changes to test.
Noticeably, you will see that Forced Shadows have not been re-activated for this test, and they won’t be once we release. As a team, we’ve made a decision to fully complete our Graphics Settings rework before we implement these changes to ensure the release can be as stable as possible, which will also avoid us having to hotfix the update consistently after launch.
We intend for this to be the final UAT build we release, so we would appreciate any and all feedback you may have.
Keep your feedback and bug reports coming to our Discord server (channels: #v1-beta-feedback and #v1-beta-bug-reports) so we can get it in the finest shape it can be.
These are the changes from v1.0 UAT #4 to UAT #5:
We’ve got another large update to the v.1.0 Public Testing today with optimizations, features, fixes and changes from your feedback so far.
Remember to keep your feedback and bug reports coming to our Discord server [discord.gg] (channels: #v1-beta-feedback and #v1-beta-bug-reports) so we can get it in the finest shape it can be.
For this testing phase, we are encouraging any community members who consider themselves a part of the Competitive community to come try this version of the build so we can gather any feedback you may have regarding the new Graphic Settings options. Take the time to fill out this feedback form [forms.gle] if you do have any thoughts regarding these changes.
These are the changes from v1.0 UAT #3 to UAT #4:
Updated the MapRotation.cfg with all available map layers for v1.0.
We’ve got another large update to the v.1.0 Public Testing today with optimizations, features, fixes and changes from your feedback so far. Thank you for taking the time to help test these builds and check out all the new changes and features. As testing continues, we’d like to continue looking at all MEA map layers, as well as explore the different graphics settings options now available, to dial in the settings that are right for your system.
Firstly, it is of the utmost importance that once you have this update to CLEAR YOUR CACHE. So crucial that here it is again. CLEAR. YOUR. CACHE. There have been significant changes made to our settings menu, specifically the Graphics menu, which will likely cause many problems if you do not CLEAR YOUR CACHE (3rd time’s the charm). We are looking at ways for this to be auto-performed in future updates and for the release, but unfortunately, it did not make the UAT #3 build.
Be aware this will also reset your keybindings, so any custom keybinds you will need to reconfigure once you update.
One of the most significant changes for the Graphics menu is the reworked shadows options, which now has «Low» as the lowest shadows option. We have had reports of this DF Shadows (even on Low) causing hitches when a player ADS’ and want to verify how prevalent this is with a larger number of players.
Secondly, the team needs more information about 100 player matches, especially those containing helicopters. Since Fallujah does not feature any map layers with helicopters, this will mean the rotations you encounter will feature it to a limited degree. Fallujah is not restricted, but it won’t be the highlight of your time in UAT #3. This will benefit the team in the long run for testing purposes and make sure we can iron things out for most maps before release.
Remember to keep your feedback and bug reports coming to our Discord server [discord.gg] (channels: #v1-beta-feedback and #v1-beta-bug-reports) so we can get it in the finest shape it can be.
These are the changes from v1.0 UAT #2 to UAT #3:
An entirely new graphics menu has been added to the game, designed from the ground up to standardize image quality between different quality levels. It includes more granular options, new rendering features, and higher overall fidelity while opening up some key new features for low-end players, such as a supersampling slider that smoothly scales below 100%, temporal upsampling to improve image quality at low resolutions, and an overall reshuffle of behind the scenes graphics configuration options, which should result in better performance for some users.
These settings will still need bug fixing, adjusting, and may have additions or removals in the future. While we test with as large a variety of systems as we can, it’s difficult to fully adapt the game for every hardware configuration in the wild. We hope to gather hardware and performance data from a wide range of players in the public test and adjust accordingly.
While the entire menu has been more or less reworked, a brief list of the major changes is included below
Updated our Net Update Frequency to have a greater impact on server performance optimization. The intention here is to save time on the GetRelativeUpdateFrequency call in the replication process on the server. When this is enabled, less time should be spent in «Get Relative Update Frequency Time» on the CPU.
Public Testing обновлен до версии V2.0 UAT # 5
Добро пожаловать в последнюю версию наших сборок UAT. Команда была занята работой над проблемами, которые вы, замечательные люди, находили в наших предыдущих сборках UAT.
В настоящее время мы намерены провести тестовое мероприятие в это воскресенье, 21 февраля 2021 года (подробные сведения будут опубликованы в другом сообщении, следите за информацией в наших социальных сетях). Мы хотим протестировать эту сборку и посмотреть, не окажутся ли какие-либо критические проблемы вредными для выпуска v2.0.
Если все будет хорошо, это, вероятно, будет последняя версия UAT, которую мы выпустим, а V2 выйдет вскоре после этого. Скрещенные пальцы. Мы хотели бы, чтобы вы присоединились к нам в воскресенье для тестирования, чтобы убедиться, что мы понимаем, как эта сборка работает на полных серверах, и надеемся, что вы с нетерпением ждете скорого выхода полной версии.
Читайте дальше, чтобы узнать больше о том, как сообщать о любых обнаруженных вами проблемах, а также полный список изменений и известных проблем с UAT # 5
Reporting Issues.
Помогите нам протестировать этот выпуск! Если вы столкнетесь с проблемой, мы искренне признательны игрокам, которые пишут отчеты об ошибках и оставляют отзывы в наших каналах отчетов на нашем сервере Discord. Каналы: # v2-beta-feedback и # v2-beta-bug-reports.
v2.0 UAT Update # 5 Известные ошибки и проблемы
Эта сборка включает в себя улучшение сети для турелей и вертолетов. Если вы столкнетесь с какой-либо десинхронизацией (например, с неправильной репликацией вертолета или странным поведением турели), пожалуйста, снимите ее на видео и отправьте нам. Это нам очень поможет!
v2.0 Обновление UAT # 5 Примечания к выпуску
Оптимизация производительности
Обновления и исправления карты и окружающей среды
Изменения игрового процесса