Madfish

Generally that's good advice but is it applicable here? Just out of curiosity: have you managed to run the dedicated servers as a service, so without autologon?

That machine will run fine. On that CPU you can easily run multiple DCS server instances. 15 players on a single DCS server with that CPU and 32 gigs of ram will be no issue at all. Bad mission design might change the picture though. Especially grouping tons of active radar systems together have been found to crash servers. Nowhere does it say DCS needs a minimum frequency of anything. What those requirements are saying is your CPU should be able to go above said frequencies. In fact I wouldn't give too much about those values - they are inaccurate and also depend largely on your settings (I/O, resolution etc.) to make the game work or break.

If you're hosting IPv6 only then only IPv6 capable clients can connect. Considering even the most established providers do not support native non carrier grade IPv6 that's very unlikely to happen in a squadron. Literally all your members would have to fix their own WAN IPv6 first. Most carriers still apply dual stack configs. What you can ask them to do is to apply a carrier configured port forwarding. Your ISP sets up the routing for necessary ports which will terminate at your endpoint. That way you can host a dual stacked IPv4 server.

@c0ff It would be awesome if the server window rendered the local web gui so you could easily see numer of players connected, mission state etc. Personally I don't mind if it's red, green, blank or has unicorns on it - but the local WebGUI would be awesome to have per server instance. It would help instanced configurations (especially those connected to multiple accounts).

The question is: does it show the flag of the country the server resides in. Since this flag is the actual geo-ip resolve of where the server itself is located so potential clients can easily spot servers in their area. If I do understand you correctly and you are hosting it from home the cause of this is your ISP. Usually ISPs buy into backbone providers like level 3 etc. - the public IP you're being aside is usually tied to a server in your ISPs network. That get's resolved by a geolocation service like Maxmind, W3C Geolocation, Quova, IP2Location etc. It can be very close, but also very far away. For example: being from south Germany, if I lookup my own WAN address at https://whatismyipaddress.com/ I get localized in West Germany, which is false. It uses W3C Geolocation. https://www.whatismyip.com/ locates me in East Germany, which is also false. It's using Maxmind. I'm sure if I tried another service e.g. using Quova I could get another result. So it can easily be wrong just by what geolocation provider is being used, but also because your WAN address could be tied to a server literally thousands of kilometers away. If you meant you're hosting it on your own home network you can easily check this yourself and see if you get an odd match - that way we could at least see what geolocation provider is being used. For 99.9% of the people, and especially servers in a data center, it should resolve the country nicely though.

+1 from me as well

Thanks. Same thing happened to me. I'm not even sure why I was affected since both planes are part of the FC3 bundle which I already own.

Hi there, can anyone confirm after the latest update to open beta if the ModelViewer2 works or also gets you the same error on start: ---------------- ModelViewer2 Can't load Config/ModelViewe.lua! ---------------- Already tried a repair - no luck Tried to rename the lua - no luck ModemViewer2 has worked before just fine on this system but that was a few patches ago last I checked. Any advice or is it reproducible for others too? ModelViewer.lua

Hi, you could do this by placing it in autostart. E.g. for a default admin account here: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup Your shortcut would be the default one for the server or something like this: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin\DCS.exe" --server --norender

I checked the documentation but unless I have overlooked it there is no such flag. How are other server owners solving it? Just checking for the ED news and then manually patching the servers?

Has anyone found a way to automate the DCS dedicated server updates as soon as they are released? I searched around on the web and forums a bit and found nothing on the topic. Personally I experimented with some AHK scripts clicking the updater popups but wasn't impressed in terms of reliability. Does anyone have a solution for this?

Interesting point - but sad at the same time. There is IL-2 for example where the community can just mod maps as they wish. Also there is MS Flight Sim and others which just cover the whole planet. I will never understand why we're so restricted in maps and map sizes, especially when they're relatively low detail compared to most other products out there. Would be fun to be able to use DCS for extended flights or even sightseeing or fictional theaters with certain challenges (e.g. just imagine Sahara dessert, Himalaya etc.)

Also got a timeout but again on a different time (mine are set to ZULU/UTC) 15/11/2019 7:53:02,15 detected session timeout on eu_training_1 15/11/2019 7:53:02,16 detected session timeout on eu_training_2 Again this only happened to both machines under 1 account. The other server kept running fine. This time both servers were able to recover themselves with my script by restarting them however. So that's a plus from last time .

Can confirm but on a different time: 13/11/2019 21:16:58,13 detected session timeout on eu_training_1 13/11/2019 21:16:58,16 detected session timeout on eu_training_2 13/11/2019 21:16:58,35 killed eu_training_1 13/11/2019 21:16:58,35 killed eu_training_2 13/11/2019 21:17:13,45 started eu_training_1 13/11/2019 21:17:13,48 started eu_training_2 - and what's even worse: they couldn't connect again after the failure. This was 3 minutes after the the first session timeout was detected by my script. What I got on both servers was: DCS Login Failed DCS web site is not available at the moment. Offline mode requires a saved password and a successful login to operate. Even more interesting: from 3 servers only two failed - and both were on the same account. Is any more troubleshooting required from our end? More logs etc.?

All those issues are still there - plus a lot more that aren't mentioned. If you aim at flying the A10C a lot I recommend buying it - if not I recommend skipping. Especially because the Warthog lacks a lot of necessary controls you need to replicate fighters or space aircraft. Neither the stick nor the throttle have good mechanics / electronics. Modding and upgrading will get you easily where better alternatives sit that will last you for decades because of decent construction. By the way, even real planes don't always have metal grips. In fact the more advanced the plane the less likely it has a metal grip.

