MrMgrMatt

Hi Hollywood, First off, I want to thank you for creating this. The depth is amazing. This is mandatory when playing in VR, not to mention substantially increasing the immersion factor. :-) I have a suggestion that I have implemented in my own profile that others may find useful. 1. For the F10 Aux commands, to help it be more of a catch-all, I duplicated and edited the "proceed" command into 5 different commands: *menu* - Removed top 5 lines *alpha* - Removed top 5 lines; Changed Set text command from 'proceed' to 'alpha'. Removed Execute command, '_Menu_Execute_Aux' (and wait until it completes) *bravo* , *charlie* , *delta* , *correction* - set each of these up like alpha, but changed the key press from F1 to F2 for bravo, f3 for charlie, f4 for delta, f11 for correction. Below is a sample interaction with the above: <hold hot mic> Speak "Mystery menu" {F10 menu pops up on screen} If you want option 2, speak "Bravo" {Vaicom simulates F2 press, menu reflects F2 press and remains displayed} You were wrong, you really wanted option 3; Speak "correction charlie" {Vaicom simulates F11, F3; Menu reflects the presses and remains displayed} You want option 1 of this submenu, which ends up being the final choice "Speak Alpha" {Vaicom simulates F1; Comms menu disappears as it normally would when you hit a final command option} </release hot mic> With that being suggested, I have ran into an actual issue though too. Some of the missions I play have 2 tankers (S-3B "Arco" for the fast movers and KC-135 "Texaco" for us who play in the dirt), but the current script assumes 1 tanker only and always stops short, usually on the wrong tanker. Single Tanker Comms Flow; Initial refuel request HM, F6 for Tanker(s), F1 for rejoin. Multiple Tanker Comms Flow; Initial refuel request HM, F6 for Tanker(s), {F1, F2 ... or F6} to select the appropriate tanker, F1 for rejoin. Are there any changes that can be made that will work for single and dual tanker missions? My first thought is a mod similar to the ATC mod that will always list all tankers in a specific order, but I hope that you (or someone else here) knows of an easier way.

For all we know, it is a simple fix that the devs figured out and fixed over a month ago. The real issue is the time between 2.x updates. You can't post a fix if a version isn't released to fix it. For most early access / beta products, there is a clear understanding that not everything currently works as intended as the product is a work in progress. However, every 1-3 weeks a new version should be released. That new version may include new features that are in progress, may fix some bugs, and unfortunately may even create some new bugs that will need to be fixed in next week's version. When is the last time we've seen an update for the 2.x version? Mid April? Before that? February? That timeline sounds more like an official content update cycle rather than a Alpha / Beta update schedule. As much as I enjoy watching Wags weekly updates and admittedly get excited with what the future may bring, I can't help but feel like they are only taking the time to publish new versions only when there is a new module they would like to sell, rather than releasing new versions to the Alpha as fixes / updates as is standard for what is considered to be a constant work in progress. Just my $.02. I'll shut up, put back on my vive, jump in my A10C and continue to bomb those damn Reds that somehow made it to the middle of Nevada (since I can't get into Mission 3 to bomb the people just pretending to be Reds as part of OPLAN 1402B).