-Mop-

thx for your answer... but the problem is that, for example i select fixed gun, but it moves... or i choose gun and the HUD shows everything according to vikhrs... or a mixture of both quite an interesting issue

the bug shows up on mission 13... try the same on non-campaign-missions everything works fine Since one of the latest patches my shark behaves really strange according choosing gun, choosing Vikhrs, box around the hitzone of the gun on the HUD and so on... the HUD doesnt show that that gun is elected, the box around the hitzone doesnt appear, nor in move- or in fixed mode, no matter automated tracking is on or not. I cant choose vikhrs, the usual HUD-look doesnt appear. and - i can´t fire/shoot anything... the track-files exceeds the limits, so i´m not able to post it... sry I think ED stopped reading any posts and dealing with any problems about the shark a year ago... somebody else help please

Well spoken...

Thx for your help... all you mentioned i tested before... so it didnt help... after i tried to create a track-file as xxxjohnxxx (by the way: Thx for many very helpful tutorials) mentioned, it worked without any problems - as it was before the problem occurred... the only thing that might have made the difference: i updated the game back to the current version... we used the older one the last days to play a MiG-21 campaign... but i´m not shure that this made the point, because the problem has appeared before that... so beyond all of that: it works again... so thx again for helping... i come back to this thread, when it appears again

Since a few weeks ago my chute doesnt flare and since about the same time also Chaff and flare refuse to dispence... The Keys are bound correctly... looking at the buttons in the cockpit shows that they are being pushed down... the typical sound appears... but nothing happens... so... whats the point? Please help... of course its a nice training landing without using the drag chute, but doesnt work on short tunways... so... again... someone got an idea?

Alle paar Monate treibt mich das Thema Performance-Verbesserung an... auf der Suche nach ein paar FPS mehr, hatte ich gestern abend das Gefühl den Heiligen Gral gefunden zu haben... auch nach heute morgen bleibt dieses Gefühl mit kleinen Einschränkungen erhalten. Gestern abend bin ich auf folgendes Video gestoßen: Dieses und dessen 4 Folgevideos (insgesamt so 50 Minuten) erläutern empirisch sehr gut wie durch das Ändern einzelner Parameter sich die Performance des Spiels ändert. Mal auf die Gefahr hin, dass ihr das alles schon wusstet und ich der einzige Trottel war, dem das bisher nicht klar war, will ich mal versuchen das ganze zusammenzufassen: Es wird hier zwischen fps und der Schnelligkeit des Bildaufbaus unterschieden, sprich fps und Latenz ?!? Zweiteres verbessert sich maßgeblich, wenn man die Cockpit Displays, egal ob runter oder rauf, auf "512 sync every frame" setzt... kein Witz sagenhafte Flüssigkeit der MFDs und vor allem kaum noch Microruckler, wenn man in die landschaft schaut... probierts aus. Zudem haben leichte Reduktionen der Grafik - Reduzierung von MSAA 8x auf 4x - das wars (bei mir jedenfalls) dazu geführt, dass 50 % mehr frames hatte (auch hier kein Witz: während ich bisher zu Beginn der ersten Instant Action-Mission der A10c immer so 50-60 frames hatte, hatte ich gestern abend zwischen 70 und 80 frames (teilweise 90 frames und das ohne in dem himmel zu schauen) - im beschuss des Bodens mit gau und rockets immerhin noch 50 frames... das hat dazu geführt, dass ich zum ersten mal in meinem Leben VSync eingeschaltet habe... und das ist echt, solange man mit 60 fps bei der nativen Darstellung unserer Monitore liegt, ein echter Lustgewinn... wenn man natürlich darunter fällt wirds ruckelig... aber jetzt das tolle - hab ich selbst rausgefunden ;-)- wenn man VSync nicht nur ingame, sondern auch in der Nvidia-Systemsteuerung anschaltet und auf "Adaptiv" stellt führt dies dazu, dass man bei mehr als 60 fps Vsync hat (damit ist der wert von 60 pfs gefixt und geht logischerweise nicht höher. bei weniger als 60 fps schaltet sich das Vsync ab, aber dafpür hat man dann keine Vsync-typischen gefixten 30 fps sondern eben normale 45-55 frames (zumindest bei mir)... und jetzt zu der Einschränkung: die Repoduzierbarkeit... eigentlich sind die Aktivierung von Vsync ingame und in nvidia zwei paralell angelegte Operationen... dennoch klappt das oben beschrieben nur dann, wenn ingame vsync und dann in nvidia auf "apaptiv" geklickt wird... und das jedes mal beim neustart des Spiels oder des Rechners... das alles, auch die sache mit den Cockpit-Displays funktioniert nur dann, wenn man jedes mal wieder ingame die werte verändert, dann abspeichert, und dann wider zurückstellt... das gleiche in nvidia... klingt komisch - ist aber so ;-) Versucht es mal und gebt mir ein Feedback... und idealerweise auch ne erklärung... falls ihr genau meine einstellungen wissen wollt - fragt... und schaut euch die videos an... echt super gemacht und verständlich... keine gelabert basierend auf annahmen, sondern basierend auf tests

