Mortal Kombat 4 graphics problems

[Likwid_Nitrogen]

All the 2d graphics on the screen such as the health, and the pause menu are missing in-match, unless transforms are set to internal, and then they appear, but the 3d graphics go a little crazy. Playable, but the backgrounds get really messed up. As far as I know, this isn't a "known issue", as I've read through just about everything on the front page of here the last couple days for different reasons, and haven't seen MK4 mentioned. Its also not in the PJgameFAQ. Anybody have a suggestion?

[Allnatural]

It's a problem with your hardware and/or drivers. It's been suggested that the issue is unique to ATi cards, but I have the same problems with my GF3. I'm still trying to figure out whats causing it.

[Ogy]

sounds like a bad rom to me...

[Allnatural]

Originally posted by Ogy
sounds like a bad rom to me...
I don't think so. He's probably having the same problems I am, and I know my rom is good.:p Besides, it's not just this game. I'm still trying to pinpoint the cause.

[Ogy]

erm, didn't read all the post.. sorry

[Likwid_Nitrogen]

I guess I should say I'm running a gf3 ti200, and I can't remember my driver number right now, it's the most popular unofficial driver currently I think. 27.xx i think.

[sxxxe83]

Originally posted by Allnatural

I don't think so. He's probably having the same problems I am, and I know my rom is good.:p Besides, it's not just this game. I'm still trying to pinpoint the cause.

