Profiles for VoiceAttack & other projects

=VG= Kavelenko · May 30, 2019 at 05:00 AM

OMFG! More shit I gotta learn rofl.

=VG= SemlerPDX · May 30, 2019 at 06:52 PM

14 hours ago, =VG= Kavelenko said:

OMFG! More shit I gotta learn rofl.

I agree - when they changed up the radios and radio menus for 4.34, I started by taking pics of all of them (the bottom graphic) just to wrap my head around the changes. Then I built this voice control profile so I didn't have to memorize anything (except those 5 "add/remove hoomans" commands). To use this profile myself, I have that bottom image on my tablet or phone just as an image reference so I can see "what" I can ask of AWACS or other contacts, in case something is new. I certainly don't know everything by memory myself, but I also don't find that I use everything in every flight. I definitely use the AWACS and ATC stuff a lot, and the ATC has really changed! A little learning is half the fun of a sim, right? haha!
:hi:

I'm relying heavily on Jeffu's blog post here to figure out these new features in Falcon BMS 4.34:

Windblow · June 16, 2019 at 01:06 PM

hi =VG= Kavelenko,

I am testing your beta profile. For me it works fine. I just need to learn the proper commands, but one done, it is ok.

The way you have write the profile is unusual for me, and at that time, I am not sure to fully understand it. But no matter.

As a french user i just need to set windows10 with US keyboard. My windows is in english version.

Really good job, I love to use it. Thanks

=VG= SemlerPDX · June 18, 2019 at 07:34 PM

