Tulkas

Where do the PDF briefings get installed?

I totally agree, I hope someone listens to you up the chain. It is frustrating to see how it is possible to trap with no harm while not giving a damn about AoA or alignment. HB does a praiseworthy effort with the hook physics, skipping and breaking to reward or punish good or bad passes but it looks that they are very limited to what they can do as long as ED has full control of trapping dynamics. There are plans for LSO and Airboss posts, ready rooms... within the SC but I don't recall any emphasis on improving trapping physics. Anyway, with the SC apparently abandoned for the time being we have what we have for the long run. We will keep on trying to improve flying ball, AoA and line up even knowing that it does not matter so much for the end result, and we will keep on welcoming HB efforts to improve the carrier experience.

Thanks sir, your criticism is always welcome. I find difficult though to assert in the tacview when did I touched the deck due to lack of proper carrier graphic, I though the contact hapened at 720-750VSI and solid 7 degrees nose up, but I admit I was comming down fast on the glide slope and in addition dived a bit to correct the ball it was a CASEIII after a 3h mission, very short on fuel, some slack?

It was a 3h mission, long a heavy ACMI. If this helps: This was my trap, funny enough we did not hear the breaking noise on the deck but quite some time after the bolter. We did not know what the noise was until we found out we did not have a hook anymore. For reference, this was my buddy's trap. He came in way too fast, but his hook did not have corrosion

Yesterday I broke my first hook. The thing is I was quite light, just two sidewinders left and emergency fuel, 2000lbs or so. CASEIII in a no horizont night. I though I touched down on speed. I checked tacview afterwards, 133kts and 10,1 alfa. The guy before me trapped way too fast, 145kts and 7 alfa, and with phoenix still on board, nothing happened to his hook. So there I was, no hook in the darkest night an no divert While I’m happy with a degree of randomness so things do not always break at the exactly same parameters, on speed hook breaking is not fun as long as we don’t have barrier After I saw my buddy landing at 145kts and keeping his hook while I lost it I wished I had crashed on him after ejecting.

Thanks with the inputs. I will pay attention to the carrier course, but having several F14s aligning and take off at the same time and most of them having no problem I'd discard this. Jester is not a problem, is with a human RIO. NAVGRID input error is one of my main suspects. It's easy to mess if you don't notice that you have something hooked and start introducing coordinates. But a NAV FIX should put you back on place and fix the issue and apparently it does not. User error is still my main suspect and where we focus our investigation, the second one would be some kind of pilot-RIO desynchronization over the net. We don't really have dedicated RIOs per se, we all are mainly pilots, but in order to enjoy this amazing module to its full potential we try that every pilot have basic knowledge on the back seat so we always have a fully crewed Tomcat. And then, you know, if you sit a stick monkey on the back and starts to push buttons anything can happen. Literally. We have a few good stories on that I personally don't fly online mission on the F14 if we are not two on the plane. The work HB have made with Jester is brilliant, but nothing compares to the fun and interactivity of having another person on the back. It really has brought a new level to the simulation.

1.No, we are doing carrier aligment 2.Yes. Sailing through the seas (other Tomcats flying off the same boat have no trouble) 3. Yes we are. We love NAVGRID