If this is a problem with your GF3 card, have you ever tried to update your card`s bios??, I flashed my GF3 bios, and to my MSI motherboard since I had troubles with my GF3, and some games and so on...

sXe

[Allnatural]

Originally posted by Likwid_Nitrogen
I guess I should say I'm running a gf3 ti200, and I can't remember my driver number right now, it's the most popular unofficial driver currently I think. 27.xx i think.
What motherboard are you using? More specifically, which chipset does your motherboard use?

[sxxxe83]

via chipset offcourse..

MSI KT72 Turbo (or was it K7T2 Turbo)..

[Allnatural]

Originally posted by sxxxe83
via chipset offcourse..

MSI KT72 Turbo (or was it K7T2 Turbo)..
I was asking Likwid_Nitrogen actually, but this could be helpfull too. Have you ever had graphics problems with games like MK4 (see screenshot), JFG, or DKR? This problem is present in these and some other games requiring the internal pipeline.
I have a sneaking suspision this is related to the mobo chipset.

[Likwid_Nitrogen]

I'm running an Asus A7V, via KT133 chipset. I basically have the latest mobo bios (the next update didnt do much, wouldnt affect this). I believe I have the latest 4 in 1 chipset drivers, I'll check. I don't believe I've had graphical problems with JFG or DK64. If I did, I didn't notice anything as obvious as total lack of status bars, etc. Yes, that screenshot is what it looks like with internal. Is the game supposed to be run with internal pipeline, just on most ppls computers the graphics defects aren't there, or is it regular on external normally?

[Allnatural]

MK4 like many others is supposed to be run on the internal pipe. For some reason, some people, like you and I, have problems with the internal pipe. I can't seem to find a common hardware link between the people that have this problem.???:plain2: Checking "Force Depth Enable" fixes the bad graphics in these games, but at the cost of losing some important things like the health bars in MK4.

By the way, this is the problem you may see with JFG:

[Remote]

Quick q: Are you using the DirectX 6 or DirectX 7(HW T&L) port. If I remeber correctly NRage posted a couple of pics similar to that one during the bets testing phase, also I think the problem was pinned down to AMD... But don't take my word for it...

[Allnatural]

It doesn't matter which I use, the problem is the same.

The problem was thought to be ATi specific at first; I don't remember reading about an AMD link.

[Likwid_Nitrogen]

Okay, I get the same messed up screen as posted above when running JFG on internal pipeline, without force depth enabled. With it enabled, I can find nothing wrong with the graphics. Are there graphics problems I'm not catching or don't see at the beginning of the game with force depth enabled? Still havent checked DK64.

[Quip]

I thought that jabo didn't finish the 2-D portion of his gfx plug-in.

[Allnatural]

It's not a plugin issue, it's an issue with some hardware/software configurations.

[Allnatural]

Originally posted by Likwid_Nitrogen
Okay, I get the same messed up screen as posted above when running JFG on internal pipeline, without force depth enabled. With it enabled, I can find nothing wrong with the graphics. Are there graphics problems I'm not catching or don't see at the beginning of the game with force depth enabled? Still havent checked DK64.
The problem here is that we shouldn't have to use force depth enable to fix these problems. The setting was put in to fix an issue with the Zelda games if I remember correctly. Other games should still look fine with it off.

By the way, the other game I was refering to was Diddy Kong Racing, not DK64.:p

[Likwid_Nitrogen]

Ah hehe. Hmm, the only problem I see in DDR with internal pipeline is the sky, which I think is a universal problem, fixed by force depth enable.

[Allnatural]

Originally posted by Likwid_Nitrogen
Ah hehe. Hmm, the only problem I see in DDR with internal pipeline is the sky, which I think is a universal problem, fixed by force depth enable.
I'm not sure that it's a universal problem.

What we really need here is input from others, to figure out what specific systems are affected.

[Ogy]

mine isn't (u know my specs)

[Allnatural]

Originally posted by Ogy
mine isn't (u know my specs)
Actually, I don't.

[Ogy]

oh,

cel 850mhz
voodoo 5 5500 AGP
sb live value
win98 FE
dX 8.0a

my motherboard is asus cuv4x and i don't remember what chipset it is.

[edit]
you know what.. i'll check...

[edit2]
it's via

[Likwid_Nitrogen]

Well, it shouldnt be a VIA specific problem. Allnatural and I have via chipsets, his newer, and we have problems, but Ogy with older via chipset doesn't. Unless it was an issue introduced with the KT133 chipset and onward. Problem people have Geforce 3s, I have ti200, Allnatural has ti500, shouldnt matter, same drivers. Ogy has Voodoo, while others have had this problem w/ voodoos, according to a previous post. Yes we need more input from other systems. Maybe a sticky?

[Allnatural]

Originally posted by Likwid_Nitrogen
Allnatural and I have via chipsets...
My Epox uses an AMD Northbridge.:sly:

[sxxxe83]

Originally posted by Allnatural

I was asking Likwid_Nitrogen actually, but this could be helpfull too. Have you ever had graphics problems with games like MK4 (see screenshot), JFG, or DKR? This problem is present in these and some other games requiring the internal pipeline.
I have a sneaking suspision this is related to the mobo chipset.

I don`t have seen things like that before.. What kind of motherboard do you have? what kind of chipset?

sXe

[sxxxe83]

Originally posted by Allnatural

My Epox uses an AMD Northbridge.:sly:

Try to update your bios, on motherboard, and your geforce(if you had one ??? .. maybe and se if it helps..

sXe

[Smiff]

there is something here that needs checking out ,ill talk to Jabo some time, don't get to do that much nowadays :/

[Allnatural]

Thanks Smiff. I can't seem to find any commonality between us with this problem. Radeons and GeForces, VIA and AMD chipsets (don't know about the Intel folks). It's growing more bizarre.:plain:

[Smiff]

k sorry if this has been covered but is this Dx6 or Dx7 port or both, and HAL, TnL HAL, or both?

[Allnatural]

Originally posted by Smiff
k sorry if this has been covered but is this Dx6 or Dx7 port or both, and HAL, TnL HAL, or both?
Both and both.

[Ogy]

have you seen this happening with an Intel CPU as well?

[Likwid_Nitrogen]

I am experiencing this problem on everything mentioned (dx6,7,t&l), on every graphics plugin I have (1.20b, 1.30, 1.60)

[Likwid_Nitrogen]

Don't have an Intel to test here.

[Allnatural]

Originally posted by Ogy
have you seen this happening with an Intel CPU as well?
None that I can remember. Hmm...