Galf

Beh contro i MiG-28 è tostissima visto che non esistono :D Scherzi a parte, intendi gli F-5 con la skin da Top Gun, oppure intendi i MiG 29? In qualsiasi caso l'F-14 non è un aereo da dogfight ed i MiG-29 ti mangiano a colazione, contro i Su-27 AI puoi farcerla ma contro i giocatori lascia stare: in entrambi i casi si parla di aerei con limiti di manovra molto superiori e contro i quali non puoi fuggire neanche in verticale (ce la puoi fare contro un Su-27 pieno di carburante, però, con il Fulcrum lascia stare, è un missile.) L'F-14 funziona per i dogfight, ma non è fatto per quelli. Ricordati comunque di disabilitare la Roll SAS, eiettare i serbatoi esterni e di usare tanto timone per rollare. edit: ed ovviamente i maneuvering flap! Auto. Ogni tanto le chiudo del tutto se devo andare full afterburner ed accelerare il più velocemente possibile, ma solitamente Auto è abbastanza veloce per fare la stessa cosa senza tuo input.

Fase di rilascio completo e DCS sono due parole che insieme non esistono :D L'aereo (ed il gioco) è stato relativamente stabile e "pulito" fino ad un mesetto fa. Nelle ultime due-tre patch OB han cominciato a fare casini seri... I "piagnistei della gente" non c'entrano niente, è che la stable onestamente non ha ragione di esistere. Dovrebbero rallentare con gli aggiornamenti dell'open beta a renderla stable (tipo 1 aggiornamento grosso ogni 2 settimane, 1 aggiornamento minore ogni settimana) e poi creare una VERA open beta dove patchano e fixano i piccoli bug che saltano fuori con cadenza più o meno giornaliera - e non sto esagerando, molti dei bug che sono saltati fuori vengono risolti in meno di 12h da utenti o developers, ma ED attende anche 5 giorni prima di mandare il fix sulla OB, fix che spesso non è proprio definitivo ma che grazie agli utenti viene nuovamente sistemato in meno di un giorno. Se mettessero subito l'hotfix live (per questi bug minori) il gioco ne guadagnerebbe. Detto questo dovrebbero anche rivedere le loro priorità... JDAM prima del TGP? Mah.

+1 CTD. Sadly no logs, but I was in multiplayer in a super short range dogfight, I was preparing for a sidewinder shot on a Su-27 on my like 3 o'clock, so probably Jester was going to call something. Otherwise if its related to aircraft damage, I was pulling quite hard - I did manage to break the plane without crashing the game though.

The problem is that it does! It moves to off, it CLICKS to off, but if you go to right click it again it "clicks" again and stays on off, this time actually going off and disabling the weird AP autotrim bug.

Not worth it for DCS imho, and you want to buy minimum a 2080... a GTX 980Ti performs close to an RTX 2060.

Alright I can reproduce this every time 1) fly around 2) enable autopilot through a keybind (I have autopilot on and off set to my switches on the X-55 throttle) 3) disable autopilot either by flight input or by actually disabling it with the "autopilot off" keybind EDIT: I've used only altitude hold mode THREE THINGS happen: 1) trim is disabled. Holding trim doesn't change stick position nor the gauge or the actual control surfaces 2) the plane feels like it tends to hold attitude more, but I'm not 110% sure about this 3) most importantly, even if the switch is off, you can physically click it again to switch if "off" for real once you either click it off again or disengage AP through the emergency disengage paddle or you disabled manually (i.e. by clicking the switch in the cockpit) in the first place, the plane appears to behave normally, with trim working as intended.

Yeah bringing the MCAS in as a whole was in bad taste and I apologize. But it's just to make you realize that if you isolate the issue, wrong human interface management (such as a painful noise or the lack of a physical light-up warning) can lead to undesirable circumstances. (edit: again, the full extent of the MCAS issue is yet to be discovered, so I'm not opening that again, my mistake.) And this is where your reasoning should start, not at the end ("the source says this") but at the beginning ("why would the engineers do this").

