majapahit

great news, thx

Slewing the maverick TV (by button, axis) too imprecise? Trying the new TV Mavericks, great fun, now we’re talking. But, slewing the maverick TV (by button, axis) seems too imprecise? The slewing by a designated button hold/repeat is too fast, perhaps needs an accelerator, and be slow at the start for small movements. Binding to a joystick HAT axis (Logitek G940) produces rather haphazard movements. Or am I missing something? Anyone tried these and can lock 65 missiles somewhat with ease (as in quickly and with some precision)?

Here too, first time I put on my VR I thought 'oh my god what the hell is this' out of focus, blurry, washed colors, cross eyed, its like looking through the bottom of milk bottles, horrible. After a couple of hours adjusting, and figuring out what pixel upgrading is, you start to see the 3D advantages, the 3D situational awareness of VR. Then, when you actually figured out how to create somewhat of a sharpish 3D picture, you find out how much easier and 'real' your CASE I II III carrier landings are (and helicopter flight), for now you actually know where you are and can glance quickly 'everywhere' to anticipate your next moves. Then, never mind the 'blurry' view, you never go back to 2D. P.S. (I removed the foam rim and holder of my Oculus Rift, getting my eyes closer to the screen - with some spacing foam, for my eye lashes were now hitting the lenses - great improvement, if your eyes are towards or over 7 cm separation) N.B. DCS, the IL-2 recent VR versions and Car racing sims are the ONLY software games that make VR worthwhile, and very much so, which is why there are problems scaling the user base, me thinks.

settings in "<drive>:<documents>\Saved Games\DCS\Config\options.lua" .. ["graphics"] = { .. ["multiMonitorSetup"] = "<your selection>", ; << default is "1Camera.lua" ["height"] = 1080, ["width"] = 1920, ["aspect"] = 1.7777777777778, ..

Why are you even asking?

<HIPPO> changes flaps setting, prob a bad idea, also prob, you can only spool up to 'on speed' for that trim, when you reach that, your gear and flaps need to be raised, or attack the sun.

Well, ask you money back then.

" I touch down, set flap to half, full military power " You're outside coded protocol, F18 is in beta. I suggest, either you're heavy and land full flaps and power up full flaps, or you're light and land half flaps and power up half flaps, or when power up when pitching up, you either power down quick till proper ascend pitch, keep it there (FCS will be stuck on certain number), and proceed, then asap gear up flap up when gained safe height, or always as soon you notice uncontrollable pitching (rather anticipate) gear up flaps up. The problem lies in the FCS. Ascend zero pitch is managed by FCS that needs gear up and flaps up, or, when changing to half flaps during a touch and go you need your UFC page on the display and adjust manual pitch [sTAB] ~12-16 for FCS take off. You shouldnt change flaps in a controlled touch and go with the present FCS for the FCS seems not to know it your landing or do a go around (and perhaps that's RL, dont know). 2cts

Nope, nothing wrong, just dont do that.

Screenshots look bloody marvelous. THX

There was a problem with the TrackIR so he had to mess around with a mouse view, seems to be the real distraction, plus I'd say, someone who knows FA-18 keyboard commands should have had the keyboard in hand and he would than just jell out commands I'd say. (better still put a VR on his head, but then, in particular and specifically, you need someone to pound in keyboard commands or something such)

This

