Strange crash

Any issues with the XWAU or X-Wing Alliance? Please let us know here!
Post Reply

Strange crash

TNT
Cadet 4th Class
Posts: 15
Joined: Mon Mar 09, 2015 2:04 am

Post by TNT » Fri Mar 20, 2015 7:23 am

I am getting the same crash as spoken of here:

http://www.gog.com/forum/star_wars_xwin ... ange_crash

But it has been fixed? Maybe it's that I am running the game on 2560x1440? I am using the 1.2 version of XWAUCP.


Edit: Changed the resolution to 1920x1080 and I was able to complete the mission.

User avatar
Darksaber
Vice Admiral
Posts: 10931
Joined: Mon Jan 10, 2000 12:01 am
Contact:

Post by Darksaber » Fri Mar 20, 2015 11:55 am

Just flown the mission myself, B1M2 Rescue Uncle Antan, completed it with no problems.
“You can please some of the people all of the time, you can please all of the people some of the time, but you can’t please all of the people all of the time”.”
- John Lydgate

Good Things Come To Those Who Wait....
Darksaber's X-Wing Station

TNT
Cadet 4th Class
Posts: 15
Joined: Mon Mar 09, 2015 2:04 am

Post by TNT » Fri Mar 20, 2015 6:37 pm

The very first mission of the game was crashing. After completing the first mission in 1920x1080 I switched it back to 2560x1440 and it crashed on the second mission. Noticed the exact same thing as this poster reported in that thread:

"Had same issue as OP - the first mission will always CTD at some point when trying to target anything (usually after chasing off the Viraxo) while trying to run in 2560x1440. I've noticed a square in the middle of the screen will flash white when entering hyperspace in 1440 as well."

I am running it in Windows 8.1, XWAhacker, GTX 980. Maybe I should try running it in compatibility mode?

User avatar
Darksaber
Vice Admiral
Posts: 10931
Joined: Mon Jan 10, 2000 12:01 am
Contact:

Post by Darksaber » Fri Mar 20, 2015 7:23 pm

Can you PLEASE SPECIFY what you regard as the very first mission please?? Because as far as I'm concerned the very first mission is "Family Business: Mission 1: Aeron's Lesson" which we regard as B0M1

* PROLOGUE: Family Business
B0M1 - Mission 1: Aeron's Lesson: Transport Operations
B0M2 - Mission 2: Emon's Lesson: Weapons
B0M3 - Mission 3: Aeron's Error: Data Recovery
B0M4 - Mission 4: Sticking it to the Viraxos: Covert Delivery
B0M5 - Mission 5: Black Market Bacta: Cargo Transfer
B0M6 - Mission 6: Rebel Rendezvous: Aid to the Alliance
B0M7 - Mission 7: Nowhere to go?: Escape Imperial Attack
* Joining the Rebellion
B0M8 - Mission 1: Deep Space Strike Evaluation
B0M9 - Mission 2: Starfighter Superiority Evaluation
* BATTLE 1: Clearing the Way
B1M1 - Mission 1: Convoy Attack
B1M2 - Mission 2: Rescue Uncle Antan (Family mission)
B1M3 - Mission 3: Reconnaissance of Imperial Task Force
B1M4 - Mission 4: Rescue Echo Base Prisoners
B1M5 - Mission 5: Recover Imperial Probe (Family mission)
B1M6 - Mission 6: Stop Resupply of ISD Corrupter
B1M7 - Mission 7: Destroy Imperial Sensor Net
* BATTLE 2: Secret Weapons of the Empire
B2M1 - Mission 1: Flight Staff Transfer
B2M2 - Mission 2: Ensnare Imperial Prototypes
B2M3 - Mission 3: Kill K'Armyn Viraxo (Family mission)
B2M4 - Mission 4: Raid Production Facility
B2M5 - Mission 5: Defend CRS Liberty
B2M6 - Mission 6: Destroy Imperial Research Facility
* BATTLE 3: Over the Fence
B3M1 - Mission 1: Liberate Slave Convoy
B3M2 - Mission 2: Supply Rebels with Warheads (Family mission)
B3M3 - Mission 3: Recon Imperial Research Facility
B3M4 - Mission 4: Investigate Imperial Communications Array
B3M5 - Mission 5: Plant Listening Device (Family mission)
B3M6 - Mission 6: Rendezvous with defector
B3M7 - Mission 7: Scramble!
* BATTLE 4: The Bothan Connection
B4M1 - Mission 1: Shipment to Mining Colony (Family mission)
B4M2 - Mission 2: Reconnaissance of Imperial Convoy
B4M3 - Mission 3: Mining Colony Under Siege: Rescue Aeron (Family mission)
B4M4 - Mission 4: Capture the Freighter Suprosa
B4M5 - Mission 5: Abandon Rebel Base at Kothlis
B4M6 - Mission 6: Protect Imperial Computer
* BATTLE 5: Mustering the Fleet
B5M1 - Mission 1: Protect Alliance-Smuggler Meeting
B5M2 - Mission 2: Attack Imperial Convoy
B5M3 - Mission 3: Break Emon Out of Brig (Family mission)
B5M4 - Mission 4: Protect Smuggler Retreat
B5M5 - Mission 5: Rescue Smugglers
B5M6 - Mission 6: Recover Family Data Core (Family mission)
B5M7 - Mission 7: Attack Pirate Base
* BATTLE 6: The Darkest Hour
B6M1 - Mission 1: Meet with Bothan Delegation
B6M2 - Mission 2: Locate Mercenary Base (Family mission)
B6M3 - Mission 3: Raid Mercenary Base
B6M4 - Mission 4: Rescue Bothan Spies
B6M5 - Mission 5: Steal Imperial Shuttle
B6M6 - Mission 6: Escort Rebel Fleet
B6M7 - Mission 7: Family Reunion (Family mission)
* BATTLE 7: The Battle of Endor
B7M1 - Mission 1: Battle of Endor
B7M2 - Mission 2: That Thing's Operational
B7M3 - Mission 3: The Shield is Down
B7M4 - Mission 4: Death Star Tunnel Run

Also, I only have Windows 7 x64 and the highest resolution I can go too is 1680x1050 but I normally play at 1280x1024, so specifying your system is pointless.

If the mission runs on my system then I'm happy it will run on any, if you start changing your screen resolution so wide that when you play the game and each time it crashes on that resolution then that tells me it's a problem.

First try running the mission with a standard default in-game resolution, if it runs without crashing, then I doubt its anything we can help you with, and the cause is the resolution your trying to play the game at.
“You can please some of the people all of the time, you can please all of the people some of the time, but you can’t please all of the people all of the time”.”
- John Lydgate

Good Things Come To Those Who Wait....
Darksaber's X-Wing Station

TNT
Cadet 4th Class
Posts: 15
Joined: Mon Mar 09, 2015 2:04 am

Post by TNT » Fri Mar 20, 2015 7:34 pm

Sorry. It's BOM1.

A lot of variables in play here I'll just try adjusting some of them.

TNT
Cadet 4th Class
Posts: 15
Joined: Mon Mar 09, 2015 2:04 am

Post by TNT » Fri Mar 20, 2015 8:07 pm

Tried a bunch of different things while running 2560x1440. Tried running as admin, tried in Windows 7, Windows XP SP2, all would crash on that graphical setting. And I would always see the square box while going into hyperspace.

However once I switched back to Windows 8.1 and ran in 1920x1080 things went great. And the game still looked gorgeous of course. Was able to complete BOM2.

Maybe this is something to pass on to Reimar?

User avatar
Darksaber
Vice Admiral
Posts: 10931
Joined: Mon Jan 10, 2000 12:01 am
Contact:

Post by Darksaber » Fri Mar 20, 2015 8:12 pm

Ok then, when does it crash, when you exit the hangar and travel to the hyper buoy, or when you arrive in the next region, to pick up the cargo canisters, you mention that targeting a craft (pressing T) it crashes.

In your quoted section you mention (usually after chasing off the Viraxo), but there are NO Viraxo in this mission, you don't even engage any craft to fight with!
“You can please some of the people all of the time, you can please all of the people some of the time, but you can’t please all of the people all of the time”.”
- John Lydgate

Good Things Come To Those Who Wait....
Darksaber's X-Wing Station

TNT
Cadet 4th Class
Posts: 15
Joined: Mon Mar 09, 2015 2:04 am

Post by TNT » Fri Mar 20, 2015 8:18 pm

It crashes on both BOM1 and BOM2. Haven't tried any missions beyond that yet. In BOM1 it's always when trying to select the containers after the Viraxo hyper out. In BOM2 it happens when starting to engage the drones that Emon releases.

As this is happening on multiple missions I am thinking this is a xwhacker issue. Both missions on 1920x1080 do not crash.
Last edited by TNT on Fri Mar 20, 2015 8:21 pm, edited 1 time in total.

User avatar
Darksaber
Vice Admiral
Posts: 10931
Joined: Mon Jan 10, 2000 12:01 am
Contact:

Post by Darksaber » Fri Mar 20, 2015 8:19 pm

Like I said I only have win7 and play with the in-game default resolutions, I suggest you try using the default resolutions to test.

1920x1080 is not a default in-game resolution as far as I know. If the missions play through with the default resolution setting, then there is your problem. Your setting the resolution too high I know it's not the missions of the new craft as I've play through these missions numerous times without a problem, if there was a problem I wouldn't have release XWAUCPv1.2. Plus we would have had more reports of crashing, since v1.2 has been release no problems have been reported, besides your.

Sorry I can't help any more, perhaps Reimer can shed some more light on the situation.
“You can please some of the people all of the time, you can please all of the people some of the time, but you can’t please all of the people all of the time”.”
- John Lydgate

Good Things Come To Those Who Wait....
Darksaber's X-Wing Station

TNT
Cadet 4th Class
Posts: 15
Joined: Mon Mar 09, 2015 2:04 am

Post by TNT » Fri Mar 20, 2015 8:22 pm

No problem. I appreciate the feedback.

I definitely think this is a xwhacker issue. I'll let Reimar know if he isn't already aware.

Reimar
Cadet 1st Class
Posts: 239
Joined: Mon Jan 19, 2009 11:45 am

Post by Reimar » Sat Mar 21, 2015 3:04 pm

I won't have time to investigate these kind of crashes. Lately it's been mostly Jeremya who has looked into such problem.
This applies doubly if you use the new ddraw dlls - which I suspect you do since it was never possible to launch fullscreen games with resolutions wider than 2000 pixels on Windows before we had the DirectX11 wrapper DLLs.

User avatar
JeremyaFr
XWAU Member
Posts: 3922
Joined: Mon Jan 18, 2010 5:52 pm
Contact:

Post by JeremyaFr » Sat Mar 21, 2015 5:55 pm

TNT wrote:The very first mission of the game was crashing. After completing the first mission in 1920x1080 I switched it back to 2560x1440 and it crashed on the second mission. Noticed the exact same thing as this poster reported in that thread:

"Had same issue as OP - the first mission will always CTD at some point when trying to target anything (usually after chasing off the Viraxo) while trying to run in 2560x1440. I've noticed a square in the middle of the screen will flash white when entering hyperspace in 1440 as well."

I am running it in Windows 8.1, XWAhacker, GTX 980. Maybe I should try running it in compatibility mode?
Hello,
Can you please give details of the crash from the Event Viewer.

kakslash
Recruit
Posts: 2
Joined: Mon Apr 27, 2015 2:39 am

Post by kakslash » Mon Apr 27, 2015 2:51 am

JeremyaFr wrote:
TNT wrote:The very first mission of the game was crashing. After completing the first mission in 1920x1080 I switched it back to 2560x1440 and it crashed on the second mission. Noticed the exact same thing as this poster reported in that thread:

"Had same issue as OP - the first mission will always CTD at some point when trying to target anything (usually after chasing off the Viraxo) while trying to run in 2560x1440. I've noticed a square in the middle of the screen will flash white when entering hyperspace in 1440 as well."

I am running it in Windows 8.1, XWAhacker, GTX 980. Maybe I should try running it in compatibility mode?
Hello,
Can you please give details of the crash from the Event Viewer.
Obviously not the original poster, but I experienced similar troubles when trying to run at 2560x1440. Not sure if you're still interested in taking a look, but below is what I have in event viewer for the crashes. I did try other 16x9 resolutions, it only seems to be a problem at 2560x1440, 2048x1152 worked fine, as did 1920x1080. 2048x1152 working seems to imply that it may not be an issue with the width being >2000. I found the first death star mission (b7m1) to be the easiest to test against, as I would crash right outside the hangar when pressing 'y' to select a target, much quicker than waiting for the b0m1 crash.

This is using the GOG version of the game, but I had similar troubles when playing through the CD version of the game last year as well, using the non-gui xwahacker.

Faulting application name: XWINGALLIANCE.EXE, version: 2.0.0.2, time stamp: 0x3765a9b7
Faulting module name: XWINGALLIANCE.EXE, version: 2.0.0.2, time stamp: 0x3765a9b7
Exception code: 0xc0000005
Fault offset: 0x000d3214
Faulting process id: 0xdb4
Faulting application start time: 0x01d0808c3accb5e1
Faulting application path: C:\Games\Star Wars - X-Wing Alliance\XWINGALLIANCE.EXE
Faulting module path: C:\Games\Star Wars - X-Wing Alliance\XWINGALLIANCE.EXE
Report Id: 8d90f20b-ec7f-11e4-9005-74d02b909a19

Faulting application name: XWingAlliance.exe, version: 2.0.0.2, time stamp: 0x3765a9b7
Faulting module name: XWingAlliance.exe, version: 2.0.0.2, time stamp: 0x3765a9b7
Exception code: 0xc0000005
Fault offset: 0x000d328c
Faulting process id: 0x11b8
Faulting application start time: 0x01d0808950cfb886
Faulting application path: C:\Games\Star Wars - X-Wing Alliance\XWingAlliance.exe
Faulting module path: C:\Games\Star Wars - X-Wing Alliance\XWingAlliance.exe
Report Id: 46a1ff73-ec7d-11e4-9005-74d02b909a19

User avatar
JeremyaFr
XWAU Member
Posts: 3922
Joined: Mon Jan 18, 2010 5:52 pm
Contact:

Post by JeremyaFr » Mon Apr 27, 2015 6:32 pm

Thanks for the crash reports.

The direct cause of the crashes is an access violation when writing to a DirectDraw surface.
I think it may be related to the surface's pitch.

You can try that:
  1. verify that the game runs in hardware mode
  2. if it's applied, remove the xwahacker's 32bitmode patch

kakslash
Recruit
Posts: 2
Joined: Mon Apr 27, 2015 2:39 am

Post by kakslash » Tue Apr 28, 2015 1:02 am

JeremyaFr wrote:Thanks for the crash reports.

The direct cause of the crashes is an access violation when writing to a DirectDraw surface.
I think it may be related to the surface's pitch.

You can try that:
  1. verify that the game runs in hardware mode
  2. if it's applied, remove the xwahacker's 32bitmode patch
Thanks for the response JeremyaFr. You all have done amazing work in extending the life of this great game.

I did some further testing tonight. I can verify that the game runs in hardware mode. I also tried both with and without the 32bitmode patch applied (via the gui xwahacker) and experienced the same crashes when the resolution was set to 2560x1440.

I decided to test further, and installed a fresh copy of the game (again, GOG version), and did not install the 1.2 craft pack. I tested various resolutions, and the absolute highest 16x9 resolution I was able to achieve was 2352x1323, the next multiple up would cause a crash. The event viewer messages all have the same exception code and fault offset for the crash. The fault offset is apparently mission related, hence the two different ones in my above post (b0m1, b7m1). The crash also specifically seems to relate to the targeting display. If the ship is in third person view, the crash will not occur when targeting the specific object that seems to trigger the crash.

It is certainly an interesting problem, and not knowing enough about DirectDraw, I am sure you are correct in your assessment that there is an access violation in DirectDraw related the surface's pitch. That said, if there are no simple fixes, I'm more than content playing the game at a slightly lower resolution, as it still looks beautiful with all the modifications.

Thanks again for taking a look, and for your work.

Freebeard
Cadet 4th Class
Posts: 10
Joined: Sun Oct 09, 2016 8:54 am

Post by Freebeard » Sun Oct 09, 2016 9:53 am

I'm having this same problem. Have you found a solution yet?

Freebeard
Cadet 4th Class
Posts: 10
Joined: Sun Oct 09, 2016 8:54 am

Post by Freebeard » Sun Oct 09, 2016 10:15 am

Nevermind, I read the thread over on the GOG forums. Seems the game can't handle anything above 1080p resolutions.

User avatar
JeremyaFr
XWAU Member
Posts: 3922
Joined: Mon Jan 18, 2010 5:52 pm
Contact:

Post by JeremyaFr » Sun Oct 09, 2016 10:47 am

Hello,
The max supported resolution height is 1200. With higher resolution, the game will crash.

Freebeard
Cadet 4th Class
Posts: 10
Joined: Sun Oct 09, 2016 8:54 am

Post by Freebeard » Sun Oct 09, 2016 6:05 pm

Yep! I was able to set a custom resolution of 2844 x 1200 for my 21:9 monitor and it worked fine. Kind of an odd resolution, but it looks good. Thanks!

Post Reply