Maverick87Shaka

Not sure it was the problem, but on line 5282 of the log you have: 2023-01-13 14:57:06.433 INFO Scripting (Main): event:t=1144.311,comment=winner: , msg: ,type=mission end, It looks like on server was triggered mission end.

Not really recommend to make several jump between builds but yes, it's possible. In this post you have a very detailed procedure for many different actions, but basically you need to open a prompt command in the BIN folder of your DCS installation, and run DCS_updater with some arguments depending on what you want to do. On top of this, you can also consider to use the really great tool DCS GUI Updater, to manage your installation.

2 core is not even enough to run decently windows itself, I will not recommend to run a VM with 2 core a DCS server. Go for at least 4 cores. not enough to run 15 days without any reboot, but you can schedule most of the work

Era stato annunciato un heavy lifter, le opzioni erano CH-47 o CH-53, io avrei preferito quest'ultimo anche per integrarlo in eventuali missioni Navy etc, ma anche il ch-47 ha il suo perchè, finalmente abbiamo un qualcosa anche lato coalizione blu per fare logistica a livello serio. Condiviso la speranza per il blackhawk, elicottero stupendo e molto versatile, semplicemente non era il suo momento su DCS, speriamo possa arrivare per il futuro

Non sono esperto di TrackIR perchè ho sempre usato il TrackHat, che utilizza una webcam normale ( ps3eye ) di cui puoi visualizzare all'occorenza per fare un pò di "debug" guardando il flusso video. In una occasione simile alla tua, il mio problema era dato da una maglietta che indossavo che rifletteva su una parte di decorazione, e dava fastidio alla camera. Quindi il consiglio che mi sento di darti è quello, controlla che non stai usando cuffie o indumenti con superficii lucide che possono riflettere o cose simili. è un consiglio banale me ne rendo conto, ma a me era capitato proprio questo, magari è lo stesso oggi per te.

Ragazzi non voglio deludere nessuno, ma giusto per non creare false aspettative, non aspettatevi un 30% / 40% di FPS in più in ogni circostanza, sempre e comunque. Non è che parliamo di magia nera o di una bacchetta magica, dove basta mettere una spunta su multithread o DLSS e come per magia tutto funziona, non è così "banale" la questione. Sicuramente avremo dei benefici che arriveranno tra l'altro gradualmente nel tempo, probabilmente per primo avremo i risultati dallo sforzo della ED di parallelizzare di più il carico di lavoro ( MultiThread ), che aiuta nei momenti di "affanno" del simulatore e appiana un pò nei momenti di "stutter". Questa tecnologia non è un "super booster" di FPS, aiuta nei momenti in cui si "impasta" principalmente. Poi arriverà il DLSS (e non sappiamo ancora in che versione purtroppo) che aiuterà sugli FPS massimi, andando però un pò a penalizzare latenze e qualità dell'immagine in alcune circostanze. Se per le latenze non è un grosso problema visto che non parliamo di uno spara-tutto competitivo, per il discorso qualità immagine bisognerà vedere il risultato finale. L'upscaling AI è una bella tecnologia, a volte sembra restituire immagini addirittura migliori di quelle a risoluzioni native, ma potrebbero "discostare" dalla reale, visivamente appagante, ma non "reale" in tutti i suoi minuscoli pixel. E infine, più in la, arriveranno anche le Vulkan, che anche qui, non parliamo di magia nera o bacchetta magica, è semplicemente uno strumento di sviluppo più moderno e che consente agli sviluppatori di cercare di spremere al meglio l'hardware a disposizione, accedendo anche direttamente a funzioni hardware di GPU che con librerie vecchie non erano gestibili dagli sviluppatori. E' sicuramente tutto positivo, ma non mi aspetterei un secco +30%/+40% sempre e comunque, altrimenti rischiate di rimanerci molto molto male. Non è dando il cacciavite più avanzato del mondo in mano a una scimmia che potrete sperare che questa vi aggiusti il motore della vostra auto! Sicuramente dato a mani esperte e sapienti può aiutare a far fare bene il proprio lavoro un cacciavite stupendo e avanzatissimo, ma non è che farà il lavoro al posto vostro, non so se rendo l'idea Detto questo, buon 2023 ricco di novità, speriamo in bene, ma coi piedi per terra anche se siamo aviatori virtuali, che poi se cascate dall'alto vi fate male Fly Safe.

Since the limited number of available IPv4 address ISP can put their users behind a "natted" network, at least for the IPv4. If you don't have a public IP address you can't host services, including DCS server. ( or you can try, but no one will be able to access your hosted service ) DCS Server also support IPv6 apparently, but I've not used personally under pure IPv6, so I'm not sure how ( and if ) it will works. You can try to use packet sender app to verify your network configuration and be sure if you have a public or natted IP address. You can also try to call your ISP and asking them if you've a public ip address or not.

