davidp57

It was in the post you replied to : here

Hi Grimes, thanks for your answer ! Your explanation is clear and interesting, I'm learning stuff, and I like that. However, in the mission I attached the check() function is called automatically after spawn (which may cause the effects you described), but also in a radio menu command that can be triggered at will. And if I run this command say, 10 seconds later, the check() function has the same output as when it is ran right after the spawn : You can try this by yourself if you want, this is perfectly reproduceable. I may have overlooked something, but I think that the way MiST spawns the groups make DCS behave weird afterwards. Could you have a look, please, you're the only one I know with that much experience of DCS scripting ^^ :helpsmilie:

Self-quoting, the narcissim of the internet-era ;) More seriously, this is probably due to the way Mist spawns units in DCS. I tried with Moose, which does not respawn the group but instead create a new one, considering the first group as a template ; it works, but it's not possible to actually respawn (i.e. make the group disappear, and reappear as if new, at its original location). Anything ?

Hello, world of DCS scripting ^^ I think I found either a bug or something really weird in mist. I've got a test mission set up to demontrate this behavior, attached. If I use mist to respawn an aircraft group (late-activated or not), the :getUnits() method returns an empty table, but the group is actually alive with all its units. Can anyone help ? test.miz

Hi, I tried your mission but I have no F10 radio menu. Are you sure this mission is not missing anything else ? Or maybe I have to do something ? Occupy a specific slot ?

And we'll donate, promised !

Great, thanks Ciribob and as always a big thank you for your work !

That's excellent, thanks Flappie ! Do you think that we can help with hosting ? Are there any fees on your side ?

Unfortunately I've got voice chat disabled since the beginning. So that's not it, I guess.

The error message you showed said (translated to human language ^^) "mist is not loaded". Could you attach your mission file, I'll test it and tell you what's wrong.

Not sure I get the problem here but on my side the COMM volume knobs on the UFC work well with SRS. On another subject, is GUARD supposed to work on the F18 with SRS ? I can't make it work. On the A-10, the following scenario works : - for client #1, set UHF radio to GUARD (rotate the switch to the GUARD position) and emit a message using just the SRS PTT control that was configured for this radio - for client #2, set UHF radio to anything else that 243Mhz (the GUARD frequency on UHF) - client #2 hears client #1 message, the line corresponding to the radio used for this test lights up red in the SRS window On the F18, the following scenario does not work : - for client #1, set UHF radio to GUARD (rotate the knob until the channel indicator indicates "G") and emit a message using just the SRS PTT control that was configured for this radio - for client #2, set UHF radio to anything else that 243Mhz (the GUARD frequency on UHF) - client #2 hears does not hear client #1 message Addendum to this test : - for client #2, set UHF radio to 243Mhz (the GUARD frequency on UHF) - client #2 does hear client #1 message, the line corresponding to the radio used for this test lights up white in the SRS window Did we miss anything ?

Same crash here, on 2.5.6.45317. Log attached. Context was IA Su25T and IA F15C dogfight in a complex mission. dcs.log-20200327-195930.zip

Ici : https://docs.google.com/document/d/1fV9UQBjxZuvVEG8kueDSqthmOpHzYsf5QB_1oxuLJ60

That's because the mist script has not been loaded. Either you didn't load it in a trigger, loaded it too late (after the script you showed us), loaded it wrong (bad path) or an error occured while loading (see dcs.log)

Make your modifications as mod packages that you'll apply using OvGME. I've got a document explaining how-to, but in french ^^

Updated server and clients to 2.5.6.45317 and still the same crashes, with the same clients and the same mission : 2020-03-21 21:15:40.111 DEBUG Scripting: make: country: 0 2020-03-21 21:15:40.111 DEBUG Scripting: Phrases make : key = 4250 2020-03-21 21:15:48.594 WARNING EFFECTS2: BowwaveEmitter: unknown parameter 2020-03-21 21:16:13.918 WARNING LOG: 1 duplicate message(s) skipped. 2020-03-21 21:16:13.918 DEBUG LuaGUI: --- onChatMessage--- BLUE player Brep disconnected nil 2020-03-21 21:16:13.918 DEBUG LuaGUI: --- onChatMessage--- BLUE unknown returned to Spectators nil 2020-03-21 21:16:13.918 DEBUG LuaGUI: --activeGroupId, activeRoomId--- 0 0 1 2020-03-21 21:16:13.919 DEBUG LuaGUI: ----onPlayerDisconnect--- 5 0 2020-03-21 21:16:13.919 INFO VOICECHAT: peer ID = 5 disconnected 2020-03-21 21:16:13.919 DEBUG LuaGUI: --activeGroupId, activeRoomId--- 0 0 1 2020-03-21 21:16:35.755 WARNING EFFECTS2: BowwaveEmitter: unknown parameter 2020-03-21 21:16:38.792 INFO EDCORE: try to write dump information 2020-03-21 21:16:38.793 INFO EDCORE: # -------------- 20200321-211639 -------------- 2020-03-21 21:16:38.794 INFO EDCORE: DCS/2.5.6.45317 (x86_64; Windows NT 10.0.18362) 2020-03-21 21:16:38.795 INFO EDCORE: 2020-03-21 21:16:38.796 INFO EDCORE: # C0000005 ACCESS_VIOLATION at B5FB8610 00:00000000 2020-03-21 21:16:38.798 INFO EDCORE: SymInit: Symbol-SearchPath: '.;C:\jeux\DCS World OpenBeta.2.5.6;C:\jeux\DCS World OpenBeta.2.5.6\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'dpier' 2020-03-21 21:16:38.799 INFO EDCORE: OS-Version: 10.0.18362 () 0x300-0x1

