|
KnightHawk75 -> RE: Aircraft Missing (6/26/2021 3:20:00 PM)
|
Thewood1 - You actually have to repeat what he did to see the problems.
quote:
When I did so, almost all the aircraft I had based there disappeared off the group - but not off the mission screen to assign them.
---
Why would they they disappear or be expected to disappear off the mission screen, as the aircraft still existed?
"disappeared off the group" - It's not clear to me what you mean here, do you mean in the group status XX/XX aircraft count, do you mean in the air-ops screen, you mean the right side of the mission screen?
In the loaded scene all 48/48 aircraft are listed when the group is selected in it's status panel for me upon startup. When I delete the group and recreate it all 48/48 are listed when the new group is re-selected again. Are you sure it wasn't just some gui thing where you needed to click off and onto the new group again for it to update\refresh the group status view? (cause I _have_ seen that.)
I _do_ however noticed something else very weird though. The aircraft air-ops screen (after deleting and re-creating a air-base-group) upon selecting an aircraft has all the option buttons incorrectly disabled, such that the only way to arm them is to use the right-click menu after selection. However once I added a new aircraft, and selected only that new aircraft first, then after that step selecting any of the 48 Backfire's the options were no longer grayed out, exiting the screen required a repeat of that (first click other newer aircraft once, then any of the 48 Backfires).
Bizarre.
So deleting the air-base group and recreating it will produce this behavior on member aircraft present at the time of delete.
1. Using loaded sample scene, delete the airbase-group.
2. Highlight all regroup.
3. Goto air-ops screen and see the above mentioned gray-out condition
4. Add a new aircraft, doesn't matter what.
5. Goto air-ops screen select confirm problem again on Backfires, select newly added aircraft, now select Backfires, everything ok.
6. Exit air-ops re-enter airops..repeat 5.
7. Exit air-ops delete airbase group again and recreate it again.
8. Re-enter air-ops screen for new group, now all 49 have the gray-out issue.
[img]https://i.postimg.cc/DWCvkDdy/114725-Airops-WTFO.jpg[/img]
quote:
Thinking I had inadvertently hit the delete button somehow and blown past the warning
You very very likely did. There is no warning for deleting a group via delete key. Pressing the delete key while in the air-ops screen with a group selected in the background (as will often be the case), will always delete the group without warning btw so be careful.
Mission Editor..
---
No missions in the editor for that side so little confused on that part of it.
But I did notice 2 problems after deleting the airbase and recreating it.
1. The 48 aircraft there are listed with their OLD group name as a base after the name.
Investigating with lua also confirmed that fact, that each units .base was STILL set to the old group object that should not even exist anymore, but probably does because it's still referenced, although a 'get' on that old-group will fail so it's def marked as deleted.
[img]https://i.postimg.cc/ppDPXyYS/Airbase-Group-Not-Updated-On-New-Group.png[/img]
2. Double clicking on any of the 48 aircraft while in the mission editor gui, resets the map to center on 0,0'ish coords, not that of the actual units location, and changes the zoom level. This does not happen to 'new' units added to a fresh Airbase group, just the ones associated with a now deleted group.
Guesses as to what is happening:
1 Upon an AirBase group being deleted via the delete key the prior member units hosted objects are not being updated to reflect their parent host unit as their 'base', instead they are left as the old AirBase group.
2 Upon an AirBase group create new member units that have hosted units are not having member thier base property updated to reflect their new Airbase group membership of their host.
3.Upon aircraft create\insert to an existing group\base the issue does not occur.
This would explain the mission editor weirdness and most of the gui issues in air-ops screen as the buttom buttons probably has some validation logic that wants at least one to actually belong to the air-base to enable the buttons, but once one does they stay active and the right click menu items maybe don't even have said validation.
Workarounds identified to clear up the issues in the presented scene\situation:
- Via the gui manually delete all aircraft from the AirBase group after it's been re-created, and re-add them.
- Run a script to update the .base property on all the affected aircraft either by explicitly assigning the new base group object for the base property, running ScenEdit_HostUnitToParent for each assigning the new base, or run SetUnit base= ... on all affected units, to force-update them to their new Airbase group.
Either workaround clears up all problems mentioned here in my testing.
|
|
|
|
