Changes

<div style="overflow-x:auto;width:100%">{| class="wikitable" style="text-align:center;width:100%"

<div style="overflow-x:auto;width:100%">{|class="wikitable" style="text-align:center; vertical-align:middle;width:100%"

| Ray-tracing<br/><small>([https://devblogs.microsoft.com/directx/announcing-microsoft-directx-raytracing/ DXR], [https://www.khronos.org/blog/ray-tracing-in-vulkan VRT] and [https://developer.apple.com/documentation/metal/metal_sample_code_library/accelerating_ray_tracing_using_metal MRT])</small>| <small>Ray-tracing already supported on PlayStation 5 system.<br/>But there are ways to improve path-tracing implementation even further like increasing ray length or more rays per light source etc.</small>|

| Super-resolution techniques<br/><small>([https://github.com/NVIDIAGameWorks/Streamline/blob/main/docs/ProgrammingGuideDLSS.md DLSS], [https://github.com/intel/xess/?tab=readme-ov-file XeSS ] and [[Wikipedia:GPUOpen#FidelityFX_Super_Resolution|FSR 2+]])</small>|<small>Requires access to the depth buffer and temporal data like motion[https://gpuopen.com/fsr3-vectors so it's quite challenging and unlikely to be feasible in the near future-games-technical-details FSR 3] is already supported on PlayStation 5.<br/>FSR 2 is already supported on Rumors suggest the upcoming PlayStation 5Pro revision most likely include support for a new super-resolution technique called PSSR.</small>

| colspan=3 | <small>Implementing frame generation technology in an emulator AFMF is unfortunately quite challenging and unlikely to be feasible in the near future, however post-processing techniques such as [[Wikipedia:Motion_interpolation|motion interpolation]] is quite possible. [[Input_lag|Input latency]] will be a crucial factor, but its impact likely varies depending (technically) already supported on the specific technique employed, it's recommended to use '''after applying the "Internal Framerate Hack"'''PlayStation 5.</small>

| rowspan=4 6 | Post-Processing

| [[Wikipedia:Comparison_gallery_of_image_scaling_algorithms|Post-rendering scaling]]<br/><small>(Sharp bilinear, Lanczos and [[Wikipedia:GPUOpen#FidelityFX_Super_Resolution|FSR 1]])</small>|<small>FSR 2 3 is already supported on PlayStation 5.</small>

<div style="overflow-x:auto;width:100%">{|class="wikitable" style="text-align:center; vertical-align:middle;width:100%"

===Potential roadblocks===Due to the PS5's [[POS_(Pong_Consoles)_CPUs_and_Other_Chips#x86_CPUs|x86 architecture ]] and FreeBSD-based operating system[https://www.reddit.com/r/PS5/comments/juggo1/has_anyone_done_an_nmap_scan_of_the_ps5_to/], emulators for the device will, by and large, be very unconventional. Despite the x86's instruction set being huge<ref>{{cite web | url= https://en.wikipedia.org/wiki/x86_instruction_listings | title= x86 instruction listings | Wikipedia}}</ref>, a trait that would typically lead to years of development time by emulators, it opens the ability for pre-existing hypervisors to do the heavy lifting, eliminating the need for a recompiler. There is also, as of this time, little to no documentation on the GPU used in the PS5's APU, and it will require a complete re-implementation by emulator developers. In recent years many [https://www.playstation.com/en-us/games/pc-games/ PlayStation 5 exclusive titles are now being ported to PC] with [[#Enhancements|enhancements]], so similar to [[PlayStation_4_emulators#Emulation_issues|PlayStation 4 (Pro)]], [[Xbox One emulators#Emulation issues|Xbox One (X|S)]] and [[Xbox_Series_X_and_Series_S#Emulation issues|Xbox Series X|S]] situations this '''could''' lead to a decreased interest in development. Having said that, there are still considerable amount of games exclusive to those consoles, this includes games for both PlayStation 5 and Xbox Series X|S that haven't been ported and titles lacking enhanced/next-gen update for PC. See [[List of notable ports#External_links]] section for all of those games.