It is truly a cornerstone of flight sim development. It just sits on another level, and in a few months when minor things are ironed out (we're talking about these DCS-related crashes, ground handling, Jester using LANTIRN... nothing really major except performance optimization.) all other developers will have a hard job to match the level of the Tomcat. I mean honestly before Heatblur most people would have said a realistic and effective but not overperforming RIO AI would have been impossible... and here we are, with Jester. Heatblur literally made the impossible work and I'm happy I preordered in December. Buy it if you have already some experience with DCS, it is honestly a game changer. Entire F-14 soundtrack plus their previous works, go check it out!

1660 is quite behind the 2060. It's a good 1080p card though, if you do not intend to play VR or 1440p, it's fine. For VR it's very limiting though. edit: sorry for the double post, I'm used to another forum with auto-merge... my bad.

The RTX 2060 is effectively 90% of a GTX 1080. It'll be fine! Go ahead :)

No, I made a logical remark over proof and physical reaction to a sound ;) Think of it in another way: it's an annoying sound by any way you look at it, we can agree on this. It's painful for some people. You want a shoot sound to warn you that it's the right time to shoot, BUT do you want it to force the pilot to turn it off OR fire prematurely? You, as the sound designer, would be putting lives at stake over a sound. If turned off, it defeats the purpose. If it isn't, it leads the pilot to override his brain process to fire prematurely to make the noise to stop or to turn the weapon off making reaction times longer. Not that it would be the first time, since 300 people recently died in the span of 6 months over Boeing placing a warning light as optional (the whole MCAS issue, if airlines bought the optional warning light, pilots woould have instantly know that the AoA sensors were malfunctioning.) - but really you can't take this for granted.

I didn't test it throughly, but I did notice that switching off the autopilot BY BINDING allows for another click of the autopilot engage on/off switch VISUALLY. Meaning that there was a sort of "half autopilot" state that seemed to mess with trim. I check for trim visually on the stick and gauge btw.

*sigh* no, I'm not falling for this. Let's put it this way: you're saying all other modules are wrong, that ED is wrong, etc. So, why are you not asking this from Heatblur, given that they're the Galileo of the situation? Food for thought. And I'm off, because it's a sterile argument where you won't obviously change your stace: I'm looking at it from a human, engineering, sound design and military efficiency perspective. You're looking at it from "if HB has the data, it's true". I'll just wait for HB to address this, since it's close to not putting epylepsy warnings on your game when you introduce such harmful sounds.

Multiple videos around of that, I already replied to this in full extent, it's not a "like" it's "painful" ;)

There's a video here of an official F-14 intercept. There's videos of modern AIM-9 lock tones. There's on the other hand absolutely zero proof of this lock tone. Again, burden of proof.

We're not talking about something that applies uniquely to fighers, pilots or technology limitations though. We're talking about an artificial sound made to make aware of the pilot that the missile has achieved lock. Something that, for example, is expected to be heard from the pilot for minutes in case of an intercept where ROE doesn't allow fire. I.e. stray GA aircraft unresponsive on the radio, you might have to sit there 30 minutes waiting to take the shot, listening to THAT. You realize the pilot would switch off the weapon, leading to consequences? Slower response time because of a stupid noise, do you just trust Heatblur on this? No. Just no. This is a strawman in the purest sense. Do I even have to tell you that when a bullet explodes there's a chemical reaction, it's not a speaker inside the weapon that goes "bang"? Are you so out of touch with reality? You do realize that "hear in helmet" doesn't dampen important alerts, you're hearing those from the headset inside your helmet, you silly? "Yes let's make the pilot isolated from all warnings when he puts his obligatory flight helmet on" said no airforce ever ;) The issue is that the burden of proof is always on who has to prove that something is different. If you want to prove that Earth is flat you have to provide proof. If you want to prove that the sidewinder lock tone is an ear damaging screech nobody has ever heard before, you have to produce proof. Galileo proved the Earth wasn't the center of the universe with hard facts, if you forgot.

