Says That it Has Encountered a Segmentation Fault, I am Using Halo CE Pc

[Rockship2910]

When It tried to load the game using the new maps that contained the bumpmapping, it said it encountered a segmentation fault and I was wondering if there was a way to get it to work, like making the game not recognize segmentation faults when playing/running.

[pR0Ps]

Can you upload the specific map that caused the issue here so someone can attempt to reproduce it?

[Rockship2910]

Not Sure just put all the maps in at once

[PseudoProxen]

What are the map names and where did you download them?

[Rockship2910]

But was in the PC version of halo, I'm guessing that that could be an issue

[Rockship2910]

The newest chimera version

[PseudoProxen]

Ok so few things we need to know.

Version: PC (Check) Maps: Need to know exactly download location so we can troubleshoot Chimera: Latest (Check) Chimera Scripts: Need to know which ones if any installed Other addons: Mostly need to know this as well to troubleshoot

[mmillar-bolis]

System

OS: Windows 10 x64 (21H2) CPU: Intel Core i7-8700T @ 2.4GHz RAM: 16.0GB GPU: Nvidia GeForce RTX 2060 Game Ver: Custom Edition 1.00.10.0621 (LAA patch, e.g.: 0x2F at offset 0x136 in haloce.exe) Chimera Ver: 1.0.0.r1001.b575031 (2024-05-13) dgVoodoo2 Ver: 2.82.5 (2024-04-16) CEnshine Ver: 1.0.0 (2022-07-16) Map Set: Halo CE Refined 3.0.0rc2 (2022-05-21)

(No Chimera scripts are present in this setup.)

EDIT: I forgot to mention that I replaced msvcr71.dll with the final version of the VC 2003 runtime obtained from the .NET 1.1 SDK, ver. 7.10.7031.4 (Custom Edition ships with 7.10.3052.4). I do not believe that it should make any difference, but I thought it worth mentioning.

---

Chimera Settings

CLI Args:

-path %Absolute_Path_to_Writable_Custom_Directory%\Profile

chimera.ini Changes:

[halo]
intro_videos=1
main_menu_music=1
multiple_instances=0

[error_handling]
show_segmentation_fault=0

[video_mode]
windowed=1
borderless=1

[server_list]
auto_query=0
enable_map_memory_buffer=1

[controller]
enabled=1

<<using controller_config/windows/xbox_360.txt configuration>>

Unmentioned settings are at their supplied defaults.

preferences.txt Entries:

chimera_aim_assist true
chimera_uncap_cinematic true
chimera_widescreen_fix 2
chimera_throttle_fps 60
chimera_auto_uncrouch false

---

dgVoodoo2 Settings

dgVoodoo.conf Changes:

[Glide]
3DfxWatermark = false

[DirectX]
dgVoodooWatermark = false

Unmentioned settings are at their supplied defaults.

---

Issue

Description: Starting up the program and resuming campaign from a checkpoint, then pressing Esc to bring up the menu, results in a Segmentation Fault. Waiting for 10 seconds, after having entered gameplay, will generally avoid the issue.

One simple checkpoint that reliably produces the error condition is on the level Pillar of Autumn: begin a new game from the level select menu, then proceed through gameplay as normal until reaching the second boarding craft (containing two overshields). The hallway outside this second boarding craft features a stationary shield. Continue passed the shield and trigger a checkpoint just before ducking under the blast door (before triggering the event where covenant descend on two pistol-equipped crew members at the end of the hall). Finally, quit and relaunch the program. This particular checkpoint reliably triggers a Segmentation Fault when continuing the game and immediately pressing Esc to open the menu.

Attempts to Resolve: Using a default chimera.ini, removing dgVoodoo2, removing CEnshine by restoring a default EffectCollection_ps_2_0.enc, then starting a new game, playing up to the aforementioned checkpoint, quitting, relaunching the program, and resuming from the checkpoint, appears to resolve the issue in 3/4 brand new gamesaves (e.g. starting Pillar of Autumn from the level select menu). In following this method, only once was a checkpoint produced that resulted in a Segmentation Fault upon starting the program, resuming, and immediately pressing Esc.

Reintroducing dgVoodoo2 (and continuing to use a default chimera.ini) appears to have no negative effect on the chance of incurring a Segmentation Fault.

Reintroducing CEnshine (and using dgVoodoo2 with a default chimera.ini, as well as starting a new game from the level select screen to account for the difference in shaders which may affect the checkpoint save) appears to increase the chances of encountering a Segmentation Fault to a near certainty. However, waiting 10 seconds, as mentioned above, appears to work around the issue once again.

I don't know if this is exactly the same as what @Rockship2910 has encountered, but it sounds at least superficially similar to what I am experiencing.

If I can explain anything better, please don't hesitate to ask.