MadDog-IC

Frequency doesn't matter, you just have to use the frequency selector as it was the on / off switch for the radio, from memory you just toggle it one way then the other, this is for the first and second radios only, the third works as advertized, this bug has been reported. https://forums.eagle.ru/showthread.php?t=215887 Regards, Ian.

So far there is at least two users with this issue in DCS, one with Win8.1 and Win10 (Both can't fly for more than 10-20 minutes without CTD and have exactly the same error in the DCS.log). I have googled the issue to find a solution, hence, my large post earlier, there is no clear cut answer, DCS is not the only game having this issue so it is more of a Windows (Patches or settings), Nvidia (GPU drivers or settings) or general hardware conflicts (Overheating CPU, GPU or Overclocked CPU, GPU, RAM or a PSU that can't deliver enough power on demand), this goes beyond just simple troubleshooting. This one is just too hard to talk you through advanced things to try, I have never had the issue so can't replicate it. Hopefully ED or some other users may be able to help you. Regards, Ian.

You don't seem to be using a pagefile. Try this: In computer BIOS, set XMP profile off (Memory timings) and manually set RAM timings to ones that were supplied for the Dimm RAM (On packaging hopefully) or from manufacturers website. Set the Windows system performance options to "Automatically manage paging file size for all drives". Alternatively set the Windows system performance options to 32Gb paging file size. Check the total size of all files in your "c:\Windows\System32\DriverStore\FileRepository" including all subdirectories, is it in the multiple gb or just 1 or 2gb ??? There a few Window 10 updates that could be causing the instability also. Regards, Ian.

Can reproduce problem in DCS OB (Using the good report and test mission), but "NOT reporting" as it is fixed in internal version of DCS, so it should be corrected with the next release patch of DCS OB / Stable. Regards, Ian.

Copy the mapResource file out of the .miz file and edit with "NOTEPad ++" (Free programmers editor), don't use wordpad or notepad. Once edited copy back the mapResource file into the .miz file. If you have header problems, there is some more serious issue in the .miz file, can't give a solution but one of the files is going to be corrupted, its stored crc code doesn't match the re-calculated one, but would be happy to have a look at faulty mission .miz file for you if you can't sort it out. I use "total commander" for all file, zip and .miz manual file copying, with Notepad ++ as editor. Regards, Ian.

Log looks really clean except for that dreaded DirectX error still, the one that is causing a lot of problems with mainly GTX-1080 based cards. Quote from another user: The problem can arise if the gpu bottlenecks the cpu or vice versa, and then you get the error 'failed to map the vertex buffer . . . '. It can be caused by quite a few things: Including too high settings in the game. A driver issue. Weak CPU and strong GPU and vice versa. Corrupt file(s). Faulty GPU (maybe). Not enough system RAM. Not enough VRAM. Other hardware issues. Simply, Vertex buffers are used to optimise or share processing by both the CPU and the GPU. Vertex Buffers provide us with a mechanism of being able to load vertex buffer data into the CPU (and RAM), while at the same time allowing the GPU to process an earlier batch of vertex data. This gives us a good image at reasonable frame rates. Problem talked about in other ED forum: https://forums.eagle.ru/showthread.php?t=157540 I really can't see anything wrong within the log provided, virtually no errors at all shown, which would suggest to me, that DCS is functioning reasonably well, but your system has some issue with GPU processing for DCS. Suggestions: Some revisions of Window 10 updates have caused issues in the past and had to be rolled back to fix the issues, but I don't run Win 10 so I can't state what works and what doesn't. As your physical system RAM is only 12gb I would increase your Windows Pagefile to 32gb, but try 52gb or system managed as well (just a hunch, test and see if it makes any difference at those three settings). Try Deleting all files in the: "C:\Users\Pierre\Saved Games\DCS.openbeta\fxo" and "C:\Users\Pierre\Saved Games\DCS.openbeta\metashaders2" folders. If you have bit defender or Antivirus enabled, put a entry in their exclusion lists for the DCS folder, so scanner will not be doing on the fly checking or files as DCS runs. Try reducing some graphical settings in DCS config, Preload radius and other heavy settings. Try running system in 1080p temporarily instead of 4k res to see if that make a difference. Use GPU-z or MSI afterburner utility to monitor what performance your card is doing when running game (Any anomolies). Try DCS on a faster SSD drive maybe. Stuck for anymore suggestions. Regards, Ian.

