All Activity

Aha! No I didn’t realize that. Thanks

You know when I say “still the best?” it’s somewhat in humor. It’s a device from the 90s. But it serves the purpose. And there wasn’t a 12 week back order. One day I’ll get up the motivation to replace these but I’m not in the mood for mass button mapping right now. Fun discovery, when you get another of the same device the ID# stays the same. Plug in and game on.

Alright, I think I got this one and can help you... So you need to drop the gear, wait for them to down-lock, before dropping the flaps. If you take another look, you can see you put in full 50 deg flaps and were somewhere around 120-140 knots (my short term memory already forgot the speed I just witnessed moments ago). The flaps couldn't push their way down into the airflow and were stuck at maybe 20-30 degrees by the look of it. The flaps were in their "blow back up" state, which means the hydraulic valve was still stuck open, trying to feed more hyd oil to the flap actuators. All of your hydraulic pressure was consumed for this task and not enough oil flow and pressure was diverted to the landing gear. It's apparent you are not flying with a checklist because you missed a few other things as well. These were not related to the landing gear issue: Fuel tank selector needs to be on reserve, and mixture full rich for landings. The checklist also calls for gear first, then hook, then flaps after slowing to 100-110 knots. Have a look at some official checklists and follow them exactly until you get the hang of things, and then continue to use checklists before you find out that complacency kills. If you'd like, search for my Corsair checklists which I have uploaded in this forum, as well as the user files section. Install them, and make sure you wear out the Shift+K keys on your keyboard. I collected the info from game manuals, old 1940's training videos, and the actual POH, and compiled the info together. I've been flying my Corsair per these lists and don't really ever have any issues with the Corsair, knock on wood! Anyway, I think you'll be good from now on. Track files for the win! Send more any time Cheers, -GT-

you may have found the answer already. If you set the alt to 0 it will auto populate to the ground alt. It is a bit annoying to have to do it manually but its better than nothing

I answered in the other thread you made: Please don't make duplicate threads.

I believe it's not unheard of to hit on a PGM 3, and I think that's the lowest threshold which a HARM launch is considered 'feasible' to hit the target, but obviously if you can a higher precision value, go with that, and PGM 2 will be more on the money than PGM 3, but my recollection is that PGM 3 represents sort of the 'maximum sized basket' in which you could sling the missile and have no expectation to just straight up miss.

Hey there, ‘’I’m trying to figure out if it’s possible to program a button box for the CTLD menu? I’d like to press 1 button and have say 1 Abrams tank crate appear in front of the Chinook. Is this possible to do with a button box? To get to the tank crate I have to select the comms menus, then, CTLD, other, ground, heavy machine, then whichever tank I want. I hate losing the mouse on the screen. is this a simple or doable task? I’ve been told that it is doable, but you need to buy vioce command or other programs. thanks

Analoge Uhr (Ziffernblatt) nicht, aber eine im IFEI unten rechts und mit TIMEUFC unten auf der HSI Page kann man eine im HUD einblenden lassen.

Here's the track in question. F4U - 04 - Carrier Landing one gear down.trk All the shakiness in the track didn't seem apparent to me during the actual flight. I did notice difficulty in turning the plane though.

And you can do it after you start the plane, but it does need to be changed on the ground with the ground crew REARM/REFUEL menu

Can you also comment as to when this exactly started happening. Has this just been a problem in the last few days, but was always fine before that? Any PC system updates, or Quest firmware updates (there are known issues with disconnections on the latest firmware when using 3rd party link cables).

Не нужно жалеть. Это ваше мнение и оно имеет право на существование. Другой вопрос, что многие на этом форуме, в пылу спора, переходят на личности и это, по моему мнению, недопустимо. Хорошо, допустим, ВМС эксплуатировали, вероятно уже ближе к концу службы, F-14-е с такими "убитыми" кабинами. Я, даже, готов поверить что окружающая среда не повлияла на состояние кабинета с 2006 года до момента оцифровки её Хитблюрами. Но, это не исключает того, что данный борт, в процессе эксплуатации, имел кабину разной степени изношенности, от новой, до нынешней "говнообразной". Хитблюров устроил вариант крайней степени износа по, для меня, понятным причинам. Я согласен, что такой "ушатанный" вид это тоже реалистично, но когда вижу кабины от ED, Миг-29А или Су-25 (на выше показанных скринах), которые, тоже, не вчера были приняты на вооружение заметим, меня охватывает печаль, ведь F-14 один из моих самых любимых аппаратов.

