Joined
·
398 Posts
@iCatButler, I think is a good idea to pay attention to development of this.
Posts by u3L05 vh9jV
1 - 20 of 1133 Posts
Joined
·
398 Posts
Hmm... the worrying part is the license.
PGXP need to have a more permissive license, like BSD...
The license can have a negative impact in development of a project, like in ReactOS case.
PGXP need to have a more permissive license, like BSD...
The license can have a negative impact in development of a project, like in ReactOS case.
Joined
·
398 Posts
I don't know how PCSX-R is actually working in relation to textures. But I think learning how other emulators work with textures can be very educational. Example:
https://github.com/gonetz/GLideN64/issues/1443
https://github.com/gonetz/GLideN64/issues/1443
Joined
·
398 Posts
@loathingkernel, I tested your branch 'sync-with-codeplex' on my Xubuntu 16.04.4 LTS (x64). Thanks for your good job.
The few bugs that I have detected also exist in the original code. Example, the portals in Soul Reaver.
The few bugs that I have detected also exist in the original code. Example, the portals in Soul Reaver.
Joined
·
398 Posts
Never specify the architecture, so I think it was x64... I recall having problems activating PGXP in certain branch, but such branch worked correctly with PGXP deactivated.
I probably mix-up the branches by mistake and the one that worked correctly was the 'master' one. Now 'sync-with-codeplex' is merged with your 'master', so makes more sense.
My original test was on a Radeon HD 5750, but I can not use that GPU ever again.
I'm currently using a GeForce 210, but that GPU with nouveau drivers does not play fluently mpv with gpu-hq profile, much less an emulator
I abstaining myself of doing tests until my new GPU arrive, at least on mupen64plus =P
Joined
·
398 Posts
https://ci.appveyor.com/project/iCatButler/pcsxr
or
https://ci.appveyor.com/project/loathingKernel/pcsxr
Configuration: Release > Artifacts...
Joined
·
398 Posts
Visual C++ 2017 Redistributable replace the 2015 redistributables. In any case, the AppVeyor build uses 2017.
In addition, other plugins may require another redistributable versions (Visual C++, DirectX, .NET, etc).
Personally, I can't think of any third-party plugin that fits at all with "PCSXR-PGXP". Maybe those from here?
In addition, other plugins may require another redistributable versions (Visual C++, DirectX, .NET, etc).
Personally, I can't think of any third-party plugin that fits at all with "PCSXR-PGXP". Maybe those from here?
Joined
·
398 Posts
Edit "win32/pcsxr.vcxproj" and change the platform toolset from v140 to v141. That's all.
Edit:
@iCatButler, about the logo. The 'pcsxr.bmp' image has 32 bits in the color depth, 'about.bmp' has 24 bits. Perhaps a new "security update" is restricting the type and properties of the logo image.
Joined
·
398 Posts
Xubuntu 16.04.5 LTS / AMD64
I can't reproduce your issue @SolisX. Compiled using Clang 7, many warnings but zero problems.
The old glitches on Soul Reaver portals are gone
P.S: I can't test xvideo plugin (RX 560). I really liked xvideo plugin, but without support for planar video, is useless for me T.T
I can't reproduce your issue @SolisX. Compiled using Clang 7, many warnings but zero problems.
The old glitches on Soul Reaver portals are gone
P.S: I can't test xvideo plugin (RX 560). I really liked xvideo plugin, but without support for planar video, is useless for me T.T
Code:
X-Video Extension version 2.2
screen #0
Adaptor #0: "GLAMOR Textured Video"
number of ports: 16
port base: 63
operations supported: PutImage
supported visuals:
depth 24, visualID 0x21
number of attributes: 5
"XV_BRIGHTNESS" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_CONTRAST" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_SATURATION" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_HUE" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_COLORSPACE" (range 0 to 1)
client settable attribute
client gettable attribute (current value is 0)
maximum XvImage size: 8192 x 8192
Number of image formats: 2
id: 0x32315659 (YV12)
guid: 59563132-0000-0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
id: 0x30323449 (I420)
guid: 49343230-0000-0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
Joined
·
398 Posts
Is just your gcc =P
I had to reconfigure from scratch in each test... it take more time than I thought, but is done. Zero problems.
Tested with gcc-5, gcc-6, gcc-7, gcc-8, clang-4, clang-5, clang-6 and clang-7. Logs (make -j5).
All my GCC compilers come from ppa:ubuntu-toolchain-r/test. Clang-7 come from ppa:oibaf/graphics-drivers. I use the kernel branch "hwe-16.04", currently 4.15.0-43-generic and my CPU is "AMD Phenom(tm) II X6 1090T Processor".
I think that is the most relevant info.
cya
I had to reconfigure from scratch in each test... it take more time than I thought, but is done. Zero problems.
Tested with gcc-5, gcc-6, gcc-7, gcc-8, clang-4, clang-5, clang-6 and clang-7. Logs (make -j5).
All my GCC compilers come from ppa:ubuntu-toolchain-r/test. Clang-7 come from ppa:oibaf/graphics-drivers. I use the kernel branch "hwe-16.04", currently 4.15.0-43-generic and my CPU is "AMD Phenom(tm) II X6 1090T Processor".
I think that is the most relevant info.
cya
Joined
·
398 Posts
Last official WIP: https://www.ngemu.com/threads/pcsxr-pgxp.186369/page-46#post-2725243It's been ages since I've checked this thread! Still seems to be going quite strong.
However, I can't seem to find any download link to PCSX-R on the PCSX-R website (except one for an archive
Last GitHub WIP's: https://www.ngemu.com/threads/pcsxr-pgxp.186369/page-42#post-2717337
Last unofficial pack (good OOTB): https://www.ngemu.com/threads/pcsxr-pgxp.186369/page-46#post-2724895
Joined
·
398 Posts
PCSXR-PGXP is a fork of PCSX-R, PCSX-R is currently discontinued. By default, PCSXR-PGXP behaves almost like PCSX-R but with less issues.
To use PGXP, you need enable it and a plugin that support it. That is all, it's a feature. You can also use said feature in Beetle PSX HW.
To use PGXP, you need enable it and a plugin that support it. That is all, it's a feature. You can also use said feature in Beetle PSX HW.
Joined
·
398 Posts
The official WIP isn't OOTB. It expect that you know where and how assemble all the pieces. That's why I offered multiple alternatives.
If you don't care about PeteOpenGL2Tweak (like me), you don't need the official WIP.
If you don't care about PeteOpenGL2Tweak (like me), you don't need the official WIP.
Joined
·
398 Posts
Nowadays very few people know HOW to make the CD plugin work. Is better use CUE, BIN, IMG, etc.
Only if you want a more accurate emulation and avoid many problems with memory cards. You can use the simulated PSX BIOS if not.
Better remove your previous configuration, that never happens in a clean environment.
Joined
·
398 Posts
Then use my attached file.
I don't understand what's the issue... merely download the last GitHub/AppVeyor WIP. If you don't understand how AppVeyor works, read this guide.
Unzip pcsxr-pgxp.zip and run pcsxr-pgxp.exe, I don't see the difficulty.
If you want to save to memory cards, create a 'memcards' folder. If you want to use BIOS, you create a 'bios' folder and put your BIOS in it. The same story for 'cheats', 'patches', 'sstates', etc.
If that seems too difficult, use this. Different strokes for different folks...
This is the safest configuration. You can try all possible configurations that would work best in each game.
Joined
·
398 Posts
Emulators are very susceptible to Wetware issues, there is no software immune to Layer 8.
Jokes aside, that is a good example of why it's not good to trust 100% in the simulated BIOS (PSX...).
Jokes aside, that is a good example of why it's not good to trust 100% in the simulated BIOS (PSX...).
Joined
·
398 Posts
There is activity:
The problem is that there is no "leading" fork.
The differences between each project file are so different that practically each one could be classified as a independent emulator.
Plugins do not share common code between platforms. The only thing they have in common with plugins is the "modular" part.
From my perspective, the only PSX emulators that have potential are Mednafen PSX, Beetle PSX*, XEBRA, Avocado and DuckStation.
Other emulators to keep in mind, PSXACT, Rustation NG and PCSX-ReARMed.
The problem is that there is no "leading" fork.
The differences between each project file are so different that practically each one could be classified as a independent emulator.
Plugins do not share common code between platforms. The only thing they have in common with plugins is the "modular" part.
From my perspective, the only PSX emulators that have potential are Mednafen PSX, Beetle PSX*, XEBRA, Avocado and DuckStation.
Other emulators to keep in mind, PSXACT, Rustation NG and PCSX-ReARMed.
Joined
·
398 Posts
User space installation (without root or sudo):
Bash:
git clone https://github.com/iCatButler/pcsxr.git
cd pcsxr
mkdir build
cd build
mkdir $HOME/pcsxr-pgxp
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=$HOME/pcsxr-pgxp ..
make
Bash:
apt-cache search libpng | grep 'dev'
sudo apt-get install libpng16-dev
Bash:
make installTo launch use "LIBGL_ALWAYS_SOFTWARE=1 pcsxr" from terminal or create a launcher...
Other much better alternatives:
DuckStation
RetroArch with Beetle PSX / Beetle PSX HW
PCSX-Redux
Avocado
XEBRA on Wine
Joined
·
398 Posts
Joined
·
398 Posts
1 - 20 of 1133 Posts
