speedbird5

Hi, The Special for joystick commands for Master Arm do not allow toggling between Off and Arm and Simulate when used with a button. They toggle to the desired position but when you let the button go, the switch moves back to the starting position. Is there a way to toggle this switch between the three states so that it can be bound to a button ? thanks

I observe elevator flutter in the M0.94-0.98 regime when under G and also observed when firing missile. Observable inside and outside aircraft. Caucuses map. Single player mission.

Bingo. thanks

Does anyone know why the LSO says “Abeam all down Tomcat” when I am in the Hornet ? It used to say “Abeam all down Hornet”. Heck I don’t even own the Tomcat.

Try this....

Thanks - IAS is now showing. I didn't realise there were two separate .acmi files for the same mission. :doh: Also, one thing that is not clear is how to set the Tacview options on the server - to set things like delayed playback etc. I eventually worked out that by manually adding a Tacview section to the plugins section of the options file in the saved games folder for the server I could change those settings. When you run the server with no-render, you cannot access the Tacview options under Special. Is there an easier way to set these options in the server or is the only way the manual editing?

Logs attached dcs.zip

The F/A 18

Hi BusyBee, I still cant record my IAS if I join my own server as a client. As i said, I have a server set up with Tacview installed on the server and also installed locally. The server is installed as the same machine as DCS. I have "Allow Sensor Export" and "Allow Player Export" in the server - see attached image. I have the Tacview options as shown below. What am I doing wrong ?

bob, great considerations. Thanks.

Thanks for the great info Fused. At this stage I am just trying to investigate the feasibility. I will report back if I end up going ahead.

Thanks Bob. 60 FPS is perfect for me. I am very doubtful about SLI as the implementation doesn't seem to be right. I will start with one card at this stage

TheNelphim, Ok so you are saying DCS can not be used with two separate GPUs, one for each projector ? Romeokilo is successfully running two 1080 p projectors off one 1080 ti. What do you think would be the max resolution for two projectors you could run off a 1080ti and if I upgrade, a 2080 ti ?

Hi, I want to set up a curved screen as Romeokilo has done in the image below... He is using two 1080P projectors... However, I want to run two 4K projectors and use warping software to display the images on the curved screen using two viewports. My questions are: 1. Would it be possible to smoothly run two 4K projectors from one graphics card with my current system ? - system specs are in my signature below. 2. If not, can DCS use two graphics cards (Not in SLI) so that one GPU drives each projector/viewport ? 3. If so, how do you set up DCS to use two graphics cards ?

Hi, I have a server set up with Tacview installed on the server and also installed locally. The server is installed as the same machine as DCS. I cannot get it to record IAS when I view the .acmi file in Tacview from a mission run on the server. I have the Tacview options as shown below. However, when I play the same mission in SINGLE player, it does record IAS. How can I get it to record IAS when I play the same mission on the server ? I have Tacview Starter 64 Bit Demo with 14 Days left on the demo - not sure if this is relevant.

Hi RomeoKilo, I am thinking of using the same screen and projector setup as you except using 2 x 4k projectors with two non-SLI GPUs. Is it possible to set up DCS world so that each projector uses a separate (non-SLI) GPU ? If so, how ?

Hi Damien, First, thanks very much for the analog slew sensor, it is great and a huge improvement. I would however, like to make one suggestion. Please see image below. I think the sensor could be improved by making the shaft of the sensor where the finger cap attaches a bit shorter so that the throw isn't quite as long. This would give you better control. I would like to modify mine by shortening the shaft by about 2-3 mm, (or maybe 1-2 mm), but would that mean I would also have to shorten the shaft of the finger cap as well? How can I cleanly shorten the shaft without damaging it? Can you think of a better solution?

Hi all, Just received and installed my Deltaalphalima1 analog slew. Wow ! What a difference !! So many dead SU 27s !! One point to note is that after calibrating 3 times with the supplied calibration software, the sensor would not centre and the TDC Cursor would constantly drift on the radar in the F-18. The solution for me was to go into the Windows Game Controller Setup and then select the throttle > Properties > Settings > Reset to Default. As soon as I did that, the sensor was centred within the DCS Axis Controls. I did the above after I had calibrated the sensor, but maybe it should be done before. Anyway, working perfectly now.