Same Problem here. I deleted in every Plane-Config the "LShift + R"... but it didnt help... Workaround: I placed "LShift + LAlt + LCtrl + R" for it :-(... it helps me to set an appropriate Keybinding for my G-Keys on my Logitech G11

Same here...

MegaLOL:thumbup:

Thx to Coolhand... and a big sorry to sithspawn... after trying to get a proper aim at the enemy i realized that i wasnt able to proof that there is still a Problem... ist quiet hard to get the Opponent in a flight calm flightstate, where i was able to adjust the k-14 in a way where i can be sure that it was adjusted the right way... so if a Problem is not reproduceable (because i hit him every time) - its not there thx for now

Thx for the offer... as soon i´m back from work this evening i´ll do some flights and post the trk.-files afterwards...

Nearly 2 years have passed since the above Statement has been made... and i have to say that NOTHING HAS BEEN FIXED !!! still the K-14 calculates not the correct lead... in my opinion you have to add additional lead at about the lenght of the plane you are targetting... so please fix it... maybe thos has been forgotten... has anybody realized any difference from that time to now???

What was mentioned in the previous post i now have again... during the use of 1.2.7 i had also a massive Input delay, as described before... with the update 1.2.8 it was gone... but since a few days it came back during the use of my msffb2... of course only when ffb was enabled in the Options... has some1 an Explanation why this mess came back again... in the meantime i havent installed an update or anything else

Doesn´t work out on my pc... everything i try - the weapon hints, Autopilot and Crew Status doesn´t move in any direction... maybe something has changed in 1.2.7 and 1.2.8? please don´t Forward me to older Posts an threads - i tried everthing here on this Forum... any other idea?

The ADF-Frequency-Button should be corrected... the frequency you choose is always on the oposite side of the button.... as said above, the INU-Drift should be modelled... The WIngman-AI sucks... but i dont expected that there something will be done... Apart from that i´m very happy with this module ;-)

why should simFFB be better than the ingame feature? imo it isnt... just for the time ED wasnt able to fix the ffb problem ( it was a veeeeeeery long time)it was a very good help... but now?!?

Maybe I discovered an error... i don´t remember if this is a new an old one or just a misunderstanding of mine... Of course you feel resistance when you use the stick with the AP-Channels engaged and no trimmer-button pressed... so far so good... but if you enter the FD-mode the HUD behaves as described in Numeros threads... but... still i feel the resistance of my forcefeedback-stick pulling itself back to the last datum.... should it do this? in my understanding in FD-Mode Damping should still be active but the Attitude-Hold-Mode should be disengaged... and so no resistance should be recognizable... True or Wrong? Please help... and please no guesses... just answer if you really know what you are talking about... thx in advance:pilotfly:

I know the Problem... ive read the mentioned Manual about a hundred times... i do exactly what is described... and exactly how dr arrow described it happens to me... btw: switching off altitude channel doesnt make sense, because the only Job of the collective brake is to stop this channel from working til you let the handle go... so without the altitude channel the collective brake is useless... at least if you´re not keen on zeroing the measurement on the bottom right of the HUD

:-)

This is true... with the g940 you can trim as much as posible, but because of the ffb-Deadzone in the center - and the lack of a spring the weight of the stick always pulls itself to one side -its impossible to let the mustand fly straight ahead... i helped myself with using the HOTAS WARTHOG(distance flights) and the MSFFB2 (combat) at once silly, but that´s the way...:pilotfly:

DCS Mig-21BIS

NO... ED wants to earn Money with new modules and obviously forgets old customers like us:mad:... i´m very sad about this

makes me sad to see a f-16 to be shot down just for targetpractice... but nice pics :joystick:

believe me... you have shoot the Dora 3 times more "Swiss-cheese-like" to get her down... explain you personal trick not to blow your engine... did you do something with the the cooling?

use both and you´ll get better:joystick: