chromium Posted August 30, 2017 Author Posted August 30, 2017 Wow, you won't believe me but I exacly planned that course of events, including bubbling ai on and off. Funny that, if you saw DGWS code I sent you a lifetime ago, I already have a good approach for making the AI to move autonomously with a bit of behaviour... and that is why I didn't bother that much to retain group routes: The DGWS will re-assign them at every mission start anyway. About reloading, I'm on my way I believe. With warehouses... well, I can move the proper file to a mission to another, and I can edit them... but I don't know how to retrieve the proper information in a simple and reliable way from the SSE. For the vehicles oil, in my logistic system I was estimating a hourly comsumpition per class of vehicles. After "n" hours, or a logistic group will move whithin 100 m for at least 5 min of the running out fuel groups, or it will go AI off. Anyway I still can't track or set ammo in the ground vehicles... they will be anyway "fully armed" at each mission start. PS: logistic groups are real vehicles that move from the nearest oil warehouse to the prioritized group... if someone intercept them... the refuel will stop. Doesn't work with FARP obviously. If you can get an ideally updated "warehouse" table with the same format of warehouse.lua, imho we are almost done. I can make that move. Send me a PM. 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.
chromium Posted September 5, 2017 Author Posted September 5, 2017 Auto-reload by scripts only achieved... need a stupid workaround but it works. Sadly I can't find a way to recover the route, therefore I think I will continue on the auto-movement commands at each mission start for now. 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.
Pikey Posted September 8, 2017 Posted September 8, 2017 Couple of things, and 1) is just an opinion, so feel free to disregard. 1) In my opinion warehousing using the inbuilt RM is more of a restriction you have to work around than a benefit and if i were doing it for campaigns and contiguous missions, i'd ignore it and make the limits in code, because that you can easily change on the fly. I made a simple fuel script that added and took away fuel for every landing using the event system. You can control ground, Air spawns easily in script, what you can't so so easily is control weapons loadouts. 2) Routes...arghhh....here be dragons. Route calcs are expensive on CPU and can cause stutters. I worked with Birger on this for AutoGFT. He came up with a "partial route" to reduce load, ie the group puts his waypoint Xkm in the direction of travel. However, you can still get problems with long routes in certain areas of the Caucasus. 1 problem is that the AI doesn't always create the same route! You can sometimes see them recalculate and go back and forwards continuously forever and never reach the destination. Second problem is the current Caucasus map. Rule of thumb...SOUTH roads BAD, Russian roads good. Some roads stop and do not continue, like one south of Poti and one West of Tbilisi. Those two are killers to troops movement over long distances. Off Road and On Road formation switching is really complex. You wouldn't need it, but for one reason...BRIDGES...the most lethal weapon in DCS. If you want to get groups to go anywhere in Georgia, they need to handle bridges. It's almost impossibly complex to fix bridge errors, they will fall off, stall, generally get confused and it's an intermittent, random issue (especially in the south of the Caucasus map). Having better results in NTTR. Also...the circling bug messes large group movements. Sometimes groups (happens in NTTR also) get caught in silly terrain like a lamp post and one unit will circle forever and fall behind. These things were the showstoppers for a campaign for me that relied on lots of troops movement. Not the performance....no, that's bad, but not that. ___________________________________________________________________________ SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *
Pikey Posted September 8, 2017 Posted September 8, 2017 You can store the route. If you want. But I wouldn't, it won't scale well. The routing part of the code is a bit complicated. If you give a route (Mission Task) to a group, it exists and can be stored. Check the later part of the doc I uploaded. It's using Moose but the structure is just the same and you can use any other scripting to get it out and store it. Auto-reload by scripts only achieved... need a stupid workaround but it works. Sadly I can't find a way to recover the route, therefore I think I will continue on the auto-movement commands at each mission start for now.DCS and MOOSE GROUP points discussion.doc ___________________________________________________________________________ SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *
chromium Posted September 8, 2017 Author Posted September 8, 2017 about route to be honest I don't want waypoints, I only need to get 2 information: - last waypoint - road/offroad Those routes then would be loaded together in the very first seconds of simulation. Given a wanted limtation for moving groups, shouldn't be a nightmare for calcs... but I need to test. Thansk for the hint. 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.
chromium Posted September 8, 2017 Author Posted September 8, 2017 About warehousing, I have faith in ED ideas. A lot. And if only we could get 3 thing, we might be done: - Scripting access to ammo/fuel amounts change in vehicles, warehouses and cargo objects; - option for physical transportation of resources by truck/cargos (not unlimited storage in vehicles) - vehicles ammo & fuel bars in F10 View, like life bars. So I will investigate this thing only when I'm done with AI behaviour enhancement. 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.
chromium Posted September 17, 2017 Author Posted September 17, 2017 About routing. I understood what you put in the word file. I also looked into MOOSE, but I didn't get how it retrieve the current route by coding, and how it updates the current route (for example how it could retrieve a F10 inserted route). What I don't get is how to dump or read the current tasks of a group. Using the search button and _G dump, it seems that a "getTasks()" fuction doesn't exist. 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.
chromium Posted September 17, 2017 Author Posted September 17, 2017 About routing. I understood what you put in the word file. I also looked into MOOSE, but I didn't get how it retrieve the current route by coding, and how it updates the current route (for example how it could retrieve a F10 inserted route). What I don't get is how to dump or read the current tasks of a group. Using the search button and _G dump, it seems that a "getTasks()" fuction doesn't exist. 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.
chromium Posted September 17, 2017 Author Posted September 17, 2017 About routing. I understood what you put in the word file. I also looked into MOOSE, but I didn't get how it retrieve the current route by coding, and how it updates the current route (for example how it could retrieve a F10 inserted route). What I don't get is how to dump or read the current tasks of a group. Using the search button and _G dump, it seems that a "getTasks()" fuction doesn't exist. I'll write an open question in another thread. The point of this one is closed :) 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.
Recommended Posts