mkel2010

I've been trying to figure out a way to pre-set F-16 cockpit knobs through the Mission Editor. The clickable cockpit command works well for switches, not so much for knobs that need to turn. I've researched using setCommand but cannot see the required commands for the knobs in the Controls settings. According to what I've read in the DCS manual, hovering over the name in the far left column of the Controls page should provide the command numbers for setCommand, but all I get is a name. Specifically, I'm trying to turn off the Comm 1 and Comm 2 power knobs at start up. Edit to add: I've set the Options and Commands tooltips to true.

I don't know if the plugin you're using is from ED or a user called Tobi. I found that Tobi's EDM plugin would not work with anything above Blender 2.X. Downloaded an earlier version of Blender and it worked fine. You might try that.

Years ago this may have been the case, but not any more, particularly if you're not running a full security suite and are using just an anti-virus. This is one of the many articles out there that debunk the old premise that anti-virus causes latency on gaming machines: https://www.kaspersky.com/blog/tests-gamers-antiviruses/47576/

I think it really depends on the horsepower of the computer and the AV itself. Bitdefender, running in the background for me, takes virtually no CPU cycles and uses under 1.5 GB of RAM. I get no changes in the resource usage by Bitdefender when starting DCS (monitoring with Process Explorer.) There is little point in running an AV if you're excluding large chunks of data on a system.

Another AV option (better than either McAfee or Windows Defender, IMO) is Bitdefender. I get ZERO false positives with DCS files.

For some reason it didn't work for me the first few times, but does now. Thank you. Do the created kneeboards get pins assigned to them based on the groups in game?

@AlaskanGrizzly After watching the video on your website about changing and modifying groups, I find that there is no option to deselect individual files like you showed in the video (No checkbox next to each page.) Is there a different method to use for this process?

Try excluding your DCS World and Saved Games folders from your Anti-Virus. Once you get them excluded, I'd suggest running a full repair before you try DCS again.

@cfrag: I get the idea behind the ATC traffic recordings in the mission. Is there any way to move them to a frequency other than the Anderson AFB tower frequency? On the Cold Start mission I could not get a response from the tower for anything (with the exception of after landing I did get the taxi to parking blurb.) It seems like the recording playback has stopped the game's ATC responses on that frequency.

I've got the issue figured out. I'm using the JanJan plugin for VA and discovered that the comms menu needs to be open for the game to respond to the ATC voice commands.

@Lord Vader Did you read my last post? I AM NOT USING VAICOM!!!! This is not a VAICOM issue; VAICOM is not installed in my system!!!

No, I'm not using VAICOM, just Voice Attack by itself.

I have Easy Comms turned off. Whenever I use voice commands to contact ATC, i.e., to request startup, taxi and take off, I get the repeats of my command by the game but no response to the request from ATC. I end up needing to use the F-Key commands on the Comms menu and the response from ATC is almost immediate. I have the radios tuned to the correct frequency. Any way around this issue or is there something else I need to be doing? Another issue I've noticed is that after ATC issues the take-off clearance and I start to taxi onto the runway, ATC tells me they are unable to clear the take-off, followed shortly by a repeat of the take-off clearance. Any ideas on that?

So I've been having a back and forth email conversation with ED regarding my bug report. The last two messages I received are pasted below. Bottom line: this is the first time a DCS update has required a reboot and the programmers are aware of the issue and are looking for a fix. "Programmers are already aware of the problem and may be able to find a way to prevent the game from restarting the system without user permission in future updates. I once again apologize on behalf of the ED management for what happened. Sincerely yours Alexander Maximov" AND "Mark, this is the first update that requires a system reboot. I sincerely hope that such updates will not become the norm for DCS. Good luck! Sincerely yours Alexander Maximov"

It may well be a Microsoft issue. That said, I run a number of other programs that require .NET frameworks or other run times to be installed as part of an installation or update. NONE of them use a silent installation. This is a choice by someone at ED to run them silently and in my experience it doesn't have to be done that way. My computer is used for many things and there may be (often is) a reason I wouldn't want to reboot arbitrarily since other processes might be running.

False positives from Norton.

I took a look at the Autoupdate Log (in my case marked as the old log because of the repair I did following the reboot.) Interestingly, the log ends with the following lines: 00086.362 STATUS: Cleaning up... 00086.362 STATUS: Cleaning up... 00086.501 STATUS: Successfully updated to 2.9.7.58923 00086.501 STATUS: Asking Yes/No: OS restart is required before running the application. Restart now? 00086.501 STATUS: Got YES when asked: OS restart is required before running the application. Restart now? 00086.513 === Log closed I never was prompted to give permission to reboot so clearly this is a bug in the updater or the update process. I was sitting there watching the update so I know for a fact the prompt was never issued. The log file is attached and I am tagging @BIGNEWY. In reviewing the Windows System Event Log, I found the Event where the reboot was initiated: The process C:\Program Files\Eagle Dynamics\DCS World\bin\DCS_updater.exe (XXXX) has initiated the restart of computer XXXXX on behalf of user XXXXX\Mark for the following reason: Application: Installation (Planned) Reason Code: 0x80040002 Shutdown Type: restart Comment: OS restart is required before running the application. EDIT: A Bug report has been submitted. autoupdate_log_old.txt

As @rob10 said, you've likely got more issues with your hardware. Windows is finicky sometimes and not easy to troubleshoot. My issue was just during the update, otherwise DCS is solid on my machine. Google system file checker and run that first to make sure you don't have a corrupt operating system. You can also dig through the Windows Event logs to around the time of a crash to see if you can get an idea what's causing your issues.

If properly coded, the component that needs to reboot should warn the user ahead of time and not arbitrarily reboot a system. If what you described is truly the reason, then there is a bug in the process.

I used the launcher today to install the latest update. Towards the end of the process, I suddenly received the Windows "Restarting" screen and the computer rebooted. On restart I did a Repair DCS and ran it through the slow option. That reported everything was updated correctly. There are three log files that are timestamped around the time this all occurred. I don't think they show anything but are attached anyway. dcs.log cef_log.log dcs.log.old

The same thing happens with the stock personnel, i.e., the Carrier LSO

Not sure if this is a bug or by design: When I place a static personnel unit from the Massun Humans pack under a parking shelter at Nellis AFB on the Nevada map, the unit ends up on the roof of the parking shelter and not on the ground. I can place aircraft under the shelter and that works fine. Any ideas?

You need to modify the model viewer autoexec file to point to the Saved Games Folder. Starting about 3:01 in this video tells you how and what you need to modify:

I've been using the Model Viewer from the bin/mt folder without issue. Have you tried repairing DCS?

Thanks for the link. I would caution against making the file read only, however. You never know what other changes might be made during subsequent updates that could cause unforeseen issues. This may be one of those things that will need to be manually changed with each update.