OpenMW 0.31.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
raevol
Posts: 3093
Joined: 07 Aug 2011, 01:12
Location: Caldera

Re: OpenMW 0.31.0

Post by raevol »

https://gist.github.com/mickeylyle/a804 ... /revisions
scrawl wrote:Draugr is still spelled wrong and #1216 is not mentioned.
Fixed Draugr (thanks) and #1216 is covered: - Fixed several dialog link issues
Zini wrote:#1567 was fixed.
Thanks, added.
User avatar
scrawl
Posts: 2152
Joined: 18 Feb 2012, 11:51

Re: OpenMW 0.31.0

Post by scrawl »

#1216 is covered: - Fixed several dialog link issues
But that was actually a game breaking bug, so it would be nice to have a separate item.
User avatar
raevol
Posts: 3093
Joined: 07 Aug 2011, 01:12
Location: Caldera

Re: OpenMW 0.31.0

Post by raevol »

scrawl wrote:But that was actually a game breaking bug, so it would be nice to have a separate item.
Oookaaaay. ;) https://gist.github.com/mickeylyle/a804 ... /revisions
HiPhish
Posts: 323
Joined: 02 Jul 2012, 08:36

Re: OpenMW 0.31.0

Post by HiPhish »

corristo wrote:Is it possible to run OpenCS under debugger? You should have lldb or gdb available.
Is this what you need?

Code: Select all

lldb OpenCS 
Current executable set to 'OpenCS' (x86_64).
(lldb) run
Process 19657 launched: '/Volumes/OpenMW-0.31.0-Darwin/OpenMW/OpenCS.app/Contents/MacOS/OpenCS' (x86_64)
Loading config file: /Users/hiphish/Library/Preferences/openmw/openmw.cfg... done.
Loading config file: ./openmw.cfg... done.
2014-07-10 23:40:40.231 OpenCS[19657:d0b] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
Data dir /Users/hiphish/Library/Application Support/OpenMW/Data Files/Data Files
Adding BSA archive /Users/hiphish/Library/Application Support/OpenMW/Data Files/Data Files/Morrowind.bsa
2014-07-10 23:40:41.802 OpenCS[19657:d0b] invalid drawable
Process 19657 exited with status = 1 (0x00000001) 
(lldb) exit
SquireNed
Posts: 403
Joined: 21 Dec 2013, 22:18

Re: OpenMW 0.31.0

Post by SquireNed »

Lazaroth wrote:One thing I noticed is that whenever you coc, you face 180° wrong.

I'm also getting a crash when switching from fullscreen to window.
win 8.1 64-bit
Attached the log.

I *think* the error is this;
09:04:03: OGRE EXCEPTION(3:RenderingAPIException): Unable to disable texture '0' in D3D9 in D3D9Device::clearDeviceStreams at ..\..\..\Source\RenderSystems\Direct3D9\src\OgreD3D9Device.cpp (line 630)
Lazaroth's errors confirmed on Windows 8.1

Also, my shaders don't compile in DirectX (at least, so sayeth the console), turning almost everything orange and some other things shades of green and red. Turning on shadows causes an immediate CTD.
corristo
Posts: 495
Joined: 12 Aug 2011, 08:29

Re: OpenMW 0.31.0

Post by corristo »

HiPhish wrote: Is this what you need?
what about backtrace?
HiPhish
Posts: 323
Joined: 02 Jul 2012, 08:36

Re: OpenMW 0.31.0

Post by HiPhish »

How do i do that? I'm not a programmer, but I do know how to use the Terminal. I just don't know what to do with LLDB, what commands to give it.
corristo
Posts: 495
Joined: 12 Aug 2011, 08:29

Re: OpenMW 0.31.0

Post by corristo »

You can write "backtrace" command in lldb console when execution pauses because of fatal error.
There's corresponding command in gdb as well.
User avatar
Zini
Posts: 5538
Joined: 06 Aug 2011, 15:16

Re: OpenMW 0.31.0

Post by Zini »

Okay, where are we standing? From what I see we have two issues:

- An OpenMW crash on Windows (definitely not a release blocker). Is this reproducable enough, that we should add it to the known issues?

- An OpenCS crash on OS X. Not reproducible, I believe? In this case this would also not be a release blocker.
User avatar
Lazaroth
Posts: 220
Joined: 30 May 2012, 05:04

Re: OpenMW 0.31.0

Post by Lazaroth »

Zini wrote: - An OpenMW crash on Windows (definitely not a release blocker). Is this reproducable enough, that we should add it to the known issues?
One person confirmed the crash on 8.1 and one said he didn't experience it on 7. One or two more windows users testing this should settle it. Preferably one with 8.1 and one without.
Post Reply