Open Sauce Ideas thread

[ShadowSpartan]

The post I quoted from in the Manual said that, by default, it is DISABLED, not unimplemented. Unimplemented, in most cases, means not even structured to function.

I said that it was not implemented....so what is your point? I know that it is not implemented, but you acted like it was in your previous post when you said you didn't "trust" OS as a test environment. Just don't touch anything networking related in OS, and it is a fine testing environment.

and you didn't bother to even research the SDK, did you?

See below.

You never saw it coming because you didn't test a build you comiled yourself. You relied on the stock DLL file provided on the release thread's first page.

Shut the fuck up. You have no fucking idea what you are talking about. I may not have messed with OS2, but I have with the original OS release, and I have compiled numerous of my own OS dll's. I fail to see your point with that statement. You sure do love jumping to conclusions without any evidence to back it up don't you?

beore you start spewing diarrheic nonsense, I'd advize you to make sure that the conditions for your statements are fully met on all levels and from all angles. That means, do your so-called "homework" before you post another negative spiel such as this.

I did do my "homework", I said it was not implemented. You were the one who was acting like the networking code was implemented by default, not me.

Yea ShadowSpartan, Just because you can't do ANYTHING!!!!

Lol, really now? I can't do anything? You have no idea what I have done in terms of Halo modding, so do not act like you do. A lot of my work is private, and exclusive to the team it was created for.

[formlesstree4]

This argument is getting us nowhere. Let's just wait until we have some more information from either Kornman about OS, or skarma if he's reading this about reversing some of the netcode [possibly]. Internal corruption was a benefactor to Rome falling, let's not become an example and look like idiots arguing with ourselves, which will only get us nowhere.

[Rambo]

Why is this even an argument when we can all just wait for Skarma and worry about more apparent problems?

I'm terribly sorry for making this seem like an argument and thereby humbly apologize for seeming as such.

Chaos and I care because we have a yearning desire to understand the nature of this beast, not because we want to meddle around is business that may not be our business. That is why we persue this so ambiguously.

[skywalker71291]

Agreed but Spartan needs to clean up his act. And stop doing all this trolling.

[teh lag]

ugh all of you shut up

[Rambo]

OK, here's what I want to do. I intend to prove that this is a network related issue having to do with 1.04's security fixes.

I will work with Chaos on getting the 1.08 build working with network code updates. Then I'll take a video of me opening a door on the client side in Blood Creek and the client crashing the connection as a result. When this happens, and I know it will because Kornman00's manual for the current public build says it will, I'll present the data here for all to see.

EDIT: We have a problem. When compiling the DLL and placing it into the root CE folder, when we run Halo CE, the BSP does not show. In fact, the only video we have is the HUD. Any recommendations on how to fix this? The only change we made to the codebase was removing version check in an attempt to get it to accept <1.08 builds. Could this be what causes the video to not work properly?

All I can think of is that the DLL is "confused" as to what program to hook the wrapper routines into, so it bugs out.

[p0lar_bear]

ugh all of you shut up

This.

Seriously Shadow, chill out man. Your posts make me think you're going to give yourself an ulcer.

And skywalker, for the love of what's good, please don't jump into the community making blind assumptions about our established members.

[Dwood]

EDIT: We have a problem. When compiling the DLL and placing it into the root CE folder, when we run Halo CE, the BSP does not show. In fact, the only video we have is the HUD. Any recommendations on how to fix this? The only change we made to the codebase was removing version check in an attempt to get it to accept <1.08 builds. Could this be what causes the video to not work properly?

All I can think of is that the DLL is "confused" as to what program to hook the wrapper routines into, so it bugs out.

Use 1.08 ? Get Omega's Version changer, set to 1.09 or get an alternate ui that removes autoupdate. Then test. (After replacing the code that checks for version #)

You're better off making Halo think it's v. 1.09 than making it not check versions via OpenSauce.

[justin108]

Use 1.08 ? Get Omega's Version changer, set to 1.09 or get an alternate ui that removes autoupdate. Then test. (After replacing the code that checks for version #)

You're better off making Halo think it's v. 1.09 than making it not check versions via OpenSauce.

I made halo think it is 1.09, but it will not join the majority of 1.09ce servers. To do so I simply hexed Omegas files, I replaced the 1.00ce version string with 1.09ce in both dlls; now i am able to change to 1.09ce no problem, however it only joins certain servers.

I see you mentioning code that checks for a version number, I am half retarded, what are you referring to?

if anyone could help this old moron, I would appreciate it.

[Rambo]

Use 1.08 ? Get Omega's Version changer, set to 1.09 or get an alternate ui that removes autoupdate. Then test. (After replacing the code that checks for version #)

You're better off making Halo think it's v. 1.09 than making it not check versions via OpenSauce.

Nonono, listen. I manually updated to v1.08 with a hotfix and blocked the updates with my own UI (download it here). From there, I was able to run the Open Sauce no problem.

What I was saying is we removed the version check on Open Sauce itself so that it wouldn't come up with an error dialog while running on older versions of Halo CE. In doing so, we must have broken something else. Sad-face...