Maverick87Shaka

Fonte: ASC Official Discord.

Nothing spectial, the following screen is the test env, but prod is the same settings in terms of VM: CPU: Intel i5-12600H RAM: 32GB (2x16GB) Disk: 1Tb nvme

It's able to use multiple threads, but of corse a single thread task can't be splitted furthermore. Basically, it's still valid the reccomendation to have a faster CPU in terms of IPC / Ghz rather than have several cores at lower clock speed. It may also depends of kinf of mission (AI units) and player population. For a middle complezity mission and 20 players, modern server cpu even if it's cloccked at 2ghz can do the job. Just stay away from old atom/celeron cpu or really low wattage cpu intended to be used more for NUC/Router/firewall, and you're fine. If it's possible select a cpu with choerent core, all p-core for example (even if I do the exact opposite ). Here the example of our last setup:

Direi che solo lo sviluppatore della mod può aiutarti, aggiornandola per renderla compatibile con l'ultima versione di DCS. Purtroppo è una cosa abbastanza comune con le MOD, che si spaccano con le nuove release, se sei fortunato che la MOD è ancora mantenuta, arriverà un aggiornamento, altrimenti fine. C'è poco che si può fare onestamente lato "utente".

Fonte: ASC Official Discord e DCS Newsletter

Happens to me several time also, normally not on first spawn, but after I died and take again the plane. When happens, tipiccaly I just go back to spectator, then select again the module, and it start normally. Not sure what was the cause, and also it's not happening 100% of the time, but quite often to be notice if you fly everyday jeffy

I've reported internally several times, memory usage increase at point that we had to shutdown one of our instances. We didn't receive any offical feedback from ED on this particular problem. It's just been added to a generic "investigating" status, but no update so far, so as per my understanding, they are not putting any effort on that to mitigate the problem. The stuff can only getting worst in the future. This was my internal report:

Direi proprio di sì, è un buon candidato per vedre la luce in questo 2025

Thanks to link also the other thread, the unreliability of master login server is still an issue, and it looks like it's still more often around the 08:00 CET rather than others reboot. @BIGNEWY can you raise the attention of the team on this issue pls? It's already reported internally? Actually on facebook groups I see even more frequent error comes for the client too, the feeling is that the situation is not getting any better, maybe worst than before Regards,

AFAIK no, it's not a planned feature. Best things that you can do is just place a .zip in a website, keep the same link, stick it in your squadron channel, and drop a message on new release. Hope the people will update the liveries. nothing else you can do on that. Please also note that liveries can be very demanding in terms of space, so it's quite possible that client that join without liveries will start to download everything etc..... leaving less bandwidth to manage the real need, to run netcode. Honestly I don't believe it's a great idea "embed" this feature in dedicated server, it will be more usueful have something integrated with launcher and DCS users files, like arma or other games with steam. where you can subscribe a specific content and will be automaticaly updated if required by launcher, and not by the game server.

SSD for sure, HHD should not be considered for any "realtime" usecase nowday, honestly! You can also find good offers for NVMe drive, so go for that

I can confirm, our "prodcution" DCS server are running on Windows server 2022 as a VM on Proxmox, and it's rock solid for the use case. Just pass to the VM the full cpu accelleration (HOST) to guarantee some extra hardware coding cabability and you'll be fine (works well even in default x86-64-v2-aes to run DCS, SRS and this tasks). Just keep your eyes on RAM, since even simple server are now buring a LOT of RAM; and despite my concerns and warns raised to ED, situation is not getting better.

Hi all, We ware usual to restart all our instances, up to 4 but 3 at the moment due to RAM excessive usage of server, whinith 4 minutues of span between each other. What we've notice lately is that the DCS master login server becomes less reliabale, cousing our server to fails to start. Most of the time the fail occurs at 8:00 CET, but we've experience the same behvioour also during other restart window. Any chance we can get an investigation on this? Thanks.

Fonte: ASC Official Discord

Potevano farla a motori spenti almeno ci sarebbe stato meno blur! Dai che il 16 Gennaio magari ci sarà qualcosina di interessante anche sul C-130