viper2097

A few days ago, we had a sortie wich also included aerial refueling. I captured it on video and thought that I could show it to you. I did that with wings in Auto and a KC-135MPRS which was flying a circle pattern. The key to success on aerial refueling with the Tomcat is to follow the rules: Fly in formation with the tanker until your are trimmed hands free. Do it slow, don't hesitate and don't get into osscilation with the stick. Set the tanker to cruise around 250kts IAS. Use this link: Or jump here to 2:15: n0CjS15bdhM I still don't know why there are so many wrong informations and fairy tales about the wingsweep: The F-14 have NEVER been refueld with wings in bomb mode. NEVER. New IRL turkey drivers have been advised to refuel with wings in 40°. Bomb mode would be 55°. This was advised, to avoid turbulences on the vertical stabs coming from the wing of the tanker. According to the swept back wings, the AOA rises and the vertical fins are lower then they would be in Auto. This effect (turbulences on vertical stabs) is not even modelled in DCS. So there is no need to sweep the wings back. Second, I hear often that the slats and maneuver flaps are going crazy. Thats the next fairy tale. You are flying constant and straight with 250kts IAS. There are no slats or maneuver flaps being used. And if they would, it would also not matter because you are flying straight and constant. No difference if they would be out 50% the whole time. Experienced IRL turkey driver refueld with wings in Auto. Just a matter of training. In fact, refueling with 55° (bomb mode) makes your life harder. The turkey gets really nervous to roll inputs and you are very slow and near a stall with the resulting AOA. If your problem is the restriced view, then better try to change your viewpoint. So let me say as conclusion: The F-14 is not a FBW aircraft. If you add one thing (thrust), two other things (speed and lift) will happen. You have to avoid those effects already before they start (pitch down when adding thrust) to happen. Only thing that helps: Training, training, training. Follow the rules for aerial refueling as said above. (And don't forget to set the air source to left unless you wan't to breath some kerosene :smartass: )

Don't get me wrong, I'm the last one who will find that hell of a bug pile or workarounds ok, but there seems really to be something messed up on your side. Ok, I'm useing IFA all the time, but I don't get a CTF when turning the switch from off to IFA (over all other modes) when the turbine did already started up and the generator is running already.

I don't care who is responsible and I don't care about the reason, I just want to get it fixed to be able to startup the F-14 from the carrier without getting seasick. Read again post. nr. 3. Heatblur says, that it is EDs fault, and ED says that they can't do anything about it as long as Heatblur does not bring it up to ED. So, they are both pointing at each other and let us in the dark. Probelm is existing since the F-14 got released, so over an half year later, at least an statement of the actual situation would be be highly appreciated.

Pikey, just twist the INS knob to IFA, wait 2 minutes and fly. No need for doing a sea or ground alignement with datacable or coordinate entry. IIRC, the Harrier was released in EA on November 29th, so prepare your cake, we have a 2 year anniversary.

Sorry, but that is just not true.

4790K@4.5GHz, 32GB, GTX 1080, SteamSS 150%, PD 1.0

Odyssey+ with GTX1080 here. No problems about readability in the F-14. On my personal opinion, the cockpit looks much better, and is better readable then the Av-8b cockpit. Also I feel not a big difference in performance between those two. Flying both on nearly max settings with stable 30-45fps.

Bei dem was ich bis jetzt gesehen habe, sieht es für mich so aus als ob sie die Prioritäten alle richtig gesetzt haben. (Siehe optisches Erscheinungsbild Tpod z.B., sehr vollständiger EA Status, keine großes Aufreden im Vorhinein etc.). Die JF-17 finde ich zwar IRL jetzt nicht so prickelnd, denke aber das Deka da ganze Arbeit mit dem Modul abliefern wird. Bin sehr gespannt...

Since the last update, the first two aircraft on the Stennis spawn next to each other. Related to the massive desync and rubberbanding issues on any carrier, this is a guarantee to have both airframes demolished within seconds. Maybe the team can also investigste on that issue.

