majapahit

R/L Pilot on youtube mentioned F/A-18c can do actual autoland on ILS on carrier (his was the Kennedy). Yep.

Flaps (full, maybe half is OK too), landing gear down, the W and the E will pop up in the HUD, if that's what you mean.

" ... and its a whole lot better than pre the last patch .." which is a relative opinion, wherein lies a certain relative value, it's still awkward.

Its the massive pitch movement which is awkward

DCS update 4 / F18 - trim, flaps up, full flaps, trim12, speed behavior gone bonkers? EDIT: Never mind I re-installed my USB drivers

Y Saturation 95 about solves this (for now)

This.

OK THX

I prob am missing something What does this "W" symbol in the HUD exactly do? When does it appear and disappear and for what purpose? Velocity Vector the round circle prediction, and "W" (called 'watermark'?), somehow these designators are mixed-up on the forum?

Most examples above describe 'turning into the groove from downwind leg’' which is somewhat ideal but overlooks to mention crosswind. When I practice 'straight in' from my own edited saved mission which puts me a couple of miles out at 1000ft (when time is in short supply), the carrier is sailing 000 straight into the wind, the landing strip though is offset about 10 degrees, so, you're landing in a crosswind, where you compensate for the relative resulting (and somewhat variable) crosswind angle of prevailing wind, boat speed and aircraft speed, which is 10-15 nearing maybe 20 degrees varying with the gusts. You have to compensate for this crosswind (and there is a lee behind the tower perhaps). That is why still at distance from the carrier my reference target is the carrier tower for height and distance and where I want my velocity vector to end up when I can actually know where the groove is (when one can see the full length of the landing strip), where, depending on how you deal with cross landings, I let myself slide from upwind to exactly before the carrier threshold where this shifts to the textbook 'crotch' of the carrier which is where landing strip top right side meets the port side of the ship (rudder, a tad of roll, and necessary throttle). So, when ‘turning in from the leeway side’ from downwind leg, either your hit the spot perfectly (like you see in these perfect Youtube landings) OR when not sure, prefer to be a tad upwind, or at least consider there's wind force coming from your right side.

I have TMWH Joystick connect problems often because I have way too many USB devices connected Try connect to a clean computer or use USBDeview.exe to delete all USB entires in your registry and the connect only the joystick Maybe it will come up

Autopilot CHAIN A/P, ATTH // unreliable (for me), some times does, a lot of times does not has to be button in target CHAIN DOWN+(A/P binding), delay (111ms), UP+(A/P binding), delay (111ms), DOWN+(ATTH binding), delay (111ms), UP+(ATTH binding) This does work and puts the F18 in ATTH mode when simply switching up to PATH // TMWH 3-way AP - "A/P","ATTH" - (L_CTL+'1',L_ALT+'1' key bindings) MapKey(&Throttle,APPAT,CHAIN( DOWN+L_CTL+'1', // A/P D(111), UP+L_CTL+'1', D(111), DOWN+L_ALT+'1', // ATTH D(111), UP+L_ALT+'1' ));

I was experiencing the same ‘slow buttons’. ‘Buttons’ are not so much broken, but this is the way F/A-18C interface is coded. F.i. TMWH AP 3-way switch Up, I programmed as A/P ATTH, When simply using TARGET MapKey: CHAIN “Pulse A/P button” (needs extra key binding), “Pulse ATTH button” this gives unpredictable results. Sometimes catches, lot of times not. Then again if one codes a Target CHAIN like actual button pushing. e.g. the TMWH flip AP 3-way Up ‘PATH’ does: // TMWH 3-way AP - "A/P","ATTH" - (L_CTL+'1',L_ALT+'1') MapKey(&Throttle,APPAT,CHAIN( DOWN+L_CTL+'1', // A/P D(111), UP+L_CTL+'1', D(111), DOWN+L_ALT+'1', // ATTH D(111), UP+L_ALT+'1' )); which does ‘UFC A/P’ down, 111msec, ‘UFC A/P’ up, 111ms, ‘UFC Options button 1 Down’,111ms,‘UFC Options button 1 Up’ This works properly (as good as one manually pushing the buttons in the A/C) BTW. The actual A/P sequence would also involve UFC "On/Off" but this appears to be either broken or not implemented in the present F18 pre-release

