majapahit

not talking to you your comment appreciated

I'd say its your controller calibration or you're unaware of a duplication axis defined by a random controller?

another not a biggy After I land Go Around Stennis, wingman parks on the lift at the starboard stern, parked but floating and oscillating up and down, after a while moves down, which is a nice touch haven't actually seen this yet, but then weirdly is one deck down, tail sticking out the side. You probably want this addressed at some future point in time - (wingman when landed when yourself parked next to landing strip, when in his taxi path, will slowly but surely will run you through)

I made the middle one disappear so I can have a peak at the deck in the distance when I'm not sure my angle of intercept. Have it on a button (I need glasses but flying VR without).

Ah, that's the explanation, always was under the impressing the manuals were describing a bouncing of the hook on the deck if landing on the deck with a wrong alpha. Tss. This explains things way different by the way, for me. As a matter of fact I was already wondering why I could catch the wire by cutting throttle, if need be, drop like a brick, and trap succesful ... :) , I just thought I had found myself a loophole, pfffff .. Then, when prepping to land and you have a hook light this could indicate some sort of hook failure .. (if DCS .. )

Was checking the visuals of the no3-wire on the Stenis, i.c. by the way is the big antenna cum radar structure ahead of the bridge island.

" .. the reason you get a red hook light with the hook down on deck is because the hook doesn’t match handle position; it can’t fully extend on deck. This ensures you can snag a wire ashore during an aborted takeoff. .. " I have no idea what you're saying here?

Wonder then why anyone would put in the effort to explain 'critical alpha' by actually making a kind of a CAD drawing showing the hook off and above the plane of wheels touching point. I'll see if I can find the image and figure out what the idea behind that was. This is stupid. (But thanks for the info)

Taxi on the deck with hook down catches wire .. ? That's not supposed to happen? Or is it. Thought hook with 3 wheels on the deck floats ~1/2 foot above deck? (Remember to have seen a drawing of that somewhere, to explain critical α )

That's downgrading your first plan quite a bit, getting careful? Which is a good notion, for DCS F18 is Hard To Fly. The #1 one thing to achieve by yourself is being able to do pattern landings on the Carrier. You master this by taking as an example the Youtubes of Wags and his likes and comparing this with the CASE 1 pattern images. The short version is this. - Take Off (when you have figured out how to do this) (and afterward know how to taxi around and find the catapult at the exact right spot, which you mentally mark and recognize from the visual clues) - left bank steep 30, ease on the throttle HARD, restore throttle HARD to make a smooth bank up (you 'anticipate' the speed ribbon read out) - raise hook, gear and flaps so Flight Control System (FCS) takes over - do Not enter a steep climb, ascend only to 600 (this is hard enough) - level at 600ft (this is hard enough) and be 180° on the downwind leg (which is hard enough) - be around 170kts, not over 250kts, the speed steady to fly and ready to down half flaps and gear (and FCS in flight mode) - when your TACAN in the HUD shows around 1.3 nm (which arrives really fast), on your left there’s the top of the ICLS glideslope @ 600ft which is your target - be stable, be ready, gear down half flaps left bank turn (OR trim to landing configuration, full flaps gear down TRIM, and be and assess “ON SPEED”, you’ll pass DME 1.3 be aware this extends your pattern) - LEVEL bank left, turn towards your target ICLS DME 1.3nm intercept extending 9° CCW of the carrier heading (you have to raise speed above “ON SPEED” to compensate bank, this is really hard, less hard with a VR system) - full flaps, measured TRIM keep LEVEL @ 600ft (this is really hard) - half way check your position, you’re in a steep bank and you’re working the throttle also, you have to decide the end of the turn, keep assessing turn rate, bank, speed, position - level out whilst slowing down to level ‘ON SPEED ’ on top of your target ICLS intercept @ 600ft (128-137kts depending your weight and is a very precise speed, this is really hard) - intercept the glide slope, follow down, trap the 3 wire by WATCHING THE BALL (a good idea might be, is to taxi with your hook afore the no.3-wire on the deck and assess the view out the cockpit) Do this roundabout and touch and go-arounds 100+, 200-300 times so you can do this little short circuit with your eyes closed. Then join the squadron of you wishes and fly actual patterns (personally I lack the time but would be great fun).

