frostycab

That sounds identical to what happened to us, Drac. Flappie, thanks for the response. It might take a day or 3 to get his logs for you, but I'll have a go. He's not terribly savvy when it comes to tracking down files like that, so when I see him again I'll try to walk him through it.

Today I was doing some F-18 training with a friend. I was flying about 100ft off his wing each time. He'd set up for an AUTO drop, run in on the target, and the moment he pressed the pickle button his sim would freeze completely, requiring tabbing out and killing the process in task manager. From my point of view his plane would suddenly stop in mid-air, and hang there for a couple of minutes until he'd killed the process and disappeared from the server. I tried to reproduce the problem by making the same attack myself, but had no issues at all. This happened over and over again after he restarted DCS. I I got him to run a repair on his DCS installation and that didn't fix the problem. Does anyone have any ideas? Thanks in advance.

Wow! Thanks for replying so soon! Having run the same mission as a group yesterday we did run into most of the issues again, which does lead me to believe that many of the problems are related to DCS itself. One of our pilots managed to kill the same lamp post 4 times with mavericks when they were definitely locked onto a vehicle 30m away from it and attacking from different directions. LOL Regarding the carrier TACAN, yes I'm sorry, I meant to say 71X. I was thinking of a different mission I flew just before posting here. LOL. I'll have to check if this is reproduceable, but it seems that the carrier TACAN turned off for me around the time that I got the message about the fleet making a course reversal. When I eventually got back to the boat the fleet was still facing roughly northeast and had stopped moving. As for the issues around navigation and sensors I'm going to have to remember to save some track files to send to ED for insight. We found a couple of other odd things yesterday. The final tank on one mission took no less that 7 direct hits from GBU-12s and GBU-10s to finish off. Hopefully the next Open Beta update will sort out a few things behind the scenes. Thanks for all of these missions. Please don't stop making more!

Thanks. Is that where DCS saves the changes I make to all my profiles? Does that mean if I make a change without exporting the profiles myself, they'll be in there in the same state as when I closed DCS? That's brilliant!

Another point to bear in mind regarding the laser is when you apply power to the TGP. I got into the habit of just turning everything on during startup, and then rearming. I found that if I flipped the laser power on before the TGP was loaded then the laser would not fire. Cycling the laser power off and on again fixed the issue. I mistakenly assumed that when the TGP was connected to the aircraft the laser power would be applied when the ground crew plugged it in, but it seems like there's a flag in the software that isn't set to on until its state changes..

