ERROR: bad lexical cast

Support for running, installing or compiling OpenMW

Before you submit a bug report for the first time, please read: Bug reporting guidelines
User avatar
bwrsandman
Posts: 45
Joined: 25 Sep 2011, 05:30
Location: Montreal
Contact:

ERROR: bad lexical cast

Post by bwrsandman »

OpenMW won't launch on my boxes since this merge.
https://github.com/zinnschlag/openmw/co ... 1f47891a48

Code: Select all

Loading config file: /home/sandy/.config/openmw/openmw.cfg... done.
Loading config file: ./openmw.cfg... done.
Loading config file: /etc/openmw/openmw.cfg... done.
Using default (English) font encoding.
Data dir /home/sandy/openmw/Data Files

ERROR: bad lexical cast: source type value could not be interpreted as target

Code: Select all

Arch Linux
boost 1.52.0-1
openal 1.15.1-1
ogre 1.8.1-3
mygui 3.2.0-4
bullet 2.81-2
mpg123 1.15.1-1
libsndfile 1.0.25-2
qt4 4.8.4-13
ffmpeg 1:1.1.3-1
git 1.8.1.5-1
cmake 2.8.10.2-5
User avatar
pvdk
Posts: 528
Joined: 12 Aug 2011, 16:34

Re: ERROR: bad lexical cast

Post by pvdk »

It's because you haven't run the ini importer, but in my opinion openmw shouldn't fail so horribly.
User avatar
bwrsandman
Posts: 45
Joined: 25 Sep 2011, 05:30
Location: Montreal
Contact:

Re: ERROR: bad lexical cast

Post by bwrsandman »

OK. Had to fetch an .ini file on another drive. Thanks!

This did it for me:

Code: Select all

mwiniimport Morrowind.ini ~/.config/openmw/openmw.cfg
User avatar
pvdk
Posts: 528
Joined: 12 Aug 2011, 16:34

Re: ERROR: bad lexical cast

Post by pvdk »

The launcher now asks you too if it finds a Morrowind.ini in the path above your data path, it even asks you which one to import from when it finds multiple.
User avatar
Zini
Posts: 5538
Joined: 06 Aug 2011, 15:16

Re: ERROR: bad lexical cast

Post by Zini »

But please keep in mind, that this only happen on the first run. We should be fine now, but anyone who has run intermediate development builds between 0.21.0 and 0.22.0 may need to manually re-run the importer from the command line (since we don't yet have the feature to run it explicitly from the launcher after the first run).
User avatar
bwrsandman
Posts: 45
Joined: 25 Sep 2011, 05:30
Location: Montreal
Contact:

Re: ERROR: bad lexical cast

Post by bwrsandman »

So anyone switching from 0.21 to the future 0.22 will be okay?

I know I was prompted to find an .ini file. When skipped it, it stopped asking.
User avatar
Zini
Posts: 5538
Joined: 06 Aug 2011, 15:16

Re: ERROR: bad lexical cast

Post by Zini »

Obviously you should not skip it. Maybe we should adjust the wording a bit.

But yeah, anyone going from OpenMW 0.21.0 to 0.22.0 should be okay.
User avatar
pvdk
Posts: 528
Joined: 12 Aug 2011, 16:34

Re: ERROR: bad lexical cast

Post by pvdk »

I could change it to "ask me next time" and then not set the firstrun flag to false?
User avatar
Zini
Posts: 5538
Joined: 06 Aug 2011, 15:16

Re: ERROR: bad lexical cast

Post by Zini »

I do not see how that would be of use. Why would the user want to delay the import?

I was thinking more of a warning that not having imported an ini file may cause problems.
User avatar
bwrsandman
Posts: 45
Joined: 25 Sep 2011, 05:30
Location: Montreal
Contact:

Re: ERROR: bad lexical cast

Post by bwrsandman »

An option to import from inside owmlauncher if the import didn't work when prompted.
Locked