All our instances run more or less in the same way of the past releases, no substantial changes noticed. just the first release ( before hotfix) goes in crashloop, but it was fixed. We run servers with slmod, srs autoconnect and lot of moose script in mission environment, no strange crash so far. Cheers, and happy new year Fly Safe.

Same here on all our public servers, like was for the A-10 in the past, BS3 slot was added and not replaced. Fly Safe

Ciao Francesco benvenuto. La scelta del VR per DCS è "coraggiosa", purtroppo perchè non è un titolo nato per il VR, è stato aggiornato col tempo per renderlo graficamente appetibile, ma a discapito delle performance. In futuro ci sono diversi aggiornamenti per mitigare la situazione attuale, ma ad oggi questo è. Questo purtroppo si traduce nella costante battaglia tra impostazioni, compromessi nel dettaglio grafico, etc, e questo quasi a ogni aggiornamento di DCS o di driver della scheda grafica, purtroppo per quanto bello bisogna starci dietro parecchio. Se preferisci qualcosa di più: "installo e non ci penso più" ( o quasi perlomeno ) ti consiglio vivamente un setup tradizionale, magari con un bel monitor 21:9 e un sistema di tracking della visuale. Di discussioni ne trovi già parecchie, anche in italiano, ma nel caso apri pure un topic nuovo e continuiamo li il discorso pc. Saluti, Buon Volo!

If you un-pause the server something change? On my instances is working fine with Slmod installed: The only difference is that my server is not paused.

Hi Mark, Sorry we don't have staff dedicated to monitor the forum, so we miss your question. I guess we've solved your particular issue in our Discord, but I'll leave here the answer so it can be useful for future people with the same problem. Actually DCS-Bios relies only on DCS export.lua logics, it means that what you have to do to uninstall DCS-Bios is remove the DCS-BIOS folder from your Scripts folder, inside saved games. Then you can open Export.lua file with a text editor, and remove the line relative to the DCS-Bios. The default line for dcs-bios is: dofile(lfs.writedir()..[[Scripts\DCS-BIOS\BIOS.lua]]) dofile(lfs.writedir()..[[Scripts\DCS-BIOS\BIOS.lua]]) Not sure if the one from dogfight boss was customized, but it should be similar. Regards, Andrea