My TMWH script diabled the Joystick, turns out it was a Windows Joystick #ID that collided. You checked if the script loads with either GUI or scripteditor and your joysticks still working? TM just released a 2018 updated driver (because of their rudder) Or just assign inside DCS, way easier for a newbie.

remove the .TXT extension, has couple of added commands for AP button "TCN" "ILS" "1" etc. but you only need translation I guess and it's easy to see in your setup. Keyboard.html.TXT

RTB on the deck, parked, wingman after trap runs into me Not a biggy but my wingman does not see me parked on the deck

then perhaps it still could be the recent Oculus update (which I still have to figure out how to check) of which my Windows 'programs and features' now tells me it's version "<3", how about that .....

Not really, I forgot to mention, just should have waited for the 'background Oculus auto update' should have finished I suppose (look in the Oculus 'notification', but won't say when finished :( ) . My guess is. BUT meanwhile I deleted my .\Program Files (x86)\Steam" dir (because I am an impatient lad) If you have Steam + VR installed BUT for the " . :\Program Files (x86)\Steam\steamapps" were your games are in (or download the GB's of games again) and reinstalled Steam, reinstalled Steam VR. Deleting my .\Program Files (x86)\Steam" was a bit too drastic, forgot what exactly (some settings I suppose), but you might want to search for a better way to an enforced re-install of Steam. I think Oculus fcuked its own install (when also Steam installed in my case, cannot distinguish which was the real culprit) All Does work again though, my updated DCS no glitches now.

I rolled back and then updated again. I think it really was the Oculus 'necessary' update that fcuked the DCS VR install.

I wanted to post 'all is well here' then my DCS VR started crashing, oops. reverted to previous version, equally a lot of trouble, mission not loading, then I saw the Oculus notice 'Oculus could not do a necessary update, restart computer and try again'. Which I did, same still. Wait an hour (can't see how update is doing) DCS working again, updating DCS again, now working (yesterdays update has a tad better FPS also, but I think it is missing labels?). Anyway, might be your Oculus install messing with automatic updates.

You think JSGME could merge downloaded files into zip containers? Don't think so. (In the olden days 1.5.x Mustang mods I think to remember were the whole containers, but the more popular this gets the more MB download his file server gets to move over the internet, is prob the problem) BUT a solution for a while would be just instructions to merge the mod files

I don't ever have problems (knock on wood), I have 'easy communications' checked in the options, no dialing. I fly my training missions in Dusk and Dawn, where at summer dawn, 7.44u or something, it is clear as day, as soon as I communicate with Stennis the lights go on. If I bolter or touch and go, the lights switch off, I enter the pattern, contact the carrier ATC again, lights switch on again, which makes finding the groove easier (the angle), even when I can see the carrier clearly at a distance.

I've discovered said image with the Go Around is extracted from the official NATOPS manual. So the error or perhaps omission concerning the base leg isn't your problem, its an 'official' problem in the manual, though pretty clear.

Nope. Never mind facts, just dream on.

If you read 1 post above yours, I already mentioned upped my mission with no problem, perhaps DCS fixed my problems somewhere. By the way you're flying with your eyes, I see no ICLS on, ... landing is good though. You should uncage your HUD when lined up with the deck so you have reference to what you're doing. (I can fly cessna's like this on FSX how you're flying)

(I did the math on the windows calculator)

Happened to me, high wind, ballooning over the deck. Only happens infrequently. Ah well. (Perhaps its a freak turbulence modelling)

Have a look at some R|L videos or ask a pilot if they're allowed to dump their external tanks, which they're not, because you can watch them landing on the carrier with them (x2, as I did). Try it one more time perhaps, or try a desk job?