Hi All, I have isolated the cause for the frequent recent crashes, at least on my machine. It is due to a recent Windows 10 security update KB4338832. I uninstalled it and the crashes ceased. Once I uninstalled it, I used this tool from Microsoft (http://download.microsoft.com/download/f/2/2/f22d5fdb-59cd-4275-8c95-1be17bf70b21/wushowhide.diagcab) to hide the update so that Windows Update would not automatically reinstall it. Hope this helps.

Hi All, I have isolated the cause for the frequent recent crashes, at least on my machine. It is due to a recent Windows 10 security update KB4338832. I uninstalled it and the crashes ceased. Once I uninstalled it, I used this tool from Microsoft (http://download.microsoft.com/download/f/2/2/f22d5fdb-59cd-4275-8c95-1be17bf70b21/wushowhide.diagcab) to hide the update so that Windows Update would not automatically reinstall it. Hope this helps.

Yes, I suspected it might be a Windows issue in an earlier post of mine. Thanks for that info. My card is exactly the same as yours, with the latest Nvidia driver as well. So this is very interesting, because I checked my system and it only had KB4338832 installed when I was getting the crashes. So maybe it is that update alone which is the culprit.

Can you remember exactly the name and number (eg KB1234567) of the Windows security and OS updates you uninstalled? Have you done further testing?

Hi F900EX, I ALWAYS use DDU to uninstall my old Nvidia driver before I install the latest one. It has not helped for me. I have now had crashes due to three different dlls: nvwgf2umx.dll dx11backend.dll zlib.dll This is why I don't think it is an Nvidia Driver issue. I am not sure if it is the most recent DCS update or the one before which might be causing the problem. Then again, I installed the latest Microsoft update last week as well, so it could be Windows 10 that is the issue. BTW, there is a more recent version of DDU here: https://www.wagnardsoft.com/forums/viewtopic.php?f=5&t=1158

Hi F900EX, I did what you suggested but still got a crash after about 20 minutes. I have now had crashes due to three different dlls: nvwgf2umx.dll dx11backend.dll zlib.dll It's only started happening since the last update. 2018-07-16 01:45:58.692 INFO EDCORE: try to write dump information 2018-07-16 01:45:58.693 INFO EDCORE: # -------------- 20180716-014558 -------------- 2018-07-16 01:45:58.694 INFO EDCORE: C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll 2018-07-16 01:45:58.695 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 78447834 00:00000000 2018-07-16 01:45:58.699 INFO EDCORE: 00000000 00000000 0000:00000000 2018-07-16 01:45:58.704 INFO EDCORE: 78447834 26B0C140 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll OpenAdapter12()+361094 2018-07-16 01:45:58.705 INFO EDCORE: 78447A31 26B0C1A0 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll OpenAdapter12()+361291 2018-07-16 01:45:58.705 INFO EDCORE: 7844BD87 26B0C9E0 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll OpenAdapter12()+3655E7 2018-07-16 01:45:58.705 INFO EDCORE: 7844BFEF 26B0CA10 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll OpenAdapter12()+36584F 2018-07-16 01:45:58.706 INFO EDCORE: 783DA182 26B0CAD0 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll OpenAdapter12()+2F39E2 2018-07-16 01:45:58.706 INFO EDCORE: 783F3A2B 26B0CDB0 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll OpenAdapter12()+30D28B 2018-07-16 01:45:58.706 INFO EDCORE: 78363456 26B0CDF0 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll OpenAdapter12()+27CCB6 2018-07-16 01:45:58.707 INFO EDCORE: 782B9764 26B0CE30 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll OpenAdapter12()+1D2FC4 2018-07-16 01:45:58.707 INFO EDCORE: 782BECB7 26B0CEB0 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll OpenAdapter12()+1D8517 2018-07-16 01:45:58.707 INFO EDCORE: 78D3DAEE 26B0CF30 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll NVAPI_Thunk()+39910E 2018-07-16 01:45:58.707 INFO EDCORE: 78CE6641 26B0FB20 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll NVAPI_Thunk()+341C61 2018-07-16 01:45:58.707 INFO EDCORE: 782B6C05 26B0FB70 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll OpenAdapter12()+1D0465 2018-07-16 01:45:58.708 INFO EDCORE: 780F8BFD 26B0FC60 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll OpenAdapter12()+1245D 2018-07-16 01:45:58.708 INFO EDCORE: 783623A3 26B0FD30 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll OpenAdapter12()+27BC03 2018-07-16 01:45:58.708 INFO EDCORE: 783D571F 26B0FD70 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll OpenAdapter12()+2EEF7F 2018-07-16 01:45:58.708 INFO EDCORE: 783D565F 26B0FDA0 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll OpenAdapter12()+2EEEBF 2018-07-16 01:45:58.710 INFO EDCORE: 79198338 26B0FDD0 0000:00000000 C:\windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvwgf2umx.dll NVAPI_Thunk()+7F3958 2018-07-16 01:45:58.711 INFO EDCORE: BD9A3034 26B0FE00 0000:00000000 C:\windows\System32\KERNEL32.DLL BaseThreadInitThunk()+14 2018-07-16 01:45:58.711 INFO EDCORE: BE441431 26B0FE50 0000:00000000 C:\windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 2018-07-16 01:45:58.949 INFO EDCORE: Minidump created. 2018-07-16 01:45:58.949 INFO DCS: try to write track file

I have attached logs of yet another crash 2018-07-15 09:55:16.721 INFO EDCORE: # -------------- 20180715-095516 -------------- 2018-07-15 09:55:16.725 INFO EDCORE: C:\DCS World OpenBeta\bin\dx11backend.dll 2018-07-15 09:55:16.726 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 645DB65F 00:00000000 2018-07-15 09:55:16.728 INFO EDCORE: 00000000 00000000 0000:00000000 dcs.log-20180715-095516.zip