Ithronwise

It seems you have a very similar problem to mine

Hi Aviators, hi ED Team, I tested a little around (deleted the options.lua and started with a fresh one) but there were no changes. DCS 2.7 ran with 1920x1080 no matter what resolution I set. Then I changed the resolution of my Windows to 2560x1440 and now DCS runs with 2560x1440. But this is no solution for me, because the Windows fonts and symbols are looking blurry with this resolution and I use my Rig for other tasks than gaming, too. I tested the following settings: 1. Windows resolution: 1920x1080 DCS resolution: 2560x1440 Result: DCS runs with 1920x1080 2. Windows resolution: 2560x1440 DCS resolution: 2560x1440 Result: DCS runs with 2560x1440 3. Windows resolution: 2560x1440 DCS resolution: 1920x1080 Result: DCS runs with 1920x1080 It seems the max. resolution limit of DCS 2.7 depends of the resolution of Windows now. Lower than Windows resolution is working, higher than Windows resolution doesn't work anymore. I think this issue is caused by this change in the patchnotes: "Graphic system. First game start will be in main display resolution, not 1280x768." Something is buggy there. Best regards, Rene

Hi Aviators, AMD VSR doesn't work anymore in DCS World 2.7. I have an 1920x1080 Screen and have set a resolution of 2560x1440 in DCS graphics settings with activated AMD VSR in the radeon settings. Right after the update DCS ignores any resolution settings and runs only with the native resolution of 1920x1080 no matter what resolution is set. I already deleted the fxo and metashaders2 folders, ran cleanup and repair but nothing helped. I also have the impression that all graphics settings like MSAA or SSAA are ignored now. At least I couldn't see any difference between MSAA 2x and MSAA 4x or between SSAA Off and SSAA 1.5. Best regards, Rene

I cannot reproduce this. I start the TARGET profile every time before I start DCS. Never had a problem like this. Have you tried to create an empty profile without any mappings just for testing?

Ok, that means there is a problem with weight balance at the moment that also can affect the rolling/braking on the ground, but ED is working on it. That sounds good for me. I will be patienced and waiting for a fix in the near future. Thank you very much for the information.

Hi BIGNEWY, I just tested it with a very gently and slightly using of the toe brakes (I hope you know, that the hard using of the wheel brakes in the track was only to demonstrate the issue), but even then the F-16 breaks out left or right. And it also dramatically breaks out when the jet has almost stopped and you hit the brakes (can you also see in my first track) no matter how gently you do it. That cannot be normal. As Machalot, Hammer1-1 and Dee-Jay wrote, if the Anti Skid isn't implemented yet, then of course the plane breaks out if one wheel blocks during braking. It has nothing to do with an unbalanced fuel load (especially not if this unbalacing is between the forward and the afterward tank because of their different sizes). I know the F-16 is an Early Access plane and a lot of systems are WIP or just will be implemented in the near future. But the Anti Skid is a basic and important system to handle the Viper on the ground. I think, the way how to create a module should be 1. roll, 2. fly, 3. navigate, 4. fight. Best regards, Rene

Ok, thank you. Interesting information. But then I don't understand BIGNEWIE's explanation. I thought he talks about an unbalanced load of the wing tanks. A different load (by design) of the fwd and the aft tank shouldn't cause an unbalanced behavior of the wheel brakes.

I know this fact but no other plane in DCS behaves so and in the test mission for the track to demonstrate the issue the Viper was clean, there was no wind set or other circumstances they could explain this behavior. I am an old Falcon 4.0 veteran with almost 600 flight hours on it and I don't know this from the F-16 there. It is a fact, the nose wheel steering and the wheel brake behavior of the DCS Viper is strange. My question is, is it realistic? If yes then I have to learn to handle it, if not ED should fixing it.

