0xDEADBEEF

a crashlog from dynamic caucasus. Seems there's something to find in there. Crashed while engaged by sam in a mirage from close range. https://drive.google.com/file/d/1fgDvz4zUi2PRM4-QYb7un5fmlUoNO7at/view?usp=sharing

Hey Maverick! I totally agree on your last paragraph, I have little to no doubt about it. Still, I do not want to be shy to point out, that with the quality of MP in general - and I don't think it is necessary to explain what I mean with this, you have experienced this yourself the past 8 years - it is absolutely no surprise at all that SP is much bigger than MP. The frustration levels reached on many levels are just to high for MP to take off in any way that makes economic sense. I am inclined to say this is an incredibly waisted opportunity. Yes that is my personal opinion. I think it is safe to say: Yes, flying MP in DCS it is the single most cool experience in multiplayer I have ever had in my life, while at the same time it is the heaviest continued frustration I have ever experienced in Multiplayer in the past 20+ years (how long is multiplayer around? I started MP with a cable hung between two houses because the internet only existed in magazines). And the fact that you Maverick personally told to me in a Teamspeak conversation on the blueflag-ts two years ago - which I still very much appreciate to have had - that "this has not changed in the past 6 (!) years that I've been around here - how long have you been around here? one? - and you should not expect this to change any time soon because [...]" still leaves me puzzled to say the least. It lowered my expectations and thus frustration levels and I am still thankful for that. But then again, looking at this, who is genuinely surprised that SP kicks MP in terms of numbers? :huh: But I cannot resist to be a tiny bit of a wiseass. According to wags there are ~150 employees working on DCS by now. If only 10 of them would be dedicated to developing MP, we would see much more progress in MP-experience, and I think it is quite safe to assume that 9/10 people giving MP a single try will never return to MP again (which alone would result in a 9:1 SP:MP ratio). And I cannot blame them. How many times have you started your aircraft, done your preflight planning while the INS was warming up (if enabled), took off and flew 15-45mins (I love helos) towards your Target and then landed in the lobby or desktop or just experienced a hard freeze or lag-freeze which leads to ground impact? (helos once again). I have stopped counting and it's been more than 50% of the times for me, significantly more in a subjective perception which counts more than hard numbers. I stand the strong opinion that a proper MP experience is miles ahead of a SP experience especially in an environment as awesome as DCS, especially when frustration level is kept low, which sorry - speak up if you disagree - is the part where DCS fails the most and most spectacularly and for an unbelievably long time. Whats your opinion about this Maverick?

That's a pretty good idea, and seeing how things go this really might enable us to join servers quicker. If you get kicked from a server in a stuck loading screen it usually works fine the next try ... So +1!

After todays update I've been trying to join the 104th for a solid hour now. Always stuck on loading screen. Tried repair and restart. Still stuck at the loading screen. Started typing this and suddenly I can finally join. Here's my logs from the last try that eventually worked, along wiht dxdiag.txt and system.nfo Logs.zip

the dcslog on the server should give you hints about where it fails to load things, it's the first file to look at whenever something is not right, or in other words to check if everything is right or not.

My dcs after joining Drexs server uses magic 18.000MB after loading. If I add all memory shown in the taskmanager it comes to about 20 Gigabytes of pure RAM used by active tasks, plus an estimated 4GB for the system plus another 4GB standby-memory allocated by I don't know what. So my 32GB system runs at 86% memory usage when flying MP in DCS. This is really just a factual report about my systems memory usage, but I'd be surprised if this was as designed.

I really don't think the poll was "wrong" per se, it did collect some good data, and while one could say the majority voted for singleplayer, that assumption is plain wrong. There were three options: SP, MP PvE and MP PvP. SP did get the most votes, but both MP added together were quite a bunch more than pure SP. Anyway, I am certain it is save to assume, that if we had the promised rewritten netcode and dedicated server already, plus more properly coded dynamic MP missions as they are popping up more and more, we would have a LOT more people in MP. Currently including myself, many people have opted out of MP, as the frustration-level is just way too high (being dead serious here). Having a bit of software background I do understand the trouble ED is having with it, and their decision to focus on 2.5 before they touch anythign else. Well with 2.5 just being hours away, my expectations on ED to finally and properly touch MP are through the roof.