You look at you velocity vector 1st, it needs to be on the tower somewhere when at distance, and moving the A/C velocity vector scanning over the deck it should lite your AOA middle circle once in a while. When getting closer you position yourself correctly with very little rudder and roll. In the mean time you check what speed the A/C is stable on a very steady decent, and your main intrument, i find, is your velocity vector that is aiming at, from somewhere a couple of hundred yards from the deck, at a point on the deck that would bring the A/C down at cable #3, by now your AOA middle circle should light a lot, you're now picking up the ball at the left of the deck and see if you're on the dot. If sinking too fast you should have pulsed the throttle, see the velocity vector go back in the direction you want to go, and before the velocity vector arrives at your aiming point you already easy down on the throttle towards where about your throttle should fluctuate around (all the time).

(from my other post) " Don't flare don't miss. Do not take off power. If anything pulse that reduction of power that u used to steer down the glide slope, fly the aircraft not the cable. Better hit cable 5 or do a touch (and miss) and go around than any chance of hitting the stern (there is perhaps even a lee effect coded when too low behind the stern of the carrier). What I noticed on actual F18 youtube footage is that the pilot (a pilot? perhaps this differs per squadron and AC type) when wheels touching the deck, actually smashes full throttle, in disregard whether they caught a cable or not (they did of course). There is no decision time for a full throttle calamity, so it appears they build the cables capable to stop the aircraft when at full throttle, and when a cable snaps (or a hook brakes? does that ever happen? or whatever), that's how the pilot has the chance to escape. "

' .. take off power and falls like a rock .. ' is how I hit the stern of Stennis, this is instinctive flaring behaviour that you apply in aircraft that have actual wings. The FA-18 is build for way to high speeds and has dismal wings attached that if one was to use this on the size of a tennis court deck of the Stennis one glides into a flare .. and risk missing the cables. Don't flare don't miss. Do not take off power. If anything pulse that reduction of power that u used to steer down the glide slope, fly the aircraft not the cable. Better hit cable 5 or do a touch (and miss) and go around than any chance of hitting the stern (there is perhaps even a lee effect coded when too low behind the stern of the carrier). What I noticed on actual F18 youtube footage is that the pilot (a pilot? perhaps this differs per squadron and AC type) when wheels touching the deck, actually smashes full throttle, in disregard whether they caught a cable or not (they did of course). There is no decision time for a full throttle calamity, so it appears they build the cables capable to stop the aircraft when at full throttle, and when a cable snaps (or a hook brakes? does that ever happen? or whatever), that's how the pilot has the chance to escape.

Did you successfully land? seems a bit much, your A/P was Off? (with "A" not only mode Off) your ATC was Off? (with "A" no blinking 'ATC' in the HUD) ?

I trim very little I wait for the FCS to catch up and let it do the trimming. It way easier. Landing speed is just above stall speed, and this F18 drops like a brick from the air when only a couple of knots from the stall speed. When dropping in altitude because of not concentrated on the speed for that millisecond, I just pulse quite a lot of throttle to see the speed rise into the safe zone and immediately throttle back to not overshoot the speed. You have to be really quit and very focused about the necessity to very quickly recover the planes positioning with the throttle. It is true what the manual and tutorials say, you fly the F18 in primarily with the throttle.

Finally figured out where the 'ball' is (simply search google images) Actually, had lots of trouble landing quick mission 'Case I carrier landing' hitting the stern every time. Then I though 'why not not think about it and land like a 'kick it down' Beech Baron 58 emergency landing' that I used to do all the time testing FSX settings .. and Boom, on the deck 2nd cable.

