Razor18

Unfortunately AI tends to dive to regain speed I guess. You can avoid this, if you always try to climb rather during the dogfight and after any simulated kills, because AI will try to go follow you and level with you.

From 360 to 180 degrees you should do the math the other way around: add 200 and subtract 20. If you don't want to do all the math with hundreds and tens, then simply add 2 to the first digit, and subtract 2 from the second. For instance: reciprocal of 140 is 1 + 2 = 3 (first digit), then 4 - 2 = 2 (second digit), so it is 320. The third digit always remains the same, leave that one alone. The other way around: reciprocal of 240 will be (you can't add 2 to 2, because there is no heading beginnning with 4, so) : subtract 2 from the first digit and add 2 to the second: 2 - 2 = 0, and add 2 to the second digit: 4 + 2 = 6. Reciprocal is then 060. Main rule: if you add to the first, then subtract from the second. If you subtract from the first, then add to the second. Good luck !

Thank you ! But now back to the original question...

Mission 5 Briefing pdf page 5, Prince says Joker will be 6k, at the end of the pdf Designer Notes #5 says: "Remember to use F10 radio menu to declare JOKER when you reach 7000 pounds !" Probably a simple typo, just saying. Oh, and then in the Mission 5 early BFM training, after the second merge for Fox-2, Prince lawndarted vertically into the water, probably because we began at around Angels 8 anyways. Maybe after the first missile shot, they should gain altitude back again.

If you press SCS FWD LONG for the HMD to switch from HACQ to LACQ, it only switches after you release SCS, no matter how long you hold it. It supposed to after 0.8 sec. Guess it was even reported earlier, together with the same problem with the TGP FLIR FOV button LONG press not switching timely, but that one was fixed, and I couldn't find the report any more. Oh, will we sometimes get back the search within the specific topic search function? I mean if I want to search only within the Bugs topics let's say? If I write something to search for to the top right search field being within the Bugs topic now, it searches everywhere, in all topics regardless. Thanks

And I guess the right format of "2 cent" is also worth learning, which is "my 2 cent", or "my 0.02 dollar". There is no such thing as .02 cent, but I dunno, I'm not american... :-D

Great link, thanks. Then I guess, in the game I should have changed the format the other way around, from HH MM.MM format back to HH.MM.SS, if I would've recognized from the 9-line, that it was told in HH.MM.SS, right? Thanks for helping out !

I appreciate the support, but if you take a look at the time of my OP (two years ago almost to the date), I dunno how much hope there is still around for someone from ED to look into it... Moreover it would be better, if settings could be stored for each modul differently, as settings can differ between a slow mover helo and for a jet fighter for instance.

In mission 3 the JTAC says apparently two sets of coordinates in the same sentence - or is the first the same but in MGRS, preceeding the Lat/Long? Or is the first number not coordinates? However I entered Lat/Long but the JDAM missed, close but just outside the compound without effect. My fault, or not precise enough coordinates? It's not the capmaign's fault, but when I enter JTAC coordinates, the zeros preceeding the number "4" are not showing up on the JDAM displyay. Instead of ...30 04". 00 it is ...30 4." 00. Bug? Oh, one more thing: in JDAM PP mode, after entering TGT coordinates on the UFC, can I slave FLIR to the JDAM target to visually acquire it too?

Button is just a slang for preset Channel Nr., nothing to do with button assignment per say. Just means "Switch to channel x (with a different frequency}.

Sorry if already discussed, I didn't find search function in this new forum format yet. Anyways, shortly after commencing, Marshall tells you to "Switch approach, button XY". But when I turn the knob to the new button number, communication seems to seize, unless I'm switching back to Marshall frequency. Is switching to Approach not implemented, or just considered done without doing it? If not, why mentioning the approach button in the radio comms at all? Not a showstopper, just asking... Thanks

That's what I'm assuming, which if so, makes me scratch my head reading replies starting with something like "Forget trimm altogether...". I dunno...

Thanks again !

Does the OP expect answers about how the Hornet CAN be landed "alternatively", or rather how a Hornet should be landed?

By the way, when asked for fuel state, what does the response "Ladder" means? Where can I find this info anyways? Thanks

