Damned - Gh0st

Thank you! I guess I jumped the gun when the update was released - I tried that exact line and received an error saying that it was incorrect, just tried it again and now it works

@BIGNEWY Howdy! What is the install ID for the Iraq terrain?

Are there plans to allow for restricting spawns on a side? With the current system you cant stop players from spawning as Red/Blue depending on airfield ownership. EX: Blue Players, Red AI Mission: When setting airfields as Dynamic Spawn, players have the option of spawning Red when that is not intended. The goal in this case would be to only allow spawns once the airfield becomes owned by Blue. Maybe in the password section, add an option in addition to Game master, Tac Commander, Observer, etc. for "Aircraft"? Side comment: The "COPY TO" other airfield function in the warehouse menu does not work for Aircraft Settings and Dynamic Slot/HotStart settings

Not all servers - see my post above. Hopefully it won't take long for either servers owners to transition to the new system or for ED to roll out a patch.

Issue seems to be related to having large amounts of the old version of player slots (non-dynamic). On the servers I run, the ones with 2,000+ slots have the issue, then ones with ~1,400 do not. I am currently transitioning all old version slots to the new dynamic system as a fix to the "DCS Not responding" issue when entering role select.

Thank you! Maybe as some kind of stop-gap, an API function could be added to the wishlist to be able to clear path generation/active combotasks? At least until the bug is fixed it would allow coders to call it prior to mission restarts to prevent the above bug

Edited the main post to contain an example mission. Replicated the bug in the following environments: Single Player Local Multiplayer Server Dedicated Multiplayer Server Regarding the mission example: After 2 minutes, the mission will attempt to restart. The bug seems to traced to order of operations for the mission restart functionality. Sometimes it will occur, sometimes it will not. NOTE: The example mission contains code snippets protected under the GNU General Public License v3.0. Contains pre-release code snippets for S.P.E.C.T.R.E. , the machine learning powered dynamic campaign framework.

Great point, Just re-ran the test mission in my original post and the bug is no longer present. Time to go remove my work arounds Considering this as Solved, thread closed

Groups with an active 'ComboTask Route' break the 'MissionRestart' event. When assigning 'ComboTask' Routes to groups during the mission, if the 'MissionRestart' event is triggered, the dedicated server becomes unresponsive and does not finish the MissionRestart event. Logs appear as follow: INFO Scripting (Main): event:type=mission restart WARNING TRANSPORT (Main): CREATING PATH MAKES TOO LONG!!!!! INFO Dispatcher (Main): Stop WARNING APP (Main): task "ComboTask" still exists WARNING APP (Main): task state for "ComboTask" still exists At this point the mission will hang and not continue the MissionRestart Event. Is there a way to clear "ComboTask" tasks and task states? Cycling through all groups and assigning an empty combotask/route before the MissionRestart does not prevent the server hang. Destroying all units before the MissionRestart does not prevent the server hang. I cannot find any documentation on the lines: WARNING TRANSPORT (Main): CREATING PATH MAKES TOO LONG!!!!! WARNING APP (Main): task "ComboTask" still exists WARNING APP (Main): task state for "ComboTask" still exists If groups are not assigned a ComboTask Route during gameplay, the MissionRestart event completes successfully. Any guidance on this would be extremely helpful, thanks! --------------------------------------------------------------------------------------------------------- Example Mission and Log is attached. After 2 minutes, the mission will attempt to restart. The bug seems to traced to order of operations for the mission restart functionality. Sometimes it will occur, sometimes it will not. NOTE: The example mission contains code snippets protected under the GNU General Public License v3.0. Contains pre-release code snippets for S.P.E.C.T.R.E. , the machine learning powered dynamic campaign framework. ComboTaskHang.miz dcs.log

Are there any updates for this bug? Thanks.

I discovered later in the evening that removeMark also triggered the bug. Thanks for sending it up the chain!

When trigger.action.markToCoalition() is used/triggered, it closes the re-arm & refuel menu. When markers are being generated by the server this prevents the player from rearming. In the test mission I have a marker created every 10 seconds for the first minute. If you open the re-arm window and activate a dropdown/right click on a pylon, when the marker is placed, it closes the menu. This happens in single player + multiplayer. MarkerTest.miz MarkerTest.trk