Will need the following info: To see one of your current DCS.log files produced when CTD happened. What mission / missions are you using when problem happens ??? What aircraft you flying when it happens ??? Does it happen in Single player and / or Multiplayer when it CTD ??? Dxdiag.txt looks ok, so far as graphics drivers installation. Regards, Ian.

This points to a faulty GPU driver installation or your graphics card is not up to DirectX 11 standards, (Although the GTX-1050Ti obviously is capable). Laptops are usually problematic with GPU's for what ever reason and not supported by most game manufacturers. Because you have both an integrated graphics card in CPU and the GTX-1050 the system may be a bit confused, as is shown in your DXDIAG report, I have highlighted the entries that show "UNKNOWN" where they should show useful information about your GPU drivers capabilities, I have only shown the GTX-1050Ti. Exert from your DXDIAG log errors: An Exert of my DXDIAG report to show what a graphics driver install should look like: So solution would be to fix the Nvidia GPU drivers, this might involve using DDU utility to remove all traces of Nvidia drivers from system and then download drivers from NVidia and re-install the drivers for the GTX-1050Ti again and recheck with DXDIAG report to see if it seems installed correctly re: my report. Regards, Ian.

No expert with USB stuff, but I do know different chip sets with v2.0 and v3.0 ports can make a huge difference as to what peripherals will work correctly (Looks like that card you used comes recommended). Each USB root hub or port does have a limited amp rating of 500ma (self powered) as far as I know, so could easily be overloaded with multiple devices on the same shared Root hub (causing some issue). Shared IRQ lines between USB controller and other peripherals could also be involved in problems. I had issues with my X52 pro joystick playing up, swapped around some USB ports and left the microsoft USB drivers installed for win8.1 and works pretty good, but if I load the drivers for the actual chipset (Asmedia) that is on the M/B for those USB ports it doesn't work very well at all. Also recommend that you go into Computer -> Manage Devices -> Universal Serial Bus Controllers -> All HUBs and turn off the selective power OFF options (Allow computer to turn off USB port to save power). Best of luck with it. Regards, Ian.

Can't see to much wrong with it, but: One thing that sticks out is the multiple times that your controllers get initialized, it may be due to them disconnecting and reconnecting during gaming (Issue with your USB ports / HUB) or you just run multiple missions and it has logged them correctly (I thought DCS made a new log for every run of a mission). Nvidia's GPU 400 series drivers for me have been a nightmare on my rig (YMMV), 411.xx seemed to work ok initially, but would cause my machine to lock solid when DCS was running and in other games and senarios, only options were the reset button or turn of the computer. Tried the 416.xx drivers and once they were installed my computer was totally unusable, windows run so slowly it took a mouse click minutes to happen, it was like the worst spyware infection I have ever seen on a computer, my machine was so slow, it took me more than 1+ hours to just get the drivers uninstalled and rolled back to the stable 388.71 drivers that have always worked well for me. You might try some different versions of GPU drivers and check out your USB port setup for you peripherals. Regards, Ian.

Mission supplied is so wrong: The players Su-25 flight has no waypoints at all. The second Su-25 flight is AI driven with waypoints (I assumed you may have changed them around eventually). Waypoints from runway are incorrect in that the don't fly into wind, as there is none, for plane to fly towards the first waypoint after take off, you have to go to the weather section and point the ground wind towards the end of the runway you want to take off from and add 2-3 m/s of wind pressure (This would account for the waypoint being a long way a way as you take off from the wrong end of runway and have to do a complete 180 degree turn to go to waypoint 1, effectively twice the distance. The final landing waypoint, whilst on the runway is actually still set as a "turning point", this needs to be changed to "Landing", the waypoint will snap to the runway when done correctly. Did all the changes needed and tested "Players" flight and waypoints work as expected. Regards, Ian. Test - Users SU25T Landing Practice.miz

I have uploaded a few within the last couple of weeks without problem, this is after reading someone elses report of upload issues. Be logged in to site, obviously ;-) The only issue I have every had was that one campaign I was putting up was over 60mb which was the max size allowable at the time so it wouldn't upload , now the limit is 100mb I think. Regards, Ian.

As I haven't played around with missions to much lately, and my memory is very fallible (I could be slight wrong with some of my advice, and I would normally make a mission to test my assertions, but I grow tired of doing this on a daily basis), I would suggest you follow Feefifofum's advice, he knows what he is talking about. All the best, Ian.

