Skip to content

[Runtime Feature]: Ability to configure the RemixAPIs target layer. #1076

Description

@RuneStorm

What is the context of the feature/improvement?

I am currently using the RemixAPI to set fog values and other defaults when loading a map, however this will clash with logic graphs since the way configs are layered.
Mark explained to me that the rtx.conf is below the logic configs, with the user.conf being above all.
At the moment the API will set properties as the user layer which would override the logic graphs, effectively preventing me from using them to drive things like underwater effects or the like entirely.

Please describe the feature/improvement?

Please adjust the remix api layer or expose an option to change which layer the api would write to. I.e. rtx.conf instead of user.conf so that logic graphs can override values.

What would be your solution? (optional)

I'll forward the message from NV_Mark as he found the line of code that would need to be changed, however an added option to change if the API should write to rtx.conf, logic.conf or user.conf layers would be greatly appreciated.

NV_Mark
it'd be easy to hack the API to just set into the derived layer(under Logic layers but above rtx.conf layer) instead of the user layer. just replace
dxvk::RtxOptionLayer::getUserLayer

with
dxvk::RtxOptionLayer::getDerivedLayer

in src\dxvk\rtx_render\rtx_remix_api.cpp (line 1263 in the version I have checked out right now)

Version

1.5.2

Media

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature or functionality to add to Remix.runtimeRTX Remix runtimetriage

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions