Next Generation Emulation banner

1 - 8 of 8 Posts

·
Leading the way.
Joined
·
836 Posts
Discussion Starter #1
I'm sure that to caustik or kingofc, or anyone who knows what they're doing, this is a rediculous question.

Does code really need to be written for each individual xdk? There can't be a kind of internal wrapper to translate the individual xdk commands into something generalized? I'm sorry if I'm offending you with such a rediculous question, but why must everything be rewritten for every version? It must be incredibly painstaking and frustrating.
 

·
Registered
Joined
·
350 Posts
You have to remeber, some of the features are added/removed/dramaticly changed.
You dont have to write individual source code for every XDK, you only have to add code for the changed features.
And if i am corrrect some of the "System Calls" are diffrent also.
 

·
Leading the way.
Joined
·
836 Posts
Discussion Starter #3
Hmmmm... How dramatically different is the Halo 2 XDK compared to what caustik has done so far? Maybe we can work something out.

And how many XDK's are there?
 

·
Registered
Joined
·
350 Posts
The new xdk, 5849 is only like 10% supported.
EDIT: Halo 2 is made w/ 5849.

As soon as i uhh... "obtain" a copy of XDK5849 I'll look into it.
 

·
Leading the way.
Joined
·
836 Posts
Discussion Starter #5
That would be cool. I'm no programmer, but I'll help any way I can.
 

·
Premium Member
Joined
·
6,071 Posts
Hey, is there any way to substitute for the KeSetTimer in certain XDKs (ie 3936,4400,4721 etc)? There are more, but I forgot the rest. :(
 

·
Premium Member
Joined
·
6,071 Posts
1 - 8 of 8 Posts
Top