I am trying to make a simple test of an AI Tu-22M takeoff attack a ship and land. I can make the attack happen with an air start but when you add a landing/takeoff task - the aircraft won't attack. Any ideas?

Just a heads-up for folk that DCS has native support for this now so no need for NVPI to achieve this, unless you're wanting to apply to all your games. DCS also allows you to not use DLSS on MFD's and the HUD, which is where some of the larger complaints were around the ghosting on those when moving cursors etc. Just add the below to your Saved Games\DCS\Config\autoexec.cfg file (create it if it doesn't exist). DLSS_Preset = 'K' HUD_MFD_after_DLSS = true

I don't mind it when someone makes an informed decision to get something that I wouldn't suggest, but I don't like it when claims get made that are not true. In particular because it can cause other people to make decisions based on incorrect info.

I think that is the seapower the models are in that game, and they have been making videos about it

Still is strange. Upload the track anyway. I’ll ignore the visual display. I’m curious to see the flight parameters because I have still not experienced this, and would like to see if there’s anything I can learn to avoid it, and of course share with you.

My wingman and I had been flying a particular mission for the last couple of weeks in my dedicated server. Until yesterday we both had excellent performances. Today, however, with no changes to my PC (DCS client), the mission or the dedicate server , my performance tanked while my wingman's remained unchanged... My dedicated server is in my LAN, 1ms ping, my wingman connects from the outside of my LAN. My SP performance is excellent but when I connect to any mission in my server , I get a slide show. I'm at a lost at the moment on how to approach the situation since I don't want to have a kneejerk reaction and changes configurations anywhere but ran out if ideas on how to troubleshot. Performance drop is apparent right at the start, in the join coalition screen, regardless of the complexity of the mission... Both machines were rebooted a couple of times each... I don't see any connectivity issue in my LAN... No windows update in the client or server, no driver changes and no AV software changes either. So, please, if you have an idea on what to look at, share it...

My experience was I did a crash and burn on a practice trap. Looked at the track replay and saw for some reason the starboard gear was not down and wondered what I did wrong during the approach. Then I remembered that my landing did not have a wing down skid when I was smacking into the island Went and hit fly again and this time I missed the wires and plowed into the static planes on the bow with no dragging wing. Looked at the track and one gear was not down. Another try same end result but during the down wind went F2 after gear down and all were down. Reviewed the track and video showed one up. Went to exit program, re- entered and could not reproduce. Second and third time I also double checked the gear indicators were all showing down. No reflection on anyone else’s procedures or flights. Only saying I believe my gear was down and locked but track was not capturing the whole picture. seabat

In addition to Esac info above, refer to the manual for laser bombs deployment beginning at page 321.

I do ... practice them a lot on training first ... what's the point of having an accurate simulation if then we go and pilot the aircraft like it were a car?

The LGB bombs should be coded before starting the plane on the ground. Use the Ground crew menu, code the laser number for every weapon and press OK. Then wait for rearm to the new code be transfered to the bomb and start up the Hornet. Change the laser code on the ATFLIR and done. Bombs codes cant be changed in flight, default is always 1688.

I am flying in Afghanistan the only code that works with the ATFLIR on the left cheek is 1688. Any other code the rounds (500lb LGB) are impacting about 100 meters off the target. The only other laser codes I've tried so far are 1686 and 1687, both are a no go. A friend and I also tried to buddy lase for one another with 1686 and 1687 and same issue, rounds impact off the target. I placed a JTAC on the ground lasing targets with 1686 and the LST won't even pick up the laser. Haven't tried the JTAC on 1688 yet, but will here soon. So far the only code that works in Afghanistan is 1688. Haven't tried any other maps yet either so I cannot speak to those. Thanks!

I know this sounds pretty strange, but I had another instance of one gear not coming down. The plane didn't fly normally again, with one wing wanting to dip. I verified only one gear down on the F2 view. I raised the gear & lowered them again, but one gear still didn't come down. I was all set to send this track . When I watched the track though, it showed both gear extended. I wish I had taken another screen shot at the time so it doesn't look like I'm nuts. I did get a chance to check the hydraulic pressure this time though & it was normal.