niston Posted July 26, 2019 Share Posted July 26, 2019 I'm trying to add Vertibird Fast Travel to the Prydwen. Since I don't want to edit the VFT Quest, I've duplicated it. Made a new Keyword, linked it in the story manager via SM Node, set conditions, etc. Added mostly the same scene phases and actions to my quest that are also in the VFT Quest. On a side note, the Scene Editor must be the worst part of the entire CK. It crashes every other click, does very often not save edits and is generally a PITA to work with. No wonder Beth's games are bugged AF, with tools like this. Meh! But I digress... What I've changed on my quest is, I've replaced the TravelToSmoke Package with my own Package that -in theory- uses the SIT procedure to make the Bird go sit on the Prydwen's main perch. The sit target is forced to the BosPrydwenVertibirdMainPerch reference in BostonAirportExt11. All well, except for it doesn't work at all. What happens is totally bizarre: The VB spawns in the distance, rises to the Prydwen's altitude, then almost crashes back to ground, then turns over and travels in direction of Fort Hagen until it vanishes, never to be seen again. For testing purposes, I've removed all Phases and Actions from my Quest's Scene, except for the Action to have the VB go sit on the perch. I've checked again that the sit target is indeed the main perch on the Prydwen. I also verified that it is indeed my quest that is being started on sending the new KW story manager event. But that doesn't change the outcome one iota: VB still flies up, then almost crashes back to ground, then vanishes towards Fort Hagen. I can make absolutely no sense of this. Does not compute. Has me bamboozled. Completely confuzzled. If all I have is a sit procedure with a forced SingleRef target, why does the VB not even try to approach that target but flies off to somewhere else completely? Link to comment Share on other sites More sharing options...
SKKmods Posted July 26, 2019 Share Posted July 26, 2019 (edited) The issue is probably that one of the scripts calls GetSafePosition() which must find a landing space on the navmesh. The sit perch does not qualify. Find that line and remove or replace it. Also check the package that manages the shadow of steel flight from Cambs PD to Prydwen, you may need a specifc travel, hover, land/sit sequence. Edited July 26, 2019 by SKK50 Link to comment Share on other sites More sharing options...
niston Posted July 26, 2019 Author Share Posted July 26, 2019 Not sure if that's the problem: If I use the original VFT quest, the vertibird comes to the prydwen but will land literally on the flight deck. But I will check for more GetSafePosition(). I know I removed it from my calling script. EDIT: I've checked, I think, all the scripts. VFTPlayerScript, VertibirdPlayerRideable, bospilotscenemanagerscript, companionvertibirdquestscript and VFTQuestScript. None of em have a call to GetSafePosition(). Can't find any more scripts. Also checked the fragments. Nope, no dice. Link to comment Share on other sites More sharing options...
niston Posted July 26, 2019 Author Share Posted July 26, 2019 Found the RR303ToPrydwenPackage. It looks exactly the same as my VFTToPrydwen one: Sit Target: BosPrydwenVertibirdMainPerch, Eat? False, Food Object: Food. Sequence -> Procedure: Sit -> Simultaneous -> Procedure: Sit -> Procedure: Wait -> Procedure: Eat *scratch head* Trying to get this to work for the past two days. I think I'mma give up for now :) Link to comment Share on other sites More sharing options...
niston Posted July 26, 2019 Author Share Posted July 26, 2019 Alright, I chased the Vertibird that flew off. And lo and behold, it gets even more bizarre: The VB flies towards fort hagen indeed, tries to land a bit above fiddlers green. Yet, shortly before touchdown, it cancels the landing, turns 180 and flies to the prydwen. Once there, it goes to sit in the perch, but half way through docking, it takes off again and flies back towards fort hagen. It then stops existing about midway to FH and it's reference becomes invalid, while the quest keeps on running. There are so many WTFs here. But this isn't all. I deleted any and all scene information from my quest. And the Vertibird is still following the exact same routine. So, the VFT system basically gives a crap about the scene info in my quest and does this... weird thing, no matter what. Link to comment Share on other sites More sharing options...
DieFeM Posted July 26, 2019 Share Posted July 26, 2019 These packages are in the Actor. You would need to create a copy of the fast travel vertibirds NPCs, set a proper package on them, and replace them in the aliases. Link to comment Share on other sites More sharing options...
niston Posted July 27, 2019 Author Share Posted July 27, 2019 I got it to work, the problem was the StartMarkerVFT Alias. Forcing it to PickmanGalleryLocation works, for whatever reason. Next problem tho: VB can't be activated once it perched on the Prydwen. Player has to go to interior cell and come back, it'll work then. Which is a complete no-go. I tried playing Gamebryo animations on the perch, but that doesn't resolve the issue. Also tried AllowPCDialogue(true) on the VB without success. Must be something else. Link to comment Share on other sites More sharing options...
SKKmods Posted July 27, 2019 Share Posted July 27, 2019 I had this with a VB module, someting to so with the 3d loaded state. What I did was; Spawn a static VB NIF ontop of the landed FVT VB as a maskDisable the landed FVT VBEnable the landed FVT VB which seems to reset the activator state Disable/Delete the static VB mask Link to comment Share on other sites More sharing options...
niston Posted July 27, 2019 Author Share Posted July 27, 2019 I've tried disable/enable; It messes up the state of the VFTFromPrydwen quest. IE the VB will depart immediately after .Enable() even with no one on board. I suppose it flies to FH then, but I didn't chase. Getting this to work seems quite the challenge. Link to comment Share on other sites More sharing options...
SKKmods Posted July 27, 2019 Share Posted July 27, 2019 Check the VB quest alias has "allow disabled" or somsuch. Link to comment Share on other sites More sharing options...
Recommended Posts