ECToo / open-sauce

Automatically exported from code.google.com/p/open-sauce
0 stars 1 forks source link

Open Sauce Effects will not work #70

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
PC SPECS:

HP Pavilion G6-1d63nr

Product Number  A6Z65UA#ABA
Microprocessor  2.4GHz/1.5GHz VISION A6 Technology from AMD with AMD Quad-Core 
A6-3420M Accelerated Processor
Microprocessor Cache    4MB L2 Cache
Memory  8GB DDR3 SDRAM (1 DIMM)
Memory Max  Maximum supported = 8GB
Video Graphics  AMD Radeon HD 6520G Discrete-Class Graphics
Video Memory    Up to 2037MB
Hard Drive  500GB 5400RPM)
Multimedia Drive    SuperMulti DVD burner
Display 15.6-inch diagonal HD BrightView LED-backlit display (1366x768)
Network Card    10/100 Ethernet LAN
Wireless Connectivity   

    802.11b/g/n WLAN 

Sound   

    SRS Premium Sound with Altec Lansing speakers

Keyboard    Full-size keyboard
Pointing Device Touchpad with on/off button
External Ports  

    Digital media card reader for Secure Digital and Multimedia cards
    3 Universal Serial Bus (USB) 2.0
    1 HDMI
    1 VGA (15-pin)
    1 RJ-45 (LAN)
    1 Headphone-out
    1 Microphone-in

Dimensions  14.72" (L)x 9.65" (W) x 1.20" (min H)/1.43" (max H)
Weight  5.22 lbs
Security    

    Kensington MicroSaver lock slot
    Power-on password
    Accepts 3rd party security lock devices

Power   

    65W AC adapter
    6-cell 47WHr lithium-ion battery

What's In The Box   HP Webcam with integrated digital microphone

Software
Operating System:
Genuine Windows 7 Home Premium (64-bit) 

Problem:

Open Sauce starts up fine. I hear the gong sounds whenever I enter the game, 
not sure if that's supposed to be there, but it plays. Then I try to enable 
Motion Blur and I cannot do so. Even with the console commands or editing the 
.XML files.

This has happened to me in the previous version of Open Sauce where none of the 
effects that are supposed to work will even enable. The ONLY effects that I can 
even generate are the HUD Display, Weapon Views and FOV. Nothing else.

Original issue reported on code.google.com by kcdo...@gmail.com on 26 Jan 2013 at 4:06

GoogleCodeExporter commented 9 years ago
There is also another error I am getting. The Xfire In-Game will not show up 
when I try to play. Xfire Won't crash, I just can't get the in-game display to 
work.

Not sure if this is related to my above problem or this one stated here but I 
have included the file Open Sauce spits out when there is an error.

Original comment by kcdo...@gmail.com on 26 Jan 2013 at 4:28

Attachments:

GoogleCodeExporter commented 9 years ago
Your grapgics chipset is integrated and uses shared video memory. It's possible 
that it doesn't support the texture format's required for the GBuffer, which a 
number of post processes rely on. I think you should still get normal mapped 
models in maps that apply them though.

That crash dump shows that you have 2 overlay programs, TeamSpeak and XFire. 
They may be conflicting.

Original comment by TheFieryScythe@gmail.com on 28 Jan 2013 at 12:55

GoogleCodeExporter commented 9 years ago
That's odd, because when I used older versions of Open Sauce, for version
1.08, I was at least able to get motion blur. And I had a lower grade
laptop during that than the one I currently have. So, how would I at least
enable the motion blur? I've tried to edit the .XML file and add it in the
console manually, and neither of those worked out for me.

Original comment by kcdo...@gmail.com on 28 Jan 2013 at 6:13

GoogleCodeExporter commented 9 years ago
You can't use motion blur it don't work at all in 3.1, but try changing the 
setting for it manually and mess with it.

Anyway in response to the xfire problem.
I fixed it, and this is how and the xfire notification boxes are invisible for 
some reason, but I found out it loads, just with no notification.
Simpler Explanation: It shows up, but you can't get the notification, its on 
though, so just do your key combo. 

To fix the crashing problem and Xfire seemingly causing it to freeze, but the 
only way to fix it until you have done these things is disconnect your 
internet. 
Now just follow these steps:

Advanced
First: Have Open Sauce 3.1 installed

Second: go to your my documents folder and find the folder called my games.

Third: Open the my games folder, then open the halo ce folder, inside will be 
saved games and etc., you don't want them, you want to open the OpenSauce 
folder.

Fourth: Once you have opened the OpenSauce folder you will see 3 files and a 
folder called reports.

Fifth: find the OS_Settings.PostProcessing.xml file and delete it.

Sixth: After you have deleted it. Copy and paste the attached file below to the 
OS folder, you must copy and paste to ensure you have a backup of the .xml.

Seventh: Open the OS_Settings.User.xml file and do the following things.

Delete the information between 
These two lines:
<?xml version="1.0" encoding="utf-8"?>
<osYeloSettings engine="Halo1_CE"> 

In other words: delete the green line at the top, but delete nothing after 
these lines:
    <postprocessing shader_directory="" 
            texture_directory="">
