Replacing my settings with the default settings didn't work. Which MS installer are you talking about?
As for the blur, yeah, it flashes around the screen weirdly. pp_unload did work at removing the blur but once I used pp_load it returned. Also, even with pp_unload those blue objects still didn't go away (see below) I've reported these problems to the google code page.

msxmlenu.msi (should be somewhere within your HCE folder, as well as on your HPC disk)

Also, you're talking about the triangles coming from your hands? they always go to the same point in the map? your graphics card is messing up on you, either starting to wear down, or drivers messing with it. This only happens with OS though? (They can come from random objects each load, so don't automatically blame OS until you load the map a few times with it enabled and disabled)

I'm pretty sure it's from the BSP itself.
I have this problem on the same map.
Also on this BSP: http://hce.halomaps.org/index.cfm?fid=5344

Maybe it's the graphics card but I dunno.

Hello, i have a problem, OS Sapien crash with all scenario O_O

The debug >

sapien pc 01.00.00.0609 ----------------------------------------------
reference function: _write_to_error_file
reference address: 401b13

Couldn't read map file './sapienbeta.map'
CreateDevice succeeded with refresh rate = 0
Sound card doesn't meet minimum hardware requirements. Disabling hardware option.
Increasing sound decompression buffer size to 1048576 bytes

tag reference name too large (this tag is corrupted).

failed to load shader_model tag 'h3\vehicles\ghost\shaders\ghost'
failed to load gbxmodel tag 'h3\vehicles\ghost\ghost'
failed to load vehicle tag 'vehicles\ghost\ghost_mp'
failed to load scenario tag 'levels\test\pass_bridge\pass_bridge'
need to get the following tags:

game_load() failed.

WTF ?!

So, its a tag name that is a space or something not normally visible, and that file is corrupt. Anyways, as you can see the failing to load hierarchy, the main issue is in the shader_model, "H3\vehicles\ghost\shaders\ghost.shader_model", open that up in guerilla, look around for any tag fields that seem off (that have a space, tab, or something strange in them instead of a path), or recreate that tag.

I verified, All are correct T_T, look : http://img703.imageshack.us/img703/271/shader.png

---------------- Edit ----------------

Nothing, it Works :D TY ! :)

----------Edit----------

Hello, i have a another problem
I open a scenario with Os Sapien, When it's open i can view my map 3 sec this depend, then Os sapien crash !

I opened Debug.txt and nothing is written -_-

Thanks -_-
Edited by benjimod on Apr 27, 2012 at 08:37 AM

I'm having a problem with OS_Sapien since my game view is black
This happened when I had sapien and a multicore so I used E3pO's sapien.

How can I get this to work ? I assume some CMT members have multi cores processors

Are you sure the camera is inside your map, and that the map has lightmaps and\or sky? And if you believe it to be a problem with cores, open the task manager, process tab, find os_sapien, right click, set affinity. And there is actually very few people who sapien dislikes their multi-cores, I have never had any issue with it on either my laptop (Dual) or desktop (Quad) without even having to set affinities.



Also, other person who edited his post many times. <user>\documents\my games\halo ce\opensauce\reports\debug.txt

I've already tried to change the affinity... Maybe I have to restart the computer.
Also I tried with the tutorial map, if the camera was outside the BSP i'd just see the sky...

Well, you say this other sapien works for you. Try using the opensauceIDE, cheape applier, pick that hacked sapien, and see if it is able to make a OS version of it (or whether it completely fails because of some overlapping address change)

E3pO's HEK needs to hook somehow in the game and it gives me an error when trying to start it.


and sapien crashes. I will try restarting PC when I can

Hello,
In the Debug.txt it's written :