Ok, this makes sense, but then there are still two open questions (at least for me): 1. If the reason for the different braking effect of both wheels is the unbalanced fuel load as BIGNEWY said, why switches the braking effect from the left wheel to the right wheel and back when I use both wheel brakes simultaneously (for example by using the key command) like in the first track? 2. Why are the internal fuel tanks of my Viper unbalanced loaded even if I have a fuel state of 100% (that means all internal tanks should be completely full so there shouldn't be a different load between them)?

And why is it so? I didn't set different fuel load. The picture shows full internal fuel load on mission start (in the Mission Editor the internal fuel is set to 100%). Why I have different fuel load? And this is not an good explanation why the wheel brakes in one moment are braking left and in the other moment are braking right. The different fuel load surely wil not jump from one tank to another. It is also not an explanation why the plane brakes out left or right directly before it stops. If the real Viper does it, too, ok, but if not than the DCS Viper shouldn't does it. By the way the braking works wrong. If the left wheel brakes, the plane should go left and if the right wheel brakes it should go right, or I am wrong?

This was my old setting ... This is my current setting ... There is no difference in its behavior, no matter how i set the wheel brakes axises or I use the wheel brake command key "W".

Here is another short track that shows the strange behavior after touchdown. F-16C Wheel brake issue 2.trk

Arrgh, sorry BIGNEWY, I forgot to delete the unoffical mods from the mission. Here is a track without them. F-16C Wheel brake issue.trk

Hi florence, no, I didn't locking up a wheel. I just uses the wheel brakes command "W" (by keyboard and by Warthog button), not the commands for left wheel brake and the right wheel brake. Normally this should brakes both wheels simultaneously, not in one moment the left wheel and some seconds later the right wheel. Both toe brakes of my rudder pedals are set to the same wheel brakes command, too. I also tested it with setting left wheel brake to the left toe brake, right wheel brake to the right toe brake, but even if I hit both toe brakes the plane breaks out to the left or right randomly. This behavior of the F-16C I already noticed long before I bought my rudder pedals, but I haven't flown the Viper for a longer time and so I forgot it. Best regards, Rene

Hi BIGNEWY, here is the track. Every time the plane runs out of line, I have hit the wheel brakes. Especially right before the plane stops (last part of the track) it breaks out dramatically to the right or left. Best regards, Rene F-16C Wheel brake issue.trk

Hi ED team, hi pilots, if I hit the wheelbrakes (no matter if I use the keyboard key, a button on my Thrustmaster Warthog or the both toe brakes of my Logitech/Saitek rudder pedals) the F-16C brakes almost ever only with one wheel (sometimes with the left one, sometimes with the right one). This also happens right after landing and results in a breakout of the plane to the left or to the right, which is difficult to catch by the rudder. Only very rarely both wheelbrakes will be activated at the same time by hitting the key/button/toe brakes (like you can see in the background of the first picture). Is this a normal behavior identical to the real life viper or a bug? Best regards, Rene

Hi Art-J, thanks for the advice ... ... that was it! For some reason Nellis was red, my AV-8B was blue. Normally when I set a plane to an airport, the airport changes the coalition color to the same like the plane. I don't know why it didn't work for this mission. Maybe I accidently clicked somewhere wrong. Long story short, now the ground crew in Nellis talks to me again. Thank you. Best regards, Rene

Hi folks, I am not sure whether this issue is already known (Google and forum search didn't found anything). On cold start in Nellis the ground crew doesn't talk to me nor reacts, at least in the AV-8B and A-10C. I didn't test other planes yet but in the Zone 5 campaign for the F-14A it works. In Kobuleti on the Caucasus map it works as expected for der AV-8B (see the both short tracks in the attachment). Best regards, Rene AV-8B Cold Start Issue NTTR.trk AV-8B Cold Start Test Caucasus.trk

Ok, I also have posted it in the DCS World 2.5 bug section.

Hi, just found this bug within the first (initial) mission of the F-14 Zone 5 Campaign, but it is a general DCS bug, I guess: The ground crews are looking like ghosts (but only the guys in blue overalls and basecaps). In daylight they are looking normal. Best regards, Rene

Hi Tomcatters, not sure whether it is a bug of the campaign or of the DCS ground crew rendering. After landing on Nellis AFB during the first (initial) mission I saw this: In daylight these ground crew men are looking normal. Best regards, Rene

Hi Flappie, I tested again and I am pretty sure now, my graphics glitch has the same source like the strange graphics glitch (yellow, red) in this forum. My setup contained two M163, four Mi-8 and a Humvee as observer. Graphics glitch Mi-8 02.trk Here is a video of it: (the first 5 pictures were taken from a run yesterday) Then I changed the setup. Instead the Mi-8 I used Bf 109K-4 and there was the same glitch. Here is the video: The only differences were the colours (grey/white instead darkgrey/black, red/yellow instead black/blue). Also the shape was very similar (looks like a cone in some of the pictures). And all these glitches are not longer than 1 frame. That means, on my rig with my settings (rock solid 60 fps) it is only visible for a 1/60 of a second. If you run DCS with a higher frame rate (90 or 120 fps) than it would be visible for only 1/90 or 1/120 of a second. It is possible that you just overlook it. Best regards, Rene

At least the second crater is still there (found it by random). I mean, that's an enormous crater and maybe the digital workers of ED only have some virtual shovels to fill it in, but three years are a really long time to fix such a bug.

I also had these orange and yellow flashes together with black and grey flashes in non-WWII modules, see here: The orange and yellow flashes were gone someday. I thought because of a DCS update or a graphics driver update. The black flashes stayed. I hope you are right and my graphics card is not dying, because then DCS would be history for me at least for the next six or more months. It is almost impossible to buy a new one (no matter whether AMD or NVIDIA), and if, you have to pay moon prices.

Hi Taz1004, my glitches are also just very short flashes, not longer than 1 or 2 frames and happen in very limited situations. When a graphics card dies, then these glitches are longer or persistent, are more randomized and don't happen in exactly the same situations. My card is running within normal temperature ranges and isn't overclocked. On weekend I will dust it off and give the underclocking by AfterBurner a try. Thanks for your help so far. Best regards, Rene