Lord_Pyro

Nothing more to add. Thank you @Lange_666, Topic can get closed.

I dont really want to do that, as i need it for performance issues. And up until December everything worked fine with DLSS and DLAA. Maybe i should check the changelogs. (i checked my screenshots, the effect appeared after the patch which brought us the remodelled F5, on dec. the 4th) On a sidenote; the current patch did not fix it.

Yes, i use DLSS since it first released for DCS and for Anti Aliasing i use DLAA.

Deleting the shaders did not help

Since the last 2 bigger Updates darker areas have some kind of checkerboardpattern applied to them. Brighter areas look fine though. I fly exclusively in VR where this does not occure at all, i just have that on my screenshots (and maybe in 2d DCS in general). Anyone noticed something similiar? Maybe some shaderissue? null

Yes, i run it on a SSD. Thanks for the reply

Since the beginning there is a huge freeze incoming as soon as the radar scans for50nm for the first time due to the huge amounts of returns it receives (same thing for the Strike Eagle btw). At first i thought it had something to do with the gear up animation but it soon klicked and now my workaround is to scan at 5nm during takeoff, stabelizing the plane and plan for the sometimes 5 seconds freeze in advance. That works, but is not ideal. After aerial refuelling the same issue arises, obviously. So the question is, if it's something we just have to learn to accept or can things be improved somehow?

Looking forward then

"An update to the freely available Fear the Bones practice mission is coming soon in a new update and its being joined by a new free scenario based on the Speed & Angels campaign. The scenario is a cold and dark case I recovery practice mission, however, the details are are ramped up a bit with voice overs, hand gesture support, and a full carrier deck for added immersion." Not yet i guess? Or did i just fail finding the new carrier mission?

If it's AI try popping your speedbrakes, until he overshoots. Use scissors to avoid guns/fox 2's and as soon as he is next to you retract the brakes, full a/b and gain enough Energy to pull the reticle just high enough for a snapshot Fox 2 shot. Worked pretty consistently for me.

Because yesterday was a holliday for some parts of the world?

And then you want to buy it again after the early accessperiod?

Yes, since the day they started the preorder. To be more precise: 30/10/23 But it was bought on the HB page.

I only had it at cold starts. At Flashpoint Levant for example.

Well i dont know if it is reported to razbam yet, i looked it up too and saw one redditpost about it. All i wanted to say is, that the fault is not on your side

Its a known issue. There is atm no way to troubleshoot (at least not to my knownledge) However, i managed to at least refuel because i just had the keybind for the "ready precontact" command mapped. I asked the initial "intend to refuel" but got no response and the radio menue did not change to the pre contact menue. So by using the direct command we can bypass everything else. And for those who try to help solve the problem. It has nothing to do with anything we do inside the pit. There are servers where it works, and some where it wont. In SP it works all the time and easy comm is turned off. I tested with srs and without, it changes nothing. So i guess its something serverrelated. Who knows...

For me it was the other way around. I rarely use the pb from the pit. Btw: lowering the hook does also kill the alignmentprocess

Going slow was the point of the whole exercise. And for touchdown aoa, i dont recall the exact number (it changed constantly anyway) but i did not tailstrike (which i believe starts somewhere around 26/27 deg) so its fine by me. About the glideslope part - i let the plane settle down on where it wanted to be. Trimmed for a steady descent, almost hands off stick, so i just needed to play with the thrust a bit. I like it that way, its smooth

Thats why you aerobrake, yes.

But that takes time. If you don't want to wait for the fuel to dump, or don't can for some reason it doesn't hurt to have a skillset from outside of the normal procedures.

I tested the other extreme. Loaded the jet up to overweight (pic 1), then took off, flew away for a bit to get some speed and height, to simulate a long approach (pic 2). During the descend its true, i had to keep the speed at around 190 to 200null (so the fpm did not flash but still remained on the landingstripnull) (Pics 3 and 4). However during short final i aimed a bit short in order to prolong my flare null (pic 5) whichnullnull allowed me to be slower than 160 on touchdown. (pic 6). So my point here is that its correct that you glide on 190+ as not to stall, but the touchdown can be way slower. I admit i overshot the runway a bit (Pic 7) but i remind you, i was still heavier than max allowed takeoffspeed + i tried to get a pic of the aerobreaking too (in vr), which messed up my breakingprocess a bit, so maybe it would have been possible to come to a hold still on the runway. Oh and btw my fuelreadout after landing was still aboce 31k. null So on final conclusion i would suggest not to only rely on numbers and books alone. We are flying a simulator and there is no better tool to experiment with things and just figure out if stuff works and or not.nullnull

190? Thats really fast! Try something like 160 and let her calmly aerobrake. She actually decelerates quite nicely, especially compared to a hornet.

Maybe check for some doubled bindings. As DCS likes to bind itself per default for every connected device. (Which is why i always completely wipe every device up on first launching a new module) Maybe some achsiscommand is fighting your buttonpress for zooming.

Look back from the front pit. Is there an WSO present? If not, its by design. The wso can be disabled in the missioneditor. The ingametutorialmissions have it that way as well.

Coolie left long shows friend - foe, coolie right long delivers the type of plane (if possible).