majapahit

How about FA-18C wings fold/unfold?

After a certain amount of self-training, you can trim whilst banking towards on-speed, and certain RL YT carrier patterns show the pilot doing that. A '3-second pull the thumb' can work, but could actually be very wrong also (because the FCS is trimming all the time in banking G's). Because you know your ballpark weight and thus know the ballpark of your 'on speed', by carefully observing the movement of the bracket dancing around the VV (and also keeping an eye on the actual nose AOA 'W') whilst banking in the turn, and you actually trimming, you can figure out what the on speed of-the-day is and be right on the dot.

pfffffffffff The only ones not obligated to save any face about a DCS game that can only depict a bleak picture of what is really going on, are types perhaps like our DCS guest star pilot C.W. Lemoine who then again succinctly pointed out that real operational guns are not allowed on public fora like this, thus their opinions, if they have one, never heard, or like him, are rewarded with a very cold shoulder indeed by ‘the clan’, meaning ending their active flying career if found doing that (to even his surprise apparently). Any type of the blowhard that are left who think they might impose on us here a vicarious spec of military stardust referencing towards some vague clan relationship through erroneous vernacular, can be served a saucer of lukewarm milk for his trouble, for that’s their ranking scale I would think. BTW a USA military that insists on having a DCS employee arrested abroad, in Georgia - the nation in the Caucasus - and have him then odiously renditioned to a federal jail in Utah for having obtained old American flight manuals, because he is ‘Russian’, somehow that does ring the bell of the pussy as well. Isn’t it.

If in CQ anyone cocky enough to try, and performs a rather haphazard SHB, the Air Boss will say something, or otherwise the real boss, no doubt, and land based will welcome you on your next flight out. It's akin social darwinism in a self inflicted pecking order, for which the US military apparently attempts to be a sample of. If you don't have a taste for that, I have a saucer with luke warm milk here to comfort your thin self reflections.

'We' did not, did you now. So why say that, I'd say, SHB is not allowed 'in general', is it now, its not NATOPs, on a carrier, it's still performed though, is it now, on land side I'd call it a military landing. What do you think you're doing (not a SHB).

Grab an english language course book .. might help

Err, this I cannot quite see working, no locking - using 9M. I did do a DCS repair.

Nope its not a Case I landing, it's the renowned "It’s a Navy thing. More, it’s a CV thing, ‘CV’ being the code for carrier, the kind of carrier that has cross-deck pendants and planes with hooks. The Sh!t Hot Break: if you know what it is, you’re smiling already." " .. Nasty perfected the SHB. Distilled it and repeated it with maddening regularity. His signature maneuver was to approach the Boat at 600 knots and 600 feet. Not all that unusual in and of itself, but Nasty would bring his section of F-14s in 30 degrees inside the wake so that he would have more than 180 degrees to slow down... " dumb ass ignoramus.

indeed, an updated set of codes and settings for all of them in a big list

HMD not used. ok that seems to be the problem, HDM is working but apparently not VACQ vertical bore sight, that's no biggy 9M works with HDM or only 9X?

Perhaps I'm confusing my aircraft types but, I just did couple of runs with FA-18C and VACQ vertical bore sight doesn't seem to be working? This worked before didn't it? 2.5.5.32299 @openbeta

I always try to perform a 'military landing', whether an adjusted F18 one for practice like this: takeoff from deck flapsUp GearUp 180° @600ft@~250-300kts reaching abeam gearDWN hard bank base into final brake by pitching Flaps Full are down @ 90° estimate/calculate ‘on speed’ by examining trimming bracket past 45° final be at 170kts, cut throttle level off @320-350ft 'on speed' short final @132-135kts, on the ILS if On catch 3 wire Or, the documented actual one (flown in F14 by flight leader only, but here in F18C) 5NM@5000ft@550-650kts@30°CW left of ship heading 30° of Stennis sails N fast speed decent 'to the LSO position' @600-1000ft, @580-650kts over the LSO hard left bank pull as much G's as 1% of speed (650 slowing down to ~350kts) end up 30° wide (250°, if Stennis heading N)@~1.5/2nm TCN never level off in the whole pattern speedbreak only if miscalculated, you should do without @~350kts abeam (still wide) start the measured circling with less bank, into to final lower gear@280kts 1st flaps passing 220kts full flaps passing 185kts passing 90°-45° 'trim on speed' bracket catch 3 wire (Dotted down by memory, not tested line-by-line) Not mentioned in NATOPS NATOPS is for pussies.

From the spot you were stopped after catching the wire, one can do a very unofficial 'afterburner-full-brakes-full flaps' take off, and make it over the water. For when you're in a reaaaaallllll need and do countless go-arounds practicing lots of landings. It's nowhere near real of course.

Did you switch VR "ON" in the options right most tab ["enable"] = true, Your Oculus Home needs to be running or Rename/backup/delete your \Saved Games\DCS <version>\ folder. You want a backup or KEEP if there are clever bindings in your "..:\Saved Games\DCS\Config\Input" DCS will build a a new one, in particular the "..:\Saved Games\DCS\Config\options.lua" file Then switch the 'enable VR' on in the VR tab and see what happens. After that you need a lot of tweaking to get the vision right, the latest Nvidia driver in the 3D default games settings has 2 options now, the SS 2x 2.25x 3x 4x and a 'sharpness slider' that's the easiest now to fine tune in combination with the DCS options.

Rethinking this you might be right, there might be a bug in 'unrealistic' mode, not all setups, not all the time, or DCS would not have released it, but for now, in cases with setups like yours, if you want to use the -F you have to figure out a setup that will use depress, for that seems to work right now, not for all setups, not all the time. Mine works fine.

I'm not seeing anything unusual. It locks perfectly well on trees that have proper contrast points, it jumps when you're *not* aiming at specific contrast points or holding it steady on surfaces, surfaces which you have to fly into. I also miss your VV cross, and I assume you're way out of bounds anyway.

I'm not quite sure what is 'not working'. Releasing the depress, the cross will go in search mode, which you are pointing at grass and 'somewhere' in villages the camera recognition mode goes on weekend leave. Also the big +, which is the VV, is quite a lot from center, which pulls the 'cross search mode' hard to the right. You better, when at a measured distance 'fly' the cross on the target, so one just pickles the depress, and buildings you have to keep the cross steady on a building's even flat surface. That's how I have no problem working with the F.

We want different Axis Tune settings for MAV and ATTCK Radar AND perhaps different setting even still for MAV FOV zoomed in and out people who cannot lock, did u chk your TV screen is Active (sensor diamond)

I am confused, is this Motion Reprojection mod for the Rift also, or not?

Just checked my DCS, was ON in options, never seen it anywhere .. ?

I looked in the DCS-BIOS :\Saved Games\DCS\Scripts\DCS-BIOS\lib\FA-18C_hornet.lua and tried "STROBE_SW" with the A/T switch as per the output APLAT+ APLAT- ; MCP Switches APLAT+ = STROBE_SW 1 APLAT- = STROBE_SW 0 but get VRi ID : 0 VRi Unit : FMER VRi Button : APLAT- DCS Key : NotUsed VRi ID : 0 VRi Unit : FMER VRi Button : APLAT+ DCS Key : NotUsed

Problem Connected everything, installed DCS-BIOS in the :\Saved Games\DCS\Scripts folder renamed keys - CDU2_MCP2B.ini to keys.ini changed 'MCP2B = COM13' to 'MCP2B = COM3' commented out / deleted ;CDU2 = COM8 etc Run Vri2DCS.exe Start DCS Start FA-18C Rotate BORA/HDG/CRS but Vri2DCS.exe output says: VRi ID : 0 VRi Unit : FMER VRi Button : HDG344- DCS Key : NotUsed VRi ID : 0 VRi Unit : FMER VRi Button : HDG345+ DCS Key : NotUsed VRi ID : 0 VRi Unit : FMER VRi Button : HDG346+ DCS Key : NotUsed VRi ID : 0 VRi Unit : FMER VRi Button : HDG347+ DCS Key : NotUsed same with BARO and CRS rotary “DCS Key : NotUsed”? perhaps is meant for A10C? perhaps "VRi ID : 0" is an error? How do I get FA-18C to work? What are the "DCS Key :" syntaxes/how do I find them? what do I need to do? THX

I just discovered your VRi2DCSBIOS. I have an original MCP Combo, installed VRi2DCSBIOS and it says Creating Socket... socket succeeded: 336 Begin searching for VRinsight Units... 1-VRi Unit(s) fould! Unit 0: FMER 2.520 \\.\COM3 Ready... GREAT looked at your <keys - CDU2_MCP2B.ini> and see you got the encoders to work for DCS CRS/HDG and I wonder how did you come up with the name list of variables/designators, and can also MPCombo buttons be translated into DCS actions? Will the [MCP2B] section work with the original MPCombi v1? What is the syntax for all of this, like gear up/down, landing lights, and is there any chance to get the radio part to work (prob not) ? THX

try and see

You have to tinker with the DCS settings options, Also, the new NVidia drivers have "DSR factors" in the Global settings. I fly MP air battles, I cannot have 'pretty VR' I need a fast VR. "DSR smoothness" is the trade off between pretty and slow and an 'aliased' image, mine is set to 10%. In DCS, no aliasing, but SSAA x2 (which is DCS superampling) ["MSAA"] = 0, ["SSAA"] = 2, ["SSAO"] = 0, ["anisotropy"] = 0, in DCS VR options I have ["pixel_density"] = 1.5, which actually is also related to supersampling. Some settings only have effect on the 2D image, not the actual Rift VR image, figure that out yourself. You muck around with all these settings, to start with these days the "DSR smoothness" in the driver is the easiest setting to find/compare quick and dirty results. To find your personal optimum takes a horribly long time (very). I get 45fps with a 8600K and GTX 1080, but this can drop down to your 22 fps sometimes in heavy MP settings. Your major criteria is total image smoothness of any head movement, not how pretty or ugly it looks. Changing certain settings higher or lower, do not make any sense with any outcome in the result, which is why it can take so long.