Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No longer working in Unreal 5.5 #13

Open
IntXThOrn opened this issue Nov 29, 2024 · 25 comments
Open

No longer working in Unreal 5.5 #13

IntXThOrn opened this issue Nov 29, 2024 · 25 comments

Comments

@IntXThOrn
Copy link

Needs language updating to meet the new standard in 5.5 after deprecations.
@xessgamedev
Copy link
Collaborator

Thank you for reporting, new release will be ready soon.

@XPOL555
Copy link

XPOL555 commented Nov 29, 2024

As i did for the NVIDIA DLSS plugin i did it for the XeSS Plugin.

I pushed the packaged plugin for Unreal Engine 5.5 here in the fork: https://github.com/XPOL555/XeSSUnrealPlugin/tree/main/XeSS

And as said on the NVIDIA Thread, wait for the official plugin. This is just to not block you on your development.

Long life to open source ❤️ 👐🏼

@IntXThOrn
Copy link
Author

Hi XPOL555, that's really helpful thank you! I had managed myself to convert the Nvidia plugin, but struggled with the XeSS plugin , I gave FSR3 plugin a good go but failed there also. Have you looked at FSR3 5.5 yet?

@XPOL555
Copy link

XPOL555 commented Nov 29, 2024

haven't checked FSR3... yet

should they hire me 😅 ? ahahaha

@IntXThOrn
Copy link
Author

LOL XPOL555, I'm thinking they should! Let me know here if you do decide to take a look at FSR 3, it was just a bit beyond my C++ skills that one. Thanks again <3

@mayhemmirror
Copy link

haven't checked FSR3... yet

should they hire me 😅 ? ahahaha

They 100% should! Being version-locked sucks.

If you do the same for FSR3 x UE5.5 I want to join your fan club.

@XPOL555
Copy link

XPOL555 commented Dec 2, 2024

well we are often on our Discord channel ^^ https://discord.gg/HJSy5SMR

@WingsOfAltair
Copy link

haven't checked FSR3... yet

should they hire me 😅 ? ahahaha

Please do FSR next! I tested both XeSS and DLSS from your Nvidia link and they both work flawlessly. (except for Dynamic Vibrance)

@xessgamedev
Copy link
Collaborator

Unreal 5.5 is supported in the new release: https://github.com/GameTechDev/XeSSUnrealPlugin/releases/tag/v1.4.10
Please have a try.
If any issue, please comment here, thanks!

@EpicallyEvil
Copy link

Might be stupid but can't see it working in my project? I used stat gpu and can see it's processes running but using Ultra Performance or Ultra Quality Plus yields no difference in frame rate or visual quality.

@IntXThOrn
Copy link
Author

IntXThOrn commented Jan 19, 2025 via email

@EpicallyEvil
Copy link

EpicallyEvil commented Jan 19, 2025 •
edited
Loading

That's a shame the FSR3 plugin hasn't yet been updated for 5.5 yet either 😭

@IntXThOrn
Copy link
Author

IntXThOrn commented Jan 19, 2025 via email

@xessgamedev
Copy link
Collaborator

Might be stupid but can't see it working in my project? I used stat gpu and can see it's processes running but using Ultra Performance or Ultra Quality Plus yields no difference in frame rate or visual quality.

Which API do you use? console variable or Blueprint?
Have you checked r.ScreenPercentage? it is needed to set manually if console variable is used.

@IntXThOrn
Copy link
Author

IntXThOrn commented Jan 19, 2025 •
edited
Loading

Might be stupid but can't see it working in my project? I used stat gpu and can see it's processes running but using Ultra Performance or Ultra Quality Plus yields no difference in frame rate or visual quality.

Which API do you use? console variable or Blueprint? Have you checked r.ScreenPercentage? it is needed to set manually if console variable is used.

I set by console variable in engine ini and also modified through menu ui console command at runtime for changes, no difference no matter what setting I am on. Solely enabling Xess in a 5.5 Unreal project with no other upscalers or their associated settings, r.screenpercentage 50 and same frame rate I get the same FPS I would native but with the Xess process running. I thought it was a me issue?

@xessgamedev
Copy link
Collaborator

Might be stupid but can't see it working in my project? I used stat gpu and can see it's processes running but using Ultra Performance or Ultra Quality Plus yields no difference in frame rate or visual quality.

Which API do you use? console variable or Blueprint? Have you checked r.ScreenPercentage? it is needed to set manually if console variable is used.

