WipEout HD [NPEA00057]

RPCS3 0.0.5-6649-7303f04bc Alpha
Intel® Core™ i9-7900X @ 4.00GHz (20 threads) | 32GB RAM | GTX 1070 (8GB)

PPU: LLVM Recompiler (fastest)
SPU: ASMJIT Recompiler (fastest)
Renderer: Vulkan

Status: Playable

The default "Fury" style menu works fine, while the "HD" style menu is glitched and flickery. (To be clear, this is NPEA00057 w/ Fury)
Most levels are somewhat brighter than they should be. Enabling "Write Color Buffers" fixes this, but frequently crashes and introduces an incredibly slow main menu.

[Image: A2KMA.png][Image: A2KMP.png]
[Image: A2KMI.png][Image: A2Lrq.png]

how do you "enable" fury? after i installed the fury dlc over wipeout hd, i can see that the icon changed to Fury, but if i run it, i still have the regular wipeout hd game :\

Yeah, same here. 20-60 fps depending on track and location in track.

Did you mean "disable spu loop detection' or enable?

RPCS3 v0.0.8-9429-adcc3e9c Alpha | HEAD
Ryzen 2700X | 16 GB RAM | RTX 2060

- WCB is required to avoid certain tracks that are too white
- Wake Up Delay on 250 us in Advanced tab for stability.

Status: Playable

Hi guys. I'm new to RPCS3 and I have a problem with this game. The main Wipeout HD works flawlessly. But as soon as I install the 2.51 update it stops working. And if I install Fury without the update the expansion doesn't seem to be active.
I'd like to play it with the Fury expansion so is there a way?
Thanks in advance.

Ok I found it sorry.
For those interested you have to install all the updates one by one, then install Fury. After that it works like a charm.

Ran into some graphical glitches when trying this out for the first time.  Don't have a picture, but was racing on Vineta K and at certain parts the screen would be covered by purple/white/yellow planes. By planes I mean one sided flat polygons intersecting with the track.  I have a suspicion that it's related to sky reflections or certain lighting conditions.

This was with the Vulkan renderer, settings set to what the wiki recommends, or left default. Switching the renderer to OpenGL fixes the issue.  I didn't see a way to update the wiki, but would be nice to add a note there if others can reproduce this issue.

Hi,
Thought would ask this here instead of creating a new thread. Apologies if it was not the right choice or the right place.
I've been trying to create a 21:9 patch for a game (Wipeout HD) but the values keep changing back to 16:9 once the emulator shows up the "Sony Computer Entertainment presents" screen. I can see the values showing up as expected using Cheat Engine while the emulator is on the initial "PPU modules compiling" screen but once the game starts, they change back to 16:9 values.
The original 21:9 patch for this game doesn't work either. Found out yesterday that the PPU hash in the patch is the wrong one (NPUA80105 and NPEA00057 have the same PPU hash number) but even putting the right one doesn't do anything. I thought "Stretch to Display Area" would override the "Aspect Ratio" option but that doesn't seem to be the case.
Is there a way to override or stopping RPCS3 from changing the 21:9 values (3440x1440 - 2.38~) without using Cheat Engine? Will there be ultrawide-screen support in the near future?
I know this is patch related but my two questions could be considered default features in the emulator.

Thanks in advance.

Hi guys,
Found the correct addresses for 21:9 and 32:9 aspect ratios and wrote the patches. What can be done so that they are included in the default patch file of the emulator?

Edit: Ultra-wide screen patches now included in the default patch file.

THANKS!

Found an issue with the shield and absorb glow effect around ships when playing the game above 60fps.
The shield texture wont show up until you hit a wall or get hit by enemy weapon and won't disappear unless you go back to GPU
configuration and apply Framelimit to 60fps. Similar thing happens with the glow effect while absorbing a pickup.

These effects seem to be bound to the framerate and used for the rumble feature.
Added patches for all versions to fix this bug.

(They are for 120fps but the value can be changed to match your display framerate)