?Greendogo wrote:Is there an issue on the tracker for this crash?
OpenMW 0.30.0
Re: OpenMW 0.30.0
Re: OpenMW 0.30.0
Thanks! I found that earlier today, and apparently forgot about it and how to use the search feature...
Re: OpenMW 0.30.0
By the way, 1eabd71 version of x64 ffplay crashes with *all* videos in Data Files\Video, not just the intro. The strange thing is that openmw doesn't always crash - which may imply that our sound code is subtly different to ffplay (and perhaps a possibility exists for working around the issue)
EDIT: Did some digging around, it is this commit that changed format from s16 to fltp, apparently on Tuesday September 18 2012.
EDIT2: Been doing some testing with 0.30.0. ffmpeg-20120914-git-8bdba0b-win64-shared.7z and ffmpeg-20120914-git-8bdba0b-win64-dev.7z are the last builds that uses the old format (I checked by comparing the source files libavcodec/binkaudio.c). They seem to work fine without crashing on Windows x64. This might be an option until we get some new code written for latest ffmpeg. Updated the wiki accordingly.
EDIT3: Unfortunately 8bdba0b-win64 with the current master results in crashes. Not a viable solution.
EDIT4: I may have been too quick in blaming ffmpeg. The stack trace shows MWWorld::CellStore::getCell() trying to access a null pointer (or some garbage address), so it appears to be an issue with the current master, unrelated to ffmpeg. <deleted stacktrace>
EDIT5: F2> playbink "mw_intro.bik" 1 (and other videos) plays fine with the current master. (of course, had to load a saved game to be able to test that)
EDIT6: Minor fix seems to address the issue with the master.
EDIT: Did some digging around, it is this commit that changed format from s16 to fltp, apparently on Tuesday September 18 2012.
EDIT2: Been doing some testing with 0.30.0. ffmpeg-20120914-git-8bdba0b-win64-shared.7z and ffmpeg-20120914-git-8bdba0b-win64-dev.7z are the last builds that uses the old format (I checked by comparing the source files libavcodec/binkaudio.c). They seem to work fine without crashing on Windows x64. This might be an option until we get some new code written for latest ffmpeg. Updated the wiki accordingly.
EDIT3: Unfortunately 8bdba0b-win64 with the current master results in crashes. Not a viable solution.
EDIT4: I may have been too quick in blaming ffmpeg. The stack trace shows MWWorld::CellStore::getCell() trying to access a null pointer (or some garbage address), so it appears to be an issue with the current master, unrelated to ffmpeg. <deleted stacktrace>
EDIT5: F2> playbink "mw_intro.bik" 1 (and other videos) plays fine with the current master. (of course, had to load a saved game to be able to test that)
EDIT6: Minor fix seems to address the issue with the master.
Re: OpenMW 0.30.0
Where do we stand on this? I see the release is re-started, but are we re-building the release packages?
Re: OpenMW 0.30.0
I'm off at my parents, celebrating my mothers birthday. And while I could run a release build remotely, I want to be able to test it myself considering the issues we've been having.
So no release builds from me until late tomorrow at the earliest.
So no release builds from me until late tomorrow at the earliest.
Re: OpenMW 0.30.0
OS X release build:
https://dl.dropboxusercontent.com/u/284 ... 0.30.0.dmg
https://dl.dropboxusercontent.com/u/284 ... 0.30.0.dmg
- psi29a
- Posts: 5357
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: OpenMW 0.30.0
Waiting for the Debian lords to bless us.
I'll handle the PPAs tomorrow (Monday).
Update: Debian is having issues with libboost 1.55, so we're waiting until the dust has settled before uploading.
I'll handle the PPAs tomorrow (Monday).
Update: Debian is having issues with libboost 1.55, so we're waiting until the dust has settled before uploading.
Re: OpenMW 0.30.0
Right, I've now switched to another FFMPEG version. And done a test build on master, so let's see about getting some new release builds done.
Re: OpenMW 0.30.0
ACE, the latest master will need a small change to build (link). I'll be sending a PR shortly.
EDIT: oops, you beat me to it, I'll close mine.
EDIT: oops, you beat me to it, I'll close mine.