Hiromachi

https://forums.eagle.ru/showthread.php?t=212795 Just get back to default and then select preferred cockpit language again.

BadHabit, I forwarded your question and received information that explains this briefly. As you are possibly aware, an average joystick has movement of 4-6 cm measured in the middle of the hand grip. Aircraft stick has 10-15-22 cm movements (front, side, back). This means that for 1 cm side joystick movement you have simulated 1/4 - 1/6 of aircraft stick movement, which is 3.7-2.5 cm. And this is the source of your (and our) problem, as there is less precision with such a limited movement with the joystick. To move aircraft stick for 1 cm, you need to move your joystick for 2.6-4.0 mm. The other aspect is that aircraft has a max roll rate of ~420 deg/sec (IIRC). DCS MiG-21bis has to cope with the above limitations but maintain realistic levels of roll rate. And those are a bit opposing goals.

But I do not get similar issue in other games, nor when benchmarking. Thats the thing. I can reinstall gpu drivers, use software to clean the logs but not sure if this will help.

More, but those were large so coming from google drive: https://drive.google.com/file/d/1ft4TWWljKy248_VzsSjZTsJQMnxOXZrZ/view?usp=sharing https://drive.google.com/file/d/12dddxL5mY31l3GjvkS4hHyclJsI85X-1/view?usp=sharing dcslog.rar

Tonight after some break Ive been trying to get back to flying online on multiplayer and encountered a number of situations which resulted in game freeze (had to open task manager and shut down game) or game crash. I've been trying to find the root of the problem and nonticed a considerable amount of driver or api related issues. From the last log: 2018-06-22 21:35:11.826 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2018-06-22 21:35:15.274 WARNING LOG: 4 duplicate message(s) skipped. 2018-06-22 21:35:15.274 ERROR DX11BACKEND: failed to create index buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2018-06-22 21:35:15.274 INFO EDCORE: try to write dump information 2018-06-22 21:35:15.275 INFO EDCORE: # -------------- 20180622-213514 -------------- 2018-06-22 21:35:15.277 INFO EDCORE: C:\WINDOWS\SYSTEM32\d3d11.dll 2018-06-22 21:35:15.278 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 5DC927B0 00:00000000 2018-06-22 21:35:15.279 INFO EDCORE: 00000000 00000000 0000:00000000 2018-06-22 21:35:15.280 INFO EDCORE: 5DC927B0 003EE440 0000:00000000 C:\WINDOWS\SYSTEM32\d3d11.dll CreateDirect3D11SurfaceFromDXGISurface()+4E7D0 2018-06-22 21:35:15.282 INFO EDCORE: 269C5731 003EE490 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\dx11backend.dll ?getBufferManager@DX11Renderer@RenderAPI@@QEAAPEAVDX11BufferManager@2@XZ()+541 2018-06-22 21:35:15.282 INFO EDCORE: 2AF3BFDA 003EE500 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\Effects.dll ??4GraphicEffect_Impl@Effects@@QEAAAEAV01@AEBV01@@Z()+2A4A 2018-06-22 21:35:15.283 INFO EDCORE: 2AF3A453 003EE6A0 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\Effects.dll ??4GraphicEffect_Impl@Effects@@QEAAAEAV01@AEBV01@@Z()+EC3 2018-06-22 21:35:15.283 INFO EDCORE: 2AFC675B 003EE790 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\Effects.dll ?release_effects@Effects@@YAXXZ()+33CB 2018-06-22 21:35:15.283 INFO EDCORE: 2AFC5E0F 003EE8A0 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\Effects.dll ?release_effects@Effects@@YAXXZ()+2A7F 2018-06-22 21:35:15.284 INFO EDCORE: 3818C269 003EE950 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe 2018-06-22 21:35:15.285 INFO EDCORE: 3818DB4A 003EEB30 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe 2018-06-22 21:35:15.285 INFO EDCORE: 33E25CD0 003EEC00 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\WeaponsBase.dll ?explode_@?$wShellImpl@$0A@@@IEAAXXZ()+170 2018-06-22 21:35:15.285 INFO EDCORE: 33E24D6D 003EED80 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\WeaponsBase.dll ?simulate@?$wShellImpl@$0A@@@UEAA?AW4eSimulationResult@wActivityGroupMember@@NAEA_N@Z()+10D 2018-06-22 21:35:15.285 INFO EDCORE: 33E1FDE1 003EEE00 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\WeaponsBase.dll ?makeObjectStep_@wShellGroup@@IEAA?AW4eSimulationResult@wActivityGroupMember@@PEAVwShell@@N@Z()+31 2018-06-22 21:35:15.285 INFO EDCORE: 33DF5E97 003EEE60 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\WeaponsBase.dll ?simulate_@wActivityGroup@@IEAAXPEAVwActivityGroupMember@@@Z()+147 2018-06-22 21:35:15.286 INFO EDCORE: 33DF5B3A 003EEEE0 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\WeaponsBase.dll ?NextEvent@wActivityGroup@@MEAAXXZ()+7A 2018-06-22 21:35:15.286 INFO EDCORE: 4850DA93 003EEF60 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\World.dll 2018-06-22 21:35:15.286 INFO EDCORE: 4850E041 003EEFC0 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\World.dll 2018-06-22 21:35:15.286 INFO EDCORE: 38171396 003EF030 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe 2018-06-22 21:35:15.286 INFO EDCORE: 38181FE8 003EF090 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe 2018-06-22 21:35:15.287 INFO EDCORE: 37DDA25B 003EF0C0 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe 2018-06-22 21:35:15.287 INFO EDCORE: 37DDBFFD 003EF8A0 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe 2018-06-22 21:35:15.289 INFO EDCORE: 383084D3 003EF8E0 0000:00000000 D:\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe 2018-06-22 21:35:15.291 INFO EDCORE: 62AC3034 003EF910 0000:00000000 C:\WINDOWS\System32\KERNEL32.DLL BaseThreadInitThunk()+14 2018-06-22 21:35:15.291 INFO EDCORE: 64731431 003EF960 0000:00000000 C:\WINDOWS\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 2018-06-22 21:35:15.426 INFO EDCORE: Minidump created. System as in spec below, laters drivers and windows with most of the recent updates. Logs and dxdiag attached. DxDiag.txt dcs.log-20180622-213514.zip

