bswift

I have some scripts that install the dedicated server, or upgrade it automatically. But it's flakey, because there is no command line way of doing this - I have to use an app to mimic a users mouse and click on buttons. Brutal! This is really a feature request to ED - whoever is creating the Windows Server version of the dedicated server, that will supposedly replace what we have today. My ask is this - make this completely automated. Give us a script, powershell or whatever, that can auto update the server, and download all maps etc. My use case: I'll create an AWS AMI builder pipeline in AWS and share the AMI for anyone that wants to use it. The reason I want an AWS AMI because I only want to start my server on-demand (via my phone or whatever), to reduce costs and not have this thing running 24 hours a day. This also means that login information to my DCS account needs to come from a config file. Setting things up by going to a website is - kinda meh. For this to work I don't need an "update server" command, as I could always just install from a clean windows machine. If someone from ED sees this, can you let me know if these asks are unreasonable or if it would be possible to do? I really would hate to see a new version come out that doesn't support an automated install process. :)

I removed the MOOSE code in question - and the problem disappeared. I was just running a BAI mission on the B1's. I'll work on the BAI feature again soon - and try your hotplug suggestion if I see it in the new build. Thanks!

Thanks! Hopefully Anapa is fixed soon. Sounds like this was an airfield problem and not a plane problem, unfortunately.

FYI - to see it, if you get in the first plane on Blue in the client list, follow startup - -take off and fly to waypoint 2.. you will see this. It's a bit of a long lonely flight.. but.. it's also kind of a nice sunrise :D

I just tested again and it is still an issue, even with a plane that spawns late into the mission. Fri13 - I haven't done exactly what you said, but I did go into axis controls, and test the axis.. they all were responding. However, going back into the game I had no controls. The mission I liked to (on the branch) above, still has this issue. I've tried a couple of times. It's ONLY when I get to the Arco tanker though, which is a little strange. There's a moose command that fires right then sending the B1 bombers to a different waypoint. I also have a late spawn plane. When I get in it, the HOTAS axis controls work - but after about 60 seconds or so they stop working. It's probably my MOOSE code that is causing this, however, my opinion is that no MOOSE code should cause the mission to stop. Anyways, This is the moose code in question: The code here is a reference: https://github.com/brettswift/dcs-mission-mp-sunrise-scramble/blob/355f37e0d815b52bc8900c151da7a4678d8382be/MP_Caucus_Anapa_Mission_Start.lua#L63-L77

If you want another mission to test with: https://www.dropbox.com/s/i0qt89il04h5jsq/MP-Caucus-Anapa-v14-alpha-with-moose%20-%20Arco-stuck-on-runway.miz?dl=0 Arco taxi's and then gets stuck on Sukhumi.

I have that windows game stuff turned off, but it is entirely possible that something did just take focus away from DCS. I'll post if this happens again, and confirm I have focus on the window. My wheel is a Fanatec 911 GT3RS - I wasn't aware there was a conflict with wheels - i'm not sure how that could be the case. I sit in front of the wheel and I think one profile I use the wheel as a button box. Is there a link to where the conflict is being tracked - so I know when it's fixed or if it affects my wheel ?

Here are the last 2. If memory serves I was only in the ME after exiting the mission so it should be close to the end. I did run a whole bunch of missions first, and it was ok. I'm using MOOSE, but not sure that could affect something like this... Code is up on a branch: https://github.com/brettswift/dcs-mission-mp-sunrise-scramble/tree/fix/bombers-should-bomb-stuff Logs.zip

Caucus Anapa. It was a B1 bomber that was at the start of the runway at 45 degrees, and had F14's behind him, all AI, and I was in the far rear. I put it behind the F14's and it worked - although there were still about 5 B1's that sucessfully took off before the F14's.

I even did an auto shutdown (WIN-END) and the plane shut off successfully. However, still no controls, and the after burners were still on, and the plane did NOT drop out of the sky. This is after the november update. F-18 is the plane.

With the November update they sometimes just sit there. Can't predictably reproduce every time but if you get a mission in that state it'll happen

https://www.digitalcombatsimulator.c...files/3312962/ This mission is in development. But it works as is and I fly it quite a bit because the sunrise is amazing :) What it lacks: success criteria, working B1 bombers. What I love: the tomcat escort in the dark, Sunrise AAR, and after that a bit of everything for you. Main intent: Settle into dcs with a morning startup and 15 min sunrise flight, AAR, then SEAD, then A2G or A2A - or just go practice some super carrier (or Stennis) landings. I built it for a few friends to fly - and for me to learn the ME and the MOOSE framework. It's still pretty fun though, I think! There are some audio messages made by bots (AWS polly) but if anyone wants to do voice overs, that would be great. I need to change the script the bots say, they're lame right now lol As I build this out I'll make it better with the B1's actually releasing from orbit and doing their bombing run, and not just flying home. I'll probably also put in some more dynamic A2A balancing logic to make the mission harder based on how many friends fly it. Read the mission briefing on the download page for help - this mission is a bit of a unique one I think. If you like it, let me know. If you hate it, let me know how I can make it better! :) And if you want to fly it with me, I'm up for it!

still crashing with the latest update.

I moved the stennis around - saved - and reloaded the mission. Still crashes.

