Search the Community
Showing results for tags 'dedicated server bug'.
-
2021-04-18 06:21:56.641 INFO EDCORE: # -------------- 20210418-062157 -------------- 2021-04-18 06:21:56.644 INFO EDCORE: DCS/2.7.0.4625 (x86_64; Windows NT 10.0.17763) 2021-04-18 06:21:56.647 INFO EDCORE: D:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin\ed_sound.dll 2021-04-18 06:21:56.650 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 890A52C6 00:00000000 2021-04-18 06:21:56.656 INFO EDCORE: SymInit: Symbol-SearchPath: '.;D:\Program Files\Eagle Dynamics\DCS World OpenBeta Server;D:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Adm034Naop86frh3sfwd' 2021-04-18 06:21:56.659 INFO EDCORE: OS-Version: 10.0.17763 () 0x110-0x3 2021-04-18 06:21:56.947 INFO EDCORE: 0x00000000000152C6 (ed_sound): SND_speaker_layout_get_info + 0xBF6 2021-04-18 06:21:56.951 INFO EDCORE: 0x00000000000147EE (ed_sound): SND_speaker_layout_get_info + 0x11E 2021-04-18 06:21:56.955 INFO EDCORE: 0x000000000000398A (ed_sound): SND_exit + 0xEA 2021-04-18 06:21:56.959 INFO EDCORE: 0x00000000007E4F72 (DCS): ”æ– ‡'Y½Þw»ô¾cN'%YùöjŸGÉÔ…8c8’5H¿ü}y^`ÊsÞܦµXqƒ{Ó…½3îh log_and_dump.7z
-
Two different crashes of different maps on different instances: Splitted in 4 posts (5MB upload limit) dcs.log First crashdcs.log first crash crash dump dcs.log-20210417-195531.zip second crash dcs.log second crash dump dcs.log-20210417-194900.zip 2021-04-17 19:55:31.310 INFO EDCORE: # -------------- 20210417-195531 -------------- 2021-04-17 19:55:31.314 INFO EDCORE: DCS/2.7.0.4625 (x86_64; Windows NT 10.0.17763) 2021-04-17 19:55:31.318 INFO EDCORE: D:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin\Flight.dll 2021-04-17 19:55:31.321 INFO EDCORE: # C0000005 ACCESS_VIOLATION at C9251AE4 00:00000000 2021-04-17 19:55:31.325 INFO EDCORE: SymInit: Symbol-SearchPath: '.;D:\Program Files\Eagle Dynamics\DCS World OpenBeta Server;D:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Adm034Naop86frh3sfwd' 2021-04-17 19:55:31.328 INFO EDCORE: OS-Version: 10.0.17763 () 0x110-0x3 2021-04-17 19:55:34.127 INFO EDCORE: 0x00000000000C1AE4 (Flight): woATC::recalculateTaxiwaydata + 0x1D14 2021-04-17 19:55:34.132 INFO EDCORE: 0x00000000000C4E77 (Flight): woATC::setClientStatusServer + 0x707 2021-04-17 19:55:34.136 INFO EDCORE: 0x00000000000C4235 (Flight): woATC::setClientStatus + 0x35 2021-04-17 19:55:34.140 INFO EDCORE: 0x00000000000BE662 (Flight): woATC::onObjectDestroy + 0x112 2021-04-17 19:55:34.145 INFO EDCORE: 0x00000000000A6CE1 (WorldGeneral): slot_decompose_ex + 0xCF1 2021-04-17 19:55:34.149 INFO EDCORE: 0x00000000000AAE27 (WorldGeneral): WorldManager::notifyDeath + 0x37 2021-04-17 19:55:34.153 INFO EDCORE: 0x00000000004F7F84 (DCS): ???'Y????cN'%Y??j??G??8c8?5H??}y^`????Xq?{Ӆ?3? ??B????[???LÑ?5Q!?}??i?z6QI*~c|???&?8f??M?F_hA?鮐$???. ??,????5/&?'pdVKl%???Q?ށm???bR???6}H?????\??\?????G?7??D???????Ea?E???Rg??l?R?g/?2????|X?DZ`?Zu???yS%?G?+????(\??h???8?T????d'??Ý#?????V?[3?i?+????{??0'.???B?;E??/<??ٟ?t??? b%.X'BX$??%??\$W?Onzk???L??!a??)e?????:?q?p???;z?5&?ǙP?%f?ky4ӯY????_??'??q?A????m???xRh\????˼6?n?'???']\?f_q????~?!??ɑ{a???]???k:R??|?-&? 2021-04-17 19:49:00.332 INFO EDCORE: # -------------- 20210417-194900 -------------- 2021-04-17 19:49:00.334 INFO EDCORE: DCS/2.7.0.4625 (x86_64; Windows NT 10.0.17763) 2021-04-17 19:49:00.336 INFO EDCORE: D:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin\Flight.dll 2021-04-17 19:49:00.338 INFO EDCORE: # C0000005 ACCESS_VIOLATION at C9251AE0 00:00000000 2021-04-17 19:49:00.352 INFO EDCORE: SymInit: Symbol-SearchPath: '.;D:\Program Files\Eagle Dynamics\DCS World OpenBeta Server;D:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Adm034Naop86frh3sfwd' 2021-04-17 19:49:00.356 INFO EDCORE: OS-Version: 10.0.17763 () 0x110-0x3 2021-04-17 19:49:02.033 INFO EDCORE: 0x00000000000C1AE0 (Flight): woATC::recalculateTaxiwaydata + 0x1D10 2021-04-17 19:49:02.038 INFO EDCORE: 0x00000000000C4E77 (Flight): woATC::setClientStatusServer + 0x707 2021-04-17 19:49:02.043 INFO EDCORE: 0x00000000000C4235 (Flight): woATC::setClientStatus + 0x35 2021-04-17 19:49:02.047 INFO EDCORE: 0x00000000000A600E (Flight): woATC::controlClientsStatus + 0x1FE 2021-04-17 19:49:02.051 INFO EDCORE: 0x000000000009D1F5 (Flight): woATC::Control + 0x4A5 2021-04-17 19:49:02.056 INFO EDCORE: 0x00000000000576AC (Flight): wAirdrome::Control + 0xCC 2021-04-17 19:49:02.061 INFO EDCORE: 0x000000000005B3C3 (Flight): wAirdrome::Init + 0xF33 2021-04-17 19:49:02.066 INFO EDCORE: 0x0000000000003AD6 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x466 2021-04-17 19:49:02.070 INFO EDCORE: 0x0000000000003F3D (World): wSimCalendar::DoActionsUntil + 0x1FD 2021-04-17 19:49:02.075 INFO EDCORE: 0x00000000007E9932 (DCS): ???'Y????cN'%Y??j??G??8c8?5H??}y^`????Xq?{
-
Since there is no way to turn off the big fire objects in DCS you can use the destroy command to get rid of them (when you want the fire to go out) This sadly will only work in single player If you try to do the same thing in DEDICATED MULTIPLAYER SERVER it will not work See attached miz file Instructions to reproduce SP test 1. Load this mission in DCS mission editor 2. run the mission 3. Observe the BTR in F7 view 4. To the north of it is a big fire .... it is burning 5. Wait 20 seconds the fire dissappears (there will be a message) MP DEDICATED SERVER test 1. Load this mission on YOUR DEDICATED MP server - NOT just host your own MP server , there is a difference, make sure you server pauses with no clients connected 2. Connect to the DEDICATED DCS SERVER as a client 3. Observe the BTR in F7 view 4. To the north of it is a big fire .... it is burning 5. Wait 20 seconds the fire does NOT dissappear (there will be a message) You cannot delete the fire object in DCS DEDICATED server but you can when running the mission in the mission editor/SP fire_bug_mp_test.zip
-
Hi everyone, While waiting for functional TCTS training pod in DCS, to perform Kill Removal Procedures our idea is to shoot live ordonance against each others by setting up all aircrafts in Invicible, the last thing we need is a message declaring which person has been killed. To do that we would like to use the "Unit Hits" Trigger : -> [Once] -> [Unit Hits] -> [Message to ...] Unfortunatly we are facing a problem with this condition (Unit Hits), it looks like there is a problem with it in a specific Dedicated multiplayer server environement. An important thing to note is that the trigger "Unit hits" is working perfectly in any condition as soon as your a playing in SinglePlayer or in a Local Multiplayer Server. When playing on a Dedicated Multiplayer Server, that's only here where we are facing the problem bellow. In multiplater dedicated server (not local server) 1- Player shooter | AI Target "Immortal ON" | Trigger Condition: Unit Hits | Result: Text message NOT received. 2- Player shooter | AI Target "Immortal OFF" | Trigger Condition: Unit Hits | Result: Text message received. 3- Player shooter | Player Target "Immortal ON" | Trigger Condition: Unit Hits | Result: Text message NOT received. 4- Player shooter | Player Target "Immortal OFF" | Trigger Condition: Unit Hits | Result: Text message received. 5- AI shooter | AI Target "Immortal ON" | Trigger Condition: Unit Hits | Result: Text message received. 6- AI shooter | AI Target "Immortal OFF" | Trigger Condition: Unit Hits | Result: Text message received. 7- AI shooter | Player Target "Immortal ON" | Trigger Condition: Unit Hits | Result: Text message received. 8- AI shooter | Player Target "Immortal OFF" | Trigger Condition: Unit Hits | Result: Text message received. Conclusion : "Unit Hits" trigger is not detected and is not registered in the logs only when : + Mission is hosted on multiplater dedicated server. +"Unit hits" trigger is used when a PLAYER is shooting against an immortal AI or an immortal PLAYER. According to the values ahead, it looks like that the event "Unit hits" is not published/broadcasted in DCS code on a dedicated server when a player shoot against an immortal units (AI / Player). Because the "Unit hits" trigger registers well in SinglePlayer or in a Local Multiplayer Server, I don't think the problem comes from the DCS code but from the Dedicated Multiplayer Server that doesn't register all data. You will find linked to this message a test mission .miz that i have made to test every possible situation. (mission is made according to the values in the table above) _________________________________________________________________________________________________________________________________ Bellow you will find not the problem listed above but an improvement idea to the "Unit Hits" Trigger. Aditional Improvement Idea : Get the ability on the ME to get an other "Unit hits" trigger without specific number of hits on dedicated target, by the way, using a "Switched condition" Trigger, at each a time a unit has been hit by something we can have the trigger activated. (not only once) -> [Switched Condition] -> [Unit Hits] -> [Message to ...] (exemple : an information message is displayed everytime a specific immortal aircraft has been hit by something) _________________________________________________________________________________________________________________________________ Best Regards Wolf4Pm and Gemini from the JTFF. This message follows the three previous topics on this subject : Unit Hit - MP Trigger Test.miz