As is implied in your own post, the crucial element of base turn merging into the groove is speed, thus is your throttle hand, thus is how quick and precise your throttle hand is in executing the planned flight path. Managing and anticipating the speed is by rather fast jerking the throttles, by relative Big initial movement of correcting up or down, but then watching very carefully (together with all the other stuff) when your speed reaches the planned anticipated speed and then slowly 'rolling' into your planned speed, thus your throttle hand slowing down, you're now 'oscillating' your throttle hand around the 'on speed' which you're now - also - 'determinating' for the exact number, and in the back of your mind the consideration of the spooling up and spooling down of your massive engine. The 'window' of 'on speed' is but a couple of knots, spool under and you drop like a brick, spool over and you'll do 160 kts all of a sudden (or worse I can remember when starting to train, mind you the final turn in might be a 'high' of 170-180kts or more when heavy, depending on correcting your altitude when catching the ICLS groove), where you'll simply blow yourself off away from the deck. (Of the cuff, if (ideal) 'on speed' settled and descending in the groove would be for instance ~134kts in a given fuel load, configuration load, temp etc and which final number you determine because of the movements of your aircraft, 128ktn drops you like a brick and passing 138ktn blows you out of the groove, which makes your speed 'correction window' about from 131-137kts you'll have to stay in when maneuvering yourself onto the deck, whilst, while you're at it, meanwhile also determining that precise 'on speed' number of the day going down, which is quite the handy number for a smooth trapping) So, whilst keeping your eyes on the VV, or rather watching through the VV and steering your plane to the upper right quadrant of the landing deck (this is with ICLS ON and flying VR, it's very hard to see the ball, but do not follow the needles if your ship is bouncing, you fly in-between-the-bouncing-needles), you continually keep an(other) eye on the speedbox and in particular the 'rate-of-change' in the speedbox, where, because of the anticipation aspect, the 'rate-of-change-of-the-speed' in the speedbox, within the 'on speed margin' that is, is more important than 'the-speed-of-the-moment' shown. And indeed, you train yourself to get used to the massive amount of information you have to process when you're passing 90 in the base leg, and then you catch wire #3. 2 cts

Looks like it - his latest demo of mav - G

it's exactly that, as f.i. Wags explained in his tutorial

You're in error about your view. I you think you're high enough and explode then you're not aware - enough - of the length of the FA-18 behind you seat, when you think to see you don't have runway enough, that's comparing your view with a land based runway, and you're not considering the brake wires that decimate your necessary runway length.

Its a peculiar indeed, no keyboard command, I just also have it bound to a (shifted) button. I guess most people do this likewise or use the mouse, because else how are you going to hook up?

I have no recent experience of bolters (I smash on the wire if need be), but I can remember there was an issue with 'wheels stick to the deck in a bolter' many moons ago, which was fixed. You point to something here, which can be circumvented by taking back throttle until the plane 'behaves' (and/or simply raise gear and flaps and at alt lower them again at abeam bank is what I did when training) as I can vaguely remember, but I'd say ED knows by now all that needs to be looked at, I'd guess it's just a matter of time and resources (and it ain't easy I bet, which is a problem).

What about the non-librarian 'the climb out is flown by smashing the throttles forward until it stops .. ' after which you ease the throttles for banking speed and so forth .. You're describing a bolter or training here that stays full dirty, and would - maybe - make sense in an immediate go-around. I wonder if that's the rule or the exception. I'd say it's safer to just throttle away from the deck, military or afterburner, gears up flaps up into the 'did not trap' procedure of the day, and then get new permission to approach? I think that's what I read about bolters (unless this is training without regular traffic?).

Exactly Fly your DCS F-18 Beta release according to what works for now and which is frighteningly similar (pun intended) to real life, and have the coders add ACLS landing capability (my second choice), air-to-ground MK missiles and a TGP screen (would be my first choice), but who am I. Just another guy enjoying himself with a joystick and a screen. Don't bother trying to fly outside the available envelope, since you have to factor time and resources, though no one can stop you and report this, but going on and on about this why would you do that? Why is grass green? Why is it raining and no taxi cab will stop for you? Why did you forget your dentist appointment and now you're miserable? Why?

You seem to confuse, 'I like to fly this thing my way', with 'This thing flies as it is programmed to replicate the actual thing' Why do you do that? What has F-18 done to you?

Most likely because your wheels are not fully up and locked yet, and after which you still need an instance for the FCS to kick in correctly. With you wheels down, the FCS will (might) think you're stalling (until above 200 kts or so) and thus FCS will drive the nose up for it doesn't know you're taking off, for you're in a wrong configuration. After launch I always back the throttle for in instance, no nose up, then 100% throttle or whatever is planned for ascent, meanwhile wheels lock (flaps lock), FCS kicks in, flight continues 'normal'. No idea if this is RL, but it works (and makes some sense).

There are still some weird bugs in F-18, and you can report this in the bugs section. I have no doubt ED is quite aware of this. Landing and take-off parts of flight modeling are likely put in separate coding bubbles, and either they can go expand on that, or, in the mean time, they cannot. Staying within the parameters of the coding, i.e. staying within the limits of what is possible, keeps you within the parameters of the simulation 'as is'.

This who do not have their CILS turned on, you really should, then you know where you are.

The FCS does