I work in the AWS Cloud in my day job, so It's pretty easy to set stuff up there. I fly with friends a few times a week so don't keep the servers on full time. And at 16GB RAM I pay about 0.22$ CAD / hr. If using spot pricing (bid on market price) usually 1/3rd of that. With AWS you'll pay for data leaving the cloud - which will be a decent amount with DCS but shouldn't be that bad for my use case. I'd expect a couple hours flying with friends after tweaking all this is going to be less than $1 Canadian. I know this is a bit of a heavier lift, but if you're ever wanting to try this those are the rough numbers. There's a guy that built ready-room.net as well which you can check out. The backend of it is also AWS. It's a new service but you could give it a shot. If anyone is technical enough to get going with AWS and has a question feel free to ask away.

It's probably more than sporadic now.. It seems every time. The contents of the crash logs are: # -------------- 20200408-235805 -------------- Ok now we're done with crash logs the main logs have some errors right before it crashes. and the full log file: https://www.dropbox.com/s/0cbq9plhvbmpwxx/dcs.log.crashing_on_anapa_mission?dl=0

This worked well on 2.5.5, 2.5.6 (first update), and in single player. However in multiplayer I will sometimes be ok, but everyone that joins will crash right out to the desktop. It's probably more valuable and easier for ED QA's to run this mission and figure out what the bug is in DCS that causes this. I have a hard time believing a mission file could cause the whole game to crash (shouldn't ideally). Anyways, here's the mission you can test with: https://www.dropbox.com/s/01kp5spiwg9k1bp/MP-Caucus-Anapa.miz?dl=0 Let me know if there's something I can do to fix/help. It might be a bit tough / take a while for me to get logs from a client joining.

I'm going to try to get this set up. So far I'm customizing it myself and doing the whole install. ED (or anyone for that matter): do you have an AWS AMI with the dedicated server installed and ready to go? I will customise mine a little bit after, but I figure SRS and TacView might be at least good to have bundled for everyone, with the maps already downloaded. If anyone has this AMI pipeline (packer or whatever) built, let me know. I feel like this is a long shot but ED.. you guys have to test somehow? If you do have one and want to make an AMI available that'd be sweet :) Edit: any pointers to hands free installation guides would be great. I see most of the instructions on the forum here are "GUI clicker" instructions. I'd like to get this at least in a user data script so when I want to set up a new EC2 / AMI, there's less grunt work involved.

I see 35-40 FPS in my oculus normally. Sometimes it gets crap when I land at about 15 fps (ugh), but in the air it's ok. I just bought this "F/A-18C Aggressors BFM Campaign". I just watched that stupid first mission where the c-130 lands at Nellis, and the whole time that was at 6 frames per second. I'll just struggle through this and get into the f18 .. it won't be that bad when I'm actually flying.. NOPE. 5 fps in the hornet on the deck. Completely unplayable, a mission I just payed money for.... when there are all those great free missions out there. I'm an idiot. I have 16GB RAM, 1080, and a decent CPU. I'm on the beta, is this another problem with it (2.5.6)? I've been through the VR optimization videos.. Any idea why this is so crap?

Ok I did that. It loaded. I reinstalled SRS, copied over my Liveries, and it still works. I moved my inputs folder over, options.lua, and that's all I really needed. Still works. So there must be something in the saved games that is breaking this, that I haven't moved over? Or something that was reset in the core install directory once wiping out the saved games folder? You surely know better than I. It looks like i'm good... any files I can send to help you figure this out?

This is only in 2.5.6.44266. I'm loading this mission (which seems to work for others): https://www.digitalcombatsimulator.com/en/files/3301137/ What i have done: 1. Repair (via dcs updater utility) 2. reinstall of DCS completely. 3. SRS is installed, it's the only mod. 4. enabled all logging with the autoexec.cfg file. When I open a mission (mission 3 in this case, from the campaign.. via missions --> mission 3), It loads the mission file. Then another window pops up with a green "Fly" button. At that point, DCS hangs. Windows see's the process as unresponsive, and I have to kill the process. Not sure what is going on.. I see a bunch of error messages in the logs.. Advice is requested. I haven't deleted my entire saved games folder, I would prefer not to have to re-import all my joystick settings...but if that's what I have to do... ugh. Attached: log files Thanks! Logs.zip

There's something unique going on here because of I load this mission in the beta 2.5.6 the tanker is invisible even without that flag being set. I see contrails but no tanker. And if I delete the tanker and re-add it the same thing happens.

I have a mission with two tankers. I can't seem to get them to work properly. One is scrambled from the f10 menu and one is already flying. TACAN works and I'm taken to the tanker. I can declare intent on f10 with easy comms (as default). But I always get "return pre contact"and no distance on approach. I'm using a KC-130. I noticed the second tanker wouldn't appear on f10 unless I picked a different frequency, and then that worked. But still can't seem to get it working. I've eyeballed a working mission and I can't seem to find out what's different? It's a multiplayer mission with a bunch of other stuff going on. This tablet is set to invulnerable and invisible too. I don't think that's it? What might I be missing here?

So .miz files are basically compressed archives. Is there a setting somewhere to have the unarchived structure remain? I'm not sure if storing these in git makes sense - if a buddy and I make mods to these will the diffs make any sense? Lua files seem like it'd be easy to mangle it. Is the best option to just.... save file copies with a different name?

I'm not sure if this has been posted (97 pages .. search didn't come up with something). I watched the youtube video posted recently that links to this thread. It mentions to enable the shaders, you should delete files in the saved games folder - I did this and the cached files return. However, in deleting files in: DCS World\Mods\terrains\Caucasus\misc\metacache, and renaming the dcs folder to dcs.old, no files return and the original dcs folder doesn't get re-created either. I'm guessing something didn't work... can someone confirm what the behaviour should be?