I really dig the new auto-log feature when dcs crashes. One suggestion though: implement a button to automatically send to ED. Alternatively increase the filesize for zips in the forums to make uploading them easier ... what happened? 99th server, spooled up in senaki, climbed angels 20 and flew 70nm towards target area, a bit more than 10 nm ahead of targets DCS just crashed. https://drive.google.com/file/d/12q70PTDb-8pzw4Dy-ROeGoQYtcLmJYWO/view?usp=sharing

Hey Bufo! You are correct, there is one additional script file (attached to this post) that handles the server environment (slotblocking, connections, kick/ban). You will have to rename the file without the underscore so it reads GameGUI and put it into your "Saved Games/DCS/Scripts" folder. It will be loaded on game-start and only needs to be on the server. You will also have to unsanitize your "DCS Root/Scripts/MissionScripting.lua" file (basically comment out the 3 lines that call sanitizeModule() in order for the scripts to work! Have fun playing around and don't be discuraged if it takes a bit to get it running. Read the dcs.log as the system puts lots of debug-messages there, if something does not work it is likely you will find the solution there. koServerToolsGame_GUI.lua

Would you guys mind including the short runway of Skydive Dubai next to the palm jumeirah in the dubai marina? It is marked here on the runway. You guys already seem to have the skydivers landing area included (the green grass part in what would otherwise be sand). I think it would be a fun addition to the map. It is usually used by Twin Otters, Cessna Caravans, occasionally by a Pilatus Porter and Helicopters. Situated right between the Marina and the Palm I think it would be a very interesting asset in Dubai that should not demand too much of work to get integrated, as most of it is apparently already there as seen in the screenshot :)

I am in no way against it, but it simply does not work in the current state, unfortunately.

I would sincerely love to, but I have found that this only leads to ppl exploiting possiblities, hiding assets where they cannot be found (ie. below farps) plus a few other problems (bugs, crashes) and generally CA lacking very far behind in development, that make CA unsuitable for this campaign.

Just open the topcover, remove the big spring, and put 3 of the 4 small springs on the top of the big slider, then close it again. Very simple and effective. I never used trim eversince.

Yes that works well. I do this especially to get the turbine loaded again so it would rev up. If you bleed all the energy into the rotor, the tubine spins down to idle, if you then request a lot of power, it takes a bit until the turbine is able to provide it and your Rotor-RPM will sink below minimum. Another very nice fast-stop technique is to do a 180 turn. Come in fast a little offset to the LZ, with collective down and stick aft, bank the helicopter hard and pull collective to initiate the turn. You should be able to keep the stick relatively close to hover position, so you can manage nose attitude with collective and be at a stop when the turn is finished. With a little practice you can put the huey on the pad right after the turn with ease. Imho one of the fastest stopping techniques. I have frequently observed AS350s with a cement-bucket on a slingload use this technique on concrete runs. Looks very spectacular :)

The trick may sound boring, but it is very simple and rewarding: it's called approach procedures. I found this a good read: http://www.copters.com/pilot/maneuvers.html If you do them right, all of the sudden your helicopter will stop jinxing and you will land exactly where you want to. I also second to not use trim like said before, but remove the springs of your joystick. I modded my warthog so it would roughly stay in position if I let go of it, but still feel some force (Jets fly fine this way). I would only use trim if I had a force feedback joystick, because then it works like the real thing. With spring loaded sticks trim is really just a compromise.

