cfrag

Well, at least here I can help: DML's bank hasn't officially opened yet - that module is still experimental and hasn't yet received an UI part

Unfortunately, DCS itself isn't compatible with the "Save Mission" feature. Meaning: any mission that you save using that feature is so broken, that you can't really continue it. To me, that feature appears as a low-effort attempt to shoehorn something onto DCS that was never designed with save & continue. To me it also seems evident, that very little, if any engineering has gone into this. Should ED continue with the present-day architecture of this feature it won't ever become a "Save & Continue" feature that we are hoping for. All we will have is a (very) cheap & dirty solution for a non-existing problem. So is Expansion compatible with "Save Mission"? No. Currently DCS does not meet the requirements for such a feature. I'm thinking about bringing Expansion to other maps, yes. The stunning deterioration of quality in DCS's core gives me pause, though, and I'm currently scaling back my efforts.

Until DCS offers commands to units, it's always single-player groups, yes.

Well, I can always take a look at the miz - if you send me a (mods stripped) version of the miz.

Just to be sure that you are not as stupid as I was a few weeks ago when I encountered something similar, please try the following - remove the action that loads scribe Create a new DO SCRIPT action, and paste the scribe source inside I accidentally pasted another module twice (to make it worse, I managed to do it across different actions). Maybe that is the issue?

Version 20250502 - DCS Bug fixes, minor cosmetic updates This update works around a show-stopping bug introduced with the past DCS release. And, whatever you do, DO NOT USE DCS' "SAVE MISSION" FEATURE. THAT WILL FUBAR THIS MISSION. Changes in Detail: - hardening against many show-stopping DCS bugs - small optical enhancements

Version 20250502 - DCS Bug fixes, minor cosmetic updates This update works around a show-stopping bug introduced with the past DCS release. And, whatever you do, DO NOT USE DCS' "SAVE MISSION" FEATURE. THAT WILL FUBAR THIS MISSION. Changes in Detail: - code hardening against DCS bugs (a lot!) - smoke zones upgrade - fireCtrl, airTank - minor scenery alignment - minor optical tweaks (Hips) - persistence DCS show-stopping bug hardening

Ah. Thank you for the additional information. Please try the following: look for, and delete the folder "tempMission (data)" in your Missions/ folder. Restart the Mission. Does it work now? If so, remember that you now (until ED fix the bug that causes this) must supply a saveDir and saveFileName attribute with some nice names in the persistenceConfig zone.

I'm having difficulties re-producing the issue. Can I trouble you to do the following: download the demo mission from DML (updated for current DML), see attached Run as SP, go to communication->Other and choose the option to spawn the CSAR via flag 100. The CSAR mission should spawn. Do the same in MP. Is there any difference for you? Note that - unless you configured DCS differently - when you run local server, the mission starts paused, so in order to be able to spawn the CSAR, you must un-pause the mission first. Do SP and MP give different results on your DCS? They seem to work the same on my DCS (which may mean nothing ) demo - CSAR of Georgia.miz

Thank you. Can you elaborate what "working" means? Put differently: what does "does not work in MP" mean specifically? Can you describe a situation in detail as it happens correctly in SP, and how that happens incorrectly (and how that seems incorrect) in MP?

Up until recently, invoking DCS.getMissionName() would return the name of the mission currently running. Now it ALWAYS returns the same constant 'tempMission' Simply run this script in any mission -- say my mission name local mn = net.dostring_in("gui", "return DCS.getMissionName()") trigger.action.outText("Hi, my mission name is <" .. mn .. ">", 30) it now ALWAYS returns "tempMission", which is wrong This breaks a lot of functionality, especially for missions that need to know their name (e.g. any mission that wants to use some kind of homegrown persistance). Dear @Flappie, may I enlist your help in directing this to the attention of someone who can help? Thank you, -ch Oh, I've attached a mission to reproduce the issue, as described above say my name.miz