Is there anywhere a roadmap for EA or something similar? To get a picture of what is included on EA release and what will be WIP and / or missing?

Zeus answered it already. Add it to "the List". https://forums.eagle.ru/showpost.php?p=3075959&postcount=693

Great idea. Maxbe boring, but at least interesting to get a look behind the scene. Thx for that!

1. NRAS does not affect a CTO as you don't rotate the nozzles. 2. Thtas more or less a DCS Simulator against real life problem. You don't have the feeling in your butt and especially take offs are with most modules not as smooth as they should be IRL. 3. You get those two adversary lights because you also try to turn on the ECM (lowest knob) and you have not equipped the ECM pod.

Ok, thank you and good to know! (When I said no AM/FM messed up, I meant that I did not accidently selected another modulation in the ME)

Why not? TPod on station 2 and Aim-9/Agm-122 on station 6 would sound quite good to me... However, Zeus made this promise already over 1 1/2 year ago: So better to not expect him to keep his promise.

Just would like to ask if there is a known bug with the radio presets? Observed it so far only on the RIO radio. If I enter the correct frequencies in the ME, and then manualy (as RIO) select a preset, or tell Jester to select a preset, I don't get a respond from the one I try to talk to. When dialing in the frequency manual (as RIO) it works. When i tell Jester to dial in the frequency manual (digits, no preset), it works. Seems like there is still a wrong preset frequency, or? Nope: Stennis was on Preset 2. Told Jester to use preset 2. He dialed it in, got no response from the Stennis. Told Jester to dial in the Stennis (TAC -> Stennis). Radio stayedl on the preset and did not change to a manual frequency. -> Suddenly it worked. (No AM/FM messed up) When this problem occours, it is reproduceable (no answer when on presets, ansewrs when dialing in manual or via TAC), unfortuantely, I did not found out when it occours. Did anybody else observed something similar?

Need to try it one day with the L-39, but as the whole sync is really messed up, I'd guess it will be the same. Caught it on tape yesterday: I-LV6A3ManE I would not see that as a low priority bug...

Still present, unfortunately, very annoying :-/ : I-LV6A3ManE Are there any news on that topic from the Dev side?

As requested, we did a trackfile especially for that purpose. I was running the dedicated server on my computer where I also joined the server as client. My buddy and me have a very stable connection and usually a ping between 30-60ms. I was lasing, he was droping as you can see in the trackfile. He intentionally let Efuz stay at Off, so that the exact imapct point of the GBUs can be seen better. Unfortunately, we were also a little bit unlucky. Vehicles have been hit while they were very, very slow because they exactley arrived at a turnpoint, and I also forgot to equip myself with some GBUs to show that it is no problem to hit the moving targets when I'm lasing myself. However, on the first drop / vehicle, you can clearly see how the GBU is trailing behind the vehicle. Second vehicle was very slow and got hit because of that. On the other two drops, it was a bit unlucky, but can still be seen. Attached is the trackfile from the server and both clients, also the tacview. Please advice if you need any further information for investigation. Buddylasing_trailing_laser.zip

Updated manual even before the patch is out? Awesome! Thats how it should be done.

Thx. I have no idea if the Devs read this here or not, however, I'm pretty sure they'll find a solution that works well.

It isn't. At least not reliable. Tpod can't be slewed with a Ministick. Laser just stops working. ARBS has no wind compensation. Sidearms won't get off the rail. Frequencies can't be entered at first attemp. Tacan is bugged for navigation, CTD are still commen when aligning. So there is no system for weapon delivery which is complete and bug free. Maybe if you only wan't to fly around a little bit, but as soon as you study the Natops and dig a little bit deeper then just scratching the surface, you realize how is state really is.

No. Nearly every function or system is either bugged or missing features. Even the ejection seat is bugged. 35% of the system / functions being completed and bug free is very, very positive thinking.

Clear statement, very welcome! Realism is the most important in DCS, if that can't be granted, the its better to not do it.

If you are thinking positive, then maybe 75% complete. If you are thinking positive, then maybe 35% complete and bug free.