OGRE 1.8

Everything about development and the OpenMW source code.
User avatar
lgromanowski
Site Admin
Posts: 1193
Joined: 05 Aug 2011, 22:21
Location: Wroclaw, Poland
Contact:

Re: OGRE 1.8

Post by lgromanowski » 24 Mar 2012, 21:02

Greendogo wrote:Here's Ogre's page about what to do with bugs. If you haven't already registered on their forums, you should, since each one of you is working on an Ogre related project and this also gives you access to posting bugs in their bug tracker.
http://www.ogre3d.org/mantis/view.php?id=517
best regards,
Lukasz

EmbraceUnity
Posts: 28
Joined: 24 Oct 2011, 04:41

Re: OGRE 1.8

Post by EmbraceUnity » 25 Mar 2012, 20:47

Does using OGRE 1.8 mean we automatically get DX11 support? Will that be an option in the launcher?

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

Re: OGRE 1.8

Post by scrawl » 25 Mar 2012, 20:49

No.

DX11 has removed fixed function, therefore OpenMW in it's current state wouldn't work with it.

User avatar
WeirdSexy
Posts: 611
Joined: 15 Sep 2011, 18:50
Location: USA

Re: OGRE 1.8

Post by WeirdSexy » 26 Mar 2012, 02:45

Haha DX11 support in Morrowind would be awesome

I want to see OpenMW with HDR rendering, simulated global illumination, object motion blur, depth of field, sub surface scattering, parallax mapping, volumetric smoke and clouds, soft body physics, cloth simulation, and hardware tessellation.

No rush though, whenever you guys get around to it ;)

User avatar
sirherrbatka
Posts: 2159
Joined: 07 Aug 2011, 17:21

Re: OGRE 1.8

Post by sirherrbatka » 26 Mar 2012, 05:04

OpenGL works as well, you know? ;-)

ezzetabi
Posts: 407
Joined: 03 Feb 2012, 16:52

Re: OGRE 1.8

Post by ezzetabi » 26 Mar 2012, 12:15

Can anyone explain why supporting the DirectX n (where n is usually 9,10 or 11) is somewhat important? I genuinely confused. Supporting a particular DirectX changes something? Make something easier or harder to implement? What gives?

Chris
Posts: 1583
Joined: 04 Sep 2011, 08:33

Re: OGRE 1.8

Post by Chris » 26 Mar 2012, 12:53

ezzetabi wrote:Can anyone explain why supporting the DirectX n (where n is usually 9,10 or 11) is somewhat important? I genuinely confused. Supporting a particular DirectX changes something? Make something easier or harder to implement? What gives?
Newer DirectX versions typically expose new functionality, or more efficient ways to do pre-existing functionality. Unlike OpenGL, a given DirectX version doesn't really have a way to provide new functions without breaking ABI, and it's very limited in being able to extend beyond what the version originally defined.

So while you could use OpenGL 2.1 and add in extra support for geometry shaders on capable hardware, for example, you can't just use DirectX9 and add support for geometry shaders. It requires fully updating the renderer to DirectX10 or 11.

User avatar
psi29a
Posts: 4915
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: OGRE 1.8

Post by psi29a » 27 Mar 2012, 14:31

I finally got mygui 3.2 and ogre 1.8 up and running and decided to check out 'next' branch of openmw.git , sadly while compiling I get this error message:

[ 0%] Building CXX object components/CMakeFiles/components.dir/bsa/bsa_archive.cpp.o
/home/brick/workspace/OpenMW/openmw/components/bsa/bsa_archive.cpp: In member function ‘virtual Ogre::Archive* {anonymous}::BSAArchiveFactory::createInstance(const String&)’:
/home/brick/workspace/OpenMW/openmw/components/bsa/bsa_archive.cpp:347:31: error: cannot allocate an object of abstract type ‘{anonymous}::BSAArchive’
/home/brick/workspace/OpenMW/openmw/components/bsa/bsa_archive.cpp:220:7: note: because the following virtual functions are pure within ‘{anonymous}::BSAArchive’:
/usr/include/OGRE/OgreArchive.h:228:33: note: virtual Ogre::FileInfoListPtr Ogre::Archive::findFileInfo(const String&, bool, bool) const
/home/brick/workspace/OpenMW/openmw/components/bsa/bsa_archive.cpp:348:3: warning: control reaches end of non-void function [-Wreturn-type]
make[2]: *** [components/CMakeFiles/components.dir/bsa/bsa_archive.cpp.o] Error 1
make[1]: *** [components/CMakeFiles/components.dir/all] Error 2
make: *** [all] Error 2
Any help around this issue?

User avatar
Zini
Posts: 5538
Joined: 06 Aug 2011, 15:16

Re: OGRE 1.8

Post by Zini » 27 Mar 2012, 14:33

The next branch is still using OGRE 1.7. Not compatible with OGRE 1.8.

User avatar
psi29a
Posts: 4915
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: OGRE 1.8

Post by psi29a » 27 Mar 2012, 14:45

Zini wrote:The next branch is still using OGRE 1.7. Not compatible with OGRE 1.8.
OK, good to hear. Is there a branch that does use 1.8 ?

Post Reply