Crash Tag Team Racing [SLUS 21191] (U)
#1
status=5;
version=1.3.0;
console=PS2;
crc=AA525269;
img_t=empty;
img_f=empty;
wikiurl=Link;
Code:
empty
Intel Core i7 920 @ 3.4 Ghz | 6 GB DDR3 RAM in Triple Channel | GeForce GTX 285
2.5 TB Hard Drive Space | Windows 7 Ultimate x64

Official betatester of PCSX2
Reply

Sponsored links

#2
PC Specs:

CPU: Intel Core i7 @ 3.4Ghz
GPU: Nvidia GTX 285 768MB

Build Description: PCSX2 24 02 2013 1.1.0 r5576 - Windows
GSdx 5570 SSE41 [23 02 2013]
LilyPad 0.11.0 [13 01 2013]
cdvdGigaherz 0.8.0 [13 01 2013]
USBnull Driver 0.7.0 [13 01 2013]
SPU2-X 2.0.0 [24 02 2013]
DEV9null Driver 0.5.0 [13 01 2013]
FWnull Driver 0.7.0 [13 01 2013]
USA v02.00(14/06/2004) Console
DC and MTGS | VU1Rec and VU0Rec | rCache 0 | Console 1 | Patches 0

EE/VU Clamp modes: Normal/Normal
EE/VU Rounding: Chop/Chop

Speedhacks Used:

N/A

Gamefixes Used:

N/A

Amount of testing done (little/medium/much/completed-game): medium

Comments:

Status is unchanged.

Bugs:

VU1 must be in SuperVU or game will hang at menus. Gets ingame and crashes shortly afterward.

Status
Ingame
Intel Core i7 920 @ 3.4 Ghz | 6 GB DDR3 RAM in Triple Channel | GeForce GTX 285
2.5 TB Hard Drive Space | Windows 7 Ultimate x64

Official betatester of PCSX2
Reply
#3
I get no problems in menus with mVU but ingame it crashes because of running out of memory for the VU rec.
Also menus are *slow*.
At least the sound is working better now.
Reply
#4
1)Game Title:ESPN NFL 2K5
2)ELF nameWackoLUS 20919
3)Game CRC-42F9D5AF
Compatibility report:Work fine.

PC Specs:

CPU: I5 3330
GPU: HD radeon 6850

Build Description: PCSX2 1.3 Git 28 of May Release Pack - Windows
If other please specify: N/A

BIOS Used: USA v02.20(10/02/2006) Console

EE/VU Clamp modes: Normal/Normal
EE/VU Rounding: Chop/Chop

Speedhacks Used:
Standard Speedhackers

Gamefixes Used:


Amount of testing done (little/medium/much/completed-game):
Medium


Comments:Fine now.OK

Bugs:Its possible minimuns slowdowns in the memory card screen reader.
Shadow below main character(square formact,not afecct the gameplay fun and not disturb the vision)

Status

Playable
Reply
#5
How does it work without speedhacks?
CPU:
Intel Core2 Duo T5450 (1.666 GHz)
[Image: gzztty.png]
GPU:
Mobile Intel® 965 Express Chipset Family (500 MHz)
GPU-Z Validation
Other:
RAM: DDR2-666 (2 GB)
---
Not a gaming PC, but I'll try to get a better one in the future.
Reply
#6
Read again the postage,only used standard spedhackers,(not the addictionals)
Reply
#7
That's why I said that, I wanted to know how the game works WITHOUT speedhacks, I see that with speedhacks it works well.
CPU:
Intel Core2 Duo T5450 (1.666 GHz)
[Image: gzztty.png]
GPU:
Mobile Intel® 965 Express Chipset Family (500 MHz)
GPU-Z Validation
Other:
RAM: DDR2-666 (2 GB)
---
Not a gaming PC, but I'll try to get a better one in the future.
Reply
#8
DESTRUIDOR is saying that it works with the default settings. Standard speedhacks means:

INTC Spin Detection is enabled
Wait Loop Detection is enabled
mVU flag hack is enabled

All others are disabled.
[Image: XTe1j6J.png]
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Reply
#9
Oh, sorry then.
CPU:
Intel Core2 Duo T5450 (1.666 GHz)
[Image: gzztty.png]
GPU:
Mobile Intel® 965 Express Chipset Family (500 MHz)
GPU-Z Validation
Other:
RAM: DDR2-666 (2 GB)
---
Not a gaming PC, but I'll try to get a better one in the future.
Reply
#10
PC Specs:

CPU: Intel Core i7 3930K
GPU: AMD Radeon HD 7850 1 GHz 2GB

Build Description: PCSX2 23 03 2014 1.3.0 r5927 - Windows
GSdx 5932 AVX
LilyPad 0.11.0
SPU2-X 2.0.0
cdvdGigaherz 0.8.0
USBnull Driver 0.7.0
FWnull Driver 0.7.0
DEV9null Driver 0.5.0
Europe v02.00(14/06/2004) Console

EE/VU Clamp modes: Normal/Normal
EE/VU Rounding: Chop/Chop

Amount of testing done: medium

Bugs:

Will crash every 5 minutes, regardless of whether speedhacks are used or not. Memory usage goes up at 20MB per second, reaching roughly 1.5GB, before GSDx prints "out-of-memory, texturing temporarily disabled" to the log a few dozen times, then PCSX2 crashes a few seconds later. If in a minigame, memory usage does not increase as drastically. Problem occurs in DirectX and OpenGL, in both software and hardware rendering mode.

Status
Ingame
Reply




Users browsing this thread: 1 Guest(s)