Thanks for the answer. Interesting. We have RIOs much more prone to suffer this problem, almost every mission. Others very seldom have seen it. But if the IMU is damaged, shouldn`t we get advisory lights? We always look at the caution panel but it does not appear to be caution lights associated to this error. I understand that this IMU fails are not connected to random fails so it is not possible to try to turn off this fail possibility?

We are encountering a recurrent problem when flying with a human RIO. It does not happen always but often, too often. We fly always from the boat so we have no checked if it also happends from shore. Right from take off appears that all waypoints have drifted. Ten or more miles. Coordinates are correct for the waypoints and they have correct position regarding each other. Datalink contacs appear on the correct position regarding the Wps, but our plane thinks is somewhere else. An INS fix does not correct it. It has happened to more than one RIO and so far we have not been able to detect some error on the start up rutine so I wonder if anyone alse has encountered the problem and has a fix for it or maybe knows what are doing wrong. thanks!

Air source to BOTH

Are you properly coordinating the turn with lots of rudder or letting the adverse yaw to take the nose to the opposite direction? it will go above the horizon as soon as you get some bank, ergo climbing a bit as you start your turn. Also is a bad technic to base your flying on the VSI, is an instrument with a lot of lag on the indication so you will always be behind the plane and overcorrecting.

It is a matter of practising more. You have a good set up, you should avoid dead zones and curves. Curves flattening the center will make your life easier with formations, landings and AAR, but as soon as you go to more agressive maneovering, like aerobatics and ACM, you will enter the steep part of the curve and not be able to control the Gs and AoA. If you are going to fly the Tomcat like an Airbus, sure, use curves. If you intend to fly the whole envelop of a fighter, better not. Practising. The time it will take will depend on previous experience, natural abilty and quality of your hardware but many of us have been flying close formation and AARs with shitty joysticks since DID EF2000 or before. What we have now is luxury. That said, the longer the better, you have more range, you need to be less careful. The developers encapsulate the response of the aircraft in the range of movement of your stick, whatever it is. So if the range is equal to the real thing, you should get a response like the real thing. Is typical to see a real pilot trying a consumer sim for first time, with a traditional short joystick, and overcontroling all over the place. If the range is half than the real, their muscular memory obtains double response than expected. I had the luxury of flying for ten hours or so the real AV8B Navy simulator, I wanted at home the closest possible feeling to that, so I messured the range of movement of the stick on pitch (not the length of hte stick!) and I calculated that a 27cm extension on my Warthog would give me roughly the same pitch displacement. It was an amazing change, very close to the real (sim) thing. Now we are just missing a quality force feedback that properly simulate trimming and we will have it all (why is nobody developing that?!) Sorry! I took the liberty of answering not being a SME of anything at all!

Apparently that’s 95% of the people in this forum

Well, depends when you extend the DLC. I’m not using the Beta at the moment so I’m not able to test but NATOPS clearly warns that DLC is optimized for on speed AoA and deploying at higher speed can produce significative pitch changes. Also deploying the DLC before the flaps are fully deployed can produce high pitch rates. Also retracting flaps before retracting the DLC. Sometime ago I made a video about the CASE I, I used a document by Victory205 and the NATOPS. Regretfully for most of you is in Spanish but if you go to 10:39 you can see a screenshot from the NATOPS regarding pitch changes deploying the DLC.

If you follow the NATOPS, you should no rely so much on the DLC, instead correct the glideslope with power adjustments. You should reserve the DLC for the last moment, in close at the ramp to correct a rising ball with a couple of bangs.

I’d pay 80 bucks for that if includes extended debriefings, «DCS Victory205 LSO». 100 if includes voice over for the pilot on a serie of RIO tutorials missions, calling names whe lock is lost or setting the radar wrong

Thanks for the doc, please, keep them coming. This is going my F14 library together with the CASE I pattern which I read every night to dream with sharks and sea snakes. And 80's moustaches.

Picking up with the mechanization of the computer. I found out that to avoid getting stuck on a wapoint unhook every time (half HCU action on a empty portion of the TID) is as healthy as pushing CLEAR all the time: That solved my problem regarding introducing coordinates for the YY. I have another issue regarding introducing waypoints after a ramp start, if I just select for example WP1 on the CAP, push CLEAR, LAT, N or S and try to start to punch coordinates, nothing happends. Nothing shows up in the TID. And easy work around is to do a full action HCU and WP1 is created in the TID and then I can change the coordinates. But I believe I should be able to introduce coordinates from scratch? Without an existing WP? And a question, is ok to introduce coordinates while aligning or should I wait? Thanks!

And economically, at my aeroclub we will get charge a full flying hour if we take the clubs aircraft over 4.5G when doing aerobatics, we learn not to brake wings

I knew about the additional lift from the flat fuselage and the drastic effect it has on the F14s wing load, what surprised me was the fact that it actually takes so much load off the wings with high AoA that they get protected from an over G. Of course, sure you are right and most players probably break the wings with massive instantaneous loads. For the record it has not hapened to me, but being in love with HB Tomcats since it came out, in these years I’ve convinced many friends to buy it, and as a consecuence, I have witnessed so many snatched wings on inaguratin flights (and stalls, spins... ) that I thought it maybe was a little overdone. Never gets old to share an online flight with a new Tomcat guy

Wow! That was very interesting, very detailed and many stories unknown to me. Of course all is the 40 years old memories of a pilot but still some things cought my attention, free quoting: «we were concerned about wings flexion with high loads but to our surprise we discovered that with high AoAs the pressure transferred to the fuselage reliving the wings. So the plane was basically unbreakable with simetric Gs. Assimetric loads put a lot of twisting stress on the back of fuselage thoug, because of the huge stabilators» I could not help to think in how «easilly» we break the wings in DCS with high over Gs, which at first looked logic to me, thinking they would be the weakest spot.

Hi. I sent an email for an order, just wondering if these parts are still available. Regars

Yes, I press CLEAR all the time. Actually it is second nature to me because is like pressing ESC when using Revit to clean previous selection/command, my daily job, point is, I never forget CLEAR. Testing a bit yesterday. After entering YY I run into the same problem, could not enter coverage and direction, but I did a «half hook» on an empty space on the screen and then I could proceed. Like if YY was already hooked.

Hi there. taking my firsts steps in the back cockpit. I have some problems with entering data, such as waypoints or navgrid parameters. I appear to get stuck some time like if I enter the first WP I don`t get to introduce data for any other WP. When I select WP2 and push lat, N, and punch the numbers nothing hapend. Other times I am setting up the navgrid, I get to enter YY, maybe the number of sectos but then the coverage and direction do not work, even if the nulbers appear to get after pushing ALT and HDG. If I get out of the plane and come back, apparently Jester fixes it and it works again. I assume that it is user error but I was not able to find anything about it. thanks for the help!

Anyones knows how this new parameters in the lua affect the fonts? Whit the old lua I only had to set to 0 the DMC outline and I had great fonts. With the new one I had many tries yesterday but the fonts become semitransparent and they are impossible to use with the map. Also the MFDs night mode appears no to work that well. I have to use day mode at night and turn down a lot brightness and gain.