Maverick87Shaka

Thanks for feedback.... opened thread under bugs since looks like the voice chat server is not turned off at all.

Not sure if it's apply only on menu item build with moose, or should be a general FIX for every script generated menu item, but today it's happen to me again that i have to do the ESC trick to shown CTLD menu. With latest OB 2.5.6.45317

Hi, Anyone else with the latest OB 2.5.6.45317 has lot of entry on server for the voicechat? 2020-03-21 23:53:45.423 INFO VOICECHAT: Get message from peer_id=15, peer_message {{ "event": 1, "peer_id": 1, "coalition": 0, "mic_mode": 2, "room_id": 0, "display_name": "[bSE] Shaka" } } even with voice chat server disabled in serverSettings.lua: ["voice_chat_server"] = false, it's pretty "flooding" my DCS.log at the moment!

There is a mission with scripts on auto start? try to load a simple mission without any scripts, also try to remove ( if you have ) mods like tacview,lotatc and slmod. Clean install of latest OB dedicated server and even full client installation running with --norender is running fine on all three different machine where I tested.

Is this a clean installation ( without slmod,tacview etc ) or you have any mods? I'm running clean open beta server without any issues.

:thumbup: Title it's a little bit generic but linked to this thread for reference........ And I really appreciated to have changelog linked with Forum thread to give it a consistency! Thanks @c0ff ;)

Doesn't sound like a good option, but no other chance to make RestartOnCrash working since seems not able to select program based on the command line parameter, or window name, so it's impossibile to use it on multiple instances i think :(

The FIX is inside the 2.5.6.45317? I Can't find anything on changelog regarding this issue. Thanks. :thumbup:

If you want use Restart ON Crash you just need to append in the ROC configuration in the execute command the -w parameter with the instance name, for example "C:\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe -w server1"

Windows Mixed Reality è la piattaforma AR/VR sviluppata da Microsoft e integrata con Windows 10. Non è un software a parte da comprare. Dovrai solo utilizzare questo per confgurare il visore, e usare il plugin steam per poter utilizzare un visore Mixed Reality dentro SteamVR. Ma non è nulla di sconvolgente, accade anche con Oculus o i PiMax ( almeno fino al 4K che ho provato di persona ) Non mi preoccuperei più di tanto di quello :thumbup:

La pedaliera la trovo molto comoda, i pedali sono alla giusta distanza per essere confortevoli, anche se i materiali plasticoni li si sentono nettamente "flettere", ma va beh, se la trovi al suo prezzo minimo di 116€di Amazon secondo me è perfetta, a listino pieno di 150€ secondo me non li vale. Arrivavo dai Thrustmaster Flight Rudder Pedals, che trovavo un pò "scomodi" per la vicinanza dei pedali, ma che ai tempi mi servivano per ragioni di spazio perchè compatti. Quelli erano molto precisi e più "solidi" ma ora che ho spazio odiavo il fatto che fossero così attaccati. Per il VR, taccio perchè lo odio, forse perchè ci lavoro chi lo sa! :megalol::megalol::megalol: Scherzi a parte, detesto il fatto di dover scendere a compromessi sulla qualità grafica per usare il VR, e che in alcune circostanze per me tipiche di gioco multiplayer, è troppo limitante, aprire e gestire più robe che con un monitor fai con un alt tab, diventa impossibile in VR. Diciamo che il VR non matcha con il tipo mio di gameplay, ma non mi dilungo oltre e lascio la parola a chi predilige quel tipo di esperienza ;)

Don't take a Nitrado Server for DCS ( I think also doesn't exist ), completely useless and worth the money. Select a bare metal provider based on the zone you want host ( for EU zone ) I personally recommend OVH . It's one of the most reliable provider for price. Then you need to think how many instances and how you want host server: dedicated, full client host, full client with --norender option and so on. Based on this you can tune you server specification. I personally recommend to don't go under 3.4Ghz CPU with at least 16GB of RAM and SSD disk. If you plan to run multiple instances 24/7, you should probably get 32Gb or more.

If your server is inside your LAN, the short answer is no, if you disable ipv6 on client or server, you will no longer be able to see it in the server list at all. You can always use connect by IP button and fill up your internal IPv4 address manually, and connect using that protocol. But there is no reason to do that.

Allora il suggerimento è sempre lo stesso, provare la funzione singola e poi dare un'occhiata sempre al dcs.log, se c'è qualche errore alla fine esce sempre li anche se sbagli qualcosina sul moose ;) Altro consiglio, cercare sempre "ispirazione" dalle missioni di esempio del moose, ci sono molti esempi interessanti. Ultima cosa, vedo che stai facendo un ForEachClient, quindi devi gestire poi singolo client, mentre invece cerchi di restituire il messaggio mandandolo a tutto il SET, quindi non a un singolo client, ed è quello il problema che hai in questo tuo script. Provalo cosi: -- Create the zone MTA = ZONE:New("STATIC BOMB MTA B") -- Create a set of Cadetti Client Cadetti = SET_CLIENT:New():FilterCoalitions("red"):FilterStart() Cadetti:ForEachClientInZone( MTA, function( MooseClient ) if MooseClient:IsAlive() then MESSAGE:New("PROVA CAZZO", 20 ):ToClient( MooseClient ) end end ) Dove nella variabile "MooseClient" tu avrai il singolo client a cui passare il messaggio: Non ho avuto modo di provarlo, in serata magari se riesco provo e ti dico ;)

