Stops Responding when I get into Hangar

[Horace Hogan]

Everything is fine until I get into the Hangar for the first mission, as it stops responding almost immediately. Help

[spyderDFX]

Same problem

[FuchsiaShock]

Same.

[*U.P.A* KidCalvo]

Same problem. I just played Simulator, and stop responding when I get into Hangar. Run Win 10.

[Modulous Prime]

I found it only does this if I use the mouse. If I use the keyboard (and press space in the hangar), it solves this (for me)

[FuchsiaShock]

Fixed it by using runfirst.exe to start the game (you can find it in the XWAUpgrade & Darksaber crat packs or in the post in this forum about music & cinematics skipping). It's because the game doesn't like multiple CPU cores. Also apparently you can use task manager while the game is running to change the affinity and that fixes it too.

[spetsnaz23]

yeahhhhhh it works, thnx a lot :)

[pushdawn3]

Originally posted by ThatSabineGirl:

Fixed it by using runfirst.exe to start the game (you can find it in the XWAUpgrade & Darksaber crat packs or in the post in this forum about music & cinematics skipping). It's because the game doesn't like multiple CPU cores. Also apparently you can use task manager while the game is running to change the affinity and that fixes it too.

XWA crashes on me in both mission and sims when I select "Go to Hanger". I get a resolve Backbuffer: pathway is incorrect message. I have setup RunFirst.exe and also set affinity to CPU1. Doing this helped with the latency between video and audio; however, I continue to hit this impass. I am running Vista 32 on an HP Pavilion dv8000 series. I am running DX11 and I have 2G Ram, 1.73 dual core processor and Intel GMA 950 chipset.

Is my issue resolution size?

[FuchsiaShock]

Originally posted by pushdawn3:

Originally posted by ThatSabineGirl:

Fixed it by using runfirst.exe to start the game (you can find it in the XWAUpgrade & Darksaber crat packs or in the post in this forum about music & cinematics skipping). It's because the game doesn't like multiple CPU cores. Also apparently you can use task manager while the game is running to change the affinity and that fixes it too.

XWA crashes on me in both mission and sims when I select "Go to Hanger". I get a resolve Backbuffer: pathway is incorrect message. I have setup RunFirst.exe and also set affinity to CPU1. Doing this helped with the latency between video and audio; however, I continue to hit this impass. I am running Vista 32 on an HP Pavilion dv8000 series. I am running DX11 and I have 2G Ram, 1.73 dual core processor and Intel GMA 950 chipset.

Is my issue resolution size?

I dunno. That's just what worked for me when I had the crash. That's the limit of my knowledge, I'm afraid.

[pushdawn3]

Thanks for posting back.

[tarasis]

Same problem. I've tried both RunFirst.exe and just setting the affinity to a single cpu, but neither solution has helped. Though it managed to go a little longer before crashing.

Using Win 10, 64 bit
i7 4970k
16GB Ram
GTX 970 4GB

[tarasis]

I've found that IF I launch immeditately then I can start the mission and it won't hang. (Although there is a brief pause with the blue spinning circle during the switch from hanger to flying)

[pushdawn3]

Originally posted by tarasis:

Same problem. I've tried both RunFirst.exe and just setting the affinity to a single cpu, but neither solution has helped. Though it managed to go a little longer before crashing.

Using Win 10, 64 bit
i7 4970k
16GB Ram
GTX 970 4GB

I finally found a way "around" the crash. When I get the 'error' message, I open task manager {cntrl+alt+del}. I then end task on the error. I may have to try this step a few times, eventually it will work and a new 'end task' window will appear for "Xwing Alliance". I DO NOT SELECT END TASK. Instead, I 'X' the window - top right button. The window will close, leaving the game continuing and once it loads I never have this problem again until I exit and return to
Windows. I have been able to do this reliably and have enjoyed myself thoroughly.

I hope this helps you, gentlemen.

[aeveav]

Originally posted by ThatSabineGirl:

Fixed it by using runfirst.exe to start the game (you can find it in the XWAUpgrade & Darksaber crat packs or in the post in this forum about music & cinematics skipping). It's because the game doesn't like multiple CPU cores. Also apparently you can use task manager while the game is running to change the affinity and that fixes it too.

that just made it crash immedietly. just start up, black screen, crash.

edit: now the game launches, but its extremely laggy (like, 1 frame every five seconds)

[SgtSchultz]

I encountered similar problems to the ones that others have discussed here, and found a solution that works in my particular case.

I normally run a display management program called "DisplayFusion" that this game does not appear to agree with. After disabling DisplayFusion, I was able to play the game normally without the "Hangar crash" (or lockup) that I was experiencing with DF enabled.

There's at least one other older game (that I can't recall off the top of my head) that I've had to do the same thing with.

Note that I am running XWA with the XWAUpgrade v1.3 mod installed, which will run the "RunFirst" application ThatSabineGirl mentioned previously IF you run the game using the desktop link that the XWAUpgrade installer creates.