EntropySG

The 132nd Virtual Wing is a community of close friends and aviation enthusiasts, flying DCS for over ten years now. Within the 132nd, we have multiple squadrons, each specific for one aiframe, but we also have dedicated JTAC/FAC(A), ATC and AWACS squadrons. Check us out and see under the recruitment page which squadrons are currently open for new applicants. Do you fly the mighty Tomcat, or control this iconic beast from the backseat, and are looking for a home of like-minded friendly fellow nerds? If you are EU-Timezone based, and have a solid understanding of operating the F14 in either the front- or backseat, stop by and check us out! http://www.132virtualwing.org/index.php/page/about We won't teach you how to start up or land the plane- this we expect you to know, but we teach you how to fly in an as real as it gets environment with dedicated training events and complex multi-package missions. We don't expect you to be a seasoned pilot, we welcome newcomers and experienced aviators alike, but we expect you to to be willing to learn. 108th Virtual Fighter Squadron - The Spectres Flying the legendary F14-B Tomcat, the Spectres are the 132nd Virtual Wing’s first genuine multi-crew squadron. The dream became reality when Heatblur released this iconic aircraft, and the 108th Spectres were formed in July 2019. The Squadron consists of two sub-squadrons: the 108th Pilots and the 108th RIOs – both with individual training programs. Trainees choose either role and, after a successful Mission Qualification in one of the two arcs, a 108th pilot can then pursue training as RIO - or vice versa - if they so wish. The Spectres are a multirole squadron, with a focus on (but not restricted to) carrier operations, flying Air-to Air, as well as Air-to-Ground missions, for the 132nd Virtual Wing.

yeah, sorry, I noticed its all back to normal thanks a lot guys for your efforts and the huge update over the holidays !

is anyone able to update? my d/l speed decreases and then gets stuck at zero with about 80% to go. edit: nvm, seems to be working now

We have both carrier sqds and non carrier sqds within the wing (132nd Virtual Wing), we had 10 hornets and 2 tomcats on the carrier on last sunday's comat event. We do our best to simulate carrier ops as IRL, with zip lip procedures, pre-brief launch and recovery cycles and all that. As the original poster wrote, simply respawning etc won't work for us as we try to immerse ourselves as real as it gets. now, many of those carrier-based flights had tight integration with land-based sqds with regards to time on station, and time on target. That matters a lot for our operations (opening of SEAD windows against IADS networks etc, CAP/SWEEP being on station before the A-G flights arrive etc etc) No matter how much our individual flight-leads plan their sorties (and a lot of the playtime goes into planning, which is fun!), but no matter how much we plan and practice: A singel stuck jetblast door ruins the timing, and more importantly, as its an obvious bug, ruins the immersion. It happened on several events now. Please, give some more love to the supercarrier module, I realize such bugs or many of them only happen in multiplayer, but maybe a simple code could be impleneted that checks when a JBD remains open for xxx amount of seconds respawn it or something. Ofc dear Nineline, I can understand that you guys need trackfiles and bugreports, and I will try to grab it from our server for that event, but in either case, those stuck JBDs are something that can be very disruptive for us. Not complaining, just hoping that those could be adressed. many thanks!

manually sweep your wings to 20° wait for the wings to stop moving, then press the handle of the sweep control down, then press the master reset switch then you should be able to put it into auto

mmh I just gave it a spin today for the first time. we had a viper trying to give me coordinates and talk on for a ground target. first, the coordinates are (of course) way too inprecise, not being able to enter 2 digit seconds so Nxx xx.x only makes it hard for a talk-on via sensors in CAS, so your starting point for the talk-on might already be quite off. Then, there is (as far as I can see) no manual zoom control. That makes a talk-on very hard, as you need to be able to manually zoom out and in and switch back and forth. then, when I slow the lantirn to the steerpoint I just manually punched in, and read back the coordinates from the lantirn display, they are totally not even close to the coordinates of the waypoint. It probably is me just making a mistake with the format or something, but we totally didnt get it to work. also giving Jester the option to slew to lates missile coordinates etc makes it very arcady, being a good solution for many, but not all. maybe it would be feasable to have a menu option in DCS for the tomcat to enable a system like the old lantirn mod (where you simply give the pilot control of the pod, all you need is zoom, move, and slew to coordinates I guess) or the arcady jester implementation. Either way I will love this module forever, with all its pros and cons, but maybe this feedback is helpful. oh and if someone coudl point me to why my steerpoint coordinates totally differ from the lantirn coordinates after slewing, Id be very grateful.