CRAP!!!! It seems that the kind (if not, as it seems, very talented) people at ED have f*(%ed up the Mission Scripting Environment with the last release. Yeah, as a result it has taken down DML's persistence. The only workaround at this point in time is to use both saveDir and saveFileName in your persistenceConfig, else it will always save (and overwrite) to this stupid "tempMission" folder/file. saveDir A folder (allocated if it doesn’t exist) inside serverDir where persistence will save the mission data into a separate file. You can use this to pool multiple missions’ data into the same folder. Defaults to “<mission name> (Data)” (see note below) <-- NO LONGER WORKS, MUST BE SET IMPORTANT NOTE If you completely omit persistence’s config zone, it reverts to simplified save mode, and defaults saveDir to “” (empty string), saving the mission’s data file directly into the serverDir. saveFileName The name for the data (plain text in JSON format, can be edited with any text editor) file inside saveDir. Defaults to “<mission name> Data.txt” <-- NO LONGER WORKS, MUST BE SET Thank you @Recluse for alerting me to this. And WFT ED????? Yes all missions that use DML's persistence now need an overhaul. This includes all my missions (Expansion, all Angels, and 20+ others that I have published). So, which bunch of clowns at ED thought it a good idea the screw with the internals so that DCS.getMissionName( ) now always returns "tempMission()", and which band of jokers did not regression test this before releasing it to production? Franky, you know that I work in the industry, and where I work people are getting fired for less. I can take a lot amateurism from a game company, but I think you should draw the line somewhere before it reaches the clownishly absurd. Does DCS Mission Creation really have to be such a clown show?

How did you notice that? In other words, how did you set up csarManager, what did it do in SP (single-player) that it did not do in multi-player? I'm sure that we can get to the bottom of this quickly. As a general rule, DML does not differentiate between SP and MP, and works the same for both.

Why do you think they can't?

That is how persistence works. Unless you change the defaults, it saves all data into a file of given name x: as a file named "X Data.txt", and that file is put into a (new) folder "x (data)", and x defaulting to the name of the mission file sans extension. Details are outlined in 5.3.31.2 and 6.9.1 of the "shock block". If the mission is called "tempMission.miz" then yes. Note: the name "tempMission" sounds awfully close to the mission name that DCS's Mission Editor assigns to a mission by default should you 'fly again' or responded "no" to "Save Mission" after a change before entering it from ME Please revisit the config zone for persistence and see if maybe there is a setting for saveDir that sets it to "tempMission".

This is only for dynamic players, and it is indeed annoying. Changed, thank you for the hint! SSBClient.lua

OK, let's try that again I may have detected a bug in the hysteresis handling valet.lua demo - valet on the groundI.miz

Let’s try and approach this methodically: can you get it to work without firstGreeting? if so, that helps me home in on the potential cause.

You asked for it, you got it Attribute is "groundOnly", setting it to true only triggers when the unit also is on the ground (so yes, you can use it for runways, and it only triggers after the unit has touched down). Demo miz included. valet.lua demo - valet on the groundI.miz

It's used in the "Angels" mission to add some "flavour" - when you close in on a hospital, you hear a voice greeting you, and when you leave, it thanks you and wishes you well. Similarly, in the Cesar missions, all pilots leaving the safe zone are warned that they are entering contested airspace, and those that return are warmly welcomed. Valet is to meet and greet, and usher out. It's especially useful for units that spawn in, yes. And it can do a lot more

and I probably can add one of those: add a 'groundOnly' option that only applies to units that when they trigger valet will only be considered as eligible if they are on the ground. This means probably that the will NOT trigger after they land, because when they are in the air at point of triggering, they are discarded and will not trigger after landing (you can use LZ for that, though).

Version 20250428 Update Added Chinook (hot and cold) Major framework update to guard against DCS bugs

It can be connected to frame rates, but the cause is a bit deeper: People can get 'VR-' or 'simulator sickness' when their vestibular organ and eye coordination still works very well IRL, and haven't yet trained their brain long enough (or haven't aged sufficiently) to have their brain allow some discrepancy. You see, a couple of million years of evolution have programmed our brains with a very efficient behaviour pattern: if the horizon as seen by our eyes diverges by what our inner ear (vestibular system) tells us, the most likely cause is that the body has ingested some neurotoxins. The immediate reaction is that the body wants to get rid of whatever it ingested. It's an effective and pragmatic strategy that has allowed us to survive. Unfortunately, minute discrepancies in what a HMD shows (especially at lower fps) and what the vestibular system tells you (in real-time) can trigger this reflex. So what can you do to avoid the symptoms? firstly, make sure that the HMD has very fast (high fps), very precise tracking (use outside tracking like steam's lighthouse, and avoid inside out like the plague), so that the depicted horizon is always level. Then, make sure that you have local references in your image that makes it easy for the brain to understand what is horizon, and what is the local frame of reference: the cockpit. Cockpits with large, panoramic views without local references will generate more vertigo than tight ones: in Elite Dangerous, the Vulture's panoramic cockpit is much more likely to induce vertigo than Elite Dangerous Eagle's. In DCS the same is true: a jet's cockpit usually provides lots of local frames of reference (dashboard, cockpit frame, seat). Some helicopters (Huey) do too, while others like the Gazelle can induce vertigo. The Hook's panoramic cockpit can be problematic as well (although the default pilot's head setup is well contained within local frames of reference). But - the Hook puts a noticeable drain on performance, so it may well be that your brain notices the lag/latency between head movement and horizon, and triggers vertigo/queasiness - even if you yourself don't notice it. So this may indeed be frame rate related (not so much resolution, yet your frame rate may inversely correlate with resolution: the higher the resolution, the lower the frame rate). Try to maximize frame rates in the cockpit. Note that this is highly individual: I can tolerate much lower fps than some of my friends who tend to show me their breakfast if the VR experience is too low-fps. The other option is training. So, how can you train your body to allow discrepancies in horizontal information from the inner ear and eyesight? Well, one is obvious: fly more VR, and your brain can be trained, just like seafarers of old learned to train away sea sickness. You may also try some medication against motion sickness - but taking medicine just to be able to play a game seems excessive even to me (today. I admit that a couple of decades ago, it may have been part of the entertainment). Then there is some behaviour training that may not be recommendable nor healthy: I used to frequent larger gatherings of people who played some loud music, accentuated by pronounced off-beat percussion, while imbibing large quantities of fermented produce solutions (colloquially also referred to as "beer"). I used to frequent performances of arrangements that called themselves "Motörhead" and "Iron Maiden" or similar, who performed some catchy ditties in a good-natured atmosphere. Over time, this helped train my brain - especially after the performances came to an end - to come to terms with discrepancies in eye/vestibular coordination. But that was just my personal background and personal experience may not apply to others; and there are still some VR titles that can trigger my brain's toxin reflex; the older I grow, the less pronounced the effect becomes. There may be other training regimes that are more healthy and/or socially acceptable. -ch

Thank you for that report. Can I trouble you to please verify that you are using version 5.3.0 of PlayerScore? This one looks like something that was already fixed.

I'm now reading less than reassuring reports from users of the MegX, which is disconcerting to say the least, as I was trending towards that HMD because of overlap and higher res. And thank you all for the additional hints to look at, this decision isn't even half as clear-cut as I hoped it to be.