AND DON'T DELETE ANYTHING AFTER THOSE LINES!

Lastly: Save the File and continue on.

And also if your Xfire isn't loading ingame when you open halo ce, since I 
found a trick that works every time that happens, and it usually happens every 
patch, I will share it with you.  By the way after I do I will explain the 
simple way to fix OS.

To make Xfire load Xfire ingame when running halo ce follow these steps:

1. go to this folder C:\ProgramData\Xfire it is where xfire_games.ini is 
located unless its set to another drive, in that case just change the C to your 
drive's letter.

2. After open up xfire_games.ini and search for halo custom edition.

3. It will show you the part of the ini that halo ce is coded at so look it 
over then continue.

4. It should look like mine (pasted below) except the LauncherDirKey is what 
you need to change. I have mine set to my path, but the fix is changing the 
path to your path keeping the 
LauncherDirKey=HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ then the Microsoft 
Games\Halo CE\EXE Path follows.

NOTE: Do not keep anything of the game link except for when you get to program 
files, then when you open it, you should see the microsoft games folder, and 
thats what you want, Microsoft Games and Anything after it ending with EXE Path 
like I put.

[4239]
LongName=Halo Custom Edition
ShortName=haloce
LauncherDirKey=HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Halo 
CE\EXE Path
LauncherExe=haloce.exe
LauncherPasswordArgs=-password "%UA_GAME_HOST_PASSWORD%"
LauncherNetworkArgs=-connect %UA_GAME_HOST_NAME%:%UA_GAME_HOST_PORT% 
%UA_LAUNCHER_PASSWORD_ARGS%
Launch=%UA_LAUNCHER_EXE_PATH% %UA_LAUNCHER_EXTRA_ARGS% 
%UA_LAUNCHER_NETWORK_ARGS%
ServerStatusType=HALO
ServerGameName=*
ServerBroadcastPort=2302:10
InGameRenderer=D3D9
InGameFlags=USE_PRESENT|ENABLE_MOUSE|USE_DINPUT_MOUSE

5. Then save the file and close it, if you don't have Notepad++ then you have 
to do save as and keep the name of the file but instead of .txt at the end put 
.ini, and you have to change the text documents only to all files.

6. After doing that, close xfire, then turn it back on after you see it leave 
he task manager's process list.

7. Do not start the game yet as you would to test xig with halo ce without open 
sauce as we are not done with OS.

Simple Way to Fix OS Crashing Halo CE:

1. Just copy and paste what I paste below for the OS_Settings.User.xml file or 
download it below as an attachment.

<?xml version="1.0" encoding="utf-8" ?>
<osYeloSettings engine="Halo1_CE">
    <client>
        <dx9>
            <nVidiaActiveCamouflage basic="true" />
            <GBuffer enabled="true" />
            <PostProcessing>
                <Bloom enabled="true" />
                <MotionBlur enabled="false" amount="0" />
                <FXAA enabled="true" />
                <Internal enabled="true" />
                <External enabled="true" />
            </PostProcessing>
            <Upgrades dynamicTriangles="true" renderModelNodesPatch="true" />
            <ShaderExtension enabled="true">
                <Model>
                    <NormalMap enabled="true" />
                    <DetailNormalMaps enabled="true" />
                    <SpecularMap enabled="true" />
                    <SpecularLighting enabled="true" />
                </Model>
            </ShaderExtension>
        </dx9>
        <Fov value="0.967138" />
        <Hud show="true" scale="true" />
        <networking gsNoUpdateCheck="false">
            <map_download enabled="true" />
        </networking>
        <objects>
            <weaponViews>
                <entry name="Picked up an energy sworder">
                    <position x="-0.01" y="0" z="0" />
                </entry>
            </weaponViews>
            <vehicleViews />
        </objects>
        <version_check day="23" month="0" year="2013">
            <server_list version="0" />
        </version_check>
        <cacheFiles checkForYeloFilesFirst="false" />
    </client>
</osYeloSettings>

Finally: Save the file and your all finished.

If you have done this and problems still exist, it is not OS's fault, or 
Xfire's.

THESE FILES ARE ATTACHED BELOW:
OS_Settings.User It is an .xml file.
OS_Settings.PostProcessing It is an .xml file.
and xfire_games.ini with the fix already put in.

Original comment by LSPRa...@gmail.com on 29 Jan 2013 at 3:38

Attachments:

GoogleCodeExporter commented 9 years ago
Sorry for double posting, but their is no edit button.
Anyway it also solved the freezing problem for me, I always try things before 
asking, so I didn't ask.
But I just noticed someone posted about it, this solves the issue, and for 
connectivity it fixes it, also uninstall the OS Sapien, OS Guerrila, OS Tool, 
and OS IDE.
It helps the lagging stop, so if that's your problem, try this out.

Original comment by LSPRa...@gmail.com on 29 Jan 2013 at 3:44

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Any typing/ grammar errors here, were errors I didn't notice, and probably 
didn't even see, if they even said they were an error.

Original comment by LSPRa...@gmail.com on 29 Jan 2013 at 3:59