Thanks Ziptie, that's about what I tried. In retrospect I drifted probably too close to Rock, which then caused pretty erroneous slews on my side. Will try again of course.

I couldn't pick up bandit on either radar or on SA. Should I be able?

Yeah, RAM load is redirected I guess to a HDD/SSD swap file, before running out of RAM. Then again, GPU would be first on my list, but with a new one opening up the GPU chokepoint, be prepared to see the other components also begging for replacement unfortunately. I would later consider a second hand 1151 MoBo, an i5 CPU (hyperthreading barely gives much more for gaming) and at least 16 GB of DDR4 RAM if you don't want to give out a fortune for a brand new system. My 2 cents. Good luck !

Hi Guys, I know it is not a parachuting simulator, but after ejection, the parachute descent is waaay too slow. Those round canopies are relatively small, so they should have rather around 9 - 13 feet per second descent rate (I don't know the present in-game value now). I didn't record my ejection altitude and clocked the time until the ground, but looking at the trees and terrain below nearing the ground, it was really like slowly walking downstairs, barely justifying pilot animation falling on his back at landing. Disregard, if irrelevant, just thought to mention...

OK, but how about GPU and CPU utilisation while running DCS?

DCS is mostly GPU hungry. So, if you buy a new/better GPU first, you can use it even in case you find out you will need a bigger investment reg. CPU and new motherboard. So I would definitely start with a GPU upgrade. By the way, did you monitor CPU and GPU and RAM load in Task Manager's Performance tab to see the loads simultaneously? Anything you see there running close to 100% is a choke point, which needs to be upgraded sooner or later unfortunately. But GPU is definintely "never strong enough" for DCS, and I think the 1060 with 3GB is definitely a choke point now.

It is also bad with the Deltasim upgrade (wich is worth every penny by the way. I know waiting time is measured in months for a long time now, but what else you can do apart of ordering now and waiting? Moaning for a long waiting time without ordering?). With the original WH "slew nipple" it was even worse. The problem is, if you tune down this axis to be smooth on the HUD designation, it will become very slow on every other (proper) slew function. Reported as a bug here https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-f-a-18c-hornet/bugs-aa/7146966-correct-as-is-auto-bombing-td-box-slew-still-way-too-sensitive First they replied it is [CORRECT AS IT IS], but as far as I know, now someone with RL experience chimed in to have ED correct it nonetheless.

I don't think parallax has anything to do with aparent HUD symbology size change. The reason is HUD projection is to the best of my knowledge is focused AND projected to infinity. Focused to infinity means your eyes doesn't have to adjust / shift focus between the dot of a distant aircraft miles away, and the HUD's green radar box around it, like old eyes need to do when looking up from reading the newspaper to look to something in a distance. This is usually compensated by wearing "reading glass" to read, but no glass for driving for instance. Those old eyes wouldn't need glass to read HUD symbology, because it appears sharp for them, being in the infinite distance, and not in the plane of the HUD glass, 1.5 feet from the old eyes Projected to infinity means the entire HUD symbology always has the same apparent size (width x height) for your eyes, so if you would slide back far enough, the HUD glass FOV would not be big enough to accomodate all the HUD picture, loosing the edges of symbology, and if you would slide forward and bump your forehead to the HUD, you would see the symbology absolutely the same size and the same apparent distance from your eyes, but the HUD glass FOV would be much bigger, so that you couldn't even see the HUD glass edges, like wearing a scuba goggle. It is the same as a red dot sight on a rifle. It is always pointing to the same point in infinity, even if you shift your head around, that's why "no parallax error". If you shift head too much, you won't even see the red dot.

Hi There, every time I enter a module, my head position is off to the right by about 1 feet (and a little low too). I can adjust it with Shft+Ctrl NUM keys, and then save it with RAlt+NUM 0, but it only helps within the same session. And if afet saving, I press Shft+Ctrl NUM5, it is offsetting again. Also, next time I enter some other, or the same module, I'm off to the right again. What am I doing wrong? Thanks EDIT: disregard, fixed by unchecking "User snapview saving" in Options / Misc. page.