Can not use 5 in savegame name???

[Tassidor]

Hello,

I just downloaded and installed version 1.80 of oolite (PC). I see a very strange effect - when entering a savgame name in the text box I can use all numbers but 5. When I hit the five key, the game returns to the status screen without saving.

I have a German keyboard, but did not modify the default setup (yet)

Any Idea? Is that a known .... feature?

[phkb]

Yes, it's a known bug, fixed in the next version. https://bb.oolite.space/viewtopic.php?f=3&t=16679

[Cody]

What he said - and welcome aboard!

[Tassidor]

Yes, it's a known bug, fixed in the next version. https://bb.oolite.space/viewtopic.php?f=3&t=16679

Hmm. Thanks 4 the answer ... but 1.80 is the latest version on oolite.org. (in both a developer and end user variant). Where do you get that fixed version? I'm afraid buying a windows compiler and installing a git client is a little out of question for my gaming box

[Cody]

You can download the latest nightly build (1.81) via this thread - the usual caveats apply, of course!

[Tassidor]

You can download the latest nightly build (1.81) via this thread - the usual caveats apply, of course!

havent found a working link in there yet (only checked first and last 2 pages, though)

BTW - how do you use MFDs? I have set up a few, but I only get messages
about "mfd x activated" when pressing shift-ö, but no actual MFD.

UPDATE nice, whoever fixed the link on pg 1 - it now works. thx.

[cim]

the usual caveats apply, of course!

I should add here, if you've not seen them before, the usual caveats are:

• The 1.81 nightly builds contain prototype features which have not yet been tested or debugged. You may have strange experiences, crashes, or odd OXP behaviour.
• 1.81 will read savegames from 1.80 just fine. 1.80 will not read a 1.81 savegame at all - so once you switch, you can't go back. Take a backup of your savegame first, at least.
• We assume that the 1.81 players - at least at this stage of the development process - are OXP developers wanting to try out new features, or intentional beta testers for the gameplay.

If you do use it, bug reports and general thoughts on the gameplay will be very welcome in the "Testing and Bug Reports" forum here.

On MFDs:
- that message is the one you get while selecting which MFD you need to use.
- press the key without shift (assuming default keymapping) to change that MFD slot between your available MFDs (or no MFD, which it currently is)
- depending on the OXP you may need to do something else to activate that OXP's MFD (e.g. buy equipment)

[Tassidor]

the usual caveats apply, of course!

I should add here, if you've not seen them before, the usual caveats are:

• The 1.81 nightly builds contain prototype features which have not yet been tested or debugged. You may have strange experiences, crashes, or odd OXP behaviour.

Thanks. For now ill try to work around the 5 bug for a while.

On MFDs:
- that message is the one you get while selecting which MFD you need to use.
- press the key without shift (assuming default keymapping) to change that MFD slot between your available MFDs (or no MFD, which it currently is)
- depending on the OXP you may need to do something else to activate that OXP's MFD (e.g. buy equipment)

No, that did NOT work. Unfortunately, that keymapping thing is broken.

In order to get it working the way you describe it, I did the following:

Code: Select all

// key_cycle_mfd		= ";";
// key_switch_mfd		= ":";
key_cycle_mfd			= 214; //  upper case O-Umlaut on German keyboard
key_switch_mfd			= 246; //  lower case o-Umlaut on German keyboard

Note that the broken key assignment mechanism should do the same,
but apparently doesn't (to be precise, it does the same for ";" but not for ":",
so on the default config, O-Umlaut works, o-Umlaut doesn't).

I call it broken because apparently there seems to be an internal hardcoded
table converting symbols to numbers - for US keyboards.

Normally you should just take the symbol keys from Windows and let the
underlying OS do the translation. But even if you don't , then please
make the translation table runtime loadable and configurable via the
options screen - independently from a user key remapping mechanism.

And speaking of which - you already have a quite good runtime
button mapping module for joysticks - why can't you just reuse that
code to make a key remapping module as well? It seems to be all there.

And while im freely associating on that - is there any point in NOT
being able to call up the current keymap info for help during
gameplay, just in the main menu? Would be nice to see that
moved/added to the pause/F2 and the station save menu....

[cim]

I call it broken because apparently there seems to be an internal hardcoded
table converting symbols to numbers - for US keyboards.

It's a known bug. I'm fairly sure I know how to fix it, but since I have a UK keyboard I can't actually test any fix I write - the differences with US are too small to be certain about.

And while im freely associating on that - is there any point in NOT
being able to call up the current keymap info for help during
gameplay, just in the main menu? Would be nice to see that
moved/added to the pause/F2 and the station save menu....

Should be fairly straightforward to do, it just hasn't been yet. The key screen from the start game menu was a fairly late addition to 1.80. I'll add it to my to-do list for 1.82