eric963 Posted December 23, 2017 Share Posted December 23, 2017 Just ran a quick test in 1.58 Me in A10c and 2 ground units. On the way to the targets I did a manual save three times and each time saved the proper DAWS-SavedMission_1, DAWS-SavedMission_2 and DAWS-SavedMission_3. Killed one of the ground vehicles then tried to do a manual save. The message saying it was doing a save appeared but not the one that comes up after that which shows the path and everything. Lines 845 - 866 in the dcs.log is where the entries for me killing the unit and trying to do the manual save. Let me know if you need any other info.. Thanks Ericdcslog.txt Link to comment Share on other sites More sharing options...
chromium Posted December 24, 2017 Author Share Posted December 24, 2017 thank I'll look into that. Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously. Link to comment Share on other sites More sharing options...
chromium Posted December 24, 2017 Author Share Posted December 24, 2017 Solved. It was a stupid error. Link updated, version and built are still the same. Please retry ;) Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously. Link to comment Share on other sites More sharing options...
eric963 Posted December 24, 2017 Share Posted December 24, 2017 Ok getting it now and will give it a try. Solved. It was a stupid error. Link updated, version and built are still the same. Please retry ;) Link to comment Share on other sites More sharing options...
eric963 Posted December 24, 2017 Share Posted December 24, 2017 Ran a couple simple test missions and all seems to be working. Enabled the map object persistence and it was working as it should. Ok getting it now and will give it a try. Link to comment Share on other sites More sharing options...
chromium Posted December 24, 2017 Author Share Posted December 24, 2017 Ran a couple simple test missions and all seems to be working. Enabled the map object persistence and it was working as it should. sadly as it should now. If I get MBot code to adapt DAWS, it's going to be A LOT better. thanks! Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously. Link to comment Share on other sites More sharing options...
eric963 Posted December 24, 2017 Share Posted December 24, 2017 sadly as it should now. If I get MBot code to adapt DAWS, it's going to be A LOT better. thanks! No problem I'll watch the thread for any more updates. Link to comment Share on other sites More sharing options...
Neon Posted December 24, 2017 Share Posted December 24, 2017 I see the module icon after install but the menu is still blank and there is no menu inside the mission. Running current 2.2 Uploaded correct log this time....daws.zip [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
chromium Posted December 25, 2017 Author Share Posted December 25, 2017 Hi, seems an install problem, using 2.2 version here the menù is correct. Are you sure that you downloaded the right version, and that it's installed correctly? no entry in the log, also. Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously. Link to comment Share on other sites More sharing options...
Neon Posted December 25, 2017 Share Posted December 25, 2017 I can't try it again, but I downloaded the 2.2 version and the save folder looks like everything installed correctly. Sent from my iPhone using Tapatalk [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
chromium Posted December 25, 2017 Author Share Posted December 25, 2017 whitout log info I can only try with some question for trial and error. 1) are you running in admin mode? 2) have you writing access in saved game folder AND in main folder? 3) are you installing the mod in the saved-games DCS openalfa folder instead of main dir? 4) please check that the unzipped folder does not contain another "DAWS_Package220" folder. Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously. Link to comment Share on other sites More sharing options...
chromium Posted December 26, 2017 Author Share Posted December 26, 2017 Small update for 2.2.0 version: got MBot ways to use scenery destruction function to work. So Map Object Persistence options is going to be out of beta, only dependant by mission file and also... I might found a way to carry out external files from one mission to another :) Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously. Link to comment Share on other sites More sharing options...
Neon Posted December 29, 2017 Share Posted December 29, 2017 Not sure if this is a known bug but the new version (as of whats up today) breaks moose scripting. After installing the mod nothing defined in moose will spawn. [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
chromium Posted December 29, 2017 Author Share Posted December 29, 2017 Will check. I don't know what moose do about DAWS, my only guess could be about missionscripting.lua file. Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously. Link to comment Share on other sites More sharing options...
eric963 Posted December 29, 2017 Share Posted December 29, 2017 Neon, I am attaching a basic mission with a vehicle being spawned in by Moose at 10 seconds into the mission. It works on my dedicated server and in SP. Run it on your system at let me know what happens.dawsmoosetest.zip Link to comment Share on other sites More sharing options...
chromium Posted December 29, 2017 Author Share Posted December 29, 2017 copy, I will asap. I also wrote to FlightControl to check what is the point that prevent MOOSE to work. Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously. Link to comment Share on other sites More sharing options...
Neon Posted December 29, 2017 Share Posted December 29, 2017 From what I can tell it’s not allowing the creation of units created from templates. If you declare a spawn from the exact group name in moose it works. But if you are using moose to deploy random units they won’t spawn. I am not sure if this is a clue but with the RAT function (random air traffic) the log is throwing error saying there is no departure airports available. Sent from my iPhone using Tapatalk [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Neon Posted December 29, 2017 Share Posted December 29, 2017 Neon, I am attaching a basic mission with a vehicle being spawned in by Moose at 10 seconds into the mission. It works on my dedicated server and in SP. Run it on your system at let me know what happens. I will test it out first thing tomorrow. I am also trying different spawn code setups to try and narrow it down. Sent from my iPhone using Tapatalk [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
chromium Posted December 29, 2017 Author Share Posted December 29, 2017 (edited) Consider that in the testing version released DAWS should not interact with the SSE, it only use the available functions. Please always attach the dcs.log file: this testing version of DAWS prints out almost everything so you might and should see a lot of call in the logs searching by word "DAWS" inside the file. The more information I have, the easier the compatibility check will be done. Is maybe this the error? https://forums.eagle.ru/showpost.php?p=2557050&postcount=115 PS: you won't notice anything cause DAWS copy its own missionscripting.lua file at each mission start and re-copy original missionscripting.lua file at mission end. If moose needs any addition in missionscripting.lua, than it's not compatible with DAWS unless I and FlightControl find a way to solve the issue (I might add the necessary code in DAWS missionscripting.lua). Edited December 29, 2017 by chromium Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously. Link to comment Share on other sites More sharing options...
Neon Posted December 29, 2017 Share Posted December 29, 2017 Consider that in the testing version released DAWS should not interact with the SSE, it only use the available functions. Please always attach the dcs.log file: this testing version of DAWS prints out almost everything so you might and should see a lot of call in the logs searching by word "DAWS" inside the file. The more information I have, the easier the compatibility check will be done. Is maybe this the error? https://forums.eagle.ru/showpost.php?p=2557050&postcount=115 PS: you won't notice anything cause DAWS copy its own missionscripting.lua file at each mission start and re-copy original missionscripting.lua file at mission end. If moose needs any addition in missionscripting.lua, than it's not compatible with DAWS unless I and FlightControl find a way to solve the issue (I might add the necessary code in DAWS missionscripting.lua). I am going to do testing tonight and ill send everything over (mission, log, lua, ect.). But no that link looks to be instructions for running moose dynamically from github, which I don't do. I only run release packages on my server. [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
eric963 Posted December 30, 2017 Share Posted December 30, 2017 chromium, Attached is a zip file containing the test mission and the dcs log. Tested in 1.58. Mission runs fine with just DAWS, runs fine with just MOOSE, but no units spawn from a template with both DAWS and MOOSE. Line 658 in the dcs.log is where the error is first reported.dcs.zip Link to comment Share on other sites More sharing options...
chromium Posted December 30, 2017 Author Share Posted December 30, 2017 Interesting, a timer error. I wouldn't bet on that. I will try to understand what is going on in the coming days :) Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously. Link to comment Share on other sites More sharing options...
chromium Posted January 10, 2018 Author Share Posted January 10, 2018 Due to personal reason I didn't had the time to investigate yet. I might get some answer in the next week, I hope. Probabily the next version of DAWS will be ready for DCS 2.5, given the integration of some new (and old) features :). If this version will be ready before 2.5 release and compatible with 2.2, I will update beta links. Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously. Link to comment Share on other sites More sharing options...
Spanker79 Posted January 19, 2018 Share Posted January 19, 2018 (edited) Hello..Just a quick question. Is DAWS working with the current build of DCS 1.5.8? Cause we are trying to "instal" it on our dedicated server but with OvGME dosen't seem to work..(it doesn't show in the modules list nore in the special tab's menu) Thnx in advance for your answers. Edited January 19, 2018 by Spanker79 ◈ Lock-On Greece / DCS World Greece http://lockon-greece.forumotion.net/ 1st Hellinic Virtual Squadron for Flaming Cliffs & DCS World ~ Flying since 2008 ~ Link to comment Share on other sites More sharing options...
chromium Posted January 19, 2018 Author Share Posted January 19, 2018 This version: https://forums.eagle.ru/showpost.php?p=3334352&postcount=50 should be ok in 1.5.8, but it's not recommended for intense mission and it seems to be not compatible with MOOSE. Since I didn't find a solution a couple of weeks ago, I'm working on 2.5 version release. These are intense month in my private life and intense month in DCS updates...sorry for the delays :) Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously. Link to comment Share on other sites More sharing options...
Recommended Posts