OpenSauce Halo CE SDK Update #2 (RC)

[CodeBrain]

Ugh. You didn't remove the file from the project...

Remove the following from the Halo1_CE.rc file:

#define APSTUDIO_READONLY_SYMBOLS
/////////////////////////////////////////////////////////////////////////////
//
// Generated from the TEXTINCLUDE 2 resource.
//
#include "afxres.h"

/////////////////////////////////////////////////////////////////////////////
#undef APSTUDIO_READONLY_SYMBOLS

#if !defined(AFX_RESOURCE_DLL) || defined(AFX_TARG_ENU)
#ifdef _WIN32
LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US
#pragma code_page(1252)
#endif //_WIN32

#ifdef APSTUDIO_INVOKED
/////////////////////////////////////////////////////////////////////////////
//
// TEXTINCLUDE
//

1 TEXTINCLUDE 
BEGIN
    "resource.h\0"
END

2 TEXTINCLUDE 
BEGIN
    "#include ""afxres.h""\r\n"
    "\0"
END

3 TEXTINCLUDE 
BEGIN
    "\r\n"
    "\0"
END

#endif    // APSTUDIO_INVOKED

and optionally (doesn't do anything):

#ifndef APSTUDIO_INVOKED
/////////////////////////////////////////////////////////////////////////////
//
// Generated from the TEXTINCLUDE 3 resource.
//


/////////////////////////////////////////////////////////////////////////////
#endif    // not APSTUDIO_INVOKED

Thanks FireSythe, got it working

?

[Skarma]

MacrosCpp.hpp

#define MACRO_JOIN_TOKEN3(a, b) a##b
#define MACRO_JOIN_TOKEN2(a, b) MACRO_JOIN_TOKEN3(a, b)
// Join two macro arguments, even if the argument is a macro as well
#define MACRO_JOIN_TOKEN(a, b) MACRO_JOIN_TOKEN2(a, b)

LoL whawhawha redundant much
Were you just bored here ? haha

[Aßyll]

Actually it's allegedly needed to join Macros, but what's worse is him having that while using the boost version too:

(from BlamScriptingDefinitions)

#define HS_TYPE(hstype) BOOST_JOIN(Yelo::Enums::_hs_type_,hstype)


(from the BOOST library)

// Helper macro BOOST_JOIN:
// The following piece of macro magic joins the two
// arguments together, even when one of the arguments is
// itself a macro (see 16.3.1 in C++ standard).  The key
// is that macro expansion of macro arguments does not
// occur in BOOST_DO_JOIN2 but does in BOOST_DO_JOIN.
//
#define BOOST_JOIN( X, Y ) BOOST_DO_JOIN( X, Y )
#define BOOST_DO_JOIN( X, Y ) BOOST_DO_JOIN2(X,Y)
#define BOOST_DO_JOIN2( X, Y ) X##Y

not sure why.. maybe he added boost later, after making his own macro to combine macros.

[Skarma]

even when one of the arguments is itself a macro

Very epic. Should have read that over again. If there's one thing about Kornman00 I will never forget, it's that he loves macros and macros inside macros!

I have been looking more into OpenSauce and it's starting to pull together for me. I wasn't aesthetically pleased at first, but it sets in after some time staring at it. Usually have to open 8 files to figure out a line of code, those dang fishy macroronies. hehe

Abyll, I have been thinking about it, using OS for Forge and that other..secret project..
If only I could fix Xfire grabbing an invalid device pointer...ugh

[Kornman00]

Yeah, boost came later, those macros were from the old Project Yellow days. I think COMPILE_ASSERT may also still be lingering in the cpp macro definitions which I've since replaced it with BOOST_STATIC_ASSERT.

Macros can help in areas where I don't want some hidden compiler inititializer thunks and instead just want the compiler itself to initialize the data. However, sometimes the compiler will still amazing do both (even in optimized builds). *sigh*. That's not the only reason I use them but they really are a great tool when used properly (not saying I always use them properly though heh).

Xfire should just look at being more friendly with it's interfacing.

[the1]

did kornman just do a
"bad Xfire... you shouldn't go doing things like that!" ???
lol
meh Xfire sucks anyway XD

[Helixv3]

Question,
and sorry if im bumping i dont mean to but i would enjoy knowing this
Does this DLL work for FV(Full Version)? Or is it ONLY Custom Edition?

[Dwood]

Question,
and sorry if im bumping i dont mean to but i would enjoy knowing this
Does this DLL work for FV(Full Version)? Or is it ONLY Custom Edition?

One thing to note is that both versions are full. And no, it is not. (Only works in Halo CE)

[ShadowSpartan]

Question,
and sorry if im bumping i dont mean to but i would enjoy knowing this
Does this DLL work for FV(Full Version)? Or is it ONLY Custom Edition?

Open Sauce is only compatible with the Custom Edition version of Halo PC. On another note, is this who I think it is? You can at least be a little less obvious e3po.

[Helixv3]

Open Sauce is only compatible with the Custom Edition version of Halo PC. On another note, is this who I think it is? You can at least be a little less obvious e3po.

Im not e3po...

Previous Names
Avensys
Genesis
Triple Helix
Helix

=] If you know me by one of those names then yes it's me.