Sporg

Thanks for the report. But when is it going to be fixed? The ADF is almost totally inop now, and it renders the Argo campaign which I'm trying to go through now mostly unplayable. I made it through mission 1 because I could fly to Batumi on dead reckoning, but as the campaign progresses its no fun to keep doing that. I have tested the Gazelle on the beacons of Batumi and Kobuleti, and they work nearly perfectly there. The Huey ADF problem has been looming for a year minimum, already when I first tried Argo in start 2018,there were certain beacons not working, now it is almost all of them the Huey ADF cannot see. Hoping it will be prioritized soon, so that one can go through the campaign in a proper manner again. PS: I have been trying the fix with flying again in a second session, it doesn't work here. The ADF stays inop or swinging the needle. PPS: A propos: Similar bug report from March 2018.. : https://forums.eagle.ru/showpost.php?p=3552038&postcount=6 One more edit: After some testing, I found that the outer and inner NDB at Kobuleti seems to work in many different other aircraft. Secondly I found that the outer NDB, at 870MHz, seems to somewhat work in the Huey if I switch off "Easy Communication". Several other beacons seems to start to work too, but not all. The inner beacon at Kobuleti at 490MHz has always been troublesome, and it seems very buggy still. Only one time out of 5-6 attempts did I get it to work. I hope this can help to track down the issue. This bug really needs to be fixed, so that one can rely on the system again. Edit 2: Some more testing revealed that the the Huey seems to have wrong altitude and/or terrain masking data for receiving NDBs. I tested flying out of Batumi, tuned in to the inner NDB on Kobuleti at 490MHz. Testing with the Gazelle, it received the signal from around 80-100m (300-400ft) altitude around Batumi. The Huey only received the signal from >1500ft altitude and up, even out over the sea. This was tested flying up and down, the find where the limit was. That's the best I can do. Now the developers needs to look into what goes wrong. Thanks.

Hi Thomas Could you tell us your solution? It might help others to succeed. Thanks.

Okay, I finally came back to trying this (not much time to fly anymore, sadly): I can now confirm, wake turbulence is the issue! I tried the mission again in OB, FPS slowed to a crawl near the bombers. Switched wake turbulence off, then tried again: Smooth as butter, no FPS deterioration anymore. Checked my release version to confirm: Wake turbulence was already off there. Thanks for the tip. :thumbup:

Thank you very much! I will test this, as it can very well be my problem: I tested F-14 on OB when it came out, and of course enabled wake turbulence to try out the new feature. However, I didn't test F-14 on my release version, so I didn't think of switching on wake turbulence there. Another thing is, if it was playable, it could be marvellous to have the added challenge of having to fly through the turbulence from a massive bomber formation as well.

Exactly, that's why it is strange that the problem occurs in one version for me, but not in the other. Usually they work exactly the same.

I have now tested in the release version after update, and here the fps only drops to 35+ when the bomber action starts. In OB it still drops to around 9. I can't attach the release version log here, since it's too big. (You really should look at file limits in the forum.) Same errors seem to be present as in OB though, so I'm at a loss about the difference in fps.

B-17 wasn't shiny as in polished during WW II. For several reasons, visibility and labor being among them. The shiny polished warbirds is an airshow thing. Back then they were tools for a serious purpose.

I can report that I have a clean install, no mods what so ever. (Cleaned via the Repair and Cleanup option in the installer) Only Tacview running. (tried to turn it off, but it turned on automatically) I tried updating the GPU driver, but got same FPS drop. I can try removing my CPU OC, but doubt it will help, it is stress tested to much higher load than what DCS delivers. NineLine, could it be that you have a more powerful PC, so that you may get some FPS drop, but that it is not as critical as it is on a slower PC? I can try again later, when I have some more time.

I was switching off the engine as I usually do: Some throttle, then cut off fuel and let it die of starvation. However, this time the engine kept on running/coughing. I switched everything off: Battery, Ignition, Throttle to Idle Stop, still the engine kept on coughing and didn't stop. Only when I realized I forgot to switch off magnetos did it stop. This was online MP.

I just had this funny bug yesterday. Was flying the Free-Lance Patrol in Caucasus, when I happened to crash into a P-51 which ripped my left wing off. To my surprise, I didn't spin and crash, but was able to, rather easily, correct the missing lift with rudder and aileron, and keep on flying.. :) Second picture shows full rudder, but later on I could fly with almost neutral rudder. Track is too big to upload.

Thanks Pitbull I tried the mission after latest patch. This time with a twist: I set player aircraft to be the top cover 109. Same result: Dropping to very low fps. Extract from log: 2019-06-22 22:01:45.246 INFO Lua: Lua CPU usage: metric: average mission loading: 1.7332 % 2019-06-22 22:01:45.246 INFO Dispatcher: loadMission Done: Сontrol passed to the player 2019-06-22 22:01:49.629 INFO TACVIEW.DLL: Recording flight data in [E:\Saved Games\Tacview\Tacview-20190623-000150-DCS-Fw190A-8 - Caucasus - Bomber Intercept (2).zip.acmi] 2019-06-22 22:02:44.560 ERROR DX11BACKEND: Texture /textures/b-17g_dm_interior_main.dds is 3d but has depth == 1. 2019-06-22 22:02:54.735 ERROR DX11BACKEND: Texture /textures/damadge elements.dds is 3d but has depth == 1. 2019-06-22 22:03:01.343 ERROR EFFECTS: ODCSParticleSystem: trying to set parameter for emitter that doesn't exists in shellExplosion.lua 2019-06-22 22:04:29.010 WARNING LOG: 494 duplicate message(s) skipped. 2019-06-22 22:04:29.010 INFO Lua: Lua CPU usage: metric: average mission execution: 6.3705 % 2019-06-22 22:04:33.258 INFO Dispatcher: Stop Red line should say it all. ;) This log is attached here. dcs.log(8).txt