Experiencing this currently, but found a solution based on @BIGNEWY's suggestion that does not require losing all your configs/settings. In your \Saved Games\edModelViewerTrunk\Config folder is a JSON file named "ModelViewer2.json" Open the file and search for the "LiveriesToolPlugin" section. Replace it with the following. "LiveriesToolPlugin": { "WidgetParams": { "dockingAreas": 15, "isDocked": true, "isVisible": true, "lastDockArea": 1, "posX": 0, "posY": 51, "sizeX": 640, "sizeY": 745 } }, The short of it: We go into the config file and set the Livery Picker back to "Docked". It will show back up for you and then you can undock/reposition at will. Useful when using the keyboard shortcuts to move a hidden window doesn't work Hope it helps! (only reason I'm necro'ing this post is that it's still relevant and this post is the first google result when searching "DCS model viewer livery tool stuck offscreen")

Additionally to the above post, ensure the Flight Director is turned off and only engage it after you have come to a hover manually and trimmed your aircraft

I had collaborated with Chromium, DSMC now includes a working auto-restart as part of the mod if you wish to skip the powershell and go that route

I can confirm those folders are not in the Dedicated Server version of DCS (on my end). Additionally, the: saved games\ dir \Config\Input saved games\ dir \ fxo folders are not in my dedicated server instances. This approach may cause issues for those running a regular DCS installation as a dedicated server and not the actual DCS Dedicated Server installation though, if that matters. (E.g. regular DCS Open Beta install with --server --norender)

Thank you for the confirmation. @CaptHawk That's actually when I first noticed it, when debugging while developing scripts Luckily we have the WorldGeneral, App, etc. tags on the errors now so it's not too big a deal to filter them out

I'm sorry I don't have any experience with running separate DCS Server and Client EXEs on the same PC. I would imagine you could try using the DCS Dedicated Server Installation alongside your normal DCS, but keep in mind the Dedicated server version is about another 170GB worth of space needed. The Dedicated Server version without any special configuration sets up and uses a separate saved games folder than the normal install so there shouldnt be conflicts? (I think?) Be aware that while it might disperse the load on your CPU, you may end up doubling your RAM usage as both the server and your client will need their own resources. If you test it, I'd be curious to know your results!

Since 2.8 I am seeing errors in the logs relating to "Corrupt Damage Model", "No Property Record For Cell", and "No Property Record For Segment" in the DCS Logs. The Errors appear in relation to many aircraft in the logs, in multiplayer and singleplayer. Is this a remnant from updated/unused systems? Should we be concerned about this? Am I the only one experiencing this? Example: 2022-10-29 22:40:23.149 ERROR WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for cell "WHEEL_F". 2022-10-29 22:40:23.149 ERROR WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for cell "collision_belly". 2022-10-29 22:40:23.149 ERROR WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for cell "WHEEL_R". 2022-10-29 22:40:23.149 ERROR WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for cell "WHEEL_L". 2022-10-29 22:40:23.149 ERROR WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for segment "FRONT_WHEEL". 2022-10-29 22:40:23.149 ERROR WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for segment "WING_L_OUT". 2022-10-29 22:40:23.149 ERROR WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for segment "NOSE_CENTR". 2022-10-29 22:40:23.149 ERROR WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for segment "RIGHT_WHEEL". 2022-10-29 22:40:23.149 ERROR WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for segment "LEFT_WHEEL". 2022-10-29 22:40:23.150 ERROR WORLDGENERAL (Main): Error: Unit [F-14B]: No cell for property records CELL#146 CELL#149 CELL#163 CELL#165 CELL#168 CELL#169 CELL#177 CELL#178 CELL#179 CELL#183 CELL#184. 2022-10-29 22:40:23.150 ERROR APP (Main): Error: Unit [F-14B]: Corrupt damage model. Test Miz and TRK attached. Thanks Test.miz test.trk

As I haven't seen a complied, all inclusive guide on how to set up multiple dedicated servers using a single installation of DCS, I have created a guide that I hope will be of help to new and existing server hosters. I have also included a method I developed for automatically restarting all servers running off a single installation. This guide is meant for those with local hardware, though it may work for hosted methods with modification. Your mileage may vary. _____________________________________________________________________ I have found these methods to be most reliable for setting up multiple dedicated DCS Servers running from a single install of DCS. These methods will also allow for easy automatic shutdowns and restarts of your servers. This has been tested with many 24/7 servers over long periods of automatic restarts utilizing a combination of Task Scheduler, Powershell, and the DSMC Mod by Chromium. (6+ Months server run time, 300+ automatic restart cycles per server). I had collaborated with Chromium, DSMC now includes a working auto-restart as part of the mod if you wish to skip the powershell and go that route _____________________________________________________________________ If you would like to have auto-restarts without the use of DSMC, I will leave it to you to figure out a way to terminate your server process and not cover that here, though it should be easy to implement a modified version of the auto-restart method for auto-shutdown. GOOGE DRIVE: GUIDE - CLICK HERE

ED Changed the names in the description.lua -- F16_bl50_Fuel_Tank_300Gal {"Fuel_Tank_300Gal" }; -- F16_bl50_Fuel_Tank_370Gal {"F_16_Tank_370" }; Hope it helps for updating your skins

Since more people are experiencing this, is it possible to add a 'reported' or 'investigating' tag to this post? Also, if there is anything else I can provide/test for you, please let me know -Thanks!

Could you make a post in my thread I linked? We might be able to help solve this issue Right now we have no idea whats causing it. As of now, you and I are the only ones I see mentioning it

I have an issue being looked at over in the supercarrier bug section that sounds an awful lot like what you're describing. If you take that exact mission file and run it in singleplayer rather than multiplayer, does it work?

Hi! I removed all script elements and performed another test, the behavior from the previous dedicated server track is still apparent. Also, the issue with the kneeboard not displaying correctly from the initial post screenshots is still there. Track for the no script test is attached. Thank you for your help and looking into this! NoScripts.trk