Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
PCSX2 development picks up speed
#1
After a brief period of slowed development, PCSX2 has started picking up speed again with the help of new contributors as well as familiar faces. Several important improvements have been made since the last announcement.

The most important of these improvements is undoubtedly the new debugger. Our debugger has long been an area in need of attention, and thanks to Kingcom it has finally received a much needed overhaul. This new debugger will make it much easier to chase down the problems in broken games. Rama has already managed to get the NHL series working by using it! Featuring a live instruction assembler, thread view, full register view, a function list and more, this improved debugger will certainly be a boon for our developers.

Another area that has received welcome attention is work towards 64 bit compatibility. Although there is still a lot of work to be done before we release a 64 bit build, the foundation has been laid. GSdx compiles for x64 now, and several key changes have been made to the PCSX2 core to support x64 as well. These changes include preparing the emitter for 64 bit jumps, updating vtlb to work on x64, and changing instances of 32bit only code to be universal. These improvements help move us closer to having a true 64 bit build.

Linux matters have improved as well. Many of the new contributors use that OS instead of Windows and improvements here always help general portability in the long run.

Lastly, a few important changes have been made to some of the plugins. On top of general bug fixes, CDVDgigaherz now tries to keep the disc always spinning at a low speed instead of letting the drive spin all the way down. This improves game performance when using a physical disc because the drive is always ready to provide data. Lilypad also supports hot-plugging of Xinput devices now. That means if you forget to plug in your Xinput device before starting PCSX2, it will recognize it when it is plugged in without requiring a restart.

Here is a rundown of the most significant changes:

64 bit related:
  • Changed instances of u32 to uptr
  • Prepared emitter for 64 bit jumps
  • Made yuv2rgb and hashmap functions 64 bit ready
  • vtlb now works on on x64
  • Supported grabbing the MXCSR mask on x86_64 in cpudetect
  • GSdx now compiles for x64
VIF:
  • Fixed "Looney Tunes: Back in Action"

Improved Debugger:
  • Allows much easier debugging of broken games
  • Already used to get "NHL" games working
  • Features a live assembler (e.g. mark an instruction, type "nop" to replace that instruction with "nop")
Plugins:
  • Bug fixes for CDVDgigaherz
  • CDVDgigaherz now prevents the drive from spinning all the way down which improves performance when playing from disc
  • Lilypad supports hot-plugging of Xinput devices
Code cleanup:
  • Changed int to bool for variables that only hold 0/1
  • Fixes for potential crashes
  • Fixes for potential variable leaks
  • Preparation for WX3 (for now we still use a custom 2.8)
  • Removed managed Vsync
  • Folder name fixes for Windows/Linux
  • Improved use of namespaces
  • Fixes for ELF parser
  • Started using generic memcpy instead of custom one(this actually brings a small speedup!)
Misc:
  • Updated translations for several languages

Check out the new debugger below


Attached Files Thumbnail(s)
   
[Image: newsig.jpg]
Reply

Sponsored links

#2
The new debugger is awesome. I had Blyss do a build for me, so I can debug "Chessmaster"
[Image: gmYzFII.png]
[Image: dvedn3-5.png]
Reply
#3
wow really good job
CPU: Intel Core i7 4790K @ 4 Ghz
CPU Cooler: Corsair H75
MoBo: MSI Z97S SLI KRAIT  
GPU: AMD Radeon R9 290X
RAM: Corsair 16 GB 1600 Mhz

Desktop
[Image: 1086677.png]

Laptop
[Image: 872520.png]
Reply
#4
Amazing news ! looking forward to 64bit ver.
Pentium Dual-core G2010 2.8Ghz
RAM=4GB
nvidia GT 610
pcsx2 version-1.3.1  


Still surfing with Browser?, Try the pcsx2 forum App !
Reply
#5
Yeah its always the same with these guys...
First they don't acknowledge work from others..
Then they don't support ARM or Mantle...
And the release 3000 should have supported multi-threading in a more extended way... But still this seems not to be finalized... my cluster is still slower than my home pc... -.-''
Reply
#6
Lol? I can't tell if that is a joke or not. I guess so.

But no to clarify, I did write it, but I'm just making a silly fuss for fun.

Edit: Lol I just read that commit 3000. LOL.
[Image: vwah44]
Gaming: Intel i7 3770k @ 4.2Ghz | R9 290 | 16GB RAM | 480GB(240GB+240GB RAID0) SSD | 3 TB HDD | 1 TB HDD | 500GB HDD
Server: AMD FX 6300 @ 4.4Ghz | GTX 670 | 16GB RAM | 240GB SSD | 320GB HDD
PCSX2 General Troubleshooting FAQ
Reply
#7
Please spare us the offtopicness?
[Image: newsig.jpg]
Reply
#8
Okay here's some on topic then. It says GSdx compiles for x64, but I still get 4 compile errors. Is there something special you gotta do? Or is that code not in the main branch yet?
[Image: vwah44]
Gaming: Intel i7 3770k @ 4.2Ghz | R9 290 | 16GB RAM | 480GB(240GB+240GB RAID0) SSD | 3 TB HDD | 1 TB HDD | 500GB HDD
Server: AMD FX 6300 @ 4.4Ghz | GTX 670 | 16GB RAM | 240GB SSD | 320GB HDD
PCSX2 General Troubleshooting FAQ
Reply
#9
Are you compiling on windows or linux? I think that most of the x64 compatibility improvements are currently linux only. CMake, which is used on linux, correctly sets the 64 bit flags and defines and such. Windows uses Visual Studio project files that haven't all been updated to correctly work with x64 (IIRC, anyway).
Main Rig: i5 4670k, 16GB RAM, Nvidia 770 GTX, Windows 8.1/Arch
Main Laptop: Toshiba Kirabook. i5 4200U, 8 GB RAM, windows 8.1/Arch
Reply
#10
Ahh, that could be it. Trying to compile in Windows with visual studio 2013. I get 4 errors, but one of them is on an ifdef AMD_64 and the line it errors on is TODO. lol
[Image: vwah44]
Gaming: Intel i7 3770k @ 4.2Ghz | R9 290 | 16GB RAM | 480GB(240GB+240GB RAID0) SSD | 3 TB HDD | 1 TB HDD | 500GB HDD
Server: AMD FX 6300 @ 4.4Ghz | GTX 670 | 16GB RAM | 240GB SSD | 320GB HDD
PCSX2 General Troubleshooting FAQ
Reply




Users browsing this thread: 1 Guest(s)