Maverick87Shaka

If you mean this server: Actually ( 03/12/2022 UTC 21:00 ) is available. Make sure you're on last OpenBeta: 2.8.0.33006

L'unica cosa che mi viene in mente, per non scriversi tutto da zero, è usare DCS-BIOS. Li dovresti avere tutte le informazioni di cui hai bisogno, anche se potrebbero essere dipendenti dal tipo di modulo.

In config.lua of Slmod search for MOTD options, you can set true or false some options, as well as enable custom message instead of default.

You can use external tools and search inside all lua files (*.lua) if any of them contains the "loadUserScripts.lua" word ( yeah on windows we need dedicated apps for that, while in linux you can use buil-in commands ) I did it on my dedicated server and full client installation, and nothing found, so it's must be something related to your custom setup, scripts, mods, etc.

@Ironman78 il 3900X è troppo vecchio e soffriva molto sulle istruzioni per singolo ciclo di clock. Visto che DCS tra l'alto al momento è praticamente solo single thread, non ha davvero senso prendere un 3900X per avere più core, che poi non sfrutti. Se ci devi solo giocare con questo pc, prendi un 5600X come processore ( e occhio alle mainboard in questo caso ti conviene passare a una con chipset B550 per non avere il problema del bios da aggiornare ) Se hai budget, sali un pò e arrivi al 5800X e sei più tranquillo anche per gli aggiornamenti futuri.§ Altra cosa, piuttosto che prendere uin HD normale da 3TB, ci metterei un altro ssd da 1TB.......siamo nel 2022, basta dischi magnetici che girano pls!

@Grimes is there an options to control how often the .lua or the .json files are "dumped" to disk? I remember in the past I use it like it was a "real-time" file, but actually I see it's not update on every change, most of the time the .lua and the .json file are updated just only on server restart, just rarely I see that the file was updated when server is running, and I can't understand which is the condition that trigger the dump to disk. Thanks

Because DCS move forward With new release it can happens. Windows 7 ( and Server 2008R2 ) has already gone! Sadly some new programming technique are not available on old operating system, and to squeeze all hardware resources sometimes it's necessary to use new feature, not supported by old operating system. You should also take in consideration to keep your server up to date with OS version for a security reason, Mainstream support channel is already over, so unless you have an extended support subscription active, regardless of DCS, I suggest to update to a newer Windows version. It was not something related to OS since now is started as per my post edit, but maybe some error in your config file and folder. Another tips, sometimes ( really few time in a year to be honest ) if app crash or don't perfectly close, we've notice something like "memory corruption", it looks like some lua variables remain populated, and server fail to start without any apparent reason. In this circumstance the only way to make DCS server start again is reboot the machine, that clean everything on RAM. One of the cleanest config that I have, is the one used during maintenance like post-update and so on.serverSettings.lua

Where are you flying from? If you're EU based, or not so far ( since increasing latency can ruin your experience ) you can give a try to our squadron server. We've three different 24/7 open server, all PvE, with different level of difficulty, random weather and time. The easiest is the Caucasus, in the middle we've the Persian Gulf, and the more challenging is the Syria, but on every server you can also spawn with radio menu some A2G mission, that are outside A2A CAP zone, so you basically just have to worry about ground unit of the mission. Search for: [ITA] Banshee If you have question about that server, feel free to ask

Since DCS only runs on Windows, it was clear that is windows I would like to know the exact version. From logs look like it's a 2012R2 or a 8.1, it's correct? I guess it can be the problem, I suggest to try a newer version of windows, on server edition you have 120 days of trial, upgrade at least at Win 2016, or even better 2019. It's running as main OS of server or as a VM? EDIT: from dcs2.log server looks like start normally finally, so you've solved the problem? Maybe you had a wrong config file from a full client install that try to load some stuff?

What is the OS? Please attach the new DCS.log that you have now after clean installation.

From what I can see before do statement, you're running Slmod right? Slmod replace on each start the default Scripts\MissionScripting.lua with their custom one. Edit instead the SlmodMissionScripting.lua in Saved Games folder, under Scripts\net\Slmodv7_6

It can be something related to the mission that is running or some specific server settings? We've already flown several missions with AH-64D Pilot and CPG in multiplayer without any problem. Try on another server or hosting a mission with your friend and see what happens.

