- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
To preface this, I already asked Intel for support and they refused. The complete disregard for our project is not appreciated.
We want to fully implement the XeSS suite to Intel's standards as we aim to give users a choice of all modern technologies. Currently AMD's FSR solutions work better, but we want to show every solution as best we can, as an open-source reference for everyone else. The inclusion of XeSS can be advertised as you see fit. I am best contacted by my Discord ID "doodlum".
https://github.com/doodlum/skyrim-community-shaders/blob/xess-fg-attempt/src/Features/Upscaling/XeSS.cpp
XeSS upscaling is implemented but users complain of worse quality compared to FSR 3.1.5.
XeFG does not seem to work because XeLL says it's incompatible.
17:31:19:229 [17:31:19.221] [44836] [I] [XeSS FG] Latency Reduction is disabled
17:31:19:229 [17:31:19.221] [44836] [I] [XeSS FG] Latency reduction is not supported.
17:34:37:315 [17:34:37.140] [ 404 ] [I] [XeSS FG] xellAddMarkerData failed with: -4
17:34:37:315 [17:34:37.140] [ 404 ] [I] [XeSS FG] Failed to add interpolation start marker
17:34:37:315 [17:34:37.140] [ 404 ] [I] [XeSS FG] xellAddMarkerData failed with: -4
17:34:37:315 [17:34:37.140] [ 404 ] [I] [XeSS FG] Failed to add interpolation end marker
17:34:37:315 [17:34:37.141] [ 404 ] [W] [XeLL] Failed to add marker data, type: 1, error: -4
17:34:37:315 [17:34:37.141] [ 404 ] [W] [XeLL] Failed to add marker data, type: 2, error: -4
17:34:37:315 [17:34:37.157] [ 404 ] [I] [XeSS FG] xellAddMarkerData failed with: -4
17:34:37:315 [17:34:37.157] [ 404 ] [I] [XeSS FG] Failed to add interpolation start marker
17:34:37:315 [17:34:37.157] [ 404 ] [I] [XeSS FG] xellAddMarkerData failed with: -4
17:34:37:315 [17:34:37.157] [ 404 ] [I] [XeSS FG] Failed to add interpolation end marker
We want to fully implement the XeSS suite to Intel's standards as we aim to give users a choice of all modern technologies. Currently AMD's FSR solutions work better, but we want to show every solution as best we can, as an open-source reference for everyone else. The inclusion of XeSS can be advertised as you see fit. I am best contacted by my Discord ID "doodlum".
https://github.com/doodlum/skyrim-community-shaders/blob/xess-fg-attempt/src/Features/Upscaling/XeSS.cpp
XeSS upscaling is implemented but users complain of worse quality compared to FSR 3.1.5.
XeFG does not seem to work because XeLL says it's incompatible.
17:31:19:229 [17:31:19.221] [44836] [I] [XeSS FG] Latency Reduction is disabled
17:31:19:229 [17:31:19.221] [44836] [I] [XeSS FG] Latency reduction is not supported.
17:34:37:315 [17:34:37.140] [ 404 ] [I] [XeSS FG] xellAddMarkerData failed with: -4
17:34:37:315 [17:34:37.140] [ 404 ] [I] [XeSS FG] Failed to add interpolation start marker
17:34:37:315 [17:34:37.140] [ 404 ] [I] [XeSS FG] xellAddMarkerData failed with: -4
17:34:37:315 [17:34:37.140] [ 404 ] [I] [XeSS FG] Failed to add interpolation end marker
17:34:37:315 [17:34:37.141] [ 404 ] [W] [XeLL] Failed to add marker data, type: 1, error: -4
17:34:37:315 [17:34:37.141] [ 404 ] [W] [XeLL] Failed to add marker data, type: 2, error: -4
17:34:37:315 [17:34:37.157] [ 404 ] [I] [XeSS FG] xellAddMarkerData failed with: -4
17:34:37:315 [17:34:37.157] [ 404 ] [I] [XeSS FG] Failed to add interpolation start marker
17:34:37:315 [17:34:37.157] [ 404 ] [I] [XeSS FG] xellAddMarkerData failed with: -4
17:34:37:315 [17:34:37.157] [ 404 ] [I] [XeSS FG] Failed to add interpolation end marker
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Waited too long on this. Had to release and noted the complete lack of Support by Intel via the Intel® Game Developer Program
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @doodylum this community is not being monitored by Support Engineers anymore, only by the community
Please submit your report through the support page of the affected product through Support Tickets or go to IGCIT
This requirement was posted in our README in August.
If you reach out to us through any of the proposed channels, I'm sure we can do something to assist you
Regards
Karen

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page