Maverick87Shaka

Graphs are generated automatically by a monitoring system. I'm using Checkmk (that is also available in the RAW edition that is free ) Let me say that I've managed large infrastructure so I'm usual with that systems (I was the lead of the monitoring systems for the whole IT infrastructure) but to monitor single server, I would not recommend this way. For the purpose of managing a DCS server, even several istances on the same machine, I would probably recommend to create a scheduled task that execute netstat command and write down a text file, csv formatted for example, and than use any online tools to graphs the results when needed, or create a self hosted html files that use chart.js or similar library to have a interactive live graphs. A full monitoring system is amazing, but definitively overkill for the purpose. Main downside is that requires a dedicated server or "BOX" like a raspberry pi. It's not a simple pieces of software that you can run in the same environment of DCS server

ok, did you have the new logs to attach?

Try to manually set your Windows Page File to manual mode, with minimum 16GB ( 16384 MB) and see what happens ( preferred on SSD if it's available of course ) Looks like your server has 16Gb of RAM, maybe it's running out of it ( just an idea to make a first test, since logs doesn't say any usefull data to me at first look )

Tested with old dedicated server, a full client running in server mode, and the new modular server, it works fine for me. What you can do: make sure the file is named autoexec.cfg, and not something like autoexec.cfg.txt (windows by default hide file extension for known files type) I personally recommend to enable shown of file extension even for well known file format on a server machine. Is one of the first thing that I do even on work when joining a new server or a server for the first time. Verify port 8089 is not already occupied by another process. ( it's strange that should not revert to default, simply webgui dosn't work ) Make sure if you're running multiple instances, that the file is inside the correct server folder ( -w server01 => C:\Users\<runningusername>\Saved Games\server01\config\autoexec.cfg ) Use notepad++ or any decent editor, to make sure you don't have any un-needed white-space or/and special characters that embedded notepad loves to skip/hide/place. ....and.....I'm running out of ideas start from these and we'll see next

Sinai is not yet present in the standard list of modular server: But you can still use the old fancy style: DCS_updater.exe install SINAIMAP_terrain

Controlla di non aver impostato un limite di FPS, nel file autoexec.cfg che trovi in partite salvate\DCS.openbeta\config\ Dovrebbe apparire qualcosa come: options.graphics.maxfps = 75 Se parli di non poterlo provare su DCS, controlla meglio perchè la libreria utilizzata dalla Eagle Dynamics è la 3.5 del DLSS, ma le feature utilizzate sono quelle che erano già presenti nelle passate generazioni del DLSS, quindi dovresti poterlo abilitare anche sulla tua scheda che appartiene alla serie 3000.

simple behavior: (not optimal but it works, kind of at least) Place the slot without fuel and ammo. If the Airbase is still belong the enemy coalition, player can't refuel/rearm, so they can't take off. complex behavior: None of the built in mission editor function will works in multiplayer environment to achieve this result. What you can do is use some LUA scripting, and here you have two options: 1. Simple way is to "import" on server the SSB Script ( Simple Slot Blocking ) and than you can enable/disable slot setting the value of corresponding flags. Flags can be set by mission editor trigger in this scenario. Works great when you switch just one time from enabled/disable status during the execution of the mission. If you switch several times the status, may have some issues. This method requires that SSB is installed as a server side mod. 2. Using MOOSE library or native DCS scripting, you can do some action on a specific event, like OnEventPlayerEnterAircraft. After that you can make your check, if the airbase is of the same coalition, and then eventually send back the player to "spectator" with something like: net.force_player_slot(PlayerIDnum, 0, '' ) This method doesn't requires anything on server side, and all the code can be placed inside the mission itself ( .miz ), so you can port it to any other pc or server and it will works.

In teoria la 1.2 e la 1.5 di DCS utilizzavano il vecchio sistema di Chiavi, e sono state completamente rimosse dai server ED per evitare che potessero essere utilizzate in maniera "non lecita" da chi non possiede una licenza valida. Non ne sono certo, ma dovrebbe essere così. Mentre invece per quanto riguarda la versione più vecchia che dovrebbe essere possibile scaricare, credo sia la 2.5.3 per il discorso dell Hawk.T1 poi successivamente rimosso, quindi quella sono legalmente obbligati in qualche modo a tenerla online ( senza supporto ovviamente, va come andava e stop )

Servers on lan are really "susceptible" to appear in the server lists. Most of the time, if you don't mind, just enable IPV6 on both server and client solves the issue, or you need a proper "NAT loopback" set up to be able to see it. Currently (with a loopback nat) I'm able to see all my instances within the same lan. I hope this info can help you to try to have it back in the list.

Back in September they drop an update to address a security issues, and as consequence, no more than 5 instances are allowed to run from the same account. No special parameter that you can use. Use different account, one for slot 1->5, and another one for 6->9

If your mission is highly scripted there could be something in your code or library used ( for example MOOSE and so on ) but it will be very hard to address the single function that may cause memory leak. So far as you can see from my graph, it doesn't look strictly related to 2.9 release itself, or I should have it tracked as well.

From what I can see in our monitoring console, it's not increased. Or if.... it's just a little bit, almost imperceptible increase. This is our server report, update dropped on 19th when you see memory goes down. Don't look at the peek of 18 where we've started another instance on the same server

Fai un bel 6000Mhz CL30 e ti togli ogni pensiero. Le trovi anche della stessa serie ma CL30, nuove da amazon stanno a 160€ i 32Gb, ballano circa 20/30€di differenza, porti a casa un 5%-10% di performance in più nei video giochi ( in termini di FPS )

il file eseguibile MT diventerà di fatto lo "standard" per DCS, per questo l'icona dell'updater già dalla 2.9 rimanda all'MT. L'animazione di jester quando si chiama il menu manca ( da tempo ) ma penso che la HB stia lavorando soprattutto a Jester 2.0 al momento, per il prossimo F-4, di cui poi vedremo l'arrivo anche sul 14, forse è per questo che non ci stanno investendo tempo nella sua risoluzione. Per il motivo di cui sopra, è normale che non vedi le nuove opzioni nel file eseguibile non MT. Non è perfetta la 2.9, ma è un grande passo avanti. Tocca spettare che aggiustano il tiro

Vai sereno con un 7800X3D e almeno 32Gb di ram, meglio se da 6000Mhz con un CL decente. Per il resto, scheda grafica NVIDIA, una bella 4070 e non ci pensi più almeno fintanto che rimani sul 2K di risoluzione. Per andare oltre forse qualcosina in più aiuta soprattutto per la VRAM, che DCS, anche con la 2.9, ne usa un boato!

It depends on how many instances of DCS you want run on the same machine, plan to have it dedicated just for DCS or you want use it to host other LAN/Home services? Expected player base ( you and your friend or 40+ more players) All of this condition makes the difference..... Just for a single instance, something like a Intel® Core™ i3-10100F should be able to handle even complex scenario and a quite range of player, and you can find it at 70€

start the server directly file from bin folder to solve the issue. The problem is the launcher that is now set to start automatically the multithread version of DCS, that doesn't exist for dedicated server.

Sono due tasselli importanti figurati, comprendo la sensazione, ma non sarà la 2.9 a metterli

Non so esattamente cosa ti aspetti in termini di numero di unità, dai nostri "benchmark" con il dovuto hardware lato server e gli accorgimenti giusti in missione, si fanno tranquillamente sessioni con più di un migliaio di unità attive, anche con 10 players e oltre collegati. Diciamo che il "realismo" di uno scenario te lo devi un pò costruire di volta in volta, tenendo a mente qualche paletto. Certo non puoi mettere 10K unità AI attive in movimento, e sperare che con 40 players collegati poi vada liscio a tutti come il single player, però dai, ci si costruiscono comunque cose molto interessanti nonostante tutto.

Non mi pare che il refactory dell'ATC rientri nelle feature della prima release della 2.9. prestazioni migliori tra MT e DLSS sicuramente con la 2.9 ci sono. Questo non vuol dire che DCS può girare sulla scheda integrata di un portatile eh, ma il miglioramento è netto se si paragona a quello che c'era anche solo qualche mese fa, prima della MT.

If the quest3 becomes really popular, and it looks like, I think ED should be start to integrate a native way for MR, that is way far better than VR experience. I Didn't have the quest3 yet, but tested the mixed reality with Varjo XR-3 and it was really insane. Can't wait to have native support for it, and maybe a adeguate Mixed Reality headset as well

Sarà presente nella 2.9, che al 99.9% dovrebbe essere la prossima Build Open Beta. Non hanno indicato un tempo massimo, ma se tutto va come deve, potrebbe arrivare questo mese. Prima o dopo non è dato sapersi.

No. È una tecnologia che permette principalmente di tenere un alto frame rate, non di migliorare la qualità dell'immagine finale, almeno non nelle sue attuali versioni. Dalla 3.5 in po nvidia si è data come target quello di migliorare anche la qualità finale, ma fino alla 3.5 era il contrario anzi, il DLSS poteva in qualche modo risultare meno "dettagliato" di un render nativo a pari risoluzione.

Not even able to run it at all, not only "properly". DCS server is an X64 windows application. You have to buy Windows mini PC like intel NUC or any other clone with a strong single core performance CPU, like at least a 3.5Ghz and not older than Intel 7th gen. So raspberry pi5 => not at all Intel NUC and other mini PC depend on the performance that you expect from that server ( how many players, how big and complex is mission with AI and so on )

And you think that just this little drawback It can really annoy cheater or prevent them to do it? Adding this "forced option" you'll just "encourage" them in do it, since they will feel more fulfilled to accomplish their "advantage" against the other. It's the same behavior of problitionism.....we are ( humans ) strange animals As I said, I don't believe there will be any real benefits to do this, since the workaround is really too easy, can't be detected, and with a small drawback.