OpenMW 0.36.0

Anything related to PR, release planning and any other non-technical idea how to move the project forward should be discussed here.
Post Reply
User avatar
Zini
Posts: 5536
Joined: 06 Aug 2011, 15:16

OpenMW 0.36.0

Post by Zini » 24 Feb 2015, 18:20

No, this isn't the 0.36.0 posting. Sorry for it being delayed a bit. Will get to it in a few days or so.

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

Re: OpenMW 0.36.0

Post by psi29a » 24 Feb 2015, 18:59

:lol:

matthewfarmery
Posts: 51
Joined: 03 Feb 2015, 13:27

Re: OpenMW 0.36.0

Post by matthewfarmery » 24 Feb 2015, 20:33

as long as its not delayed too long, like a certain game from Rockstar (GTA V)

but anyway, you all making good progress, and 0.35 has been a real joy to play!

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

Re: OpenMW 0.36.0

Post by psi29a » 24 Feb 2015, 20:53

matthewfarmery wrote:as long as its not delayed too long, like a certain game from Rockstar (GTA V
We're not paid a salary... so I hope for a little slack on that front. ;)

matthewfarmery
Posts: 51
Joined: 03 Feb 2015, 13:27

Re: OpenMW 0.36.0

Post by matthewfarmery » 24 Feb 2015, 21:01

I was saying that as a joke, and just really saying that this project deserves full support and better then many full priced so called titles out there. still, 0.35 is really stable so far, (apart from one issue that been fixed) so a bit of a delay isn't too bad for this, as it this game has quality written all over it!

onionland
Posts: 61
Joined: 29 Jul 2014, 00:43

Re: OpenMW 0.36.0

Post by onionland » 25 Feb 2015, 06:21

matthewfarmery wrote:I was saying that as a joke, and just really saying that this project deserves full support and better then many full priced so called titles out there. still, 0.35 is really stable so far, (apart from one issue that been fixed) so a bit of a delay isn't too bad for this, as it this game has quality written all over it!
Well the game itself is 13 years old, but yes, the effort that goes into the openmw engine is quite impressive.

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

Re: OpenMW 0.36.0

Post by psi29a » 27 Feb 2015, 10:46

A recent pull and build has resulted in a segfault in openmw-cs, for the record, this worked just yesterday:

Code: Select all

[email protected]:~/workspace/OpenMW/build$ gdb ./openmw-cs
GNU gdb (Ubuntu 7.8-1ubuntu4) 7.8.0.20141001-cvs
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./openmw-cs...done.
(gdb) run
Starting program: /home/bcurtis/workspace/OpenMW/build/openmw-cs 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe1ad2700 (LWP 580)]
[New Thread 0x7fffe12d1700 (LWP 581)]
[New Thread 0x7fffe0ad0700 (LWP 582)]
[New Thread 0x7fffd3fff700 (LWP 583)]
[New Thread 0x7fffd37fe700 (LWP 584)]
Loading config file: /home/bcurtis/.config/openmw/openmw.cfg... done.
Loading config file: ./openmw.cfg... done.
Data dir /home/bcurtis/.wine/drive_c/aoa/Data Files
Data dir /home/bcurtis/.local/share/openmw/data
Detected unclean shutdown.
[New Thread 0x7fffbcee4700 (LWP 585)]
[New Thread 0x7fffbc6e3700 (LWP 586)]
[New Thread 0x7fffbbee2700 (LWP 587)]
[New Thread 0x7fffbb6e1700 (LWP 588)]
[Thread 0x7fffe0ad0700 (LWP 582) exited]

Program received signal SIGSEGV, Segmentation fault.
CSVDoc::FileDialog::slotUpdateAcceptButton ([email protected]=0x7fffffffdb38, name=...)
    at /home/bcurtis/workspace/OpenMW/openmw/apps/opencs/view/doc/filedialog.cpp:159
159	        mAdjusterWidget->setName (file->filePath(), !file->isGameFile());
(gdb) bt
#0  CSVDoc::FileDialog::slotUpdateAcceptButton ([email protected]=0x7fffffffdb38, name=...)
    at /home/bcurtis/workspace/OpenMW/openmw/apps/opencs/view/doc/filedialog.cpp:159
#1  0x00000000006d3fb6 in CSVDoc::FileDialog::slotUpdateAcceptButton (this=0x7fffffffdb38)
    at /home/bcurtis/workspace/OpenMW/openmw/apps/opencs/view/doc/filedialog.cpp:145
#2  0x0000000000742d9b in CSVDoc::FileDialog::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, 
    _c=<optimized out>) at /home/bcurtis/workspace/OpenMW/build/apps/opencs/view/doc/moc_filedialog.cxx:71