Thanks for the suggestions. :) I will try Xpadder and especially Joystick Gremlin as that looks updated and really clean. @Thick8 I checked and the hornet apparently doesn't have a g-limiter override in DCS so that point is moot indeed. However, it can still help to conserve buttons without having to work with profiles, which isn't too intuitive for me. I only got a warthog so I'm super limited on buttons and other stuff (way too many switches) - I don't even have a radar slew on it for example. So I tried to compress as many functions into the limited amount of inputs as much of the stuff is only in effect in certain situations. Funniest thing I once had to happen was the starter on the Huey. It was bound to my throttle pinky button in the DCS default - ironically that was also a Push to Talk button for me. So whenever I was speaking the starter came up and spooled. It never broke though so I didn't even have to change it :)

Hey there, is there any news on how to achieve multiple actions with one single button in DCS easily? I have searched and only found vastly outdated threads like this one: https://forums.eagle.ru/showthread.php?t=41127&page=2 With the Viper and Hornet e.g. that all use multibinds on the HOTAS - is there any official solution to this? For example the paddle switch on the stick being: Nosewheel steering disengage Auto pilot disengage G-Limiter override switch Or the undesignate / nosewheel steering button. How to do the same in DCS?

Actually not the host OS - but a VM running on a bare metal hypervisor. So there is two basic types of virtualization: Type 1: (native or bare-metal) sits directly on the hardware and doesn't need any other operating system installation. Type 2: (hosted) sits on top of a full fledged operating system (e.g. Debian, Windows etc.) So this config here breaks and causes the LOCAL "Server not responding" issue in ALL cases (100% reproducible): Hardware OS = Proxmox (tested, bugged) / XenServer (Citrix Hypervisor) (tested, bugged) / VMware ESXi (untested!) etc. VirtOS = Windows 10 / Windows Server 2019 etc. While this config for example is working: Hardware OS = Windows / Debian etc. VM = VMware Workstation VirtOS = Windows 10 / Windows Server 2019 etc. I tested this on the same hardware within multiple networking environments - same result every time. Hence I was asking if those who are affected by the LOCAL webgui "Server not responding" bug are eventually sitting on top of a true type 1 VMM. This can very well be the case even for rented machines as almost every server machine nowadays is sitting on some sort of native hypervisor platform due to massive performance gains and additional features like live migration, high availability etc. Keep in mind that the WebGUI broke precisely with patch 2.5.5.31917

Could you also upload something so we can compare? (I'm on latest open beta)

And how did you find that? Maybe it's SAM specific? Right side = Excellent Left side = Average Last missile lost energy and self detonated

Quick question as I didn't spot it in the changelog - was the ability to see radar locks and gazes fixed?

Great points. But just to be clear: there is the possibility of this bug having the same symptoms for different root causes. What I can say is there seem to be two main issues: 1) "Only" the remote DCS Server Dashboard saying "Server not responding" 2) the LOCAL DCS Server Dashboard saying "Server not responding" If you are having issue #1 it IS fixable (e.g. with opening / forwarding ports) If you are having issue #2 it is likely NOT fixable and is an issue that came with patch 2.5.5.31917. It is also likely NOT on your end - it's a DCS issue. I can reproduce this 100%. However, for my situation it's not related to either Certs or UDP ports being open. Let me explain why. Certs: When I install DCS ded srv on my Windows 8 / Windows 10 machine I can run it fine When I install DCS ded srv inside a Oracle Virtual Box VM on my Windows 8 / Windows 10 machine I can run it fine When I install DCS ded srv inside a VMware VM on my Windows 8 / Windows 10 machine I can run it fine When I install Windows server natively on the server and install DCS ded srv I can run it fine When I install Windows 10 or Windows Server 2019 inside a Proxmox VM on my machine I can't run it fine - It gives me the "Server not responding" bug When I install Windows 10 or Windows Server 2019 inside a Proxmox VM on dedicated server machine I can't run it fine - It gives me the "Server not responding" bug Also tested Xen with the same result. This can't be cert related. Ports being open or not Even if I block access inside Windows firewall I can't reproduce the bug. In fact I can run DCS ded srv fine even if I disable all of my network connections alltoghether. Conclusions What I can safely say is that DCS ded srv does not work if the Windows (7 / 8 / 10 / Windows Server 2019 etc.) is running on a server with a hypervisor anymore since exactly patch 2.5.5.31917. This can be reproduced 100% Steps to reproduce: Grab a computer Install Proxmox VE (free, based on Debian) Install a Windows of your preferred flavor > DCS ded srv interface breaks locally AND remotely (Server not responding) Whatever was done in patch 2.5.5.31917 broke it. What didn't help: Multiple Windows flavors, including different builds, languages and territory settings. Installed Windows patches or not. No mods / mods installed Firewall On/Off Nothing changed the fact that since 2.5.5.31917 bare metal hypervisors are broken. That is why I was asking if those, with the LOCAL DCS Server Dashboard broken, are eventually running their OS inside a VM on a hypervisor (Proxmox, VMware ESXi, Xen etc.) as it is 100% reproducable.

As it is still there - did anyone at ED figure out yet what it is they added to the game?

Hey, how was that night for you? :vertag: :D

There could be a slim chance on a reinstall for some applications but it doesn't make much sense if done correctly. What should be different? I did that dozens of times with no success what so ever. BUT there is something interesting: A striking difference I noticed however that I would like you guys to check: are you running the servers on a native bare-metal system or are you running it virtualized on a hypervisor? While: I can run it 100% working on a virtualization running on native OS (e.g. VMware Workstation on a "normal" Windows Computer) I can replicate the bug 100% when running it virtualized on a hypervisor (e.g. Proxmox, Xen or similar) So maybe that is the root cause here to some degree or it's just another bug that has the same symptom?