Try now. There is no indication in the patch notes, but seems that all the code was part of this update. I've just downloaded patch and checked it on my side on open beta client: Seems this issue is part of history now :)

Did you check and adjust brightness of the reticle ? Could you post your log please ?

No, there were some animation problems and those were fixed few weeks back: Fixed RSBN NPP Glideslope animations. But there might be an issue of a different nature. We're looking into it already.

Could you be so kind and attach your logs ?

SP. I have to try it on MP yet. It works best on Persian Gulf since this map gives best performance overall.

Hmm, I still have SSAA 1.5 available at 1440p. I even managed to find sweet spot with SSAA 1.5 and MSAA x2, sitting above 50 FPS and in the air above 65 FPS.

What do you mean by the performance ? You mean the FPS you experience in that module ? There was already some work done on that matter since November and results of it were released in December as an updated collision model: https://forums.eagle.ru/showthread.php?t=156639&page=6 As for the rest, the 3d model itself and textures are within the limits so there are really no improvements that could be achieved by messing with it. Personally Ive been flying for a couple hours on Persian Gulf and cant spot any difference to other birds. With the rig as in signature and settings on high I have around 80 FPS on the ground and stable 100 FPS in the air. That I consider very good. I will ask what else could be done, perhaps something else can be figured ;)

While everyone is learning F/A-18C I took MiG-21bis for a spin. It fits so well this map.