I don't know if that is of any help to you, but in case it is, you're welcome to use this very basic code to have an option to open a recovery window and turn the carrier into the wind for start/recovery. It's based on the MOOSE class NAVYGROUP, which was created by a very talented member of the Moose community, Funkyfranky. This is merely a teaser, with very basic functionality. The real thing is the MOOSE class AIRBOSS (also written by Funkyfranky), if you google that you will get to a very well documented page on the MOOSE wiki showing you how to set it all up, its not as hard as it first looks, check it out!. The AIRBOSS is perfect for multiplayer squadrons, as it will allow you to maintain a greeny board and even stack incoming flights in the port hold etc etc etc. But for the very basic functionality, to get started, you can do this: 1. in your mission, create a mission start trigger and load MOOSE.lua (this should be done at the very first step, and without it, subsequent moose scripts cannot work). I have attached the MOOSE.lua to this post as a zip file due to the 5MB file size limit on the ED forum, please unzip first!Moose.zip 2. modify the NAVYGROUP_basic.lua with a text editor, you only need to do a few small changes in lines 1-7. make sure you enter the names exactly as they are in the mission editor or the script wont work.NAVYGROUP basic.lua 3. load your modified NAVYGROUPS_basic.lua script as a once trigger. Make sure you load this AFTER moose.lua was loaded, else it can't work. 4. now place your carrier, no need to set tacan/ICLS via the mission editor, this is set via the script. Give it 3 waypoints and draw a box with them, the carrier group will steam along those waypoints, no need to close the box, it will steam to the initial waypoint once it reaches the last waypoint. For reference, I have attached a simple mission file navygroups_simple.miz ((in case you wonder why the tacan and ICLS channels are repeatedly re-created via the script, this we had implemented a while ago, as for some reason the carriers stopped transmitting after a while, not sure if that bug was solved on ED's side since then))

Thank you ED and also , and this should really be said, thanks to all the testers!! Thanks for such a cool update 2.7 blew me away and.. it works!!

wow, several years since the original posting, much has happened for the 132nd in the meantime. We now in addition to the Squadrons we started out with (ATC/AWACS/JTAC- sqd, Ka50-sqd and an A10-sqd), also sport Mi8s, Hornets, Vipers and Tomcats, each with their distinct set of Training Programs (IQT/MQT/CT) from basic flying up to Flight-Lead-Upgrade and FAC(A) qualifications. What made me post here, on Dec. 21, 1970, the first Full Scale Development (FSD) Grumman F-14A Tomcat (BuNo 157980) took off for its maiden flight from Grumman’s flight test centre at Calverton. That day, Grumman chief test pilot Robert K. Smyth and project test pilot William Miller decided to take off in spite of the bad weather: the poor wx (weather) conditions, however, forced the test pilots to cut the flight (consisting in a couple of visual patterns with the wings in the forward position) short. Although the flight lasted less than initially planned, the first Tomcat took the air a month ahead of the contracted data and showed the great potential of the aircraft. To celebrate this event, in honor of the well-loved F-14 Tomcat, we flew parade over the Al-Dhafra TMA, here are some screenshots. Please go and check us out if you are interesting in driving this wonderful plane (or maybe you even are up to the challenge and dare join us as Radar Intercept Officer and control the package yourself), and if we are what you are looking for, drop us an application. http://132virtualwing.org/index.php/page/recruiting Please note, due to the high demand, applications for Ka50, F18, F16, and A10 are currently not being considered. You can check back on the recruitment page to see when they re-open for recruitment. https://streamable.com/16bs6g

thank you!

please add a 'new posts' button like the old forum had.

we had a large multiplayer campaign mission yesterday and also experienced this. while it worked for some tomcats, it did not work for all. our plane had erroneous datalink first, we thought the RIO pushed the wrong button, got into a new jet, then it worked fine. some cats didnt have the problem at all, for some the datalink didnt work throughout the mission at all. so hard to give a definite report, as everyone had different issues and some had non, but we've been flying together for a while so it not like' please check you turned it to the correct freq' or something like that. we experienced no issues before the latest open beta update

+1 on phoenix. more info on how exactly they work in terms of optimal parameters, recommended ranges to fire depending on aspect, speed etc. and most important, reliable information when they go pitbull would be the most important info for me. we do a lot of tests internally and have a good grasp on how to deploy them, but Im not sure we do it 100% correctly EDIT and using this post to say to all of HB thanks again for creating the most awesome module out there, by far, and making my childhood dream (almost) a reality ! :D second EDIT (think..push.. speak..) also I think info on how to use countermeasures with Jester is a bit lacking. when flying without a human RIO, can I rely on Jester chaffing (without depleting everyinging in seconds), what does the Jammer do, is it even implemented, whats the recommended CM program, and how to use that F10/Ground Crew countermeasure radio command (that you never get a confirmation after you used it) vs the in game rearming refuelling window, I still dont know how to set countermeasures correctly in the tomcat

Thats very useful thank you very much!

We have the same problem, anyone knows a fix ?