davidp57

Hi BigNewy, thanks for your answer ! I'm afraid I wasn't clear enough in my original message. The problem is not that I cannot enforce options in my missions (I totally can), it's that everytime I save a mission, my personal options are stored in the mission (with my callsign, and everything) despite my having unchecked the "use these options for all missions" checkbox : I attached 3 missions created in 3 different environments : test1-myconfig-nomods.miz : removed all DCS mods, cleaned up DCS, kept my config and tech mods (SRS) test2-myconfig-nomods-notechmods.miz : removed all DCS mods, cleaned up DCS, removed all tech mods (SRS) but kept my config test3-newconfig.miz : brand new config (removed the Saved Games\DCS.openbeta folder altogether As you can see, there is an file named options in all 3 mission files. In the first two files, it contains my personal options (you can see my callsign). In the last of course, I created a new configuration, hence the new callsign. What do you think ? Did I misunderstand the concept ? Is this a bug ? Thank you for your help as always ! Kind regards, David. test1-myconfig-nomods.miz test2-myconfig-nomods-notechmods.miz test3-newconfig.miz

This setting used to cause (when checked) the player's options to be stored in any mission he'd create (or simply save) in the mission editor. It's been a while now, a few month maybe, but I'm sure now that this setting does not work anymore. Whatever the value I choose for this setting, a newly created mission will always contain a file named "options" that contains all my personal options (these have nothing to do with the "forced options" in the mission). Is there something I'm missing ? Can you tell me how I can help make this bug report more useful ?

*bump* Et édition pour plus de clarté et parce qu'on a changé de forum ;)

Thanks!

Nah, it was already "per application" ; I used to force it in DCS

it's in the same place as the options.lua : <Saved Games>\DCS.openbeta\Config\autoexec.cfg

nice, thank you !

I had this kind of behavior with the flashlight and some lights in the cockpit, due to my adding this line to the autoexec.cfg file : options.graphics.stereo_mode_use_shared_parser = true

Je comprends et je respecte ton choix (même si moi c'est plutôt l'inverse ^^) Mais ce que je voulais dire avec cette invitation c'est que nous avons ouvert notre serveur au public, et que tu pourrais venir partager ce que tu souhaites avec les gens qui seront connectés, sans pour autant participer à la vie de la VEAF !

Salut ! Je t'iinvite à venir voler avec nous !

Thanks Ciribob for all these answers, this is great support. You have however missed my very own question, it makes me sad :cry: :music_whistling:

Hi folks, This may already have been asked and answered but I didn't find it so here I go : is there a way to have two distinct SRS servers, each linked to a distinct DCS server on a single machine ?

Bonjour, La VEAF vous propose un serveur public, gratuit, sur lequel vous pourrez profiter de notre travail sur une mission d'entrainement ouvert dans la map Caucausus et rencontrer d'autres pilotes francophones. Cette mission propose, sur (presque) tous les aéronefs : Des opérations aéronavales pour les deux porte-aéronefs (mobiles, au vent) Des zones de combat de différents types (CAS, Strike, entrainement) dynamiques et réutilisables Des vols IA comprenant des tankers et des awacs (côtés rouge et bleu) Des vols IA aggressifs rouges Des places pour joueur dans des aéronefs rouges pour PVP Pour le moment, la documentation est en cours de réalisation, mais le serveur est prêt à vous accueillir, à condition de respecter certaines règles très simples : Pas de teamkill ! Vous serez bannis du serveur si vous faites du tk ; si vous pensez avoir été bannis à tort, dites-le nous sur notre TS ou Discord Ne détruisez pas le matériel ! Evitez de bombarder votre propre aéroport, ça nous évitera de redémarrer le serveur trop souvent. Connection audio TS / Discord - merci de vous connecter à notre serveur TeamSpeak (ts.veaf.org) ou à notre Discord (https://discord.gg/WFGbpGz). Connection SRS recommandée - merci de lancer SRS qui s'autoconnectera avec notre serveur, et de laisser ouverte une fréquence commune (U282 pour le côté bleu) ; en plus, faire les communication sol sur la fréquence de l'aéroport serait idéal ! Pour trouver notre serveur, tapez simplement "VEAF" comme mot-clé de recherche dans la liste des serveurs.

We use a dedicated server running ESXi, rented by SoYouStart

-> SlMod

Could you tell us more please ?

+1

I also noticed this, but I thought it was because my secondary screen (where the extraction goes) was darker.

Well, I don't (get an lGroup value), or maybe I do but I don't know it ? Here's my code : https://github.com/VEAF/VEAF-Open-Training-Mission/blob/master/src/scripts/veafRadio.lua The event handler is at :101, and the code that sets it is at :379

Since I installed the latest OB on my dedicated server, I can see this error in the log : Lua::Config: Call error world.onEvent:[string "-- world events hook..."]:466: attempt to index local 'lgroup' (a nil value) stack traceback: [C]: ? [string "-- world events hook..."]:466: in function <[string "-- world events hook..."]:313>. And I'm pretty sure the S_EVENT_PLAYER_ENTER_UNIT event does not work anymore. Here's the start of the log so you know exactly what we're running and on what : DCS: Command line: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin\DCS.exe" --server --norender -w ob_caucasus DCS: DCS/2.5.5.38040 (x86_64; Windows NT 10.0.10240) DCS: Hwid: A5kNoyP7z25p2aTQKkLZt6RaCiCWGYaZ7ual1A DCS: DCS revision: 158031 DCS: Renderer revision: 19261 DCS: Terrain revision: 19589 DCS: CPU cores: 2, threads: 2, System RAM: 16383 MB, Pagefile: 19327 MB EDCORE: (dDispatcher)enterToState_:0 Dispatcher: 2019/10/19 13:11 V1803061700

I would go with the NVME SSD. Extra RAM can't hurt either. My system is similar to yours (except a bit more recent CPU - i7 8700K, 32GB RAM and a NVME SSD) and I get around 45 fps with decent graphical quality (reduced shadows, 2x MSAA and HIGH view distance).

Thanks ED ! I made a "latched zoom" keybinding : {category = vr , down = iHeadTrackerZoomToggle, value_down = 1.0, name = _('VR Zoom IN')}, {category = vr , down = iHeadTrackerZoomToggle, value_down = 0.0, name = _('VR Zoom OUT')}, {category = vr , down = iHeadTrackerSpyglassZoomToggle, value_down = 1.0, name = _('VR Spyglass Zoom IN')}, {category = vr , down = iHeadTrackerSpyglassZoomToggle, value_down = 0.0, name = _('VR Spyglass Zoom OUT')},

Not that I know of ; last thing I know is that the author moved to a GitHub-hosted, open-source distribution which is the coolest thing he could have done ! I think it'd be nice to find someone to help him with this project. I may take a peek sometimes but not right now.

same, hot start + ext tanks

Just did this for the F18 : HMD off (knob fully left) or ON (fully right) {down = hmd_commands.BrtKnob_AXIS, up = hmd_commands.BrtKnob_AXIS, cockpit_device_id = devices.HMD_INTERFACE, value_down = 1.0, value_up = -1.0, name = _('HMD 2-Pos ON/OFF'), category = {_('Toggle Switches'),_('Instrument Panel')}},