Hey guys... been awhile, but still around and lurking.
We at OpenMW have been busy bees but wanted to reach out TR on a few things to see if we can make your lives easier.
This is a call out to all modders and game makers over an OpenMW Merge Tool. We need your input! What are the things you guys need and/or would like to have to make your lives easier when working with things like leveled lists, merge conflicts and etc.
Content from my PM with Zini
Sent: 15 Jul 2018, 10:01
Hey, do you still have contacts at TR? With Redemption gone they should be the biggest user of our merge tool. Might be a good idea to have them weight in on this discussion: https://forum.openmw.org/viewtopic.php?f=39&p=56665#p56665
What do you guys think?
Cheers!
2016-10-09 23:10
6 days 13 hours ago
Here's a link to our Discord, we're extremely active there: https://discordapp.com/invite/9T6TtNU
Also, here's Project Tamriel's (who we work with closely): https://discord.gg/waZcqnF
2015-09-28 20:13
2 years 6 months ago
Hi psi29a, good to see you are around still.
I'll reply directly in the OpenMW forum (same name), but for completion's sake, I'll post my reply here too.
Our workflow seems to be a bit different from that of Redemption.
As our assets are kept in the Tamriel_Data.esm and BSAs, modders just make esps adding to or overriding assets. They are first merged in a TR and PT data addon esp and merged into the real Tamriel Data later. Deletion notices are placed in text form and the lead developer tasked with merging the files has to go and do these manually. This is PT's call, as they have been leading efforts on Tamriel_Data.
The claim workflow is similarily compartmentalised: first we cut our heightmap files (TR_RestExterior) into section files, chop off worldspace bits (3x3 cells or larger) and then put them out for developers to claim. There's some border (landscape) matching happening at this stage, but that is between individual modders and claims and the esps themself never exceed their original cell boundaries.
Interiors are similarily posted and developed individually: one interior, one claim. They have temporary names until they are merged back into the section files.
Both exterior and interiors are stitched together into the section file. As these files are either using assets implemented globally in Tamriel_Data or claim-specific ones (using existing assets but a unique ID), there are (theoretically) no ID or cell conflicts.
Once exteriors and interiors are finished enough, we have NPC/Dialogue and quest claims, which is where the merge complexity actually comes in.
What I would really like:
2014-03-16 17:45
1 year 10 months ago