Messages

Here they are!

Ok. I just recompiled the executables with libtinfo.5, attached you find both the 32-bit and 64-bit versions.

About libtinfo itself, so it is a bit like the Microsoft .NET Framework, for which more than one version installed at the same time could be necessary to run both older and newer software.

Good work! Also, contribution for the team score can be considered, even if it is difficult to define properly it. If a pipsqueak is considered to contribute whether he achieves a position among the first two of the team, by taking for example ZCT232, Seeker contributed for 8 points, while I gave no contribution (by being the third of the team).

By running a lap with the Carrera 2"20 faster, I would have been the second of the team and Seeker the third, so I would have contributed for 8 points, while Seeker would have given no contribution. But in both cases the total score of the team would have been the same, 18 points: your 10 points and 8 points from one of your teammates. Thus, uploading a faster replay, allowing me to overtake a comrade, would have resulted in no benefit for my team.

On the other hand, considering all the results would not be really consistent, since it is possible that a team member classifies always with a huge gap with respect to his comrades, so a sort of compromise has probably to be defined.

Don't forget the 32-bit exec! 

Maybe it is rhetorical, but better to point out: executables compiled for libtinfo.5 are compatible with libtinfo.6 (but not vice versa), right?

Nice! I just compiled Bliss 2.5.8 on my machine with FreeBasic 1.07.1, I attach the executable for libtinfo.5.

As expected, it does not work on my Ubuntu 18.04.5

I'm not sure if it'll work easily, but you can try doing: sudo apt-get install libtinfo.6. Because the library is newer than other files in your system, I assume it'll have unmet dependencies and will try to install them too (and probably fail, as is common in cases like this... "dependency hell"). It'd be easier if it were the other way around (you having a newer system and installing libtinfo.5), but unfortunately, I currently don't have a comfortable way to compile it that way. I love GNU/Linux, but I hate this shared-library trend. Hard drives today are huge and memory is abundant, why can't fully static compilation be the default and straightforward way of doing the things? Anyway...

Hmm, I guess there is a certain degree of risk in breaking some other mechanics...

I suppose the question mark highlights when backslash has been pressed and thus two hex digits are required

Yes. Now if you wait too long or press something invalid, you get back to normal key recognition, so no more "What?  Did it crash?  What happened?"

I see, you have three seconds to input the value, which can be a good time window.

Thanks for the release!

NOTE for GNU/Linux users: distros are switching from libtinfo.5 to libtinfo.6. Because I updated my OS, the program is now compiled for libtinfo.6, which will be OK for updated distros, but may fail to work out of the box in older LTSs. If so, the program can be recompiled from source or you may upgrade your libtinfo to version 6.

As expected, it does not work on my Ubuntu 18.04.5:

./bliss
./bliss: error while loading shared libraries: libtinfo.so.6: cannot open shared object file: No such file or directory

But I managed to run the Windows version via Wine/Vineyard. I suppose the question mark highlights when backslash has been pressed and thus two hex digits are required...

An example of what you can highlight as markup with a new MediaWiki version.

PS: Star Trek Discovery spoiler alert! (I was working on that...)

It should be a bit like the Fight Club: the first rule of a backslash user is... 

Maybe a box highlighting that it is active while \ is pressed could be useful, since if you press it inadvertently you cannot do anything else unless you input the two digits or you press ESC.. .

From the manual, at the end of paragraph 5:

If you  are experienced with Stunts' track format and  would like to
have more  freedom, you can  enable "manual edition" (read more about it
in the  section  about  the "switch bar"). While manual editing mode  is
active, the backslash  key can be  used  to enter a hexadecimal code and
select any  track  or  terrain  element  directly. This includes invalid
codes. Also, the background scenery selection will allow custom  scenery
codes when this mode is enabled.  In case  you don't know what  this  is
about, it is better to first experiment with  a new  empty  track and be
aware  that  Stunts may crash  or  behave  unpredictably  when  manually
edited tracks are loaded.

It seems I remembered wrong: it is MAN, not DEB, which has to be active. Note that when you press backslash no box opens, just insert the two hex digits relative to the track element or to the terrain (depending on which set of elements do you have open).

There is also a debug mode in Bliss, did you try even within it?

Something like this?

The outer track in Bahrein is ridiculous. Lap times around 55 seconds... Talking about fast tracks: Monza has a style, while Sakhir circuit is just another nightmare from Tilke.

I want the good old Hockenheim and Spa-Francorchamps back. The latter one with the original bus stop and without the straight finish.

I want TI Aida back, Pacific Grand Prix as second race (well, first because it came before Suzuka during the season) in Japan...

As usual, my availability for a precise time and date depends on various unpredictable factors, so I will probably know at the very last...

Of course his career cannot be summarized in a few... lines...

(sorry)