B4M6 - Mission 6: Protect Imperial Computer (ISD don't dock)
B4M6 - Mission 6: Protect Imperial Computer (ISD don't dock)
-
- Posts: 17
- Joined: Fri Oct 22, 2004 11:01 pm
Hi all,
ISD don't dock on Razor on Battle 4 Mission 6.
How to fix this?
(Latest XWAU Patch installed)
ISD don't dock on Razor on Battle 4 Mission 6.
How to fix this?
(Latest XWAU Patch installed)
You do not have the required permissions to view the files attached to this post.
- Forceflow
- Posts: 7218
- Joined: Wed Oct 20, 1999 11:01 pm
- Contact:
Has this happened multiple times? I flew the mission some time ago and it worked, so it could just have been a fluke if it doesn't happen all the time...
Murphy was an optimist! I am a pessimist!
And always remember that a smile is cheaper than a bullet! (District 9)
Webmaster of the X-Wing Alliance Upgrade Project
And always remember that a smile is cheaper than a bullet! (District 9)
Webmaster of the X-Wing Alliance Upgrade Project
-
- Posts: 42
- Joined: Thu Jun 25, 2020 2:04 pm
- Contact:
Is that Star Destroyer shooting at you?
I remember being able to observe the docking without it shooting a single shot at me.
If so, did you attack it? maybe that's why?
I remember being able to observe the docking without it shooting a single shot at me.
If so, did you attack it? maybe that's why?
-
- Posts: 9
- Joined: Mon Aug 01, 2022 8:45 pm
I encountered this same bug on 5.5. Played it twice, and both times the Avenger failed to complete the docking order which breaks the mission. I tried destroying the Avenger, and this triggers a radio message telling you to protect the escape pod, but no escape pod ever appears.
-
- Posts: 9
- Joined: Mon Aug 01, 2022 8:45 pm
It's possible this has to do with monitor refresh rate. The game tends to freeze up or slow to a crawl when you're returning to hangar if you play the game at anything higher than 60hz (launching from the hangar is fine for some reason). This can be somewhat circumvented by switching camera views, though.
I tried the mission a third time at 60hz (I normally play at 144hz), and this time the Avenger did finish docking with the Razor. I feel it still took longer than it should have, though... the Avenger seemed to freeze during docking and then move forward a little in brief spurts. By the time it had docked, all enemy fighters had already been destroyed and me and the rest of the squadron were just sitting around, waiting.
I tried the mission a third time at 60hz (I normally play at 144hz), and this time the Avenger did finish docking with the Razor. I feel it still took longer than it should have, though... the Avenger seemed to freeze during docking and then move forward a little in brief spurts. By the time it had docked, all enemy fighters had already been destroyed and me and the rest of the squadron were just sitting around, waiting.
- Ace Antilles
- Posts: 7910
- Joined: Sat Jan 22, 2000 12:01 am
- Contact:
Yes there are hangar issues and hz minor bugs. Particularly in VR. The hangar is locked to 60fps to try and stop issues but this is being looked at.
That docking is a bit of a pain. Unless someone has a fix then we can try and look into it for the future release
That docking is a bit of a pain. Unless someone has a fix then we can try and look into it for the future release
-
- Posts: 2
- Joined: Sat Dec 03, 2022 8:09 pm
I've found a relatively reliable way to bring the Avenger to dock with the Razor, but it's a bit cheesy and you need Medium Difficulty or lower. (afaik the Avenger shoots at you at Hard Difficulty even without you making the first hit)
When you have dealt with the TIEs, the Avenger usually sits in "docking with Razor - 0.16" (or similar) in its action display and doesn't move.
What i did just out of interest was to fly very close to the Razor and the Star Destroyer hangar (don't attack the Avenger) and passing by it again and again. Also flying next to the Razor and giving it a little bit of throttle.
EDIT: Also tested again right now with success: You can also wait next to the Star Destroyers hangar+Razor and you see the Avenger moving suddenly.
This suddenly made the Avenger move bit for bit and the docking action countdown was going down step by step - eventually the next part of the mission triggered and the game showed that the Star Destroyer has docked with the Razor.
So in case you get stuck here and you survive the TIEs, there is a chance this might be a workaround for now.
Additional info - i tried running my monitor at 60 Hz, 165 Hz, framelock at 60 Hz, nothing helped. Funny enough this cheese did for some weird reason.
FWIW i also used this balancing modification for the mission (it doesn't alter anything for the Razor part though):
viewtopic.php?f=35&t=12942&p=174460&hilit=b4m6#p174460
I hope this could help you folks.
Cheers!
When you have dealt with the TIEs, the Avenger usually sits in "docking with Razor - 0.16" (or similar) in its action display and doesn't move.
What i did just out of interest was to fly very close to the Razor and the Star Destroyer hangar (don't attack the Avenger) and passing by it again and again. Also flying next to the Razor and giving it a little bit of throttle.
EDIT: Also tested again right now with success: You can also wait next to the Star Destroyers hangar+Razor and you see the Avenger moving suddenly.
This suddenly made the Avenger move bit for bit and the docking action countdown was going down step by step - eventually the next part of the mission triggered and the game showed that the Star Destroyer has docked with the Razor.
So in case you get stuck here and you survive the TIEs, there is a chance this might be a workaround for now.
Additional info - i tried running my monitor at 60 Hz, 165 Hz, framelock at 60 Hz, nothing helped. Funny enough this cheese did for some weird reason.
FWIW i also used this balancing modification for the mission (it doesn't alter anything for the Razor part though):
viewtopic.php?f=35&t=12942&p=174460&hilit=b4m6#p174460
I hope this could help you folks.
Cheers!
-
- Posts: 3
- Joined: Tue Jan 20, 2015 8:13 pm
Ahoy. I can confirm that this problem and workaround is still extant with XWAU2020 / XWAU2020update_v5.0 / XWAU2020fixpack_v5.6.2
The Avenger gets to 0.18 then no closer. Attack it, don't attack it, finish off all the gunboats and TIEs first or not, it makes no difference.
The only method I could find to get it complete the docking was @CrimsonEminence's suggestion to fly very close to the Razor, which jumps the Avenger forwards 0.1 / 0.2 per pass.
The Avenger gets to 0.18 then no closer. Attack it, don't attack it, finish off all the gunboats and TIEs first or not, it makes no difference.
The only method I could find to get it complete the docking was @CrimsonEminence's suggestion to fly very close to the Razor, which jumps the Avenger forwards 0.1 / 0.2 per pass.
- Ace Antilles
- Posts: 7910
- Joined: Sat Jan 22, 2000 12:01 am
- Contact:
There seems to be issues with the docking which we believe is due to FPS being higher than the original.Rogerborg wrote: ↑Thu Nov 02, 2023 12:01 amAhoy. I can confirm that this problem and workaround is still extant with XWAU2020 / XWAU2020update_v5.0 / XWAU2020fixpack_v5.6.2
The Avenger gets to 0.18 then no closer. Attack it, don't attack it, finish off all the gunboats and TIEs first or not, it makes no difference.
The only method I could find to get it complete the docking was @CrimsonEminence's suggestion to fly very close to the Razor, which jumps the Avenger forwards 0.1 / 0.2 per pass.
@LPhoenix will be on this mission soon. Maybe we can find a better solution.