it looks like you have some error in your custom code, because scripts inside Scripts/hooks works fine. We're running DATIS, SRS-autoconnect, SimpleSlotBlocking and Slmod from that folder without any issues, on both dedicated server and full client installation that run as server. Take a closer look at DCS.log and see if you can identify what is preventing your server to start normally.

Sure, i'll get in touch with the last one of us that had the error, and forward you the dcs.log

no it's not @BIGNEWY Even after auth server restart, problem persiste, even after end user change their password. I'm in touch with several other server admins, and we're still facing the same issue.

This is really strange, can you just add your DCS.log of the server just to understand if the server is actually started or it's going in "hang" status at some point?

Just tested on my client installation, with the current OB 2.8.0.32235.1 and it works as expected. You can try to run a server with a different working directory to see if there are some spurious settings that prevent the server load. DCS.exe --server --norender -w test_server where test_server it will be the name of new server folder under saved games. If it's still not working, make a full repair of the client and check the windows permission of the file itself.

Server can be installed anywhere, it should not be a problem. Just make sure you still have under C:\users\<username>\Saved Games\DCS.openbeta_server\Missions\ some valid .miz files if missions folder doesn't exist just create that, and put your file over there.

As result, JF-17 is no longer usable in any multiplayer server basically

Let me know if you need help, I can try to prepare a package with everything you need ( host + reverse proxy ) packed to run from ngnix. Put the zip on DCS server, run ngnix and you have everything Fly Safe

There are already a couple of method to know what is your callsign: If you have enabled on map at least with the own position visible,including fog of war, allies only etc, you can directly check from map: ( Chaos1-1 in the example ) Prepare the mission including in the group name the callsign ( is the method that we use as squadron for all our internal missions ) In this way the first slot will be always -1, second is -2, etc. Since in the mission editor you can't change the last digit, but it's automatically assigned and not editable, there is no way to make mistake. The first line of the group will be always the -1, second the -2 and so on. Last option, make a quick check with a fake radio call to a tanker or other AI unit, it will say in the transcription your callsign. The role selection UI is already full of information, I'm not sure I would like to have another column with an "obvious" information on it.

Simple ( but dirty ) way that comes to my mind for a quick workaround, could be read the dcs.log On second line you have all the arguments. its not 100% accurate since some people can mess the starting arguments, but it could be a starting point. === Log opened UTC 2022-11-01 13:00:50 2022-11-01 13:00:50.652 INFO APP (Main): Command line: DCS.exe --server --norender -w SyriaLiberation

You actuality need both, if you only use the webgui folder hosting you'll get the same error of trying to use webgui folder locally from any other computer. Reverse-proxy is required to make DCS believe the request comes from the same machine (127.0.0.1), otherwise it will not reply to the request. The method to host the webgui folder just give you more options to control who can actually use that url that you'll provide, you can track the log etc, gives you more options that simply provide a .zip file to your moderators/admins. Even just for any future change, without send over modified javascript again, you just take care of update webgui folder hosted by yourself, and you're ready to go!

Non conosco nel dettaglio tutte le su varianti, ma credo che sia solo la versione MB-339CD dotata di probe per effettuare il rifornimento in volo, non so se poteva essere "retrofittata" sugli A o PAN che abbiamo noi su DCS. Non mi pare che sia nei piani, quindi a questo punto non riporrei troppa speranza nel poter fare rifornimento con questo velivolo ( sarei lieto però di essere smentito con un CD in arrivo ahhaha ) null MB-339CD

Buongiorno piloti, Dopo ormai diversi mesi di non funzionamento del sito delle statistiche e info relative al server "conquest" del Persico, abbiamo deciso di investire tempo e sforzi per ripristinare questa parte del server DCS, perchè crediamo possa creare interesse nel giocatore avere un punto in cui "rivedere" i propri progressi. Con l'occasione, anziché limitarci a ripristinare solo quello avevamo costruito in passato, abbiamo colto l'occasione per fare un completo revamp del sistema. Ora è possibile vedere un overview di tutti i nostri server, entrare e vedere nel dettaglio il proprio posizionamento, e infine entrare sul proprio "logbook" e vedere i risultati personali. Stiamo ancora finendo di limare gli ultimi dettagli, ma crediamo che sia già arrivato a un buon livello, ed è per questo che abbiamo deciso di condividere con voi questa notizia! La pagina aggiornata la trovate QUI! Fly Safe!