VOGONS


First post, by lowenz

User metadata
Rank Oldbie
Rank
Oldbie

Intel (A380+lastest drivers suite on Win24H2)+D3D12 -> crash in Halo Custom Edition 1.10 + CEnshine + Chimera
No problem in D3D11.....

Reply 1 of 11, by Dege

User metadata
Rank l33t
Rank
l33t
lowenz wrote on 2024-12-16, 00:29:

Intel (A380+lastest drivers suite on Win24H2)+D3D12 -> crash in Halo Custom Edition 1.10 + CEnshine + Chimera
No problem in D3D11.....

The problem is, I only have Halo CE (whatever version) of all those... 😀
Could you give me a full log with maximum trace level == 2? Also, do you happen to have the DX debug layer installed?

Reply 2 of 11, by lowenz

User metadata
Rank Oldbie
Rank
Oldbie

*CEnshine are just XBox-correct shaders package: https://github.com/Sledmine/censhine (just backup EffectCollection_ps_2_0.enc): they have some problems with Intel d3d9 driver so you must use dgVoodoo2 or DXVK to avoid those issues
*Chimera is an engine-level mod: https://github.com/SnowyMouse/chimera (just backup strings.dll)

Reply 3 of 11, by p0werb1t

User metadata
Rank Newbie
Rank
Newbie
Dege wrote on 2024-12-18, 17:43:
Ok, here is a little update, it should fix it: […]
Show full quote
zaqzaq0802 wrote on 2024-12-16, 16:46:
Hello! I received the ddraw patch for O2Jam previously and it’s been working great. Thank you very much. […]
Show full quote

Hello!
I received the ddraw patch for O2Jam previously and it’s been working great. Thank you very much.

I’m reporting a bug found in WIP96.1. This issue occurs when the OutputAPI is set to d3d12_fl12_0, but does not appear when using d3d11_fl11_0.

Sample video: https://youtu.be/BXmmlIVGG5A
game : https://app.box.com/s/7qospa1ckrhge1lt1czcv145mutzapf2

This problem does not occur in WIP96 or in version 2.83.2.
For reference, I’m running Windows 11 23H2 on a Radeon RX 7900XTX.

Ok, here is a little update, it should fix it:

=========================
WIP96.2:
=========================

- Fixing a D3D12 surface readback bug (AMD) (O2Jam, ...)
- Changing the frontend D3D8/9 impl of texture palettes to a better one
- Async palette update on UMA architectures too (bug) (Rallisport Challenge)

http://dege.fw.hu/temp/dgVoodooWIP96_2.zip
http://dege.fw.hu/temp/dgVoodooWIP96_2_dbg.zip

WIP96.2 gives Microsoft Defender Antivirus alert "Program:Win32/Wacapew.C!ml" on MS/x86/D3DImm.dll.
WIP96.1 is ok.

Halo CE with Chimera, Refined and Censhine is great!

Reply 5 of 11, by lowenz

User metadata
Rank Oldbie
Rank
Oldbie

Intel (A380+lastest drivers suite on Win24H2)+D3D12 -> crash in Halo Custom Edition 1.10 + CEnshine + Chimera
No problem in D3D11.....

+

lowenz wrote on 2024-12-18, 20:35:

*CEnshine are just XBox-correct shaders package: https://github.com/Sledmine/censhine (just backup EffectCollection_ps_2_0.enc): they have some problems with Intel d3d9 driver so you must use dgVoodoo2 or DXVK to avoid those issues
*Chimera is an engine-level mod: https://github.com/SnowyMouse/chimera (just backup strings.dll)

Loading a savegame I got a segmentation fault error and this is the debugview trace, with 2.84:

Untitled.jpg

Menu (it's a map too) is working.

Reply 6 of 11, by Dege

User metadata
Rank l33t
Rank
l33t

Halo Custom Edition 1.0.10 + Chimera + CEShine is pure multiplayer for me. No campaign, save/load.

(And for some reason, with Chimera installed it silently crashes right at startup... If I run it from the debugger then works. ??)

Reply 7 of 11, by lowenz

User metadata
Rank Oldbie
Rank
Oldbie

Pure multiplayer because you need Refined 😁 ( https://www.proxeninc.net/Halo/Refined/ )

https://www.proxeninc.net/Halo/Refined/V4Beta … n_en_v4beta2.7z

Just unpack in "maps" and overwrite.
The segmentation fault error for me is only in D3D12 and when I load a map. In D3D11 the game is utterly beautiful (and with MSAA forcing is just perfection)

haloce-2024-12-28-16-24-59-124.jpg

Reply 8 of 11, by Dege

User metadata
Rank l33t
Rank
l33t

I tried it, but no idea... no crash for me.
I tried entering a map by loading it as a savegame, load a map by creating a new LAN game, etc.
All with NV, AMD, Intel UHD but it just worked.
Also, there was no error or warning with the DX12 dbg layer enabled.

Could you try it without any additional dx12 layers? Maybe.