Wizard1393

Y’all know you can just change the persistency file paths in the scripts to a path of your liking right? For example, I use “Saved Games/DCS/Missions/Syria/Operation Scarlet Dawn/“ That way you don’t have to run DCS as admin either, and you keep the persistency files together with the mission file nice and tidy. If anyone need instructions on where to make these changes you can PM me.

Maybe this can help you? A "true" saving mechanism doesn't exist for DCS.

Update: After reaching out to Palo Alto regarding this issue, requesting review, they have now removed the malicious tag on the executable and IP-addresses/range that DCS_updater.exe communicates with.

Support ticket submitted. I’ll try my best to supply any more info as needed if requested. Thanks all.

Excellent answer silverdevil. Idk how this works in reality, but wouldn't ED be able to contact Palo Alto and basically say, "Hey we have this IP now and we're not malicious, we're a software company that develop the worlds most popular combat flight simlulator. Please remove us from your malicious IP list, or at least OUR specific IP-addresses in that range." ?

Ok… To be fair, it’s an answer, not a reassuring one, but an answer. Excluding it is not an option in this case, out of my reach. Would you care to explain why Palo Alto thinks your software connects to malicious IP:s? I’m thinking it might be good to contact them if your IP series is falsely tagged as malicious.

Palo Alto Cortex XDR-protection software blocks DCS_Updater.exe stating it performs host sweeps and tries to connect to malicious IP. I’d advise ED to contact Palo Alto and straighten this out. This the exact block reason message: Performed a host sweep | High Once a system is compromised, the attacker often attempts to discover other systems on the network to target. One technique for finding these systems is to perform a host sweep, which involves sending specially crafted packets to each IP address in the subnet to discover and identify the addressed system. Connected to a malicious IP | High Malware authors often reuse malicious IPs names across multiple pieces of malware. It is common to find a known malicious IP used in an otherwise unknown piece of malware.

+1 Actually a rather extensive overhaul of AI A2G behavior including AI wingmen commands is severely needed in my opinion.

Firstly, thanks for your input, cfrag. This is and is very much intended to be a Basic persistence kit. It's sole purpose is aimed at those that want to easily build a mission in the editor, populate it with lots of units, and be able to fly it one day, kill some stuff, log off, and keep going where they left off another day, perhaps with a friend, like an ongoing ground war campaign. It's really the opposite of "forever-missions" that rely on complicated scripts to keep the mission dynamic and alive all the time. I'm sure there are other persistence script libraries out there that can do all that you mention and more, but perhaps also a little more difficult for a beginner mission creator to set up and configure. I could clarify this bit further in the info I guess, "Not compatible with scripts dynamically spawning units". EDIT: Updated info Also, sure I can fix the function you mention so it won't break the script if it tries to remove a unit that doesn't exist. Also good point about the all/red/blue tracked coalition options. I'll see if I can update the info a bit, and/or update the code to be all, red/neutral or blue/neutral tracking. EDIT2: Made some changes to saveFilePath options and also made adjustments to coalition tracking and documentation and the destroy-bit you were on about: if Unit.getByName(v.name) then Unit.getByName(v.name):destroy() end

Yeah this is a tricky one mate since it sounds like you already placed all aircraft. Maybe you could get away with the finicky way of copying the route data between aircraft from the "mission" file within the .miz file. But all aircraft does not share the same default speeds etc... don't know if it would actually work. But so I think the least painful way of "fixing" your problem would be to delete all but one aircraft per type, create waypoints for each one, then copy up as many aircraft per type as you want, in that way preserving the route data.

Basic (Ground Unit) Persistence Kit by Jinx / ChrisofSweden Download Purpose: This is and is very much intended to be a Basic persistence kit that is as easy to use as possible. Demographically aimed at those that want to easily build a mission in the editor, populate it with lots of units, and be able to fly it one day, kill some stuff, log off, and keep going where they left off another day, perhaps with a friend, giving the sense of an ongoing ground war campaign. How it works: It works by storing information on what ground units the gets destroyed in a file. This can be done manually or automatically at an interval you choose. On mission start/restart, loads this file and removes all previously destroyed units the mission. What this does NOT: It does not save unit positions or routes so any units that moved during the mission will be back at initial position at mission start/restart. It does not save destroyed static objects or scenery/buildnings. It does not work with dynamically spawned ground units. FILE CONTENTS readme.txt This text. Mission.lua Contains mission configuration variables, an event handler for logging destroyed units and calls to save and load file functions. File_IO_functions.lua Contains the actual file IO functions that creates/saves and loads dead units table to/from file. Persistence_demo.miz Example DCS mission file PREREQUISITES: To allow DCS Scripting Environment to create the save state file in your file system you also need to modify file: "DCS World\Scripts\MissionScripting.lua" Change: do sanitizeModule('os') sanitizeModule('io') sanitizeModule('lfs') require = nil loadlib = nil end --To: do --sanitizeModule('os') --sanitizeModule('io') --sanitizeModule('lfs') require = nil loadlib = nil end USAGE: Put the unzipped folder "Basic Persistance Kit" into your Saved Games\DCS\Missions\ folder Open file Mission.lua and configure the few variables in the USER CONFIG section, they are all explained and examples supplied. Save and close Mission.lua. Open DCS Mission Editor. Create a mission and populate it how you want, or open an existing mission you would like to add persistence to. Give the mission the same name you put in Mission.lua and save it. Add a trigger TYPE "ONCE" with CONDITION "TIME MORE" set to 3, and add two ACTIONS: DO SCRIPT FILE and load the "File_IO_functions.lua" script. DO SCRIPT FILE and load the "Mission.lua" script. Save your mission and play. Enjoy! Download

I flew it the other night, had none of the problems you are describing. Perhaps time for a repair/cleanup/remove any mods?

Funnily enough, I also get the feeling I get BETTER performance with Terrain Object Shadows set to Default instead of Flat.

Is this campaign playable with a friend in MP, or could be modified to allow for this?

Over all good experience with this feature. Well done HB! However, one thing that perhaps either I missed was documented; In VR when using QDIRECT Head Control to slew the LANTIRN, you get one small ring in the center of the display, and two large rings, one for each eye, that is not correlated properly between both eyes, so you get a sense of a crosseye.

Yes. That's what I remember also. Only hooked objects can become SPI. EDIT: To OP: You can make a markpoint on the TAD if you want to remember a spot.

Yeah that image from the Apache looks better than what we have now, but also hope it's WIP. Trees too hot. Same as today really.

I typically set it to 30. Feels alive and bumpy when down low.

Man, I CAN'T WAIT! I've been waiting/hoping for a new FLIR model since 2015.

+1

+1

Just had a short flight in an MP server and the A2G Gun Pipper was OK. Wonder if it was actually fixed in yesterdays patch or just a fluke it worked as intended this time. Can you guys test again and post your results?

Thanks Cobra!