majapahit

"The U.S. Naval Academy Class of 2019 had 16,101 applicants and admitted 1,191. If history proves accurate 1,100 will graduate in three years. Of those, 240 will select Navy pilot and 80 will enter jet training. By the time the Class of 2019 reaches the fleet, maybe 50 will be fighter pilots. (So, for every 1,000 applicants to the Class of 2019, 3 will become a fighter pilot.)" 50 of 320 graduates that choose "Navy pilot" makes for 1:6 or about 16% of flight school year. Mind you 50 of 16101 applicants, most of whom will have self selected by the 'I think I might be able to do this', of this 50 fighter pilots is 0.31%, which is 3 and something out of a 1000 with a dream of soaring through the atmosphere within a thing that can kill. Of Academy pilot graduates 50 out of 1192 (with 92 dropouts) makes for 4.1% which seems to be the biggest selector. Apparently specifically 50 of 80 who finally make it into "jet training" will actually end up in a "jet" which is another 38% cut (and no doubt the harshest one of the 'I came so close' kind).

sure but what % then after get assigned to F-18 or these days F-35?

What I think to see is that all fighter jet pilots that are the core crew on the boat are able to do the very short (rather perilous) 'abeam the stern, hard break, dirty up in the break'. There is so much risk involved in this rather acrobatic maneuver one would think the selection for carrier pilots is already made in training (when they're flying the Northrop T-38 trainer jet with a hook). Already in training one will be able to see, first land based and after some time when these trainee pilots are invited over for a spell of actual carrier training, which one of all those eager beavers make the cut, which no doubt is few and far between. The YouTube video's you see of any FA-18 pilot whether flying perfect numbers or the ones who seem rodeo bull riders, made the cut and all of these chaps (and the incidental girl) already are the cream of the crop (and then again the best of class of this selection, these days will be moved to the F-35 platform, and the very best of the best are invited to undergo astronaut training). The selection can't be otherwise, if one thinks about it, because carrier flying simply is too dangerous. It's Darwin's meritocracy materialized before your eyes out of pure necessity (and the tremendous attraction of the sport, which provides for the necessary selection pool).

I say 'right map' in my microphone: VoiceAttack (10$) does RAlt+RSft+8 (R OBS 18 menu) RAlt+RSft+8 RCtrl+RSft+2 (R OBS 2 HSI) et voila now shows HSI on the right I have roughly 150 voice commands for FA-18 alone + perhaps 50 variations 'parkingbrake/parkingbrake on, parkingbrake off/parkingbrake stow'

he has very little throttle breaking left and after the time the flaps are full he is below 200kts, no throttle, no lift. one knows he's down throttle because he throttles up later on final turn he actually flies level flight on the 90 ~170kts or so, so he started out about 1.4 from the boat, I'd say.

You can see Wags turns in downwind @ 680ft, when he puts gear down flaps down and probable throttling down, he still rises to 740ft, thus this was not 'perfect procedure', gear down below 250 @240 OK, but then he could have waited for a sec and then when flaps down whilst throttling down he would have these 3-4 seconds so he could cross 200kts full flaps and level all at the same initial 680ft, now already decelerating within the full flaps envelope, descending towards his ~ 137kts final speed which is the on level speed on final when light. For the mentioned final break turning in clean and switching full flaps in that break, this is an abbreviated final break what only jet fighter pilots do as a hot (and unofficial, very not NATOPS) shortcut, which most likely is only allowed for proven and tested pilots for its risks (or one would be send off, how unlikely is this ever to happen, anybody knows how this works?) one has to correct such a hard bank by adding throttle and the harder the break the higher the corrected speed for the required vertical descent rate (as in ~200-230kts) so to not drop out of the air because of having highly reduced horizontal surface and thus also when before the final turn the excessive residue thrust has to be anticipated to manage a projected substantial increase of lift when leveling the aircraft to horizontal and this also needs to be anticipated accordingly.

"hold for 3 seconds", or nothing happens, I had tested before and nothing happened indeed :)

Which is a button not an axis. Axis zoom when VR can only be used for outside camera's etc. (VR puts you in a fixed 3D spot in the cockpit presumably)

Why ever would you want to do that? Don't do that. As far as I can tell, light, empty, flaps down level and stable is around 200 kts, higher if heavy, a lot higher if very heavy. The FA-18 can "fly" below that speed with flaps up, thanks to the massive engines, for instance after launched, or doing acrobatics, about from 155-175 when light, which is safe with military or afterburner trust and pitch up, which puts you in a "rocket envelope" with no necessity of any wings. Hard banking in final you watch you descend rate and give whatever throttle necessary to maintain you descent path, which sometimes, in need of correction (f.i. you see you're going to be low merging final when miscalculating you descend because you're out too far whilst being short to the intercept also and are in immediate need of maintaining level flight), will dip you in the 'rocket envelope' as well.