Hi Apache600! Thank you so much for these missions. They're exactly what my friends and I need for training up new pilots as well as refining the skills of our better ones! I do have a little question about the Persian Gulf Variable mission, which we ran during our last group flight this past Saturday. About 12 of us were flying on the server at the time, and every time any of us went anywhere near the carrier group everyone on the server got huge frame drops and lag which would last for several minutes. I tested this again the next day in single-player and got the same effect. Its very noticeable for regular players, and virtually stopped the sim for those of us flying in VR. Since then I tried to look at the mission in the editor to see if there was anything I could do with my extremely limited knowledge. I had intended to break the fleet up and spread out the 3 carriers along an East-West line with about 50nm separation to see if that would mitigate the problem, but the editor wouldn't let me move the ships, so I'm assuming that's something to do with the way the mission is built/scripted. The next thing I thought of was to reduce the size of the carrier group, so as a first step I deleted the Admiral Kusnetzov (along with its compliment of SU-33s, but that can't be helped. None of us fly the -33 in our group anyway.) and loaded the mission again. This time the sim remained smooth throughout single-player testing. We're hoping to run another multiplayer test over the coming weekend. Hopefully the changes I made won't break any of the scripts. Do you think this is due to having too many carriers in close proximity, or is it more likely that the Admiral Kusnetzov is bugged in some way? Is there a more suitable workaround to the one I've tried? Also, if you believe this isn't a mission issue then I was wondering if I should submit a possible bug report to ED. We had many other issues during the mission as well, though I'm given to believe that they are DCS-related rather than mission-related. For example, while running the long-range mission at Shiraz we ran into these problems and more: - A-10C targeting systems lost all elevation data, so all markpoints and TGP designations were useless. - Any Mavericks fired into the target area ignored their locked targets and flew into the perimeter fence. - F-18 TGPs sometimes wouldn't ground-stabilise correctly, sometimes jumping far off target randomly. - On my returning to the carrier from my third sortie I couldn't find the carrier using TACAN on 55X. The server had been running for about 6 hours at this point, and I'm wondering if the carrier reached the end of its route and deactivated(?) The error rate seemed to compound as time went on. A first sortie might go alright, but the next one could throw up all sorts of system errors. I fully expect most if not all of these to be issues with DCS itself rather than your mission, but I thought I'd tell you about them in case you wanted to have a look and have any insights.

One of the most annoying things I find I deal with in DCS is control mapping. Every time there is an update many of my HOTAS control bindings seem to reset to their default settings. I've found the option to save my bindings for each aircraft, but unless I'm doing things wrong it requires me to make separate saves for throttle, stick and pedals. So I have to save 3 profiles for each module, and then have to reload 3 profiles for each module when they get reset. Can we please have single SAVE and LOAD buttons in the control editor that will just backup ALL our bindings in one go and reload them all together? Apologies if I've just missed it and been doing it wrong all this time.

Thanks. It just struck me as a bit odd. The EW page indication suggests that the offset mode is still on, yet the button indicates off. The first subsequent press of the button turns off the EW indication, and the second press turns it on again and lights the button. It just looked like it might have been wrong, as I'd expect the button to stay in sync with the EW page and relight if the offset mode was still active. Knowing nothing about the technical details of the real aircraft, I shall of course defer to the information you have. :)

Couldn't find this reported anywhere. If RWR OFFSET button is enabled, OFFSET light is on and OFFSET is displayed on EW page. If you run the BIT in this state, the test runs and the OFFSET light extinguishes, but when the BIT finishes the light stays off despite the EW page still annunciating OFFSET. Button must be pushed twice to turn OFFSET light back on.

Art-J, I suspect he's referring to users/username/local/temp. Just Type "%TEMP%" into the search on your taskbar and it'll bring it up. Sadly, this didn't solve the problem for me. Still very slow to load and shut down, and its hit and miss as to whether the MP server list will populate. EDIT: Sorry, that was really late with the reply. LOL

I use a TM Warthog so can't offer specific advice about your stick, but I always use the paddle switch to disengage AP before moving the stick. Look for Autopilot/NWS Disengage or something like that in the bindings.

I think I may have an idea concerning the problem, but please forgive me if I'm getting the wrong impression. You say you're using the rocker switch above the MPCD to set the desired heading on your HSI, right? When you then look at the UFC, is HSEL on the *bottom* OSB with no other OSBs displaying anything? If so then I think you're actually in direct input mode where you're able to type in the desired heading on the UFC. (Not 100% sure if this is what it does, but I think I've seen it done this way.) Even if you've already selected the A/P pushbutton on the UFC, adjusting the desired heading using the rocker switch will change the OSB options to this mode, and you need to manually push the A/P button again to get all the autopilot modes visible again. To enable the autopilot you need to press the A/P putton on the UFC, which should then display the autopilot mode options on the OSBs. (ATTH, HSEL, BALT, and RALT). HSEL will be on OSB2. Hitting this should then give you the colon marks next to it and actually engage the autopilot in the heading select mode. Sorry if I've misunderstood the issue, but it just sounds to me like a procedural issue rather than a hardware one. Procedures are usually cheaper to fix. :) I hope that helps

Literally just updated my my last post while you were posting. All working now. If some other software has issues with admin mode then I can happily switch between admin and normal mode. Just so happy to have this working in DCS now.

Just leaving for work, but I will investigate this when I get home tonight. Thanks. UPDATE: You, Sir (or Madam), are a LEGEND!!!!!! Where do I send the cheque??? I've just come home, and gave this a try. Shut down the Streamdeck software and restarted it as admin. Then, instead of launching DCS from DCS Updater as I normally do, I went through explorer, and started DCS.exe as admin too. Guess what....it worked!!! I've set both programs to always run as admin now. Such a simple little thing to change, but its made a world of difference. Thank you so much! A big thanks to everyone else for all the other help they've offered too. I love you all! :P

Thanks for the idea. I should have thought of that myself, but I keep forgetting that Micro$oft don't like you actually being able to do anything with Windows. LOL I saw your post just before I left for work this morning, and I genuinely thought it was going to do the trick, but I've just got home and tried it with no change in the results. Just to be clear, I've got a completely fresh installation of the Streamdeck software, with no profiles loaded. All I've done with it it is create a hotkey from the SYSTEM set of keys, and assigned the ESC keystroke to it. That should be enough to produce a result in DCS shouldn't it? It's not just me being thick and setting up the buttons the wrong way, is it? Maybe I should just bite the bullet and try reinstalling DCS. :cry:

Yeah, it's defo an odd one. I've been trying to see if there's some obscure setting in DCS that might block it, but no luck yet. I'll try and fire off an email to Elgato support tomorrow if I can find time.

Guessing that's a reference to the last sentence, which I've now deleted just in case, cos I didn't know there's a spoiler there.

I tried and failed. LOL Deleted literally everything I could find that directly related to Elgato. Exported all my profiles and saved them to Dropbox, then deleted them off my system. After reinstalling the 'deck was pure virgin. All I did after that was to create a couple of hotkeys for testing, which failed in the sim. The 'deck seems to communicate just fine with other games and software, so I just can't get a grip on what's up with DCS. I toyed with the idea of uninstalling DCS itself and reinstalling, but with my internet speeds that means a couple of days letting it download while it eats up what little bandwidth I have. Not a pleasant prospect.

Hi Strut! Thanks for the suggestion. I have just tried that, but to no avail. I've uninstalled the Streamdeck software using Add/Remove Programs, and then deleted Elgato folders wherever I could find them. I believe they were dotted around in Program Files and also 2 or 3 folders in Users/AppData. I reinstalled software version 3.0 as you suggest. Ran a quick test in DCS with just a couple of hotkeys set up, (such as F10 and even ESC), but still no response in the sim. Ran the Streamdeck update to bring it up to 4.2, and still no luck. I must be missing something so simple, but I just can't work it out. :cry: I'm running OpenBeta version 2.5.4.30038 at the moment. That shouldn't make any difference, should it? I can confirm that using hotkeys appears to work in other games, as I've just run a test in Cities Skylines with the same profile.

This is driving me right up the wall. I've been trying on and off to get my Streamdeck working with DCS for over a year now, and no matter what I try nothing seems to work. I've searched the forums over and over. I've searched Google dozens of times. I just can't figure it out. Some people suggest that its an incredibly complex job to make the SD send commands to DCS, while others seem to say its as easy as 1, 2, 3. My latest effort has been to try the profile created by pelellil which is available in the User Files area of the DCS site. I've examined the mapping of the buttons, and like many other profiles I've seen it seems as simple as assigning a Streamdeck hotkey with the appropriate keyboard command. For example, my F18 UFC "1" button is mapped to NUMPAD1, but this combination does nothing when I try it in the sim. If I try it in a blank notepad document I can see it typing the 1, but nothing ever gets sent to DCS. Can anyone tell me why, or even better spare a bit of time at some point to walk me through this? Being able to use the Streamdeck with DCS was one of the big factors that got me to buy it in the first place, and its so annoying that I can't work this out.

This is possibly where I was going wrong, though I can't be sure. I may have been starting VA and VIACOM after I loaded DCS, and didn't realise that could be an issue. I will continue to test and report any problems, though hopefully all will be good now. Thanks

Hi guys. Looking for a little help. I bought VIACOM PRO a few days ago but can't seem to get it to hook into DCS properly. The PTT page refuses to show the aircraft I'm flying, and as such nothing works. I've tried deleting the export.lua from my scripts folder as the manual suggests, and can confirm that on restarting it created a new one with just the VIACOM PRO line in it. I've also directed it to my custom DCS folder (in my case "D:/Eagle Dynamics/DCS World OpenBeta") and tried with and without checking the OB box, but nothing seems to work. Does anyone have any other ideas? I've been looking at YouTube installation/help videos and Googling my head off trying to find out where the problem lies, but no luck so far. EDIT: After about 20 restarts it has just picked up the aircraft for the first time and is letting me issue commands. I will do some testing and see it remains stable. The one thing I noticed was that PTT was showing "Easy Communication: ON" all the time, whether or not I had EasyComms on or off. I came out to look at the Gameplay Settings page in DCS and it was set to OFF (as it always was), but when I went back into a mission its now reading the state correctly. Hopefully this is going to stay good.

Ignore this thread. I've posted in the correct thread now.

Damn! Just remembered we're on BST in the UK now, so another hour to go.

Its in c:/Users/MYNAME/Saved Games/DCS/Scripts