04.27.12 14:27:42 EAX: 0xFFFFFFFE
04.27.12 14:27:42 EBX: 0x000BCF01
04.27.12 14:27:42 ECX: 0x0012F340
04.27.12 14:27:42 EDX: 0x000002CC
04.27.12 14:27:42 EDI: 0x0012F340
04.27.12 14:27:42 ESI: 0x00000000
04.27.12 14:27:42 EBP: 0x0012F218
04.27.12 14:27:42 ESP: 0x0012F208
04.27.12 14:27:42 EIP: 0x77C064F4, C3 8D A4 24 ?????
04.27.12 14:27:42 EXCEPTION halt in \halopc\haloce\source\cseries\profile.c,#442: parent_timesection->self_msec >= child_timesection->elapsed_msec

Have you a solution ?

Thanks

Run on one core? (set affinity to 1.)

yeah he needs to set the os_sapien to run on 1 cpu just.
it's just the same error as what you would get with the original sapien.exe.

Spartan314
Ally

THANKS

As requested by Kirby, my card brand is:

Nvidia.

It's the 9800GT to be precise. It runs OS fine due to OS not using very complex shaders.
However, if more complex shaders such as CSAA or sharpening filters are implemented, my card may not be able to handle them.

However, I would assume this card runs shaders more efficiently than ATI cards of it's time as it is designed for high settings of anistropic filtering and other such efficient, simplish shaders.

before anyone asks, we are doing a study on how different cards react with OS, to see if certain brands are actually running better (since TM has a stronger ATI card than my PC, and yet mine runs OS better)

Desktop use to have a Nvidia GeForce 9800 GT (before the card died) could run with everything turned on, as well as post processing that was built to fight other post processing lol (I miss that card..)

Desktop (Current) Nvidia GeForce 8400GS, runs with the default options perfectly fine, 1280x720 windowed. It will slow down to just over half speed if I turn on motion blur. (1GB video memory)

Laptop Nvidia GeForce 8200M G, runs fine with default options, basically same as my current desktop card when motion blur, etc. (512MB video memory)

Post your card type and name, and if you have some graphics benchmarking stuff, you can post that too so we can compare whether it should be stronger or not.

Even though this issue was posted two months ago, IDC!

Just run the game w/o OS, and that triangulation problem wont be there.

Nick, I thought you were a supporter of OS? o.O

Anyway, Kornman probably solved that issue a long time ago on the google code page.

Intel(R) G33/G31 Express Chipset Family Desktop,Runs Fine in mid High configs 1280 x 1024 True Color (60 Hz) though Unable to Run os
other Computer doesnt work anymore and i don't know which graphic driver it used

Will run a test on my laptop and desktop this coming weekend.

My ATI Radeon Xpress could handle a50.yelo.Not the best frame rate(less than 30) but tolerable.
Yeah,I'm sure you guys will tell me to upgrade or that it sucks.
I can run Halo 2 Vista,at about 25 FPS.

Why are some people so rude? Would've taken much less time to simply get straight to the point.

Hello can someon tell me how to control OS like visr and the screen enhancments
thank you for your help
Edited by john117 on Jul 5, 2012 at 03:12 AM

I'm having a similar error on the map Ambush. I'll try to get a screenshot of it later. (When I can figure out how, since print screen ins't working.) Also, when I play online the HUD will randomly change from stranded- to wide-screen, even though in the F7 menu it is set to scale.
System specs are Windows 7 64bit Ultimate, AMD Phenom II X6, AMD Radeon HD 6700 (1gb dedicated DDR5 RAM), 8 gigabytes DDR3 RAM.

Didn't some old maps have some kind of motion blur hack in them? Could that be what's messing up OS motion blur??

As for text, I did the MSI file thing and the chatlog appears now, but when I'm typing the text doesn't appear on the bottom.

hi kirby

the blur is being worked on (it was just responded to on the issues page like 2 days ago, after all of these months lol) The blur issue existed back in the OS 2.5 betas, it was linked to custom bipeds (and according to the issues page, it still is)

At one point, I believe I had pinpointed the HUD resolution issue, but that was to long ago; I don't even notice when my HUD changes scale now lol. You just get use to it eventually.


Hi. Haven't seen you in years, I don't even remember what we use to talk about. Whats up?

Ah okay; will that fix the tearing as well?



Yeah I usually only notice it during the death screen.


Yeah I moved to the good ole Bible Belt (a fate arguably worse than death) and only recently got "tolerable" internet speeds. I can hardly remember what we did either. I remember Zelda, gravity guns, jackal shields and... hogdriver(?).

God...hogdriver...

I haven't seen an Issue logged on google code about this HUD scaling bug (unless i've missed it). If you have a solid method for reproducing the problem add an Issue with the details and i'll get around to looking in to it at some point.