Ask a friend or someone to attempt a join on your server, and look at the DCS.log on their client ( on server side is clear you only have the line for player connecting. maybe we're lucky with client log to identify the problem ) Another thing to check, make sure that you have opened also the relative UDP port and not just TCP for DCS. Since TCP will be used for initial "handshake", but then continuous traffic will be exchanged on UDP. Let us know, Fly Safe.

In ritardissimo......auguroni a tutti di Buon Natale e Buon anno nuovo! Dai che il 2023 ci riserva parecchi moduli interessanti all'orizzonte!

UH-60 or any other variant of that superb base. CH-53, King, Sea or Super Stallion Simple but effective! Blue coalition is lacking heavy lifter to pair with AH-64

DCS dedicated server build It works really fine on windows server 2019 and also on 2022 that is my current "prod" environment for DCS public server. There is a long dispute between Microsoft and hosting companies for this, basically it's a licensing problem but they're trying to leverage on unfair business competition.......I guess it will not happens in two weeks ( I couldn't resist sorry ) to see Win 10 as main host OS on big company, but I strongly recommend to host server on Windows Server an not Win 10 / 11 even if it will be a future available options Cheers, Fly Safe and Merry Christmas

I've used in the past, for about 3 years long, a dedicated rented machine with Proxmox as host OS, on top of that a Windows 2016 VM to run DCS. I start using Proxmox just because it was one of the option available at the time, but I really love it, and then I start to use it also on work and other lab environment, it works fine. When I put back the server in my lab I've done some performance test, and DCS runs better on native Windows host rather than have it Virtualized. Not sure why, maybe lack of some direct hardware acceleration that is "translated" from VM to hardware by Virtualization software, but even just transfer speed for ssd was little bit slower. So after this benchmark that I've done, I'm now running again Windows as main OS on dedicated hardware to host 3 public instances and one private instances of DCS server. So my suggestion is go for Win Server directly on the host if you can, if not, just use any hypervisor that you are familiar with Cheers, Fly Safe.

Hi Wood, We're running all our instances with SlMod and we didn't find any incompatibility. Just usual crazy behavior that time to time ( generally works fine ) if you use -admin reload command, mission restarts but some triggers or even some hard placed vehicle thought Mission Editor, doesn't spawn. Reload another time or complete server restart usually fix it. I guess it's something related to "corrupted memory" that are not freed up correctly. ( memory leak ), but it's something that is present by many release so far. Our current release is the latest OB dedicated server, at the 21 Dec 2022 is 2.8.1.34437 Fly Safe

if ED release the current OB to stable, you'll complain about stability, as many other has told you, this current 2.8.1.34437 OB is far away to be a "stable RC". If you want fly the new KA-50 III, update or install the OpenBeta. When an OpenBeta build will be ready, it will be promoted to Stable. There is not a fixed amount of days to do that, and make pressure for a release it's only getting things worst, and you can have a stable that is really unstable, so why don't download openbeta? Fly Safe, and on OpenBeta

You have several error in your log, last one is a memory access error ( did you try to reboot the whole pc/server after update? ) First one is: 2022-12-18 13:51:18.251 ERROR SCRIPTING (Main): Mission script error: [string "C:\Users\spara\AppData\Local\Temp\DCS.openbeta_server\/~mis00005365.lua"]:1795: attempt to index field 'DBs' (a nil value) stack traceback: [C]: ? [string "C:\Users\spara\AppData\Local\Temp\DCS.openbeta_server\/~mis00005365.lua"]:1795: in function 'getGroupId' [string "C:\Users\spara\AppData\Local\Temp\DCS.openbeta_server\/~mis00005365.lua"]:1577: in function <[string "C:\Users\spara\AppData\Local\Temp\DCS.openbeta_server\/~mis00005365.lua"]:1566> 2022-12-18 13:51:26.666 WARNING LOG (9700): 1 duplicate message(s) skipped. 2022-12-18 13:51:26.666 INFO SCRIPTING (Main): 65452( -1)/I: RANGE06772.function(RANGE Training Range Helo | Range status: Running) 2022-12-18 13:51:26.666 INFO SCRIPTING (Main): 65452( -1)/I: RANGE06794.function(RANGE Training Range Jets | Range status: Running) 2022-12-18 13:51:26.666 INFO SCRIPTING (Main): 65452( -1)/I: RANGE06818.function(RANGE Mobile Range | Range status: Running) 2022-12-18 13:51:28.260 ERROR SCRIPTING (Main): Mission script error: [string "C:\Users\spara\AppData\Local\Temp\DCS.openbeta_server\/~mis00005365.lua"]:1795: attempt to index field 'DBs' (a nil value) stack traceback: And it looks like something related to your scripting. Try with a clean mission to validate your DCS server installation, and than look at your DCS.log and fix all your scripting error.

Workload on server admins are already relative high, manage .miz file, scripts, and server itself are really time consuming activity, on top of that they usually pay the bill for hardware or hosting their server and make them available to the community for free. Add more work to server admins to make a granular blacklist or whitelist of what file can be modified is not a good idea TBH, not at all! Also for final user experience that they don't even know what to expect on joining servers, since configuration can be slightly different in this hypothetical scenario, it's not good. You can end to have a gauge that work on a specific server, but not in other, but in that other works some display and not the gauge. It doesn't sound a good idea. To me what could be a great approach ( it will require times of course ) it's make all the gauge and display "public" and with their unique ID ( including front/rear seat I.e. of AH-64D ) so people can customize their multi monitor setup from saved games folder instead edit core games file. To be clear, it's not a quick solution, it will require times, edit to all the current modules, every 3rd parties should also comply with this standard, but it's the only way to guarantee that no core games file are tamped, leaving the ability to people to customize their MultiMonitor export in details, and not just MFD screen and few options that we've today.

No, updater will download only new files. The problem is that you have no control on dedicated server, what map you want to include in your installation. So basically during first installation it will download every map available, and the disk required for dedicated server is taking a considerable amount of space. Many servers admins since they don't use all the maps, would like to have the option to select which maps has to be installed ( and kept up to date ) This option is available for full client installation, but not for dedicated server package/binary.

I'm not sure remove or change how IC works it's a good idea TBH, but definitely it would be nice if it's possible to "expose" some of the feature like the gauge/display, and make them available. If every gauges, displays etc has it's own name ( public), everyone will be able to export what they want using the correct procedure of making custom MonitorSetup .lua script inside saved games folder. EDIT: I'm also a server admin, and even if it's just a PvE since we have public statistics, its fair to leave integrity check on. But I can understand who wants to enjoy their own simpit.

MIPS and other device like UFC, can still use some export option that is already available built in in DCS or using MOD that doesn't change core engine files, but create export from it.

Client doesn't need a port forward to works. You can safely remove them. My suggestion is to disable UPnP feature, and remove the automatically generated rules, and leave only the manual port forward to your dedicated server.. Regards, Andrea