Closed GoogleCodeExporter closed 8 years ago
Original comment by TheFieryScythe@gmail.com
on 22 Jan 2012 at 1:50
Could you attach your OS_Settings.PostProcessing.xml please? The crash is
occuring when validating the external post processing system, but there
shouldn't be anything to validate on a fresh install unless something is wrong
with that xml.
Original comment by TheFieryScythe@gmail.com
on 22 Jan 2012 at 2:20
I realized what must be the issue when you said that. I used previous versions
of OpenSauce, and their settings must have conflicted. I deleted the file, and
this time Halo started up properly. Excellent job on Opensauce, guys, and
thanks for the help.
PS: Good bloom. This is very, well done bloom.
Original comment by Carbatte...@gmail.com
on 22 Jan 2012 at 5:08
Attachments:
So to confirm, you deleted the settings file and it worked? or did you delete
your old settings file then reinstall to get the correct settings file? The
settings file you attached looks fine so if you are crashing when using that
one there is still something wrong.
Original comment by TheFieryScythe@gmail.com
on 22 Jan 2012 at 6:26
I simply deleted the settings file.
Original comment by Carbatte...@gmail.com
on 22 Jan 2012 at 6:42
Unless this exception shows up more we are going to say this is a one-off and
won't fix for now.
Original comment by TheFieryScythe@gmail.com
on 22 Jan 2012 at 8:49
Help, i have the same problem, except i haven't had any previous versions of
OS. Halo exceptions from start up and i don't know why. Please tell me where i
can find my postprocess.xml file so i can post it and get some
advice\assistance.
Original comment by footsmas...@gmail.com
on 22 Jan 2012 at 11:16
C:\Users\{Your Account name}\Documents\My Games\Haloe CE\Opensauce
Thar you go.
Original comment by Carbatte...@gmail.com
on 22 Jan 2012 at 11:25
Okay, here it is.
Original comment by footsmas...@gmail.com
on 22 Jan 2012 at 11:29
Attachments:
When you say you have the same problem, you mean your exception report also has
"Fault offset: 0x0000780a" as well?
Original comment by kornma...@gmail.com
on 22 Jan 2012 at 11:31
You should post the exception info first so that we can determine if it is
actually the same issue or not. See the View Details button on the Send Report
dialog that appears after Halo exceptions.
Original comment by TheFieryScythe@gmail.com
on 22 Jan 2012 at 11:31
"Fault Offset' is 000126f6 sorry, i didn't know what it was :/ I'm a noob.
Original comment by footsmas...@gmail.com
on 22 Jan 2012 at 11:38
[deleted comment]
Please don't write me off because i don't know open source or how to make it
work, i am not bad at modding halo and i really want to get open sauce working.
Original comment by footsmas...@gmail.com
on 23 Jan 2012 at 12:11
Well, using exception details aren't exactly everyday business for halo
modding, so don't feel like we'd write you off. At least you're not asking how
to install HaloCE :o)
These three (example) values are the most important to us when it comes to
exceptions as they help us narrow down the problematic code:
Faulting module name: d3d9.dll, version: 3.0.0.0, time stamp: 0x4f16444a
Exception code: 0xc0000005
Fault offset: 0x0000780a
Your crash is coming from the gbuffer system it appears. Do me a favor, in
OS_Settings.User.xml, set GBuffer's "enabled" attribute to "false" and see if
the same exception occurs. If a different fault offset (and/or faulting module)
is given, please give me those new values.
Original comment by kornma...@gmail.com
on 23 Jan 2012 at 12:21
I opened the file in wordpad and changed where it said <GBuffer enabled="true"
/> to say <GBuffer enabled="false" />. i open halo and it still exceptions.
The exception specs are
Problem Event Name: APPCRASH
Application Name: haloce.exe
Application Version: 1.0.9.620
Application Timestamp: 4ac7faf1
Fault Module Name: d3d9.dll
Fault Module Version: 3.0.0.0
Fault Module Timestamp: 4f16444a
Exception Code: c0000005
Exception Offset: 000126f6
OS Version: 6.1.7601.2.1.0.256.49
Locale ID: 1033
Original comment by footsmas...@gmail.com
on 23 Jan 2012 at 12:25
I had a brief look at this yesterday and its occuring on
pDevice->TestCooperativeLevel() before the GBuffer allocates its D3D resources,
and with this being an access violation it might be getting called with an
invalid/null device pointer.
(This should be logged as a seperate issue btw :) ).
Original comment by TheFieryScythe@gmail.com
on 23 Jan 2012 at 9:00
SOrry, a friend led me here.
Original comment by footsmas...@gmail.com
on 25 Jan 2012 at 2:26
Original issue reported on code.google.com by
Carbatte...@gmail.com
on 22 Jan 2012 at 12:37