Anything new in the next version?. is there even going to be a next version.

There is a new version with lots of cool stuff. For MP as well as SP.

CV was working on lots of animation things, but his external hard drive fell and broke, so it's all been lost, and he's been to busy to recreate his works. It is something CMT wants though, we'd love to be able to have a FP sprint animation.

Lesson learned, put externals on the floor.

It's why I don't even stand up new game consoles, they're made too cheaply.

Note: this post was adapted from the posts made at Modacity and Halomods. This place doesn't have spoiler tags, so beware the longpost...

Today, we here at the (virtual) offices of Kornner Studios are happy to announce that version 3.1 of OpenSauce is coming soon! How soon? Why, none other than next month: January!

Unlike previous releases of the v3.0.x brand, this release introduces a lot of new features and improvements instead of -just- addressing bugs/issues. Hence why that '0' after the period ranked up to a '1'.

For OS 3.1 both FireScythe and I have some really juicy goodies in store for you. But we're not the only ones contributing to this next release of OS. ChokingVictim is a special guest this time around with some more gameplay enhancing features for you map makers to play with! He has contributed work to OS before (e.g., he helped us implement the unit-infections system) but has become more active on the project for the past few months. We're hoping to keep him with us for the foreseeable future.

However, it being near the holidays and all he didn't really have the time to get all his :words: and video written up and made before this announcement was posted. So we're going to follow up later on with details directly from him on what you can expect in 3.1 and (hopefully) beyond. For today, you'll have to make do with what FireScythe and I. Deal with it.

Speaking of FireScythe, let's start with him first. He took the time to write up this longpost about this small feature he made, so why not. Wait, did I say small?



FS, if the community had a voice, I think it would be saying "music to our collective-ears". But it doesn't. It's a voiceless being. Well, until you make something that doesn't play well with Xfire. Then it grows a mouth and starts jibber jabbering and raising a bunch of stink.

But guess what?

OS 3.1 no longer fights with Xfire. In fact, they're seeing other people now. OS now infiltrates the game code via pretending to be dinput8.dll, instead of d3d9.dll. That means all you Xfire lovers who have never heard of the superior software known as Steam will be able to play Halo, use OS, and chat via Xfire's ingame overlay all at the same time. Of course, the Steam lovers have been able to do this for some time now. Neener-neener.


On top of various other fixes, we've also got some more user-oriented features coming in OS 3.1:
* You know that 'checking for updates...' message that comes up every time you try to do something MP related? Well now there's an xml setting to make the game think it already ran this check, saving you an additional second or two.
* We now have a command line parameter for specifying what version of the game you want to display a server list for. By default, if a value isn't given via this parameter, we get the ENTIRE server list from all the versions of Custom Edition. Or you can specify "disable" and the server list will behave as normal, populating the server list with 1.09 only servers.
* We've added new xml setting for forcing OS to use .yelo files first when searching for .map files (off by default). So with this feature on, OS will pick a10.yelo first instead of a10.map, assuming both files are present.
* There's now a command line parameter for turning off all OS-based gfx additions/upgrades.
* The installer has been improved. E.g. it installs the VC++9 runtime, allows the user to -not- install OpenSauceIDE, etc
* Mini-dump support has been added to haloce/dedi/tool/sapien (guerilla is the oddman out) to aid in any future debugging efforts when the EXEs crash