This has been brought up before but I could not find the corresponding thread. Still sometimes there is no smoke from manpads, sometimes there is. I just had multiple occasions where I saw some sort of small explosion at the origin of the manpad, but no missile at all, but still got hit by it. Then again the next missile the manpad fires may or may not be visible. edit: here's a link to a trackfile where it happens. the last manpad that killed me in the mirage was definately invisible, the second to last that barely missed me during the close flyby was invisible. https://drive.google.com/file/d/0B6YG8nEcMB4ick5JUTk1T05rY0k/view?usp=sharing

Has this bug been reported yet? There is no official comment on it at all, although this is a true gamebraking bug. Ways to reproduce: start an MP Server with players on and wait for it to happen. I (in a mirage) was just facing a mirage head on at 20.000ft, I launched first, he did not react on my launch. Saw M2 on the RWR, but no lock warning, 5 seconds after me he launched as well with no warning in my cockpit, saw the missile being launched though. Then my missile hit killing him, 5 seconds later his 530 hit me, which is a bit weird too because a.) he was destroyed and b.) I was maneuvering ... if it helps, here is the trackfile: https://drive.google.com/file/d/0B6YG8nEcMB4ick5JUTk1T05rY0k/view?usp=sharing

Welcome to the server. You are correct with most of your observations. The main idea of the mission was to create something small scale with rather minimum distances and improved gameplay elements. It works best if a team works together, which is what happened yesterday on blue. While there is specifically no enforcement of side it happens that people start bonding to one side as the campaign progresses, which is a good thing on one side and a bad on the other as one team may be outnumbered at times. But it is ok, it only creates a greate variety of situations that you need to deal with. Of course its more fun to be 2 fighters vs. 2 fighters, but it can also be intersting to face 4 fighters and 4 strikers alone every once in a while. Situations change rapidly, and in my humble opinion, despite being already quite old, DCS PvP Multiplayer is in its infancy. The KO is nothing but a proof of concept for whats going to be possible in the future of DCS :) Again, welcome to the server!

Very nice! Good to see more persistent servers popping up!!

Scripts are only half as harmfull as you may think :) It's always about the way it is employed. The KO are almost 10K lines of code, and it causes surprisingly little problems! I like the truck idea. It's rather simple to implement and should be easier to detect indeed.

Confirming this issue too. Heres a video of an engagement today. 2x M2K head on. I did not even see him on RWR and only spotted his S530 launch visually, wich caught me very off guard and compromised my decision making, making me a minor threat.

Hey! Just had a CTD while being shot by mirage-guns (about the time where kill-events would be issued). Here's the logs: best, beef Logs.rar

It is actually quite simple. As Pikey pointed out it all starts with a lua-table containg all unit including type and position being written to a file. On startup I parse the table and go through every unit and spawn it. If a new unit is placed by a player it is added to the file including who placed the unit, positions are updated periodically to be easy on performance, if a unit gets destroyed it is removed from the table and wont spawn again. There is not a single unit being placed in Mission Editor, they are all dynamically spawned with a lua-function.

Disregard!! My absence of dcs has tampered my ability to properly read first forum posts while troubleshooting. Installing the media update for Win 10 N version did the trick :thumbup::doh:

