Jump to content

Recommended Posts

Posted

Wow, this is the best Kof scince 98, All the characters are animated perfectly and the pace of the game is so exciting, the 3 on 3 thing works great and the specials are all very easy and smooth to preform unlike some of the other versions, the backgrounds are a little dull thats all. Kof 2002 was one of the worst kof games I had ever played it had no soul and very ugly BG. I was losing hope, but this delivered. Thanks guys for helping me to get this working. :P

  • Replies 705
  • Created
  • Last Reply

Top Posters In This Topic

Posted

i think kof2002 is one of the best kof's series.. i like the max mode system..but for kof2003 i dontl ike the leader system..and the graphics aren't that great either.. especialy on the menu screeen..haha

Posted (edited)
Anyone know if their are cheats out yet. I can't beat the game with the Korea team. I beat it with Garou, Benimaru, The Guardian or whatever it's called, and Hero. But I can't beat the damn game with the Korea team!

I can beat the game with Korea team with difficulty 8 (expert mode). I just beat the game today. :P

 

Use good use of Chang, he is really good if you can use him well. A good move with him: Keep pressing A, he will rapidly attack a person with his hand then suddenly he will spin the iron ball.

 

Any questions about Korea team, ask. I always use Korea team. :P

Edited by Genesis
Posted

Ash is a total beast against the computer once you learn to abuse his double projectile.

 

So is malin if you learn some nice complex combos with her jumping HK

Posted

imo, kof 2003 is a pretty good game, and would probably be my favourite neo geo rom is the graphics were better. they should of used the graphic style of garou (bigger character sprites, fluid animation etc..).

 

the gameplay changes like the tag system is pretty good though :P

Posted

cosmic_lord: how did you get it to load at all? i've been using the loader from epic-center and dat editing doesn't do anything. i'd like to spend a few minutes tinkering with it... but the rom won't show on the load dialog. suggestions?

 

you're right. the website says that you'd have 6 pieces to play with, after chucking one redundant piece and putting p2_4 as the header. that's 6! (6*5*4*3*2*1) = 720 distinct combinations. it's also possible that they split the rom into smaller sizes. if they split at 500k, you would have 16 pieces. throw two redundant pieces away and make the other two the header, you're left with 12 pieces to work with. 12! = 4.79x10^8 permutations. (someone check my math) man, i'm not gonna sit here and try to piece the roms together half a billion times. hmm... 17 minutes load time x half a billion... :P

 

but if the author of the mame rom can make it work (with it all cut up like that), maybe exact order is not an issue. i'm sure modern computers are capable of calculating all those permutations... only if the process is automated. anybody have a beowulf cluster running? :P

 

i'm not familiar with the innerworkings of the neogeo roms... so the only thing i can do is be patient. *sigh*

Posted

If you're using Kawaks, I don't know how to get it to show up, believe me I've tried.

 

I use Nebula 2.23d with loader, and in my dats I have one dat for KOF2003 and one for the kof2003t just like the page said, setting kof2003 as the parent... and it shows up. The original KOF2003 even shows up on Nebula, but it won't load. It acts like it's going to then finally performs an error after like 10 seconds.

 

Hell, the problem is that kof2003 uses different rom banking, so nebula's built in coding that makes drivers out of your dat files won't work on it. If Nebula was open source I could flocking fix it with little trouble... arg. Stupid El Semi :P. The same goes for Kawaks, it's not open source either, but they were both compiled with C/C++

Posted
If you're using Kawaks, I don't know how to get it to show up, believe me I've tried.

 

I use Nebula 2.23d with loader, and in my dats I have one dat for KOF2003 and one for the kof2003t just like the page said, setting kof2003 as the parent... and it shows up.  The original KOF2003 even shows up on Nebula, but it won't load.  It acts like it's going to then finally performs an error after like 10 seconds.

 

Hell, the problem is that kof2003 uses different rom banking, so nebula's built in coding that makes drivers out of your dat files won't work on it.  If Nebula was open source I could flocking fix it with little trouble... arg.  Stupid El Semi :P.  The same goes for Kawaks, it's not open source either, but they were both compiled with C/C++

FBA is open source. wanna try converting the MAME code to FBA ones?

Posted
If you're using Kawaks, I don't know how to get it to show up, believe me I've tried.

 