Of course, average joe users aren't our only target demographic. Map makers are in for some treats too:
* We've increased the max grenade types to 4. This works in multiplayer as well and there are fields in the scenario's starting profiles to specify the grenade counts for the 2 new types. In order to keep this feature working in MP without having to wait on new networking features, we couldn't go any higher than 4. Some people were already catching on to this new feature
* We've added a script function for playing .bik videos (need to be in the same location as the game's existing .bik videos)
* We've added a system for displaying UI widgets via script code. You execute a function and then it displays a ui widget definition specified in the project_yellow/globals tag.
* We've added a 'runtime vectors' system in a similar fashion as the 'runtime integers' system. This system allows you to perform vector operations in script code. CMT was able to use this setup to essentially perfect vehicle boosting. You can check out teh_lag's prototype video of this here
* We've added script functions to perform bit operations (AND, OR, etc) and converting hex string to an integer
* We've increased the maximum number of particles that can exist at any given time. We're still playing with these settings, so the exact upgrade amount isn't set in stone yet.
* We've increased the maximum buffer size for model vertex and index data that Tool uses when building a cache file.
* The project_yellow_globals tag features a new flag for forcing the game to use 'stun jumping penalty' instead of 'turning penalty' in the engine's biped jump code. We're considering this a "patch" as I'm pretty sure this wasn't the intended behavior in the stock engine.
* We patched the weapon tag's magazine's magazine-objects block so that it will no longer crash when you try to add more than 2 elements. Uses the equipment field for the block name now too. This is a "patch" for a bug in the stock HEK. If you try to open the weapon tag in the stock Guerilla with more than 2 elements in the magazine-objects block, it will crash.

I want to make two special notes here that are aimed at map makers:
* Since ChokingVictim has become a lot more active and has presented quite a number of potential new features that we'll be adding later on, we're giving him his own tag to use to implement these new features: project_yellow_globals_cv. Why this matters to you is because we will be moving the unit-infection definitions *to* this tag -from- the project_yellow_globals tag. We're not aware of any maps that have been released that make use of the unit-infections system yet, so in order to Keep It Clean, we're just going to add this system's tag fields to his new tag group. If there have been any final maps that have been released which use the unit-infections system, speak now or forever hold your peace (and not have working unit-infections in 3.1)
* The team index offset for MP teams for the GBuffer has been changed. MP teams now start at 10, not 9 (game_teams come first, tho technically the last few are 'unused' by Halo proper). This is a breaking fix, but I'm not aware of any major MP map releases that used this specific part of postprocessing.


Developers have things to look forward to as well (well, there's no looking forward as most of this is already in the code already):
* The codebase has been reworked to match that of the actual game engine's.
* There are now only two shared source folders (aside from 3rd party libs), "blamlib" and "YeloLib". These help to draw cleaner lines where there is data/code added/injected by OS, or where there is code that is specific to OS.
* The CheApe compiler has been modified to support faux tag-structs. So if you have tag definitions that have repeated fields (eg, in the case of the engine's shader and hud interface tags), you can use these to essentially have the compiler cut&paste the field definitions for that tag-struct.
* We've been working on a string_id system that is very much like what is used in the games following Halo1. A first-class citizen StringId field type has been added to the CheApe parser so it will handle the underlying hacks that we made to get such a system working in Halo1. When a cache is being built, the system will also take tag_string fields and create ids for their values, then mapping the address of those fields to those generated ids. So existing tag_string fields can be used in code that works with string_ids.


That's all we're wanting to talk about today. Again, stay tuned for future updates involving what ChokingVictim has been working on. There may be even more features that make it into 3.1 from now until release, but we don't want to comment on them until we know their fate for sure.
Edited by kornman00 on Dec 17, 2012 at 12:59 PM

When will better normal map usage be applied to bsps, like waffles said long times ago? :o
Not even sure if he's talking 'bout the truth or not, so why not ask you guys?

It's a much harder task to implement such a system than it sounds. While it's "on the table" for development it's not something that can just be *done* without a very large amount of work. They've been focusing on other, more immediately useful features like the automatic map downloader and adding the new grenade slots.
Edited by teh lag on Dec 15, 2012 at 08:41 PM