I set by console variable in engine ini and also modified through menu ui console command at runtime for changes, no difference no matter what setting I am on. Solely enabling Xess in a 5.5 Unreal project with no other upscalers or their associated settings, r.screenpercentage 50 and same frame rate I get the same FPS I would native but with the Xess process running. I thought it was a me issue?

Please try following steps and share your screenshots:

  1. Play Standalone Game
  2. Run r.XeSS.Enabled 0
  3. Run r.SceenPercentage 100
  4. Run stat GPU
  5. Run stat FPS
  6. Print screen
  7. Run r.ScreenPercentage 50
  8. Print screen
  9. Run r.XeSS.Enabled 1
  10. Print screen

@IntXThOrn
Copy link
Author

IntXThOrn commented Jan 21, 2025 •
edited
Loading

Might be stupid but can't see it working in my project? I used stat gpu and can see it's processes running but using Ultra Performance or Ultra Quality Plus yields no difference in frame rate or visual quality.

Which API do you use? console variable or Blueprint? Have you checked r.ScreenPercentage? it is needed to set manually if console variable is used.

I set by console variable in engine ini and also modified through menu ui console command at runtime for changes, no difference no matter what setting I am on. Solely enabling Xess in a 5.5 Unreal project with no other upscalers or their associated settings, r.screenpercentage 50 and same frame rate I get the same FPS I would native but with the Xess process running. I thought it was a me issue?

Please try following steps and share your screenshots:

  1. Play Standalone Game
  2. Run r.XeSS.Enabled 0
  3. Run r.SceenPercentage 100
  4. Run stat GPU
  5. Run stat FPS
  6. Print screen
  7. Run r.ScreenPercentage 50
  8. Print screen
  9. Run r.XeSS.Enabled 1
  10. Print screen

Here you go, tested in DX 12, Unreal 5.5. latest version of Xess, no other upscalers present. Note no FPS difference when Xess is running any mode.

Image

@IntXThOrn
Copy link
Author

Also noting that Xess also showed no frame rate increase in UE 5.4 for either my production FPS project or when implemented on a friends production racing game.

@xessgamedev
Copy link
Collaborator

TSR is the default upscaler in Unreal 5.
No frame rate compared with TSR, is that what you mean? It is possible, but on Intel GPUs, XeSS should perform better over TSR.

How an Upscaler Works:

  1. Render at a Lower Resolution:
    To save on rendering costs, the scene is initially rendered at a lower resolution. For example, r.ScreenPercentage 50 reduces the rendering resolution to 50% of the target resolution. This significantly reduces the workload on the GPU, as fewer pixels need to be processed.

  2. Upscale to Target Resolution:
    After rendering at the lower resolution, an upscaling algorithm is applied to increase the image to the desired target resolution. This process involves reconstructing the image to fill in the missing details.

  3. Performance and Quality Trade-off:
    The key idea is that the computational cost of upscaling is typically much lower than the cost of rendering at the full resolution. If the time saved by rendering at a lower resolution outweighs the additional time required for upscaling, the overall frame rate (FPS) will increase.

@IntXThOrn
Copy link
Author

IntXThOrn commented Jan 21, 2025 via email

@xessgamedev
Copy link
Collaborator

XeSS Frame Generation will be ready soon.

@IntXThOrn
Copy link
Author

IntXThOrn commented Jan 21, 2025 via email

@EpicallyEvil
Copy link

EpicallyEvil commented Jan 21, 2025 •
edited
Loading

That's great thank you, we look forward to the Xess Frame Generation release.

So... to summarise, the reason there is no difference seen between TSR and Xess, is that both perform the same function of upscaling, there is therefore negligible difference between them on non-intel hardware.

The confusion for users about the lack of frame rate increase is actually, because, unlike FSR3 and DLSS3, there is no frame rate generation at the current time.

Thanks again for your time and response. 🙂

That just makes me super confused then as I actually do have Intel hardware lol. I'm running the new Intel Arc B580. I get good enough performance that XeSS isn't needed for myself personally anyway, but it would be nice to have in the options menu which is a shame.

@xessgamedev
Copy link
Collaborator

I'll comment here to let you know once Frame Generation is supported.

@IntXThOrn
Copy link
Author

IntXThOrn commented Jan 21, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@WingsOfAltair @XPOL555 @IntXThOrn @mayhemmirror @xessgamedev @EpicallyEvil