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.

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

[Feature] Cross-file data references #1620

Open
1 task
Zekfad opened this issue Mar 28, 2024 · 3 comments
Open
1 task

[Feature] Cross-file data references #1620

Zekfad opened this issue Mar 28, 2024 · 3 comments

Comments

@Zekfad
Copy link

Zekfad commented Mar 28, 2024

What feature would you like to see?

I have a file structure where header and aux files are separated.
To make use of visualizers (e.g. view texture) I need to load header, read offset of aux file and display it.
I don't see any way to reference data across multiple files in data processor or pattern language.

How will this feature be useful to you and others?

This will make it easier to reverse-engineer partial files, e.g. multi-part archives.

Request Type

  • I can provide a PoC for this feature or am willing to work on it myself and submit a PR

Additional context?

No response

@paxcut
Copy link
Contributor

paxcut commented Mar 28, 2024

The pattern language allows you to open and read files from your disk. The contents of the file can be written to its own section independent of the input file. You can place patterns in the section and copy data from one section to any other section. Note that the input file itself is also considered a section. For 3-d visualization textures (currently only one texture per model) can be read from disk, but the file must contain the texture only and be in one of the image formats supported.

@Zekfad
Copy link
Author

Zekfad commented Mar 28, 2024

Thank you for response, missed that part of pattern language. Not quite sure what you mean by sections (structs?). I've expected to have some node in data processor actually to do that.

But now that you mentioned it, I think it's possible to use out var and read node perhaps?

As for textures I'm looking for a way to load DDS structure (I have DDS header in main file and DDS contents in an aux file), I think I can combine them via buffer ops in data processor, but I still need to preprocess data to be able to feed it to visualizer.

@paxcut
Copy link
Contributor

paxcut commented Mar 28, 2024

About sections.
The set of formats supported are the ones from stb. I think DDS are not included for technical problems although there have been attempted. There are many options to convert DDS textures to format supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants