Page 1 of 1

Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Mon Jan 20, 2020 5:24 am
by rafaabslu
Hi friends. I really apreciated your work in this mod. Congrats for all of the modders.
My version is 2 cds. But newly i have a big problens.
After install of the Xwaupgrade 1.6 i dont play the campaign game anymore. After the briefing screen, on the load before a mission starts my game crashs to desktop. Dont shows a error message, nothing. And crashs to desktop.
I tryed Keep updated all the hooks are writed here in Topic for beginners.
I have do a fresh install of XWA. After following the steps of the Topic for beginners. The games runs Very well in the concourse screen and some meeles or skirmish mode. Sometimes in the midle of skirmish, the game crashs too. But i tried to Begin a mission, the same problem. After the load screen game crashs every time.
Im Crazy because i loved play the campaign with the New graphics.

Please someone could help me to fix this issues?.
Thanks Very much.

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Mon Jan 20, 2020 7:06 pm
by JeremyaFr
Hello,
Can you attach a crash report from the events viewer?

1. Go in the Events Viewer.
2. Browse to the crash event (in Windows -> Application)
3. Select and Copy the text
4. Paste it here

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Mon Jan 20, 2020 9:31 pm
by rafaabslu
Hi guys. Thanks for your reply.
Sorry but, My SO is in Portuguese Brasil
Thanks for your help.


Following the log events:

-General
Falha no bucket 1686460533864911574, tipo 1
Nome do Evento: APPCRASH
Resposta: Não disponível
ID do CAB: 0

Assinatura do problema:
P1: XWingAlliance.exe
P2: 2.0.0.2
P3: 3765a9b7
P4: KERNELBASE.dll
P5: 10.0.17134.441
P6: 3da51fd0
P7: e06d7363
P8: 00111812
P9:
P10:

Arquivos anexados:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9A48.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9FF6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA054.tmp.xml

Esses arquivos talvez estejam disponíveis em:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_XWingAlliance.ex_4de77a50f73a7c703de9ef763a81b58574f649c8_430ecb5f_2d8ea822

Símbolo da análise:
Verificando novamente se há uma solução: 0
ID do Relatório: 710f7a68-33cd-4a8a-a7fc-02fe22cf519f
Status do Relatório: 268435456
Bucket com hash: 9a18d84a6e4d164b676782eb98bbd2d6Guid do CAB: 0

- EventData

1686460533864911574
1
APPCRASH
Não disponível
0
XWingAlliance.exe
2.0.0.2
3765a9b7
KERNELBASE.dll
10.0.17134.441
3da51fd0
e06d7363
00111812


\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9A48.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9FF6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA054.tmp.xml
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_XWingAlliance.ex_4de77a50f73a7c703de9ef763a81b58574f649c8_430ecb5f_2d8ea822

0
710f7a68-33cd-4a8a-a7fc-02fe22cf519f
268435456
9a18d84a6e4d164b676782eb98bbd2d6
0

-Exibição xml:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-01-20T20:13:01.938892400Z" />
<EventRecordID>30190</EventRecordID>
<Channel>Application</Channel>
<Computer>Rafao</Computer>
<Security />
</System>
- <EventData>
<Data>1686460533864911574</Data>
<Data>1</Data>
<Data>APPCRASH</Data>
<Data>Não disponível</Data>
<Data>0</Data>
<Data>XWingAlliance.exe</Data>
<Data>2.0.0.2</Data>
<Data>3765a9b7</Data>
<Data>KERNELBASE.dll</Data>
<Data>10.0.17134.441</Data>
<Data>3da51fd0</Data>
<Data>e06d7363</Data>
<Data>00111812</Data>
<Data />
<Data />
<Data>\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9A48.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9FF6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA054.tmp.xml</Data>
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_XWingAlliance.ex_4de77a50f73a7c703de9ef763a81b58574f649c8_430ecb5f_2d8ea822</Data>
<Data />
<Data>0</Data>
<Data>710f7a68-33cd-4a8a-a7fc-02fe22cf519f</Data>
<Data>268435456</Data>
<Data>9a18d84a6e4d164b676782eb98bbd2d6</Data>
<Data>0</Data>
</EventData>
</Event>

-Error
Nome do aplicativo com falha: XWingAlliance.exe, versão: 2.0.0.2, carimbo de data/hora: 0x3765a9b7
Nome do módulo com falha: KERNELBASE.dll, versão: 10.0.17134.441, carimbo de data/hora: 0x3da51fd0
Código de exceção: 0xe06d7363
Deslocamento da falha: 0x00111812
ID do processo com falha: 0x27b8
Hora de início do aplicativo com falha: 0x01d5cfccfd11930c
Caminho do aplicativo com falha: C:\PROGRA~2\LucasArts\X-Wing Alliance\XWingAlliance.exe
Caminho do módulo com falha: C:\WINDOWS\System32\KERNELBASE.dll
ID do Relatório: 710f7a68-33cd-4a8a-a7fc-02fe22cf519f
Nome completo do pacote com falha:
ID do aplicativo relativo ao pacote com falha:

- EventData

XWingAlliance.exe
2.0.0.2
3765a9b7
KERNELBASE.dll
10.0.17134.441
3da51fd0
e06d7363
00111812
27b8
01d5cfccfd11930c
C:\PROGRA~2\LucasArts\X-Wing Alliance\XWingAlliance.exe
C:\WINDOWS\System32\KERNELBASE.dll
710f7a68-33cd-4a8a-a7fc-02fe22cf519f

-Exibição Xml:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-01-20T20:12:57.982973300Z" />
<EventRecordID>30189</EventRecordID>
<Channel>Application</Channel>
<Computer>Rafao</Computer>
<Security />
</System>
- <EventData>
<Data>XWingAlliance.exe</Data>
<Data>2.0.0.2</Data>
<Data>3765a9b7</Data>
<Data>KERNELBASE.dll</Data>
<Data>10.0.17134.441</Data>
<Data>3da51fd0</Data>
<Data>e06d7363</Data>
<Data>00111812</Data>
<Data>27b8</Data>
<Data>01d5cfccfd11930c</Data>
<Data>C:\PROGRA~2\LucasArts\X-Wing Alliance\XWingAlliance.exe</Data>
<Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
<Data>710f7a68-33cd-4a8a-a7fc-02fe22cf519f</Data>
<Data />
<Data />
</EventData>
</Event>

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Mon Jan 20, 2020 9:40 pm
by JeremyaFr
Have you tried to update the ddraw.dll dll to the latest version (there is a link in the Download section) and the hooks.

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Mon Jan 20, 2020 9:56 pm
by rafaabslu
Yes. i do.
Yet is running the xwa_ddraw_d3d11.1.3.7 version and Latest version of hooks, from the latest XwaHooksSetup.
I will try again replace those files and i'll reply here if works.

Thanks.

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Tue Jan 21, 2020 7:35 am
by blue_max
I think this crash may be related to the 32-bit mode hook. Another thing you can try is disabling this hook by renaming "hook_32bpp.dll" to "hook_32bpp.dxx". The graphics will look a bit different; but if it doesn't crash, then we found the problem.

If this is the problem, then the real fix is to use ddraw 1.3.7 with the latest version of the hooks.

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Tue Jan 21, 2020 1:52 pm
by rafaabslu
Hi guys.
I Will rename that file to "hook_32bpp.dxx". But do i need to replace the "xx" to the value corresponding to my directx? For example "hook_32bpp.d11".
Thanks for your help.

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Tue Jan 21, 2020 2:06 pm
by JeremyaFr
You don't need to replace the "xx". The file extension just have to be different of ".dll".

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Tue Jan 21, 2020 3:39 pm
by JeremyaFr
Hello,
Here is an option that you may test, but it requires exe editing.

Code: Select all

At offset 0000DE, replace 0F with 2F.
At offset 000120, replace 000000 with 0EBF21.
This will set the LARGEADDRESSAWARE flag to XWingAlliance.exe.
This indicates that the application can handle addresses larger than 2 gigabytes.

The easiest way to apply the patch is using XwaExePatcher.

Code: Select all

<?xml version="1.0" encoding="utf-8"?>
<ArrayOfPatch>
  <Patch Name="LARGEADDRESSAWARE flag">
    <Item Offset="0000DE" From="0F" To="2F" />
    <Item Offset="000120" From="000000" To="0EBF21" />
  </Patch>
</ArrayOfPatch>

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Wed Jan 22, 2020 7:47 am
by keiranhalcyon7
This wasn't already set in the standard patch/hook set??? :? Seems to me like it would have been a low hanging fruit for any of the crashes chalked up to running out of memory (provided one has enough physical RAM). Is there any downside to allowing the game to access an extra gigabyte (or is it two?) of heap memory?

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Wed Jan 22, 2020 4:43 pm
by JeremyaFr
With the flag set, a 32-bit process can access up to 4 gigabytes.

The flag is part of the PE header. It is evaluated only by the EXEs. It has no meaning for DLLs.

The patch is not part of the hooks. I think that there is no downside to apply the flag.

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Wed Jan 22, 2020 6:51 pm
by keiranhalcyon7
JeremyaFr wrote:
Wed Jan 22, 2020 4:43 pm
With the flag set, a 32-bit process can access up to 4 gigabytes.
Yeah, but I've also read that windows reserves one of those gb for itself, and I can never remember if that gb is in the lower half (so by setting the flag the space available to the game goes from 1 gb to 3, a gain of 2) or the previously-inaccessible upper half (so the space available to the game goes from 2 to 3, a gain of 1).
The flag is part of the PE header. It is evaluated only by the EXEs. It has no meaning for DLLs.
I meant "patch/hook set" as a single unit - the standard set of modifications. Mostly to express surprise that this hasn't been tried yet.

I guess the PE header is read and applied (by the os) before a dll would get a chance to modify it (in the same fashion as the other runtime patches applied by the dlls, I mean), so this could only be done with a static exe patch.

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Wed Jan 22, 2020 7:29 pm
by JeremyaFr
From MSDN:
On 64-bit editions of Windows, 32-bit applications marked with the IMAGE_FILE_LARGE_ADDRESS_AWARE flag have 4 GB of address space available.
There is a difference between 32-bit and 64-bit OSs.

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Thu Jan 23, 2020 12:15 am
by Driftwood
So would this benefit installing generally at this point?

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Thu Jan 23, 2020 4:21 pm
by JeremyaFr
Yes

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Sun Jan 26, 2020 5:13 pm
by rafaabslu
JeremyaFr wrote:
Tue Jan 21, 2020 3:39 pm
Hello,
Here is an option that you may test, but it requires exe editing.

Code: Select all

At offset 0000DE, replace 0F with 2F.
At offset 000120, replace 000000 with 0EBF21.
This will set the LARGEADDRESSAWARE flag to XWingAlliance.exe.
This indicates that the application can handle addresses larger than 2 gigabytes.

The easiest way to apply the patch is using XwaExePatcher.

Code: Select all

<?xml version="1.0" encoding="utf-8"?>
<ArrayOfPatch>
  <Patch Name="LARGEADDRESSAWARE flag">
    <Item Offset="0000DE" From="0F" To="2F" />
    <Item Offset="000120" From="000000" To="0EBF21" />
  </Patch>
</ArrayOfPatch>

Hi guys, thanks for your help. But i dont have any idea how edit de .exe file. I have tried open the .xml file created in the folder of XwaExePatcher-1.0.17. I followed de Readme file.
Then i've opened the .xml file an add a string that you wrote above.

I saved the file and now i dont know what i do with this file?
Is need edit this file for the game to have access for more then 4 Gb of the RAM?

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Sun Jan 26, 2020 5:19 pm
by JeremyaFr
Yes, open patcher.xml with Notepad and add the above patch.

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Sun Jan 26, 2020 6:05 pm
by rafaabslu
I've opened the .xml files. And i added the string that you wrote above. The file looks like this:
patch.jpg
Now i saved the .xml file. And opened in "XwaExePatcher-1.0.17". A a screen with this patch appears. Then i applied "Largeaddressware flag".
After this, i move the new "XwingAlliance.exe" to "X wing alliance" root folder.

I need to do something else?

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Sun Jan 26, 2020 6:34 pm
by JeremyaFr
No

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Sun Jan 26, 2020 7:15 pm
by rafaabslu
Thats works for me. The game runs without crashs after the mission starts.
Thank you very much.

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Sun Jan 26, 2020 7:25 pm
by Darksaber
Jeremy, will these offsets eventually be added to one of the Hooks? Or will I have to add as a *.202 file to patch the exe?

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Sun Jan 26, 2020 7:37 pm
by JeremyaFr
A .202 file will be needed to patch the exe.
This patch can't be set from a dll.

Re: Ver. 1.6 crashs to desktop in any mission after the load screen

Posted: Sun Jan 26, 2020 8:32 pm
by Darksaber
Ok thanks :)