Bem-vindos ao GTA5-Mods.com

Next, could you add a feature similar to the data addition functionality when installing OIV to OpenIV, writing its XML to the local machine? For example, some OIVs can directly write item data into the ytyp file in the direct path. When unzipping the OIV to the local machine, could you also read the data from assembly.xml and create and write it to the corresponding XML file in the appropriate path?

@MagicOG I see your instructions, when decompressing to local, it is multi-level nesting, because the decompression itself is for easy viewing, so it is better to use A-B-c to represent the path, and then put the corresponding file in it

@MagicOG Thanks, I tried, it seems to be a bit of a problem, there is no difference between nester and flat, both put all files in the root path, it should read the path level of assembly.xml file to place the file.

Why does pressing L have no effect, I am the legoin version

2.0 is the same as the cs file of 1.1

Another issue is, could you avoid packaging all the dependency libraries into a single application? These are all built-in dependency libraries from Microsoft systems, which would make your application extremely large.

@MagicOG oh，This feature is also quite good. Perhaps I haven't explained it clearly. Currently, when opening an OIV file, it extracts it to a temporary directory. An additional button function could be added, such as local installation. It functions similarly to the original OpenIV installation of OIV files, extracting files locally according to the original installation path. For example, if the path to gameconfig.xml is update.rpf-x64-common-data when installing using OpenIV, this feature can extract the files within the OIV file to the local machine without relying on OpenIV, maintaining the original path style. It will create a folder named "update.rpf-x64-common-data" in the extraction path, and then place gameconfig.xml inside the "update.rpf-x64-common-data" folder. There's no need to create nested folders; just use the path names. This is very effective for unpacking older OIV files and very complex assme.xml files, as these files may be outdated.

@MagicOG Is it an open OIV feature?

I think you shouldn‘t package all the dependencies into one program; it's too large. After decompression, it's already like software built with Electron. Many are Microsoft's built-in runtime libraries; if they're not present at runtime, it will prompt to download and install them, so don't worry about beginners not knowing how to use it.

If I use the RageOpenV_MoreLogs version but disable all logging in the configuration file, will the performance be the same as the regular RageOpenV version?