:mad::mad: 480000 X 40USD (facciamo una media tra full e sconti) => 19.200.000 USD in un anno e non riusciamo a far accendere 4 luci :megalol::megalol: Era quasi meglio non saperlo! Uno schiaffo a chi spende soldi e tempo a cercare workaround per far andare questo gioco, a volte mi fanno davvero passare la voglia se devo essere onesto.

After upgrading to the latest version, i have a lot of report ( and kicked people ) for HITTING friendly unit carrier on landing or "micro lags" on spawn. (kamikaze) It's possibile to disable just for carrier? With an old version never seen it:

For simple radio, you see the frequency goes away from overlay because it's taking the one from the airplane. SO you need to start up the airplane and turn on and set the frequency directly inside the airplane, I suppose. I don't fly P-51 so i'm not sure, but it's normal behavior with all other airplane that I fly.

For sure it's not on top priority list, but it's still there on OB 2.5.6.44266 ;)

Tutto molto bello, intanto sono due anni ( e forse più ma nessuno se ne era reso conto ) che aspettiamo un fix per far accendere 4 luci della pista in multiplayer, e ancora non funziona una mazza. E la ED si prende la briga di chiudere i post a caso e dare warning se gli "ricordi" che sarebbe bello avere qualche aggiornamento in merito. Speriamo che possa davvero cambiare corso prima che sia troppo tardi, per lei e per noi :D

[maybe REPORTED?] Runway Lights by night works only server side Hello my friend, The new OB 2.5.6 brings a new looks to DCS, and it's pretty amazing in terms of lighting system. We're still suffering of Runway lights not working on multiplayer for clients, if the server starts on daylights and then turn into the darkness, no matter if you try to contact ATC or everything else, the runway lights remain off! I have a tons of feedback of player that loves sunset and some night operation, but as server admin I hate the problem of lights since there is nothing that I can do! There is any update that you can share with us? It's literally 2 years now that we had this problem, I really want to brings more night/sunset to my servers, but this bug prevent to do this. As I suggest in the past, I hope you can consider at least a workaroud where you can force the lights "on" by mission editor, or link the runwaylights to other behavior. For example, all the city lights, some airfield parking lights, even carriers lights turn on for all client based on the mission time, can you chain also the runway lights to that logic? You already have the behavior you just need to move runway lights from actual logic ( that is not working ) to this one. I'm pretty sure calling ATC and other stuff can bring more realism, but I mean, if it's not working it's not realism, it's just annoying and you need to find a solution. For your reference: ORIGINAL THREAD Thanks

Best way it's try with another computer connected with your phone tethering or some other connection ( different from the one of the server ), and take a look at server list end try to join. If you can't test in this way you can try to use ONLINE tool, fill the form with DCS server public IP/Port, and see what it's going on. Normally should say that: IP is responding on port xxxx.

I got your point ..... and I think everyone is free enough to do what they prefer. I'm not going to spend time on what could be nice and bla bla bla..... BTW..... you can take out all the scripts, making the mission "inoperative" if palyers try to run it, if you've done a lot of things by scripts. But you can't stop people from opening the .trk file and seeing (if you did it within Mission Editor) all the plane template, all the trigger zone, all the unit used to create a polygonal area with moose, see hidden vehicles etc.. etc... From this point of you, unless you move everything outside mission editor using for everyting Vec2/3 and bla bla bla, people can always try to get a little bit of advantage if they want to take a look to .trk

Si alla peggio faccio come avevo fatto per gli aeroporti all'inizio della persistenza, col riavvio della notte delle 01.30 resetto tutto quello che è stato piazzato tramite CTLD, quindi renderli persisti solo durante la giornata se vedo che inizano a piazzare SAM ovunque e rendono sbilanciato il server ahahahahah. In realtà mi piacerebbe fare una cosa diversa, così come ho fatto per gli aeroporti ora, anche per gli eventuali SAM, così al posto che essere un reset manuale diventa qualcosa di più "dinamico" e immersivo. Ma non facciamo spoiler se no poi che vi racconto per la V3.3 ? :megalol::megalol::megalol::megalol:

We've finally released the V3.2 of our popular PersianConquest server. Actually the webpage statistics are turned off, as you may know there is a problem with the OB 2.5.6 that mix up client id, and results in wrong stats. We're going to reset and start over after ED fix this issues ( seems to be ready and will be released in the next patch ) What you can expect on V.3.2? The main feature of the V3 is the persistence of conquer mode. If we take an Airfield it will be on our coalition even after restart of the server. We just have to defend it when AI try to get it back! With the last iteration released tody, we've expanded helicopter gameplay! All the units that you dedice to transport with CTLD it will be there even after server restart now! Giving a more crucial and effectiveness task like this one to helo pilot is one of our goal for the next couple of release. Stay tuned and have a nice flight. :joystick::joystick:

Sicuramente su unità specifiche dovremo lavorarci, ho paura che anche i JTAC, dopo il riavvio, siano "inerti" e inutilizzabili, purtroppo come dicevo non l'abbiamo testata più di tanto, aggiusteremo in corsa, tanto la 2.5.6 è davvero piena di problemi e ha scassato molte logiche del server, quindi in questi giorni ci lavoreremo costantemente e vedremo caso per caso cosa fare. Grazie del feedback ;) Ci guarderemo subito