#3  0x00007ffff4bc8a7a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x00000000008685ae in ContentSelectorView::ContentSelector::signalCurrentGamefileIndexChanged (this=<optimized out>, _t1=0)
    at /home/bcurtis/workspace/OpenMW/build/components/contentselector/view/moc_contentselector.cxx:110
#5  0x00007ffff4bc8a7a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x00007ffff5800ef1 in QComboBox::currentIndexChanged(int) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#7  0x00007ffff5800f51 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#8  0x00007ffff580125b in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#9  0x00007ffff5801386 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#10 0x00007ffff4bc8a7a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x00007ffff5a88e12 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#12 0x00007ffff57fcc0d in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x00007ffff4bb49d6 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#14 0x00007ffff542f0fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
---Type <return> to continue, or q <return> to quit---
#15 0x00007ffff54359be in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#16 0x00000000005bb696 in Application::notify (this=<optimized out>, receiver=<optimized out>, event=<optimized out>)
    at /home/bcurtis/workspace/OpenMW/openmw/apps/opencs/main.cpp:32
#17 0x00007ffff4bb486d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#18 0x00007ffff543507f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#19 0x00007ffff54aaf6d in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#20 0x00007ffff54aa477 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#21 0x00007ffff54d2432 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#22 0x00007ffff21a2c5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007ffff21a2f48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007ffff21a2ffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007ffff4be2031 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#26 0x00007ffff54d24e6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#27 0x00007ffff4bb34f1 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#28 0x00007ffff4bb3805 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#29 0x00007ffff4bb8f67 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#30 0x000000000057c014 in main (argc=1, argv=<optimized out>) at /home/bcurtis/workspace/OpenMW/openmw/apps/opencs/main.cpp:92

User avatar
cc9cii
Posts: 471
Joined: 28 Mar 2013, 04:01

Re: OpenMW 0.36.0

Post by cc9cii » 28 Feb 2015, 05:53

Initial guess without any justification is commit 6878e317. Will dig further.

EDIT: Wrong. It is commit 9d61457956e35b56dfbf24e9cab8a532cad61591. The logic change to hide game files apparently doesn't work well with OpenCS.

dteviot
Posts: 144
Joined: 17 Dec 2014, 20:29

Re: OpenMW 0.36.0

Post by dteviot » 01 Mar 2015, 20:25

@Zini
@cc9cii
This IS my mistake.

I included this line in the pull by mistake.
file: "components/contentselector/model/contentmodel.cpp" line 115, where I replaced

Code: Select all

return Qt::ItemIsEnabled | Qt::ItemIsSelectable | Qt::ItemIsUserCheckable;
with

Code: Select all

return Qt::NoItemFlags;
It was part of something else I was trying that didn't work and I failed to clean it up properly.
I believe if you restore the line
return Qt::ItemIsEnabled | Qt::ItemIsSelectable | Qt::ItemIsUserCheckable;
the problem should be fixed.

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

Re: OpenMW 0.36.0

Post by Zini » 22 Mar 2015, 11:57

Oops. This is late. Really late. Anyway, let's get started with the 0.36.0 release planning posting ...

We are in a different situation now. The main point is the rending engine port. On the OpenMW side we don't have a lot else going on. There is of course as usual some bug fixing. But that's about it. Looking at the roadmap it seems we have only just enough open OpenMW features left to justify one more feature release. Since most of these tasks are rather tricky and both scrawl and I are currently busy with other issues I consider it unlikely that we will be able to put out another OpenMW feature release before the engine port is done.

Of course there is also OpenMW-CS. Depending on how long the engine porting takes we might be able to have a 0.36.0 OpenMW-CS feature release instead with bits of OpenMW features and some bug fixing sprinkled in.

During most of 0.35.0 OpenMW-CS had progressed extremely slow (which was both my fault and the result of barely anyone else doing any work on it). I thought I would have to issue another call to arms in this posting, but luckily OpenMW-CS has picked up since then. Of course we could still use some more manpower.

As mentioned above the slow progress during 0.35.0 was largely my fault. I was distracted with other things, including an irritating addiction with Emacs customizing. Yep, that's about 30 hours of my life that I will never get back. 30 hours that could have gone towards OpenMW-CS instead. Sorry!

I think I have mostly overcome this addiction and most of the other stuff is also out of the way. I should be able to contribute a decent amount of code fore 0.36.0 and hopefully also my response times to PR and forum postings will pick up again.

That being said with the OpenMW/OSG situation I don't think we can set a release date for 0.36.0 at this point. For the time being let's role with it and see how it goes.

Post Reply