What I started doing lately to exercise CASE 1 (1.5) is training a CASE 1 short break/SHB, starting form the deck, immediately of the deck call Stennis, left hand to 600ft, flaps up at 600 for a sec to stabilize alt @ 200-230kts, immediate final break, ask Stennis to land, dirty up, land on the deck with the landings lights (at the moment release version), in a deep dark night, as if being in a flight sim IFR training with all views off, only relying on HUD, HSI, landing lights @ 90 in pitch dark, ball at final. It teaches you real fast to get your numbers right (this is simulating a sim only, of course).

nope, hasn't

If one checks FCS auto-trim with the Ctrl-Enter indicator on, and clearer than the FCS numbers readout , one can notice the FCS trim that accommodates a certain level flight with certain speed and flaps up while downwind, is fairly maintained after banking into final break with flaps up, because of computation lag (somewhat likely) or because of computation of the - hard - bank (which would be excellent design).

FA-18c has that, "inconsistencies". To rearrange all these, which, mind you, categorically is not a bug but a - design - wish, a design clean-up, one has to go with a fine comb through all of the present coding of all of the interface, which probably is a hell of a job. If one had to choose, we want our lightning pod, don't we.

Oh sorry, it appears you already cleaned up what you have. The original poster (loong time ago) had Coolie and Trim HAT combined

you want to edit the code and add more DX so it can map 2 Hats of the HOTAS (1 on the throttle)

This cannot be called a problem, it's a simulation wish list I'd say.

Having said this, and seems to be correct, I think I thick I remember that ATC throttle hold is still WIP with flaps down half and full, for with flaps out ATC really does nothing other than confuse..

Yep

I use VoiceAttack (10$) (VA can make appear the cursor in the center of the VR googles view and then I run a 4 way button for the VR UI mouseclicks). I say "right MAP" from the default right DDI FCS which changes to HSI on the right DDI, I say "Tacan ON" which switches TACAN on, I say "7","4","UPC ENTER" to set the TACAN channel (unless its channel 1), I say "TACAN right" which pushes OBS 5 for TACAN on the HSI, I say 'course' which makes VA hold the course button 1.8 seconds to make the course line appear in the HSI and sets the UPC to CSEL select, I say UPC numbers like f.i. "3","0","4" for the course and then say "UPC ENTER". Et voila courseline 304. I do the same for ILS. How 'bout them apples.

New Command When I Say : 'mouse' (or something) command button Mouse - 1st : Click / Mouse Click and Double-Click / Click left mouse - OK command button Mouse - 2nd : Move / Move the Mouse Cursor to Location / Move to Specific Location / drop-down 'Cursor screen Center' - OK You now have 2 commands in 'do the following sequence' list, it clicks the left mouse button to have the mouse cursor appear, then second command centers the cursor in the middle of where your head is looking so for APU first look at the APU and then say 'mouse' etc.

I just figured out mouse actions with VR goggles in the UI layer. LR click UD wheel scroll. Problem was the blue pointer 1st time shows up way in the right down corner of the VR vision (somehow, in my setup, perhaps because there's the "FLY" button). Solved this with VoiceAttack (10$), define "mouse", command-1. click left mouse button (makes the VR cursor show up), command-2. move mouse pointer to center of the visible screen, now just say 'mouse' in the microphone. Et voila (Bind to a 4 way button/shifted perhaps). Great aircraft.

I just figured out mouse actions with VR goggles in the UI layer. LR click UD wheel scroll. Problem was the blue pointer 1st time shows up way in the right down corner of the VR vision (somehow, in my setup, perhaps because there's the "FLY" button). Solved this with VoiceAttack (10$), define "mouse", command-1. click left mouse button (makes the VR cursor show up), command-2. move mouse pointer to center of the visible screen, now just say 'mouse' in the microphone. Et voila. Great aircraft.

^^^^ read the Wiki howto

I did quite some testing on my rift last couple of days (8600K @ 4.8 Ghz, GTX 1080), ended up with MSAA 2x -a must for the jaggies SSAA 1.5 - this still works for some reason for clarity of the cockpit Anisotropic OFF - MSAA works better DCS VR PD 1.5 - median for fps Oculus Tray PD 1.1 - why lower than DCS VR DP don't know but it works to keep fps up NVidia panel FXAA ON - because its cheap both Textures HIGH Traffic LOW Water MEDIUM Viz range MEDIUM Heat blur OFF Shadows MEDIUM Cockpit resolution 1024 Terrain shadows FLAT all this haphazard and rather illogically to keep the 45 fps of the sync of the VR Rift Oculus Tray Tool (Instant "Carrier takeoff") (I noticed lately DCS VR is OK'ish @ 22-25 fps BTW, but still, I play in between, with dozens of Firefox windows open, with Firefox on 'below normal priority', GPU 100%, CPU 37%)

You shouldn't then