NCAA Basketball '09 visual glitches
#1
Hey this is my first threat so sorry if I forget some things to put in it. Anyways I just got into emulators recently to try and play NCAA 09, but when I got it to work it had multiple visual glitches making the game unplayable. Some parts of it work like the intro video, but the rest is extremely distorted. I saw a thread on this same problem from 2015 but it was not answered. Just a warning I am not the most tech savvy so sorry if I ask a lot of questions.

Im using PCSX2 1.4.0 on a windows 10 computer
Reply

Sponsored links

#2
Please post the contents of the emulog.txt file after the problem occurs. The file can be found in "My Documents\PCSX2\logs" for the installer version or in "PCSX2\logs" for the portable/binary version.

Please make sure to enclose your emulog in code tags like so (remove the empty space on the closing code tag!):
[code]
Pasted emulog goes here
[ /code]
CPU : AMD Ryzen 7 3800X
Mobo : Asus PRIME B450-PLUS
GPU : NVIDIA GeForce RTX 3070
RAM : 16 Go
Reply
#3
Ok so im a little bit confused on what you mean by putting it in code tags, but I found the emulog and since the glitches happen immediately when you boot it up I just put everything after it boots up the game
Code:
isoFile open ok: D:\PS2 Gamez\NCAA Basketball '09.iso
Image type  = DVD
* CDVD Disk Open: DVD, Single layer or unknown:
* * Track 1: Data (Mode 1) (2282752 sectors)
Current Renderer: Direct3D11 (Hardware mode)
Opening USB
Opening FW
Opening DEV9
McdSlot 0 [File]: C:\Users\(removed)\Documents\PCSX2\memcards\Mcd001.ps2
McdSlot 1 [File]: C:\Users\(removed)\Documents\PCSX2\memcards\Mcd002.ps2
Plugins opened successfully.
EE/iR5900-32 Recompiler Reset
Bios Found: USA    v02.30(20/02/2008)  Console
BIOS rom2 module not found, skipping...
BIOS erom module not found, skipping...
(UpdateVSyncRate) Mode Changed to NTSC.
(UpdateVSyncRate) FPS Limit Changed : 59.94 fps
# Initialize memory (rev:4.00, ctm:392Mhz, cpuclk:294Mhz detected)

PlayStation 2 ======== Hard reset boot
ROMGEN=2008-0220, IOP info (CPUID=1f, CACH_CONFIG=14000200, 2MB, IOP mode)
<20080220-175343,ROMconf,PS20230WC20080220.bin:11824>
# Total accessable memory size: 32 MB (B:2:8:0) (400:2:7c30)
# TLB spad=0 kernel=1:12 default=13:30 extended=31:38
# Initialize Start.
# Initialize GS ...
# Initialize INTC ...
# Initialize TIMER ...
# Initialize DMAC ...
# Initialize VU1 ...
# Initialize VIF1 ...
# Initialize GIF ...
# Initialize VU0 ...
# Initialize VIF0 ...
# Initialize IPU ...
# Initialize FPU ...
# Initialize User Memory ...
# Initialize Scratch Pad ...
# Initialize Done.

EE DECI2 Manager version 0.06 Sep  5 2006 12:57:08
  CPUID=2e20, BoardID=0, ROMGEN=2008-0220, 32M

(SYSTEM.CNF) Detected PS2 Disc = cdrom0:\SLUS_218.51;1
(SYSTEM.CNF) Software version = 1.00
(SYSTEM.CNF) Disc region type = NTSC
ELF (cdrom0:\SLUS_218.51;1) Game CRC = 0x420C2451, EntryPoint = 0x00266508
(SYSTEM.CNF) Detected PS2 Disc = cdrom0:\SLUS_218.51;1
(SYSTEM.CNF) Software version = 1.00
(SYSTEM.CNF) Disc region type = NTSC
Reply
#4
Can you show us a screenshot or something of the visual glitches/issues?
CPU: I7-4770 3.9GHZ
Motherboard: Asrock B85M - DGS
RAM: Hyper X Savage 2x8GB 1.6GHZ CL9
GPU: GTX1070 8GB GDDR5
OS: Windows 10 Pro 64bit
Reply
#5
Sure here you go:

Start up screens : https://i.gyazo.com/470513aeae31be19b82b...a8ab63.jpghttps://i.gyazo.com/4a3c1672eed34e96bf83...ca39bd.jpg


Main Menu (you can select the little gray text and it sends you to more messed up menus) : https://i.gyazo.com/9e930e7893cc83b2e161...7cedf4.jpg
Reply
#6
(06-27-2019, 10:49 PM)lightningterror Wrote: Can you show us a screenshot or something of the visual glitches/issues?
Well I tried to but now its under moderation, can you not show gyazo images?

edit : nvm its back
Reply
#7
Did you try 1.5 dev builds and see if the issue is fixed?
https://buildbot.orphis.net/pcsx2/
CPU: I7-4770 3.9GHZ
Motherboard: Asrock B85M - DGS
RAM: Hyper X Savage 2x8GB 1.6GHZ CL9
GPU: GTX1070 8GB GDDR5
OS: Windows 10 Pro 64bit
Reply
#8
No but let me try it and ill update you to see if it works
Reply
#9
I think it worked! The screens no longer have any glitches, but I haven't got to far into it. It looks normal now none the less. Thanks for you help!
Reply




Users browsing this thread: 1 Guest(s)