Thank you very much! (It's my profile, not Kavelenko - lost in translation, I'm sure, don't worry about it!)

I had a feeling that the profile may look odd, all of my AVCS4 profiles follow a similar format, and must be grouped by category in order for the list to look correct. By consolidating multi-part commands, and collapsing all categories, it should begin to appear much more ordered. I enjoy placing as much as possible into "initialization" scripts so that if I change anything later, I can make changes in one place. If you look inside most of the commands like "go stack;go spread;..." their content is almost exactly the same as the next or previous commands, and again, this makes it very easy to expand or edit in future if needed.

I would love to work with someone to add localization to this profile! If we could translate my command words into French, and if Windows Voice Recognition and VoiceAttack both work in the French language, it would be very easy to modify this profile. Again, all speech variables are in one file, so anything spoken by the profile can be changed to any language without hunting for them throughout the profile. And editing the commands themselves would let you change any of the command words to French equivalents. Proper nouns would likely remain the same, of course, OR you could change ALL callsigns in the profile to different ones if you edit the .vap and find/replace all. I'll include a readme with instructions on changing/adding callsigns to the .vap profile file before the beta is finished.

If anyone would like to help with localization, RSVP

:hi:

Windblow · June 22, 2019 at 05:39 AM

Hi SemlerPDX

Of course Speech recognition and Voice Atack can work with French. Even if I don't use it, I could do the translation I think. There is an other issue you need to take into account, and wich is maybe first, this is the AZERTY keyboard instead of the QUERTY one.

IN my opinion, Most of french, german ... people are playing with english speech recognition but are not used to transpose the keys from onr type of keyboard to another one

Windblow

=VG= SemlerPDX · June 23, 2019 at 07:35 AM

Thanks for the feedback! If people prefer English for VoiceAttack, there is no sense to waste time on localization.

I believe I can include an option for QUERTY or AZERTY.

Is this correct?

// AI COMMS Menu Lists
Set Text [KEY_AWACS_LIST] to 'A'
Set Text [KEY_WINGMAN_LIST] to 'Z'
Set Text [KEY_ELEMENT_LIST] to 'E'
Set Text [KEY_ATC_LIST] to 'T'
Set Text [KEY_FLIGHT_LIST] to 'R'
Set Text [KEY_TANKER_LIST] to 'Y'

Windblow · June 23, 2019 at 07:59 PM

Yes it is correct for these commands ...

Hi SemlerPDX

Of course Speech recognition and Voice Atack can work with French. Even if I don't use it, I could do the translation I think. There is an other issue you need to take into account, and wich is maybe first, this is the AZERTY keyboard instead of the QUERTY one.

IN my opinion, Most of french, german ... people are playing with english speech recognition but are not used to transpose the keys from onr type of keyboard to another one

Windblow

Windblow · June 24, 2019 at 01:48 PM

in addition, you could include german Keyboard, which is a QWERTZ one ( see chap 4-29 list of keyboard layout, in the technical BMS Manual)

wheelchock2 · June 25, 2019 at 09:23 PM

I know this is a Stretch but what about a status command that gives you a run down on what features are on and what human pilots are set?

=VG= SemlerPDX · June 26, 2019 at 11:18 PM

*For anyone with issues, per a message I received about keys not getting through:
You can ensure that keys are getting sent to the application by opening the VoiceAttack Profile, and clicking on Options along the top, and select "Send commands to this target" and then write in *Falcon BMS* between asterisks (*) for a wildcard catchall for the BMS game window.

This will ensure these keystrokes go where they are needed. See image:

=VG= SemlerPDX · June 26, 2019 at 11:30 PM

SitRep:
I have several great suggestions and will be working on adding several of these ideas to the next working beta (0.99b), if possible. My release plan is simply this beta, and the 0.99b beta, for a few weeks until VoiceAttack beta that we are using gets it's own release, and then I'll add any final changes and polish, and release it as a version 1.0 - I don't expect much need for editing in future unless the radio menus get changed again, but will maintain the profile and entertain any useful suggestions even after final release.

If anyone has any other suggestions, feel free to let me know! Thanks for all the feedback so far!

:hi:

=VG= SemlerPDX · July 18, 2019 at 04:14 AM

BETA UPDATED TO v0.99 (final beta!)

Please download newest version! Link below and updated in the main post above! You don't have to remove the 0.98 beta profile, but it is recommended to not use both at the same time or variables may get messed up. Thanks to everyone for helping to finish up final testing!

SitRep:
I've finished integrating the proposed changes I received through the v0.98 beta, and the v0.99 beta is now available for download (click here). There is now an alternate All-Humans Mode that can be turned on, and will assume all pilots are humans unless you individually set Computer Pilots per callsign/flight/wing numbers. All the same "Set a Human Pilot" commands have been copied to make "Set a Computer Pilot" equivalents.

You can also change the Keyboard Layout from the default QWERTY by voice command or just executing the "change" command found under initialization.

Per request, to speed up the interaction of adding/removing pilots from the exclusion lists, you can now say the entire Callsign + Flight Number + Wing Number when asked for the callsign.

Example:
"Set a Human Pilot"
"say the callsign"
"Cowboy 7 3"
"Cowboy 7 3 - is this correct?"
"Yes"
...
(bypassing the need to individually set Flight Number and then Wing Number!)

This will jump to the confirmation at the end of the command and greatly reduces the time spent interacting with the voice control system configuration. During my testing, I found there must be a clear separation between the Flight Number and Wing Number when spoken, to avoid "Cowboy 7 3" getting recognized as "Cowboy 73", and your own results may vary. Please test and let me know. The old system is still in place, and you can even just say the Callsign + Flight number, and it will notice and skip to the Set Wing Number segment of the script. The entire idea was to allow a lot of options to recognize how we speak, and the only catch is that we need to enunciate and keep succinct breaks between words for this style of input. Further beta testing in this final 0.99 phase should help judge if this will work or if it needs adjustment.

Additionally, there are now VoiceAttack command log notifications whenever the profile loads showing the current profile settings, and also voice notifications if either PTT mode or the new All-Humans mode are On.

Here's a copy of the changelog:

Beta v0.99 Changelog Jul2019
New Commands:
 -Change Default Keyboard Layout allows choices between QWERTY, QWERTZ, & AZERTY (per user request)
 -Turn On/Off All-Humans Mode : Reverse mode assumes all pilots are humans, add Computer Pilots individually as needed (per user request)
 -Copy of all Add/Remove Human Pilots commands for Computer Pilots & All-Humans Mode

Fixes/Improvements:
 -Can state an entire callsign plus flight & wing numbers when asked for Callsign (per user request to speed up the voice system interaction of adding/removing human pilots)
 -VoiceAttack log entries displays profile information on startup (current keyboard layout, push-to-talk mode on/off state, All-Humans mode on/off state) (per user request)
 -Speech notifications on startup for PTT mode and All-Humans mode if they are enabled (see above)
 -Forced profile initialization if not initialized on any command use (per bug report: on first download/import of profile, trying to use any command fails until voiceattack restarted)

*wheelchock2 had asked about a query system. I have not made a system to ask which callsigns have been set/saved to either a Human Pilot or Computer Pilot, as it was always designed to be a throw-away use concept, add a few for the afternoon, adjust for different flights, reset at the end or beginning of a days' use of Falcon BMS. I'd like to know if there is serious interest in a query system before I create one as it will add a bit of size to the profile, increase it's RAM footprint further, and possibly increase profile load time even further. It would not make sense to add this if there is too little use for it. Personally, I remove all human pilot callsigns before every flight, when I'm at the 2D map/mission planning phase. Please let me know how you guys use the profile, and if you'd use something like a query system.

=VG= SemlerPDX · July 21, 2019 at 06:59 PM

A small bug has been found, the Keyboard Layout is not remembering it's settings when the profile is reloaded because the variable didn't get loaded in the initialization file as intended. This will be fixed for the final version. If you use a different keyboard layout than the default QWERTY, and you don't want to have to set this each time this profile loads until the next update, you can simply add the line to the KEYPRESS_Variables command as shown in the image below. Copy the variable AVCS_BMS_KeyboardLayout and insert a 'Set an Integer Value' found under "Other > Advanced" and paste in the variable name. Below, select the box "Retrieve Saved Value" and nothing else.

Again, this will be done for the final version, and only people with non-standard keyboards need to be concerned. :hi:

wheelchock2 · July 29, 2019 at 12:58 PM

Some nice additions and glad to see that you are actively developing this profile. It is my goto for BMS single player and am currently trying to work it in with MP. The MP side of it for me is just a trust issue mostly. I don't want to inadvertently trigger the tanker done refueling until I'm directed by my flight lead to do so, but the blind call of done refueling still needs to occur. I guess using PTT mode and setting it to something other than COM1,COM2 is the answer.

Again nice work and looking forward to the finished product!

=VG= SemlerPDX · July 29, 2019 at 06:41 PM

I think for the scenario where you are not the lead pilot, but you still want to use the profile so you can talk to Tower/Ground/ATC/etc. there should be a way to disregard comms that may try to trigger such calls.

Should I have a mode that we tell AVCS we are not the lead pilot, and therefore a certain set of commands will not trigger even if we directly call them? That would not be difficult, but we would want to compile a list of all commands that logically should be ignored if we're not the lead in a flight online with humans.

An alternate on this method would be to set only one PTT (for example, UHF) and use that for AI comms primarily, and the VHF for inter-ship Player to Player comms. The PTT mode does not require both keys to be set, just the Press & Release for VHF -or- UHF would suffice.

The way you propose an alternate use of PTT mode might possibly get more in the way than anything, if I could make it so you don't have to do work like another simple mode which could be made to handle this type of flight, it may be preferable. I hadn't thought about this, much appreciated!

wheelchock2 · August 1, 2019 at 03:25 PM

So I did what you've suggested with regard to setting a different PTT key. I used the Coolio POV switch on the Warthog Throttle as my VA profile PTT key and then set PTT mode on for the VA profile. This would work for MP but in Single player I like to use the UHF and VHF keys as I normally would . I've just set PTT mode off in SP so my blind calls are picked up by the VA profile (usually) without the need to press my alternate PTT key. It's kind of clunky but so far it works for me. I don't know how else you could do it without it ending up being an issue.

wheelchock2 · October 14, 2019 at 07:18 PM

Hey man, been using the profile without too many complications...I do have one issue which isn't an issue more of a request. I've been wanting to turn off the comms menu in game (she hack to turn the menu into a pixel so you can see it) and if I do that that is the only way I know if my command was accepted or not. It would be cool if you could get some feedback if the command was accepted without having to look at the VoiceAttack window. I typically have my VA window covered up by Helios or some other tool. i've tried setting the DEBUG command in your profile to say "say again" if a command wasn't accepted but that only seems to apply to actual commands. It fails to work if it accepted the command but didn't quite reach the confidence level. At this point nothing happens. Is there some way to do what I'm asking?

=VG= SemlerPDX · October 14, 2019 at 08:21 PM

There are two settings under Options in the Recognition tab regarding Confidence and you should test and set these as appropriate to help make sure your commands fire the first time, every time.

For feedback as to if a command fired or not at all, you might consider using an audio cue. As you've mentioned this as a feature request, it would be no trouble for me to include an optional audio cue to both of these actions.

First, (if you don't want to wait for me) get two different distinct sounds. I'll find better ones for a final addition, but for example:

For a command that was recognized and executed by VoiceAttack (I'd cut this in half for just one sfx, and give it some filtering, etc.):
https://retired.sounddogs.com/sound-effects/walkie-talkie-two-way-323236

For a command that was unrecognized (quick and bad example, but choose something distinct):
https://retired.sounddogs.com/sound-effects/walkie-talkie-two-way-323255

So, then under the command in the category DEBUG, open the F_AVCS_VAS_INVALID_COMMAND command, and under Other > Sounds, choose Play a Sound and select the second example .mp3 - these new sound actions should go at the very end of all current actions, make it the last thing to happen. When done, press ok and apply.

To handle about every other command, you can add a "Play a Sound" line for the first example .mp3 to all 5 commands in the "AI COMMS - Prefix Words" category, this will cover the first half the commands without going into each one - but for commands in categories "AI COMMS 2 - AWACS - AWACS Page" through "AI COMMS 3 - ATC - Tower Page", all 10 commands would need to be edited and have that same "Play a Sound" line added, all except those commands in the WILDCARD categories (those just call commands directly from the standard set anyway). Again, the place to put this Play a Sound line is the very end of the command actions as the last item.

I can see this being helpful, and those example sounds above are terrible, so when I get time in the coming weeks, I'll craft up a pair of good sounds, and wrap a system around it that can be turned on or off.
I hate repeating myself to voice control, too, and wondering if my command is going to fire or not, so I'm down for anything that could help on that front.

Hope that helps for now! I have some website work to do here with my download section, and once those bugs are squashed, I'm gonna finalize this profile and get it out of beta, and share it around the BMS places. In addition to the feature you just requested, I'll be adding a single adjustable Variable Pause for the time any key is held down during macros, currently at a hard set default of 50ms.
Cheers! :drinks:

wheelchock2 · October 15, 2019 at 03:14 PM

Ok so I found some sounds I can use, kind of like the ones you had there...They'll do in the interim until you get them backed in. I added the accepted sound as you stated...I'll do some testing and see if it works ok or not.

EDITED: After adding the unrecognized sound to F_AVCS_VAS_INVALID_COMMAND I found that it was playing this sound for all kinds of stuff that it couldn't recognize. From hearing the dog barking to my own breathing. I guess I didn't notice that VA was picking all that stuff up until I heard it playing the unrecognized sound all the time. So I removed it since it isn't too helpful anyway. Knowing that I should hear the "beep beep" sound after a correctly recognized command was enough for me. if I don't here the beep beep sound I added then I know it didn't get what I said and I repeat it. Works pretty well. Maybe you can come up with something fancier than that. My next test will be enabling all humans flight with PTT set to OFF and see if that works well. if so I will most likely keep it that way, typically I only fly with people and not a mix of AI other than normal ones AWACS, TOWER, TANKER.

=VG= SemlerPDX · October 23, 2019 at 05:09 PM

I should have mentioned that PTT would be required for that invalid sound cue option - as it would otherwise fire for every cough, bark, pin drop, etc.

The All Humans mode for just ATC/AWACS/TOWER/etc is actually how this profile started, years ago. It's the most tested, though these new methods are unlike anything I've written before. I think the biggest curve ball will be the duplicate commands that came with this latest patch. See note in the command reference pic for details. Best wishes and good luck!

=VG= SemlerPDX · October 30, 2019 at 12:50 AM

FINAL RELEASE TO v1.0

Please download updated final version! Link below and updated in the main post above! You don't have to remove the old 0.99 beta profile, but it is recommended to not use both at the same time or variables may get messed up. Thanks to everyone for helping to finish up final testing!

SitRep:
I've finished with all final additions and proposed changes, and all known bugs and issues have been resolved. We've tested quite extensively to try to break things, and it seems fairly stable. The final version can be found in our download section, please rate and comment if you like and share this link if you can (click here). There is now an Audio Feedback Mode that can be turned on or off at any time. It plays a short sound when a command is successfully recognized, to save time and help avoid the frustration of not knowing if we have to repeat a command.

I've given the option to have the Audio Feedback sound effect to output through stereo left, right, or center channel(s), and this is set when you turn the mode on. It is a radio cue up type sound, but a bit distinct compared to the ones in BMS to help differentiate feedback. All three sound files are very tiny, and are included in a VoiceAttack Profile Package for easy importing into VA, and will be placed in folder in the VoiceAttack program folder under Sounds automatically when the profile is imported.

Finally, there is a single Variable Pause in the KEYPRESS_Variables command that controls the time between a keypress and release for every action in the profile. Default is 50ms, and if a user has any issue with the keypress macros firing buttons too fast for their computer, this number can be increased slightly to slow down the system and fix any issues.

Huge thanks to everyone who helped out with comments, feedback, bug reports, and testing - I'm very happy with how well this profile has been developed, and I have a feeling it will be a solid tool for years to come! I'll support any changes for future BMS versions, and will try to respond to any questions about this profile.

Here's a copy of the changelog:

Final Release v1.0 Changelog Oct2019
New Commands:
 -Turn On/Off Audio Feedback Mode : Provides sound feedback upon successful recognition of a command (per user request)
 -Added a non-functional command to help recognize many variations of "Yes" words for the voice confirmations in profile

Fixes/Improvements:
 -New Variable Pause between any keypress/release for adjustment of the time any key is held down, in keypress_variable command. Default is 50ms
 -New Audio Feedback Mode has custom SFX included, and gives user option of stereo left, right, or center playback for easier distinction
 -New Speech notification on startup for Audio Feedback Mode (if enabled)
 -Speech notifications on startup for PTT mode and All-Humans mode (if enabled) have been greatly shortened.
 -Fixed issues with being able to set Humans in Computer Pilots mode and vice versa

Any problems or new bugs, or brilliant ideas, feel free to drop some feedback! Cheers! :drinks:

=VG= SemlerPDX · November 3, 2019 at 06:31 PM

v1.1 Patch has been released

A bug has been identified and removed. This issue prevented the entire Human Pilots Registry system to function and should have been caught before the final release version. All apologies to everyone who has been trying to use this new voice program. In addition to this, I've decided to not use a wildcard to catch the name of the BMS program to send keypresses to, and have gone for the "Falcon BMS.exe" method. Still, this will not catch every user, and players will need to test to be sure commands go through initially, and refer to VoiceAttack troubleshooting (and those tips we've highlighted already) to get commands to fire in the correct window. I'm happy to help new users, and the community has been helpful as well. Any questions, feel free to ask!

Patch Release v1.1 Changelog Nov2019

Fixes/Improvements:
 -Changed common Send To default from *Falcon BMS* to "Falcon BMS.exe" to avoid conflict with open PDF's, etc. with Falcon BMS in name
 -Fixed Human/Computer Pilots Registry system - last minute addition of a mode check was to blame, has been removed for now

Download: (Click Here)

=VG= SemlerPDX · December 28, 2019 at 11:53 PM

v1.2 Update has been released for BMS 4.34.1 (U1)

Falcon BMS 4.34 has just released Update 1, and with it has come some serious improvements and additional features. For this profile, and the in-game Radio Menus in general, all that has changed is an addition of a "Ready for Departure" call as the 7th choice on Page 6 of the ATC Radio Menu. I have added that command to the profile, but as it does conflict with the default "Ready for Departure" command, this Carrier specific command will need to be preceded by the word "Carrier" as a forced prefix word (see note in the large Command Reference pic).

Example use: "This is Joker 7-1, Carrier Ready for Departure"

I've also added a bit of polish to the Audio Feedback system, allowing it to recognize the word "feedback" as two words, "feed back", to help us avoid repeating ourselves to get the commands to fire, as well as a null check on the Stereo Audio Feedback output channel, so it can recover if this saved setting is lost. I've also updated the minimum version of VoiceAttack, so please be sure to update your VA program.
We've tested this version, just minor additions, and everything seems great - but let me know if any issues pop up! Happy New Year!

Patch Release v1.2 Changelog Dec2019
New Commands:
 -"Carrier Ready for Departure" : for ATC Page 6, new 7th item added for 4.34 (U1) update

Fixes/Improvements:
 -Added additional recognition words for turning on/off Audio Feedback Mode - "feedback" can now be recognized as "feed back"
 -Added Null Check on Audio Feedback Stereo Output Channel setting, if saved setting lost, will force user input on profile load
 -Updated minimum VoiceAttack version to latest release (v1.8.3) for compatibility

Download: (Click Here)

=VG= SemlerPDX · January 3, 2020 at 06:11 AM

v1.3 Patch has been released for BMS 4.34.1 (U1)

Just a simple hotfix for a bug found by Wheelchock, the standard "Ready for Departure" command was getting overwritten by the variable for the new "Carrier Ready for Departure" command added for the new U1 update for BMS. As a result, this command will call an Abort by attempting the same input key as the carrier departure. Basically, everyone does need this hotfix, can't be avoided.

Anyone can easily fix this themselve inside their own profile, if you already have v1.2, and you don't want to bother importing this new version - just open the command labeled,
"KEYPRESS_Variables →→→((ADJUST AI COMMS LISTS & KEYS USED BY THIS PROFILE HERE))←←←" and scroll down to the ATC Variables section, under the Carrier Page section,
you can change the #7 variable from "Set Text [KEY_ATC_ReadyForDeparture] to '7'" to "Set Text [KEY_ATC_CarrierReadyForDeparture] to '7'", and apply changes.

Otherwise, just download this new version...

Patch Release v1.3 Changelog Jan2020

Fixes/Improvements:
 -Fixed issue with variable conflict for "Ready for Departure" - was pulling new variable from "Carrier Ready for Departure"

Download: (Click Here)

=VG= SemlerPDX · January 16, 2020 at 09:51 PM

Happy to announce version 1.4 just around the corner! Coming next, I've created a save file system to maintain user defined settings (PTT Mode On / Audio Feedback / Keyboard Regional Layout / etc.) between updates, as well as a live update system for minor patches to systems initialization, where a majority of my AVCS4 profile gets it's operating information.

To put it plainly, in the next and all future versions, a missing variable or typo in one of the commands like INIT_KEYPRESSES can be pushed out almost instantly to any users of AVCS4 when I receive the report (1.3 exists because 1.2 had a simple typo in the new Carrier Ready for Departure command, in the init file only). Imagine one of the text-to-speech item variations had a problem, and was saying a word wrong, I could change that TTS variable on my end, and push it out to all users who would get it almost instantly when loading the profile.

I tried a test of more than 2kb (the entire keypress init without comments is only 7kb) of info and a hundred variable updates and couldn't increase the profile init time past 1 second, so it's fast, powerful, and will allow featureless updates without re-downloading new profiles.

Additionally, the 1.4 version will feature an update notification system, too, to let users know of any major updates that require a manual profile update, with minor bug-fix patches being installed silently on profile load.

Never again will a typo require an AVCS4 "download new version"! For every AVCS profile or profile builder module I make for any game (BMS, Elite Dangerous, ARK/ATLAS, the Voice Controlled Profile Builder, etc.), any custom user saved settings will no longer be lost due to profile update/delete, or even complete windows reinstall (save file backup system included).

Thanks to everyone for your continued support and feedback! Happy New Year!

Sign In

42 Comments

Recommended Comments

=VG= Kavelenko 2,298

Link to comment

=VG= SemlerPDX 6,210

Link to comment

Windblow 6

Link to comment

=VG= SemlerPDX 6,210

Link to comment

Windblow 6

Link to comment

=VG= SemlerPDX 6,210

Link to comment

Windblow 6

Link to comment

Windblow 6

Link to comment

wheelchock2 5

Link to comment

=VG= SemlerPDX 6,210

Link to comment

=VG= SemlerPDX 6,210

Link to comment

=VG= SemlerPDX 6,210

Link to comment

=VG= SemlerPDX 6,210

Link to comment

wheelchock2 5

Link to comment

=VG= SemlerPDX 6,210

Link to comment

wheelchock2 5

Link to comment

wheelchock2 5

Link to comment

=VG= SemlerPDX 6,210

Link to comment

wheelchock2 5

Link to comment

=VG= SemlerPDX 6,210

Link to comment

=VG= SemlerPDX 6,210

Link to comment

=VG= SemlerPDX 6,210

Link to comment

=VG= SemlerPDX 6,210

Link to comment

=VG= SemlerPDX 6,210

Link to comment

=VG= SemlerPDX 6,210

Link to comment

Join the conversation

Server Rules

FYI

Important Information