..:: PCSX2 Forums ::..

Full Version: Missing character models in Tekken 4.
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
I have been trying to run Tekken 4 (USA ISO), and while it runs fairly well, the character models are invisible, with only their hair and shadows remaining. Running the game in software mode restores the models, but the frame rate is much slower. Here is my system information.

Intel Core i5-3210M/Nvidia Geforce GT 650M/6GB DDR3 RAM
for the lazy ones:
[Image: 76d45f34dd77412ff82b9299d1b98ab9.png]
[Image: 37e15400d62ffdf2f5d404737e8e0719.png]
[Image: 9b1a53dcbc759c4528c366cd1e2a4e2f.png]
[Image: bd136c8e015f17c3fe40cbb069a45557.png]
[Image: 64497dc115a6b314b71ebe472c49ac66.png]
Thanks. I couldn't get the images working for some reason.
Please show the full emulog after you booted the game and saw the glitches. Not after you started the emulator.

You already have nice settings. Please check if MTVu really helps or slows you down. But I guess there is not much that you can do if SW mode is needed.

But is SW mode really needed for tekken 4??

(04-29-2015, 12:43 AM)letmetrythisname Wrote: [ -> ]Thanks. I couldn't get the images working for some reason.

you have to click once on the frame showing the picture to get to the real picture.

Or just add an 'i.' in the beginning and an '.png' in the end of the url



I have to go to bed now. Good luck finding a solution.
SW mode is not needed for Tekken 4. It only has the notorious vertical line bug in hardware mode.

Try reducing the EE Cyclerate speedhack.
Actually, now it suddenly works. I don't know what I changed or if I changed anything, but it's fine now. Thanks!
I guess the vertical lines are resolved now, or? Probably you know best.
Should be resolved with gregory's new hack. He would have to update his PCSX2 to the 1.3.1 dev build though since it doesn't exist yet in the 1.2.1 version.
I'm not having any issues with vertical lines, but I think that was only if the game was running in a non-native resolution.
Oh right, you're running it in native... missed that, oops.
Pages: 1 2