OpenGEX as .Nif alternative for OpenMW

General discussion regarding the OpenMW project.
For technical support, please use the Support subforum.
User avatar
AnyOldName3
Posts: 540
Joined: 26 Nov 2015, 03:25

Re: OpenGEX as .Nif alternative for OpenMW

Post by AnyOldName3 » 14 Aug 2017, 23:48

Well, I've finished learning the series of OSG tutorials I was looking at now. Maybe making an OSG plugin for that might be a good project to do.

Wolvman
Posts: 18
Joined: 30 Apr 2012, 15:57

Re: OpenGEX as .Nif alternative for OpenMW

Post by Wolvman » 15 Aug 2017, 02:00

+1 from me if that helps to sway the vote any. Nif files are the bane of my existence. I'd be jumping into model development far more often if we had a better file format to work with.
Last edited by Wolvman on 15 Aug 2017, 19:57, edited 1 time in total.

User avatar
psi29a
Posts: 3432
Joined: 29 Sep 2011, 10:13
Github profile: https://github.com/psi29a/
Contact:

Re: OpenGEX as .Nif alternative for OpenMW

Post by psi29a » 15 Aug 2017, 17:56

That sounds wonderful and the right way to go. Creating and maintaining an osg plugin helps not just OpenMW...

User avatar
scrawl
Posts: 2076
Joined: 18 Feb 2012, 11:51
Contact:

Re: OpenGEX as .Nif alternative for OpenMW

Post by scrawl » 25 Aug 2017, 13:02

After seeing Eric's comparison of OpenGEX vs. glTF, I wanted to add NIF and .osg to that comparison. The result can be seen here. I wrote this off the top of my head, so there may be some mistakes.
Open Game Engine Exchange.html.zip
(9.31 KiB) Downloaded 44 times

User avatar
psi29a
Posts: 3432
Joined: 29 Sep 2011, 10:13
Github profile: https://github.com/psi29a/
Contact:

Re: OpenGEX as .Nif alternative for OpenMW

Post by psi29a » 25 Aug 2017, 13:08

Nice work, have you asked to see if this gets included?

Can this be published to our wiki or in our documentation?

User avatar
AnyOldName3
Posts: 540
Joined: 26 Nov 2015, 03:25

Re: OpenGEX as .Nif alternative for OpenMW

Post by AnyOldName3 » 25 Aug 2017, 14:35

Right, so we design a binary representation of OpenGEX, and then we have everything we could ever want for OpenMW until someone makes a new game or total asset replacement using PBR.

In the event that I start meddling with this, is it a better idea to make it something OSG can load or something OpenMW can load?

User avatar
scrawl
Posts: 2076
Joined: 18 Feb 2012, 11:51
Contact:

Re: OpenGEX as .Nif alternative for OpenMW

Post by scrawl » 25 Aug 2017, 15:16

Right, so we design a binary representation of OpenGEX, and then we have everything we could ever want for OpenMW until someone makes a new game or total asset replacement using PBR.
Unfortunately, none of these aspirings standards seem to include support for particles, so we'd still need NIF/OSG for that. It would also be nice to have some form of user data in these formats, in the event that we want to add tags for engine-specific stuff.
In the event that I start meddling with this, is it a better idea to make it something OSG can load or something OpenMW can load?
Probably the latter, as we don't use the OSG animation system. Once we have such plugin, it should be possible to port it over to "plain OSG" if needed. (If we skipped animations, the OMW vs. OSG version would be identical)


User avatar
scrawl
Posts: 2076
Joined: 18 Feb 2012, 11:51
Contact:

Re: OpenGEX as .Nif alternative for OpenMW

Post by scrawl » 02 Sep 2017, 10:10

For what it's worth, commits 209e139aa89015cad87b39dc160f9a5af0998040..5e790b567e460de29bea43ec5410822db58a6e57 greatly streamlines the animation component so it should be easier to write an <insert format here> importer or extend the .osg format. Here's roughly how I'd do it:

- Move KeyframeController out of nifosg into a component (e.g. sceneutil) and make it not depend on NifOsg::NodeUserData
- Add support for other types of keyframes as needed
- Move TextKeyMap out of nifosg into a component

At this point we could start writing importers or exporters.

As for extending the osg format, one might be able to pick up some of the pieces of https://github.com/OpenMW/openmw/pull/844 , or use it as an example.

Another issue is providing a separate collision mesh. We could use a separate file for that or use tags in the visual file to denote a mesh as a collision mesh. Aside from collision meshes it would be nice to support shapes (e.g. MultiSphereShape) because they're much faster to process than triangle meshes. I believe bullet's btWorldImporter has a file format but I haven't really looked into how usable it is.

User avatar
psi29a
Posts: 3432
Joined: 29 Sep 2011, 10:13
Github profile: https://github.com/psi29a/
Contact:

Re: OpenGEX as .Nif alternative for OpenMW

Post by psi29a » 02 Sep 2017, 12:36

Nice work Scrawl and thank you for getting us this far! :D

Post Reply

Who is online

Users browsing this forum: No registered users and 5 guests