This is correct: - Uncontrolled : according to the manual if it is checked the flight will appear "static" on the tarmac and go alive when it is supposed to start. - Delayed activation : (Unit will not appear in mission until you use a trigger command of "Group activate -> Unitname".) - When I setup the starting time at 8:03 on day 10 (see picture) although I am day 0, at 8:03 it appears. (This shouldn't happen unless you have uncontrolled ticked, This is the same as a Delayed activation, plane shouldn't show in mission until you use a trigger command of "Group activate -> Unitname".) I would like that an F5 IA appears on the tarmac when I enter the simulation and start for takeoff a bit later. (To do this, use the Uncontrolled function, Set the time you want it to start, but do not specify a different day). Regards, Ian.

Been testing your issue, and it is broken, they will not disperse under any conditions. I think this already been reported, can't find a report so I entered a new one. The "Condition Box" is the likely hood of that Group showing up in mission, randomized I think, so if set to 50% will only show up once in two run through of mission. Regards, Ian.

Haven't been able to help you due to: What seems like an incomplete dcs.log, which might be truncated by your crash, but I would prefer for you to attach the dcs.log file itself instead of posting text from it and possibly the DXdiag.log also. I really can't see anything wrong within the log provided, virtually no errors at all shown, which would suggest to me, that DCS is functioning reasonably well, but your system has some issue or is just not up to minimum specifications anymore. Suggestions: Some revisions of Window 10 updates have caused issues in the past and had to be rolled back to fix the issues, but I don't run Win 10 so I can't state what works and what doesn't. As your physical Ram is only 8gb I would increase your Windows Pagefile to 24 or 32gb. Whilst your Nvidia driver is an older one it is close to one I used exclusively on my win 8.1 system due to all newer versions being rubbish. However you have windows 10 and you probably should update to a newer GPU driver such as 411.xx or 416.xx (YMMV). Also your GTX-770 has only 2gb of onboard Ram which may longer be enough for running DCS and would require a hardware upgrade to a GPU with 4-8gb of ram. Try Deleting all files in the: "C:\Users\Stéphane Parent\Saved Games\DCS\fxo" and "C:\Users\Stéphane Parent\Saved Games\DCS\metashaders2" folders. Regards, Ian.

Others would be better suited to give you answers on those questions in the hardware forums. RTX graphics cards are just highly overpriced, under performing hardware with reliability issues as per some reviews. I can't afford exotic hardware like that here in Australia: GPU: GTX-1080Ti @ $1200 GTX-2080 @ $1300-1600 GTX-2080Ti @ $2100-2250 VR: HTC Vive Virtual Reality Headset kit @ $950 HTC Vive Pro Virtual Reality Headset kit @ $2200 PSU: 1000w Power supply @ $300-$400 To just upgrade my exiting computer for VR would be $2550-$4850, never going to happen no matter how much I might want it. Regards, Ian.

The bad news I suspect is that the Graphics card (GTX-570) is no longer capable of running DCS due to its low onboard ram (only 1.2gb), the requirements have been slowly increasing and would now require 3 or 4gb or better of dedicated onboard texture ram. My GTX-780 feels like its days are numbered for DCS also, but just hanging in there at the moment. System specs for DCS: Can't help anymore, as you need hardware upgrades (Sorry for bad news). Regards, Ian.

Definitely a hard one. I feel the fault has to lay somewhere with in the hardware you run or windows and software configuration (System specs would be handy to know and which antivirus). I don't do much with Autoupdate_log.txt normally, but it couldn't hurt to have a look at it, no matter what state it is in, preferably after doing a fresh install and then at the first update that happens to download something. What about your hdd file systems, have you run chkdsk on them to check for any corruption. Are your hdd with DCS game on it formatted in NTFS and not FAT32 (Must be NTFS with correct privledges) ??? Do you install all of your software with the "Run as Administrator" right mouse click menu option ??? Have you run DCS as administator. Which modules have you purchased and installed, have you just been running the default DCS free modules and caucusus map ??? What happens on screen when you run DCS, does it show any loading screen and progress bars, just a flash of black box and back to windows desktop or something different ??? Do you have any intergrated graphics card built into you CPU, could DCS be using that incorrectly ??? Your running std 1920x1080 on single screen, or something a little more exotic ??? To help with diag: Add this "log.set_output("dcs", "", log.ALL, log.FULL); -- Full output Log" to your "..\Saved Games\DCS.xxxxxx\Config\Autoexec.cfg" file for a more complete DCS.log debug fault report. Run at command line with admin priv: dxdiag /dontskip /t dxdiag.txt to get a complete showing of you system stats in a file. Regards, Ian.

