#PCSX RELOADED PETE PLUGIN UPDATE#
#PCSX RELOADED PETE PLUGIN FULL#

Magenta: Multiple high precision values were found at the same position of the cache, making the result ambiguous, so the low precision value is used.Green: A suitable high precision value has been found in the cache.

Red: No valid value was found so it falls back on the native low precision values.Yellow: The vertices belong to a 2D sprite element.Cyan: Tracked but has lost its 'w' component (new to this version).Blue: Successfully tracked from transformation on the GTE to the GPU.There are currently three modes that can be cycled through, the first shows the different states of each vertex: There are still games that are wobbly for a number of reasons, it really depends on how the developers processed the vertices.Ĭlick to expand.The debug visualisations are available by pressing F11 when using the OpenGL 1.78 plugin (there are two supported plugins 1.78 and the Tweak 2.4 that requires the 2.9 plugin). With regards to PGXP, the reason for using PCSX-R over other emulators is that it's currently the only emulator in which it is implemented I've also found that some games like Hydro Thunder and Alundra 2 pass multiple primitives to the GPU in a single block, PGXP only currently expects one and I'm looking for a way to process this in the Tweak plugin.

#PCSX RELOADED PETE PLUGIN UPDATE#

I've fixed the first problem locally and will try to provide an update soon. It looks like an interesting solution but it can lead to noticeable wobble with PGXP because it's done before transformation. Second is the LoD system, which aims to reduce wobbling and texture distortion on original hardware by increasing the polycount, does so by gradually sliding more detailed patches across the floor. This stopped the polygons appearing correctly in 'Memory + CPU' mode. The first is that the developers have packed additional information into the top 4 bits of some vertices, Pete's plugins strip that out but I hadn't implemented it yet. In the case of THPS1 there are two problems: Others like Time Crisis or Chrono Cross have low precision animation, meaning values are already poor when PGXP gets them, while Spyro and Grandia have a lot of processing on the CPU between transformation and the GPU receiving data. In the simplest cases like Crash Bandicoot or Threads of Fate the data is animated with good precision, transformed on the GTE (where PGXP starts tracking values) and then copied straight to the GPU.

#PCSX RELOADED PETE PLUGIN FULL#

This video from an early prototype shows the differences between native PSX geometry, GTE Accuracy and full floating point data.Ĭlick to expand.There are still games that are wobbly for a number of reasons, it really depends on how the developers processed the vertices. It works by caching high precision values and then trying to retrieve them using the native low precision data, this can cause multiple vertices to all associate with a single point, you can see this where UI elements or 2D backgrounds distort when they are close to animating 3D objects. There is a feature of Tapeq's plugin and others called 'GTE Accuracy' which was originally created by Edgbla and goes some way to improving vertex accuracy and stability, although it isn't as effective as PGXP in many cases, it doesn't support perspective correct textures or improved culling. The main features are listed in the first post on this thread, namely more accurate and stable vertex positions, more accurate culling to prevent gaps and perspective correct textures that don't stretch and warp.

Many features of Tapeq's Tweak plugin will work with both ePSXe and PCSX-R because they implement all the API calls it requires to work, PGXP adds a lot of extra features that require a special build of both the emulator and plugin to work. Click to expand.With regards to PGXP, the reason for using PCSX-R over other emulators is that it's currently the only emulator in which it is implemented

Pcsx reloaded pete plugin