Thanks, it's nice to get confirmed that I am not alone. I have tried and tested also. Repairing several times, removing anything suspicious from both Saved Games and OB, turning off my FFB seat. Nothing really helps, it goes down to the same 10-12-15 fps every time the action starts. I have identified some possible culprits in the log file. Most importantly this one: 2019-06-15 16:23:44.108 ERROR EFFECTS: ODCSParticleSystem: trying to set parameter for emitter that doesn't exists in shellExplosion.lua It is recurrent,and points to the flak problem. Then these also: 2019-06-15 09:04:39.104 ERROR DX11BACKEND: Texture /textures/b-17g_dm_fuz_main.dds is 3d but has depth == 1. 2019-06-15 09:04:39.263 ERROR DX11BACKEND: Texture /textures/p51d_damage_main_2.dds is 3d but has depth == 1. 2019-06-15 09:04:39.339 ERROR DX11BACKEND: Texture /textures/p51d_damage_main.dds is 3d but has depth == 1. These could fit with the problem starting with the B-17s and their escorts appearing and the fight starting. I attach one of my test logs here, but the above lines are recurrent in all of them. There are others also, but I guess ED staff will have to look through them. dcs (4).txt

Thanks, I'll try. I'll start with the repair and see if that fixes it.

I have tried to fly the Quick Start mission Bomber Intercept However, at the time I get near the bombers, my frame rate falls to an almost unplayable 9-12-15 FPS (otherwise around 45 FPS and up). It seems that the FPS drops when a lot of AI action starts. And I don't need to be nearby, even when far away again, the FPS is low. I don't know if the problem is CPU bound, because I have tried lowering resolution to a standard 1920x1080, and tried lowering graphics settings, but the problem persists. I am aware that I have an ageing CPU (i7 2600K @4.3 Hz), but normally it can keep up decently. RAM is 24 GB, and in game VRAM use is around 11 GB when the problem arises. GPU is a GTX1080TI, and both Windows and DCS are on SSD drives. Does anyone else have similar problems? EDIT: I have a screenshot with DCS system info when the FPS are low:

Thanks, good to get confirmed. Which stick do you use?

I use an extension too. But I never used curves, even before using extension. Before, all modules had been set with 0 curve as default, so I didn't check this time. But I guess I'll have to in the future. FWIW, a number of people in a group I'm member of were happy to get informed, they had also felt the aircraft was sluggish in its behaviour.

Thanks. Wasn't aware of that.

When setting up key binds, a lot of them are inaccessible for either the throttle buttons or for the joystick, or sometimes both. One important case in hand, also mentioned elsewhere, is the manual RPM buttons, which are located on the throttle in the actual aircraft. Also the REVI 16 gunsight brightness is only possible to assign to the joystick, not the throttle. There are many of these blocked key binds. Controller: Warthog HOTAS

Actually, I felt the same initially. How weird it may sound, she became much better when I discovered that the joystick (at least Warthog) is set up with curves and deadzone as default. Removing them removed a lot of the "dead" feeling, and I can do much more precise and fast turns now. Much more agile bird, once it's up to speed. Check to see if you have curves on your axis too.

In the default quick missions for the A-8, it is always configured with the bomb rack on. Shouldn't it default to bomb rack off, unless it is actually a bombing mission? To be honest, it looks a little silly intercepting B-17s at altitude, with a group of fighters with bomb racks on all of them. ;) :)

The A-8 has curves set as default on the joystick, at least when using Warthog HOTAS. Since this affects handling very negatively, shouldn't these be set to zero as standard?

When I got the A-8, I was surprised, because it was weirdly slow in it's reactions, compared to the Dora that I also have. Especially I had to pull the stick all the way to my chair just to pull a little up. After getting annoyed by that, and investigating, I found the cause: The A-8 is set up with joystick curves as default! Curve is set to 15 on both X- and Y-axis, and deadzone at 3. After setting curve and deadzone to 0, like I have it on the Dora, I got a whole other aircraft: Swift and agile, once it's up to speed. Now it feels properly like Dora's little brother: Fast and agile, a better turner, but with less power in the engine. A much more fun aircraft, no longer feeling like stuck in rubber. I recommend very much to check your axis settings, and see if you have the same. My setup is Warthog HOTAS, the default setup might not be the same for other controllers. A second thing: The aircraft, including in missions, comes set up with bomb rack as default. It can be removed in mission editor, and I recommend to do this: It gives better speed, but above all better trim. (Btw., it also looks a little silly in the accompanying bomber intercept mission: I doubt the Germans would send up fighters with bomb rack to intercept high flying bombers. ;) )

I mounted my pedals on a plywood plate, then made holes fitting two sets of wheels on my office chair. That works quite well, and it's easy to set the chair up for flying. And easy to fold away when I'm not flying: Also, the swivelling doesn't bother me much: With both feet resting against the pedals, the forces more or less balance out, so it's not a problem, even with quite heavily spring-loaded pedals like here.

There are some missing textures in the new P-51 cockpits. These are only visible when sitting in the cockpit. Otherwise, the refreshed P-51 looks marvellous. Open Beta, 2.5.4.30038.

May I ask, why don't you have any logs? There's a Logs folder in your DCS Saved Games directory, you can find the latest and next to latest log there at all times. Try to look in them, they might give a clue.