Hey Ciribob! I was on a roadtrip for a while with SRS 1.2.7 working just fine. After I returned windows said something about a major update which I performed, nothing else on the system changed. SRS would launch fine, but whenever audio gets activated by using the test button or autoconnect, SRS would quit with "Audio Output Error - Problem Initializing Audio Output! Try a different Output device". Tried two different audio-outputs with the same result. The log says: 19:29:09 Ciribob.DCS.SimpleRadio.Standalone.Client.UI.MainWindow Started DCS-SimpleRadio Client 1.2.9.7 19:29:09 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Starting Device Search. Expand Search: False 19:29:09 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 6f1d2b60-d5a0-11cf-bfc7-444553540000 Instance: 6f1d2b60-d5a0-11cf-bfc7-444553540000 Maus Usage: Undefined Type: Mouse 19:29:09 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Adding 6f1d2b60-d5a0-11cf-bfc7-444553540000 Instance: 6f1d2b60-d5a0-11cf-bfc7-444553540000 Maus 19:29:09 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 6f1d2b61-d5a0-11cf-bfc7-444553540000 Instance: 6f1d2b61-d5a0-11cf-bfc7-444553540000 Tastatur Usage: Undefined Type: Keyboard 19:29:09 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Adding 6f1d2b61-d5a0-11cf-bfc7-444553540000 Instance: 6f1d2b61-d5a0-11cf-bfc7-444553540000 Tastatur 19:29:09 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 076306a3-0000-0000-0000-504944564944 Instance: 141f27f0-e64b-11e5-8005-444553540000 Saitek Pro Flight Rudder Pedals Usage: Generic Type: Joystick 19:29:09 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Adding 076306a3-0000-0000-0000-504944564944 Instance: 141f27f0-e64b-11e5-8005-444553540000 Saitek Pro Flight Rudder Pedals 19:29:09 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 05ba16c0-0000-0000-0000-504944564944 Instance: 141f00e0-e64b-11e5-8001-444553540000 BU0836A Interface Usage: Generic Type: Supplemental 19:29:09 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found a09f04d9-0000-0000-0000-504944564944 Instance: 298aa900-f83f-11e6-8001-444553540000 USB Gaming Mouse Usage: VendorDefinedBegin Type: Device 19:29:09 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 0404044f-0000-0000-0000-504944564944 Instance: 141f27f0-e64b-11e5-8003-444553540000 Throttle - HOTAS Warthog Usage: Generic Type: Joystick 19:29:09 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Adding 0404044f-0000-0000-0000-504944564944 Instance: 141f27f0-e64b-11e5-8003-444553540000 Throttle - HOTAS Warthog 19:29:09 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found a09f04d9-0000-0000-0000-504944564944 Instance: 298c56b0-f83f-11e6-8002-444553540000 USB Gaming Mouse Usage: Generic Type: Device 19:29:09 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found a09f04d9-0000-0000-0000-504944564944 Instance: 298cf2f0-f83f-11e6-8003-444553540000 USB Gaming Mouse Usage: Consumer Type: Device 19:29:09 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 0a4d046d-0000-0000-0000-504944564944 Instance: 101136b0-ed23-11e5-8001-444553540000 Logitech G430 Gaming Headset Usage: Consumer Type: Device 19:29:10 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found a09f04d9-0000-0000-0000-504944564944 Instance: 298d6820-f83f-11e6-8004-444553540000 USB Gaming Mouse Usage: -255 Type: Device 19:29:10 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found c328046d-0000-0000-0000-504944564944 Instance: aa4e0900-be2f-11e6-8001-444553540000 USB Keyboard Usage: Consumer Type: Device 19:29:10 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found c328046d-0000-0000-0000-504944564944 Instance: aa4e3010-be2f-11e6-8002-444553540000 USB Keyboard Usage: Generic Type: Device 19:29:10 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 0402044f-0000-0000-0000-504944564944 Instance: 141f27f0-e64b-11e5-8004-444553540000 Joystick - HOTAS Warthog Usage: Generic Type: Joystick 19:29:10 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Adding 0402044f-0000-0000-0000-504944564944 Instance: 141f27f0-e64b-11e5-8004-444553540000 Joystick - HOTAS Warthog 19:29:11 Ciribob.DCS.SimpleRadio.Standalone.Common.UpdaterChecker+<CheckForUpdate>d__2 Update Available on GitHub: 1.3.3.0 19:29:13 Ciribob.DCS.SimpleRadio.Standalone.Client.Audio.AudioPreview Error starting audio Output - Quitting! Die COM-Klassenfactory für die Komponente mit CLSID {F447B69E-1884-4A7E-8055-346F74D6EDB3} konnte aufgrund des folgenden Fehlers nicht abgerufen werden: 80040154 Klasse nicht registriert (Ausnahme von HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). Any idea what could be wrong?