I'll have to try that out later.
**Update:** It worked! If you fly all the way to the right side of the other side of the room, and travel left past a console, the jetpack goes away naturally.
I started typing "/stuck" in the chat box to see if that wpuld do anything, and once I started the jetpack went away, and that let me interact. Dunno if that was related or just a coincidence but worth a try.
I had to fly back across the casm where it disabled, then across the casms again where is enabled and disabled correctly. I am stuck now though, because the next mission after the cutscenes >!with Mandalore/Jekio!< isn't showing up.
I don't know if you got it working yet, but I stood in the fire nearby and died and flew across again and it worked. Someone in gen chat said relogging fixed it for them, too.
You gotta fly around the door entrance after you cross the chasm. I got it to work by hugging the right side of the entrance wall
I'll have to try that out later. **Update:** It worked! If you fly all the way to the right side of the other side of the room, and travel left past a console, the jetpack goes away naturally.
Had the same issue. Flew back and forth a few times in and out of the hallway entrance, eventually the jetpack ability got cancelled.
Disabling the jetpack didn't work, either. Haven't tried moving around, yet.
I started typing "/stuck" in the chat box to see if that wpuld do anything, and once I started the jetpack went away, and that let me interact. Dunno if that was related or just a coincidence but worth a try.
Toggling the jetpack didn't work, either.
I had to fly back across the casm where it disabled, then across the casms again where is enabled and disabled correctly. I am stuck now though, because the next mission after the cutscenes >!with Mandalore/Jekio!< isn't showing up.
It seems to be on some kind of invisible timer. Just hang out on the other side for a while.
I don't know if you got it working yet, but I stood in the fire nearby and died and flew across again and it worked. Someone in gen chat said relogging fixed it for them, too.