I use Nebula 2.23d with loader, and in my dats I have one dat for KOF2003 and one for the kof2003t just like the page said, setting kof2003 as the parent... and it shows up.  The original KOF2003 even shows up on Nebula, but it won't load.  It acts like it's going to then finally performs an error after like 10 seconds.

 

Hell, the problem is that kof2003 uses different rom banking, so nebula's built in coding that makes drivers out of your dat files won't work on it.  If Nebula was open source I could flocking fix it with little trouble... arg.  Stupid El Semi :P.  The same goes for Kawaks, it's not open source either, but they were both compiled with C/C++

does this mean his theory won't work?? :P

Posted
If you're using Kawaks, I don't know how to get it to show up, believe me I've tried.

 

I use Nebula 2.23d with loader, and in my dats I have one dat for KOF2003 and one for the kof2003t just like the page said, setting kof2003 as the parent... and it shows up.  The original KOF2003 even shows up on Nebula, but it won't load.  It acts like it's going to then finally performs an error after like 10 seconds.

 

Hell, the problem is that kof2003 uses different rom banking, so nebula's built in coding that makes drivers out of your dat files won't work on it.  If Nebula was open source I could flocking fix it with little trouble... arg.  Stupid El Semi :P.  The same goes for Kawaks, it's not open source either, but they were both compiled with C/C++

FBA is open source. wanna try converting the MAME code to FBA ones?

I wouldn't be converting anything... but I'm but I am 90% sure that the reason kof2003 won't work on other emus is because it uses different rom banking. The rom banking is part of the driver. All emus use drivers, but the newer ones allow you to add in new dats, and they are coded to use this information in drivers. If you've ever seen a driver, it contains all the info a dat file does, but there is extra stuff, mostly programming.

 

If I could get ahold of the source code to Nebula or Kawaks, I could add in a separate internal driver for kof2003. I would have to add a separate one... if I modified the existing one, it would be almost guaranteed to work, but instead of kof2003 being the only game that wouldn't work, it would then be the only one that would. I'm pretty sure that adding a seperate internal driver, either just like you would in mame, or coding it to take its crc's etc from Nebula\kof2003romdata\*.dat would work; I'm pretty sure that the original code makes it create drivers, taking it's crc's and such from Nebula\romdata\*.dat.

Posted

One thing I just thought about... on that page, the picture of the guy's test menu, you can only access that when your emu has its neo geo mode set to arcade! I'm switching over to arcade and starting over.

Posted (edited)
If you're using Kawaks, I don't know how to get it to show up, believe me I've tried.

 

I use Nebula 2.23d with loader, and in my dats I have one dat for KOF2003 and one for the kof2003t just like the page said, setting kof2003 as the parent... and it shows up.  The original KOF2003 even shows up on Nebula, but it won't load.  It acts like it's going to then finally performs an error after like 10 seconds.

 

Hell, the problem is that kof2003 uses different rom banking, so nebula's built in coding that makes drivers out of your dat files won't work on it.  If Nebula was open source I could flocking fix it with little trouble... arg.  Stupid El Semi :(.  The same goes for Kawaks, it's not open source either, but they were both compiled with C/C++

does this mean his theory won't work?? :(

I don't know, that's not what I'm saying. I'm going to keep trying his theory, I just have plenty of time to post here between loadings :P

 

[EDIT] I'm pretty sure that this theory is definitely on to something. I've just switched over to arcade mode, and since I did that, I tried adding P2_4 and P2_2 and then P2_4 and P2_1. Both times I got the same result : black screen, nothing happened, but when I pressed F2 to see the debug dips, I was able to go to Setting up the soft dip and get the same bios page the guy on that page had in his picture. I am pretty sure it's supposed to load up like that wihtout me pushing buttons, but anyway, the reason I think it's on to something, when I load up the whole original KOF2003.zip rom, and I try to access the debug dips, nothing happens. Hmmmmmmmmmm........ :P

Edited by cosmic_lord
Posted
fba uses the same type of drivers as kawaks last i checked and got the same error

 

 

winkawaks 1.48 offically out http://cps2shock.retrogames.com/

What's the difference between Hacked WinKawaks n the regular version? :P

 

Can the regular version run SvC:Chaos n all those other neogeo games with the asr.dat?

Guest
This topic is now closed to further replies.

×
×
  • Create New...