No real hints from that log, seems to be doing ok, then just stops, so can't recommend anything really. Were log ends is about were it would be reporting what graphics card you have and amount of its on board ram, so maybe a problem still with the graphics cards driver, I doubt it tho. Run generic command line "Dcs_Updater Cleanup" to check for any MODS you may have forgotten about. Window 7 x64 should have service patches 1,2 or 3 installed or DCS wouldn't have run in the first place. Would need to see the Autoupdate_log.txt from that update to see what modifications it did (In your DCS games root folder). Regards, Ian.

Its much better if I get a full log report, snippets aren't much use, I can't see what system your using, what graphics driver and make of card you have, swapfile settings, Windows version, DCS version and so on. I usually will not respond to such requests that don't have dcs.log and / or things you have tried to remedy the situation, I look at most logs posted for issues, but only will respond if I think I can help. What you have given me, leads me to believe that DCS can't determine if you have a Nivida GPU or a AMD GPU and as such, all required drivers aren't installed incorrectly. 2018-10-27 19:47:51.898 INFO DX11BACKEND: NVIDIA API init OK 2018-10-27 19:47:51.900 INFO DX11BACKEND: AtiAPI_Initialize Error If initializing the Nvidia API OK, then I would suspect you have a Nvidia GPU of some sort, so why it is even trying to init an ATI API and failing. I can only guess you have left overs from one of the other ATI (AMD) GPU manufacturer (Never a good thing to have a mix of old ATI (AMD) drivers and new Nvidia drivers) and I would use the DDU util to remove all drivers for all Nvidia and ATI (AMD) graphics cards, download official drivers for the card you do have and reload those drivers as "run as administrator", have any antivirus disabled whilst doing so, as they can't interfere with installs. Regards, Ian.

Issues noted with remedies: Your quite low on ram, I would up your pagefile some more 8gb ram + 24gb pagefile. Autoexec.cfg has a syntax error, correct or rename file to stop running for testing ATI Graphics card driver doesn't seem to be installed correctly, doesn't show a driver version (Not quite sure if this is normal or not), but would reload supplied one from AMD and not a windows default version, would install the VC++ package first as most graphics drivers need that to be going to install correctly or at all. Problem with the "MICROSOFT Visual C++ Redistributable Package", either missing of corrupt - reload or repair it. https://www.digitalcombatsimulator.com/en/support/faq/556/#1490800. Backup / rename your old "Saved Games folder" if you have one and let DCS start with a default set of configs for testing. Run DCS and see if helped or not. If working better, redo controls and other configs. Log errors: Regards, Ian.

Can't replicate, seems to work here, no problem placing F-18c Lot 20 aircraft and changing liveries. Can't offer much help with out logs, but I would backup / Rename your "..\Saved Games\DCS.openbeta" folder and let it create a new one and give that a quick try to see if remedies the issue (suspect problem would be in the "..\Saved Games\DCS.openbeta\MissionEditor" directory). If that fixes that issue, then reconstruct from you original copy for controllers, logbook and other needed settings, if not just restore the backup to its original place / name and try something else. Regards, Ian.

Problems from Log: Log indicates you have Mods installed, they aren't authenticating, if you updated with those installed, probably broke things. Getting DirectX disconnect, so graphics card is disappearing from system so driver can't function or vise versa. Resolution: Remove Mods manually or run DCS_updater cleanup to check for non-standard DCS files (Left over MODS) and allow it to remove them for you. Usually bad nvidia graphics driver install causes the directx problem, would recommend going back a version, and using DDU to clean out all traces of driver and reloading. (Personally I had issues with v416.xx, but v411.70 seems to work better for me and win8.1), you mileage may vary. Once steps 1 and 2 done, re-run DCS and check that it now runs correctly, then slowly introduce you MODS back in one at a time, just to see if any of them break DCS again. Regards, Ian.

I concur, the same from me, i've never had a problem with this technique, the AI will never drop weapons under fire. Haven't tested recently though. Regards, Ian