ok.
you have to start up openmw-cs from where openmw.exe is located. then choosing edit file and selecting the patch it loads up and in upper bar from mechanics there is scripts which opens up.
in there ID AA_con_compScript21 is shown modified right up on the front when ordered by name (default, i think)
you just need to right lick on the name -> edit record and the code is 3 / 4 way down in script window
this will cause her to follow normally without all the clipping relative to player position so if you cast windwalker scroll she will follow with her normal speed as it's scaled on if block after that code.
anyway more specific fix seems to be remove aifollow from the above
( if removing all, leaving getcurrentaipackage == 3 )
Code: Select all
if ( warp == 0 )
if ( GetDistance Player > 680 )
if ( coDist > 300 )
if ( coDist < 680 )
SetPos x bx
SetPos y by
SetPos z bz
AiFollow Player 0 0 0 0
endif
elseif ( coDist2 > 300 )
if ( coDist2 < 680 )
SetPos x cx
SetPos y cy
SetPos z cz
AiFollow Player 0 0 0 0
endif
endif
endif
endif
endif
which is workaround for vanilla reseting AI on repositioning. there's something fishy on openmw side as well
with mirisa (randomly selected from follownow variables) the blocking up happens after issuing aifollows from dialogue. expecially after "let's go" constance and then her. there might be distance checks overlapping main problem being with companion variable which is set on the second take and the distance of mirisa checked against npcvoicedistance but then again she will stay back to 900 which is over 750. namely
get trought initial topics with constance to get aifollow to initialise
(follownow is thus set from script to 1 and doesn't interfere further)
-> follows at distance 360
placeatpc mirisa 1 100 0 and get the travel together topic trought to set aifollow
-> follows at distance 540
then with constance select follow and let's go setting the companion var to 1
-> clipping between 337 and 664
then travel together, mirisa which sets aifollow again as in first time causing
-> follows at 900
that is when those aifollows are removed from the code and with them constance needs to place on wander with wait to get mirisa to follow.
(edit: taking out the positions and aifollows result them to be first those c400, m600 and then skips to c800, m1000, c1200, m1400, c1600 very roughly when alternating aifollows. the engine thinks of adding ghost companions)
does same order happen with your setup ie. constance, companion, constance, companion -> stuck ?
companions ?
(intervention not working is openmw bug)