This is what HB has done for all we know, to be honest. Out of common sense this should be rolled back, because it makes people physically uncomfortable - don't you think that if the sidewinder tone made people feel bad we would have heard pilot interviews about it? This is one of the few things that the common user can diagnose as wrong or right, because the human brain doesn't change when you become a fighter pilot. It means what it means. The burden of proof is on Heatblur - and in any scenario it still doesn't change that me, and other people, feel ill hearing this sound which is a big impairment to enjoying a simulator.

It's not a question of volume, it's a question of pitch. The pitch is too high compared to ANY sidewinder tone we've ever heard anywhere. And IF this is the real sound (which I honestly doubt, it's seriously disturbing and you don't want to destroy a pilot like this, duh) it's still a good idea to make it optional because it truly sounds horrid, like fingers screeching on a blackboard. There's realistic and then there's common sense - having a lower pitch would completely fix the issue while also matching what we've all heard from any lock tone ever. There's also the small fact that these sounds can trigger people, INCLUDING pilots, and I would hope that the US Navy wouldn't degrade pilot performance over something so trivial: https://en.wikipedia.org/wiki/Misophonia

I'm pretty sure this will be worked on with time. In the bigger scope of things it is a very secondary feature, I'm sure it will get in once the major stuff is done!

Thank you. If all goes well, can we expect a hotfix today, or should we just rollback to the previous patch for the moment? (i.e. fix coming later than tomorrow)

I think one of those wasn't so much controlled flight, it was a main wing spar breaking off, which grounded the fleet for a while... but that's off topic, great to bring the Buccaneer in though, would be a fun full module to have in DCS :)

I think I got this too. I felt the plane acting odd. Does trim work for you after doing that? Because my trim appears to not work anymore sometimes, and I suspect it's related to this.

l'F-18 è FBW ed è limitato elettronicamente per non farti spezzare le ali. L'F-14 è analogico, completamente, (edit: ok non è proprio esatto, ma è come l'A-10, è meccanico ed idraulico non ci sono computer che ti limitano gli input.) devi ascoltare l'aereo e tenere un occhio piantato sull'indicatore di AoA. Con i serbatoi di carburante attaccati fare G istantanei è pericolosissimo, ho spezzato l'aereo a 7G. Devi anche tenere un occhio sull'angolo delle ali, tutte aperte si spezzano facilmente.

La cosa migliore da fare è ignorare l'HUD e guardare il VDI! Quello indica correttamente l'orizzonte, l'HUD è ingannevole e la tua posizione nell'aereo ti rende difficile giudicare quando il muso è parallelo all'orizzonte. E sì, trimma sempre. Guardati come funziona l'autopilota perchè non è immediato da capire e l'emergency disconnect dell'autopilota ti disabilita anche 2 assi di stabilizzazione quindi... 'ttento. è tutto semplicemente a raggio più corto di quanto dovrebbe, ci stan mettendo una pezza poco per volta, i missili "loftano" male pure. Tante piccole cosette. Non è così rilevante per me onestamente, se TUTTI i missili seguono le stesse regole alla fine è ok per noi, quello che mi rode è che non c'è nessun detonatore di prossimità, che è ridicolo, c'è sui missili già dagli anni 50...

Una cosa interessante: Jester usa automaticamente TWS, quindi se appaiono bersagli su schermo, basta lanciare i Phoenix in successione per colpire bersagli multipli. i missili in dcs soffrono di attrito esagerato ed in multiplayer non c'è proximity fusing (non ricordo come si dice in italiano - detonatori di prossimità comunque, significa che i missili esplodono solo se colpiscono direttamente in MP a causa del netcode.) questo vale per TUTTI i missili, se leggi dati reali e li applichi al gioco, non funzioneranno.