Dear pilots, today we have for you a small update to give you a better picture of what is going on. Firstly, we would like to inform that the issue with MiG-21bis module and Persian Gulf map has been solved and you should be able now to enjoy flying Fishbed over the hot deserts of Iran or sand dunes on the outskirts of Dubai whenever you wish to. Secondly, while our programmers were working around the clock on solving that problem, our artist took his time to further improve cockpit details and add raindrops on MiG-21bis and CE2 canopy, which you can appreciate in the following video: Last but not least, while you will be enjoying MiG-21bis on a new Persian Gulf map, we've prepared a small tease of the Christen Eagle 2 spinning around Burj Khalifa and Burj Al Arab. Please, visit our website to see the entire gallery: http://leatherneck-sim.com/2018/05/30/quick-development-update/ Full list of changes is available here: https://forums.eagle.ru/showpost.php?p=3504350&postcount=11 Magnitude3LLC

So I've tried the following: SMAA x 1.5, MSAA x2, MSAA x 4, SMAA x 1.5 + MSAA x 2, SMAA x 2. Each of this on the same graphic settings, same resolution and stuff. I'm normally playing with MSAA x 2, which at 3440 x 1440p gives me 80-90 FPS in my rig. So any combination of MSAA and SMAA, even only MSAA x 2 + SMAA x 1.5 caused 30-40 % FPS drop. I was running at 50 FPS and that is on the lower end of my g-sync. Same with SMAA x 2. However it seems to me that alone SMAA x 1.5 gives better results and more detailed picture than MSAA x 2, while providing similar FPS so for the time being I will try the first one and see how I feel about it online.

I'm normally using MSAA x 4. Will try x 2 and SSAA x 1.5 to see if FPS is acceptable, but I dont think it will be good enough to run smooth on multiplayer server at 3440x1440p.

No it wasnt. It was complained by number of players due to creation of exactly what this thread mentions. An air quake, most of the time over Novo, which reduced fun for both sides. I find it weird that some decide to fly the most realistic simulation of this warbirds, but then wish to use them in the least realistic way ? Current mission on BS is a great improvement over previous mess and the only thing I wish for, is the provision of a single airfield in England and a bunch of Ai bombers to protect.

No problem, keep it coming. This only helps guys!

The lightning and illumination issues (which affect colors) are not something we can provide solution on our own alone, this issue was universally acknowledged as a bug by Ed. We're investigating what can be done to get the best out of it. See the following : Known issues External lights (flashlight, taxi light) are visible inside some cockpits. https://forums.eagle.ru/showpost.php?p=3493113&postcount=10

There was. No such issues were discovered during testing, we're investigating it. As for the second thing, its a simple livery mismatch. Just reselect livery as it was already suggested: https://forums.eagle.ru/showpost.php?p=3481261&postcount=4

Not every. This Burning Skies is the first time the airfields are more than 100 km apart. Previous ww2 servers and missions had airfields much closer - around 40 to 70 km and it always felt like things are too close. All too often Luftwaffe ended up on top of the airfields and all that developed on the server was vulching and air quake (particularly with mission on Caucasus map with airfields at Novorosijsk and Anapa) over Novo. Finally airfields are placed in a reasonable distance, though Id like to have a chance to take off from Britain as well. The problem is not the mission when it comes to low numbers.

Yep, the issue was sorted. It was just a problem with animations being flipped. Just waiting for the patch now ;)

Yup, and its already sorted. Just have to wait for the patch with it: https://forums.eagle.ru/showpost.php?p=3481022&postcount=3

I've tried it and no microstutters for me. FPS tend to drop in action but I havent noticed any stutters.

I got from Dolphin some detail on differences on Easy FM: 1. gears will auto-retract if IAS > 400 km/h and gears handle will return to neutral. 2. There is more stabillity on pitch (more damping), a mild stalling, no deep stall condition and elevator effectivenes limited at very high AoA (possible only in falling), 3. It is a bit better turning on ground (easier taxi procedure), 4. Soplo (nozzle) damage will not create vectored thrust, 5. There is no time limit for ChR use and engine is protected from the surge, Following will work if both "Game Flight Mode" and "Simplified engine management" are on: - engine won't shut down on high lateral or high negative longitudinal acceleration (such are in spins), - engine won't stop at low oil pressure time trigger, - engine won't shut down at low fuel pressure. Last 3 options will be available if either "Game Flight Mode" or "Simplified engine management" are on in the next patch.