You're welcome ! Fly safe, and fly high !

Well, looks like I'm not quick enough ^^

Well, shame on me, I didn't see this ! These lines are not normal : 2020-03-20 22:29:32.628 INFO LuaNET: SLMOD WARNING: ./Scripts/MissionScripting.lua is not up to date. Installing new ./Scripts/MissionScripting.lua. 2020-03-20 22:29:32.628 ERROR VFS: VFS_open_write: CreateFile(./Scripts/MissionScripting.lua): Access is denied. 2020-03-20 22:29:32.628 INFO LuaNET: SLMOD ERROR: Unable to open ./Scripts/MissionScripting.lua for writing, reason: can't open "./Scripts/MissionScripting.lua" for 'w' They mean that SLmod is trying to update your MissionScripting.lua file (in your DCS installation) because it's the vanilla version that you got when updating last night, and cannot load SLmod properly ; and that SLmod cannot access this file, certainly because it's protected. You should check the security settings for this file and/or all of your DCS installation. A common problem is that when installing something (like DCS) in C:\program files, the only user able to write in the install folders is the administrator. The solution to this problem is to run the program (here, DCS server) as administrator. Hop this helped !

Your SLmod log is here : "C:\Users\<your user>\Saved Games\<your dcs config folder>\Slmod\Slmod.log" Your DCS log is here : "C:\Users\<your user>\Saved Games\<your dcs config folder>\Logs\dcs.log"

This error means that the main SLmod script was not loaded. We used this version of DCS yesterday all afternoon and night, and SLmod worked perfectly. Maybe something specific on your end ? Could you share your server start log ?

Thank you Bignewy ! I'm available to help if need be (I can deploy a test version and help with generating debug logs) Regarding cleanup, I did that already. As a matter of fact I do that each time I get a crash ^^ Be advised, this was on a clean 2.5.6 install with only configuration mods (namely, added commands for multi-position switches). So, clean as can be ;)

2020-03-18 16:56:30.096 INFO DCS: DCS/2.5.6.44266 (x86_64; Windows NT 10.0.18362) 2020-03-18 16:56:30.096 INFO DCS: DCS revision: 164224 2020-03-18 16:56:30.096 INFO DCS: Renderer revision: 20092 2020-03-18 16:56:30.096 INFO DCS: Terrain revision: 20077 This afternoon I was flying with friends on our MP server. My friend Mitch's DCS crashed and he read me the last error in the log file, right before the crash (we're both in IT so we know how to read log files btw). It was something like "BowwaveEmitter: unknown parameter". 10 minutes later, my DCS crashed too. And guess what ? the line right before the crash reads : 2020-03-18 17:55:11.907 WARNING EFFECTS2: BowwaveEmitter: unknown parameter 2020-03-18 17:55:31.416 WARNING LOG: 2 duplicate message(s) skipped. 3 other friends kept flying, no crash problem on their side. I've attached my crash log. dcs.log-20200318-175532.zip

2020-03-18 16:56:30.096 INFO DCS: DCS/2.5.6.44266 (x86_64; Windows NT 10.0.18362) 2020-03-18 16:56:30.096 INFO DCS: DCS revision: 164224 2020-03-18 16:56:30.096 INFO DCS: Renderer revision: 20092 2020-03-18 16:56:30.096 INFO DCS: Terrain revision: 20077 I usually fly with the heading set to TRUE. Today, for the first time, I wanted to try and use the HDG autopilot. So I slewed the heading bug to the bearing of my waypoint on the HSI page, and turned the HDG autopilot on. My plane turned 6 degrees east of the heading bug. I tought "weird, 6° is the deviation in Georgia" and tried setting the HSI heading setting back to MAGNETIC and boom : the heading bug jumped to the heading my plane did follow. To reproduce : - In the HSI page, configure the heading to TRUE - While in the air, choose a heading and set the heading bug to this (e.g. 270°) - Turn the HDG autopilot on - Check that the plane is actually turning to 276° - In the HSI page, configure the heading to MAGNETIC - See that the heading bug is actually at 270° MAGNETIC What I was expecting : - The HDG autopilot should follow the heading bug, even with the HSI heading set to TRUE. PS : I don't have a trk but I can make one. Although I'm not sure it's necessary.

J'aime beaucoup le ton que tu as choisi pour cette vidéo !