Indeed, at least that is my experience, but 'weak' or 'strong' in this case has more to do with Video RAM and the IO speed. Texture Filtering Quality simply renders smaller bitmap sizes (which are blurrier) and when the stutters disappear it has to do with less RAM IO speeds mostly, or just less RAM (or the simpler architecture). This is what I noticed as the difference between DCS 1.5 and 2.5, DCS 2.5 behaves a lot like the old FSX and now P3Dv3 (32bits) where 12 FPS or 20 FPS and stutters were quite 'normal' ... and indeed this has to do with graphics engine and code optimization, but are exactly the hardest part of game development. If only that was simple.

If you want to test if your card is the source of stutters, in Nvidia Inspector you set Texture filtering - Quality from 'Quality' to 'Performance' you're screen will be less optimized through less size bitmaps if the stutters go away it's (mostly) your cards capabilities (bus width and speed, versus IO)

For NWS HI there are two commands to consider, that are combined with the same switch(es), autopilot engage/ON ("A", the stage before the mode select) when in the air, and “S” Undesignate Target Rader Lock when in the air, and Nose Wheel Steer Switch when rolling, which engages HI when held (and just tap for short radius burst when in taxi). "A" Autopilot/Nosewheel Steering Disengage (Paddle) Switch /Stick; HOTAS "S" Undesignate (in air radar target unlock)/ Nose Wheel Steer Switch (hold/tap for HI on the deck) / bound to the bottom of the Stick; HOTAS, next to the above mentioned Paddle) When NWS on the deck, where NWS shows on the HUD when engaged ("A" disengages and you'll roll on your engine and your rudder), you 'tap' or 'tap long' (HOLD) the NWS stick button for HI sharp radius corner, do Not have Maxed rudder steering, for the HI state will then not be engaged, you should have 'some' nosewheel rudder left or right, then tap or tap-hold the NWS pinky switch which will then shorten your turn radius for the duration of the HI Hold tap. At landing the NWS automatically comes on when wheels are weighed and this shows in the HUD. What I do on airfields I Disengage NWS with “S” when in line with runway and steer with aircraft speed momentum and rudder, and tap switch to engage NWS back on again with "S" when below 70-50 knots (like a civil aircraft or the Warthog A10) until the taxi speed crawl and then as needed to maneuver to exit, tap "S" or tap-hold to tap HI state as necessity demands, NOT at maxed rudder for HI won't engage. NWS HI will show in the HUD.

Haven't seen anything, I think you just fly the desired speed and the HUD speed will be the target speed, if you want to change this I just move the throttle (flashing ATC in HUD) reach desired new speed and engage "T" again (ATC in HUD steady)

Without a rudder axis you would probably simply take a dozen yards to roll slowly forward so you get a feel to where to point the aircraft to the end of the runway, and at that point you engage take-off throttle and disable NWS with the disengage "A" somewhere not too far above 60 knots, which means you're heading for rotate with rudders only ...

What I do is install "Nvidia Inspector" here f.i. http://www.guru3d.com/files-details/nvidia-inspector-download.html part of it is “Nvidia Profile Inspector” (direct in install dir or menu button) that gets you to the special NVIDIA game settings see my setup screen notice: 3. anti alias - .. ‘overide’ - .. ‘************* SUPERVCAA_64X_8v8 (or use less resources ‘ **** SUPERVCAA_64X_4v12, these are NVIDIA proprietary AA) - MultiSamp ‘off’ - Supersamp ‘off’ - FXAA ’ON’ ( <<<<<<<<<) 4. TexFiltering - ‘user’ all optimizations ‘off’ (can turn on, little recourses, less pretty) - ‘8x’ (or 4x or 16x) - LOD BIAS ‘clamp’ (pretty) (or ‘allow’ shaky, faster’ Basic idea: - 'override in game settings' - use NVIDIA proprietary AA **SUPERVCAA_** - Sampling OFF - FXAA ON