I just published new version 8.42 in our SourceForge "Files" download section according to the prevailing pattern. There is nothing new in version 8.42 that is not in version 8.41. However, because we now support two distinct installation strategies, we use even-numbered versions for "classic" installation in the user's ~home filesystem according to our long-established methodology, and we use odd-numbered versions for the new "global" installation option, going into the /usr filesystem.
Recent development work had advanced the features of odd-numbered version 8.41 a tiny bit beyond the features of even-numbered version 8.40. The only purpose of this version 8.42 is to synchronize the feature set. Now, with version 8.42, those that want to install in their ~home filesystem will get exactly the same features as those that have recently installed version 8.41 into their global /usr filesystem.
If you are already using version 8.41, there is no reason to update to version 8.42.
Those upgrading from version 8.40 will see just two small changes as follows:
1 of 2: Descriptive text in some of the mission menus is a little more detailed. 2 of 2: A subtle rudder-induced roll effect enhances the flight model. You will notice this when applying full rudder because your aircraft will tend to roll a bit. This is easily and naturally overcome with gentle aileron pressure as in real aircraft.
Changes in Lac08p40
This version derives directly from Lac08p38 (bypassing Lac08p39 which has different objectives). It remains fully compatible with the prior published version. If you are happily using prior version 8.38 or 8.39, there is little reason to update to this new version. However, new users may benefit, especially if they are not using a full-size keyboard. Several small improvements were made as follows:
The cockpit's "SPEED" instrumentation has been enhanced. In addition to displaying the True Airspeed, additional controls now also display Indicated Airspeed ("IAS") and Ground Speed ("GS") when in flight.
Improved Menu references to "Peabody's Mission": LAC's previous few versions have resulted in very nice completion of "Peabody's Mission". However, the menu text describing that mission was still advertising it as "BETA TEST" and "UNFINISHED MISSION". We updated those menu references to advertise the mission's completion and stable status. We also enhanced menu text associated with that mission to more clearly define its objectives and unique aspects.
Improved commentary within the LacConfig.txt file to update and clarify certain details that have been evolving during the past several months.
Improved support for compact keyboards: Many users have been running LAC on laptop computers that lack a full-size keyboard. Because those keyboards often lack or scatter the organized cluster of six keys that LAC's standard arrangement uses for zooming the Field of View, the RADAR, and the Map in and out, use of these "simplified" keyboards has proven to be cumbersome. Furthermore, the Raspberry Pi Foundation announced availability of their new Raspberry Pi Model 400, which is becoming very popular. Like many laptops, its keyboard layout does not include the convenient rectangular cluster of six keys that we have been using for all of LAC's "zoom" functions. Several other keyboard keys are missing too, including "F11" and "F12". We want LAC to run well on that hardware.
To compensate, this version allows an easy option to "double-map" the keyboard keys for affected functions. In addition to the existing logic that maps keys to functions according to our existing online documentation, this new option hard-codes the following additional keys and functions:
Num+ = RADAR Zoom In.
Num- = RADAR Zoom Out.
NumDel = FOV Zoom In.
NumIns = FOV Zoom Out.
NumEnter = Query Forward Observer for status of selected enemy airfield.
Z = Cycle Map View Zoom.
As you can see, most of those hard-coded changes rely upon formerly unused numeric keypad keys.
We now activate all of this new logic by consulting the "64" bit of the "NetworkMode" variable as configured within the "LacConfig.txt" configuration file, according to the established pattern for other run-time configuration options. The prompting text associated with "NetworkMode" within the "LacConfig.txt" configuration file has been expanded to explain all of this. It prompts the user to use the "64 bit" of "NetworkMode" to designate use of an alternate keyboard map and guides him in the calculation of the appropriate value.
Brief online testing confirms success: Now, if the user sets the "64" bit of "NetworkMode", (s)he can use the following extra keys from the numeric keypad (in addition to any already configured for the same purposes) to zoom FOV and RADAR range in and out:
NumIns: FOV Zoom Out
NumDel: FOV Zoom In
Num-: RADAR Zoom Out
Num+: RADAR Zoom In
NumEnter: Query Forward Observer
Additionally, if the operator presses "z", (s)he can cycle Map Zoom through all available settings. Each "z" zooms Map Range in farther and farther until maximum zoom is achieved. An additional "z" resets Map Zoom out to maximum, and the cycle repeats indefinitely as the operater presses "z".
As a consequence of this new optional keyboard map, LAC players that use laptop computers, Raspberry Pi Model 400 computers or others lacking a standard, robust keyboard will still have easy access to all of LAC's important functions through formerly unused keys on the Numeric Keypad.
Alternative Makefiles: This version also includes two alternative Makefiles, for use by those that have had trouble compiling LAC with our standard Makefile. The alternative Makefiles are named "MakefileV2" and "MakefileV3". As you might well suppose, the file named "MakefileV1" is a duplicate copy of "Makefile".
Thanks to a new posting in our online forums by Daniel Barland, we have learned of improvements in LAC's Makefile that seem to help Ubuntu compilation efforts. In his post (in the "Welcome to Ubuntu" thread), he refers to our YouTube video playlist showing exactly how we downloaded, compiled, installed, and tested LAC on a brand new Ubuntu system in September of 2020. Here is the YouTube playlist to which he refers:
Here is the text of Daniel's original post containing his improved PlayList:
========== BEGIN ==========
For those running Ubuntu 18.04LTS, things may be a little different from 20.04LTS as shown in the video playlist. You must still install the needed libraries, but successful compilation (Lac08p38) with 18.04LTS required a couple of tiny tweaks of the provided Makefile, as shown below. My 18.04 installation is using gcc 7.5.0, make 4.1, and glibc 2.27 on AMD64. The tweaks needed are to remove g++ PIE flag and that the linker requires libraries to be appended at the end of the compiler call.
Daniel's new Makefile is included herewith as "MakefileV2". If our standard Makefile doesn't work for you, replace it with MakefileV2 and give it a try (or use the "CodeBlocks" option, with which many, many people have had success). "MakefileV3" derives from Daniel's MakefileV2 but includes compiler directives for "speed at any price". It should result in better frame rates. Further information about compiling LAC with all of these options can be found in our "Compiling and Installing LAC" forum here:
No changes were made that affect flight. When used in any of the three classic online, multi-user, server-based missions, this version remains operationally compatible with all prior versions since Lac07p92.
Changes in Lac08p38
This version derives directly from Version 8.36 (bypassing version 8.37). Three minor bugs were fixed in "Peabody's Mission" as follows:
1 of 3: RADAR was tracking targets flying too low to be realistically detected (down in valleys, etc.)
2 of 3: Target reticles were drawn around those same targets even when flying too low to be tracked by RADAR.
3 of 3: The rotating RADAR antenna at field "RED2" was positioned a few feet to far to the West.
Note that none of these bugs affected any other missions.
We also eliminated run-time diagnostic reporting during Peabody's Mission, resulting in much quieter operation. This was done by simply "commenting out" the associated source code lines. Accordingly, Mission Developers can easily re-enable that run-time reporting should they ever want to enhance the Mission or derive some future mission from it.
We also eliminated the "TEST" label associated with Peabody's Mission in the main menu, since it is now confirmed to be of "production" quality.
We also tweaked some of the graphic detail settings in main.cpp to achieve a very very slight improvement in frame rate.
No changes were made that affect flight. When used in any of the three classic online, multi-user, server-based missions, this version remains operationally compatible with all prior versions since Lac07p92.
Changes in Lac08p36
This version derives directly from Version 8.34 (bypassing version 8.35). This version fixes two bugs in "Peabody's Mission" as follows:
1 of 2: Peabody's Mision was failing to display the RADAR antenna at secondary airfields,
2 of 2: In Peabody's Mission, the player's aircraft was prematurely destroyed whenever his secondary airfield was heavily damaged.
(Extensive online testing has recently confirmed that "Peabody's Mission" is now well-behaved and although it is still marked "TEST" in the menus, it can now be considered to be of "production" quality.
No changes were made that affect flight. When used in any of the three classic online, multi-user, server-based missions, this version remains operationally compatible with all prior versions since Lac07p92.
Last edit: bbosen 2021-02-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just published new version 8.42 in our SourceForge "Files" download section according to the prevailing pattern. There is nothing new in version 8.42 that is not in version 8.41. However, because we now support two distinct installation strategies, we use even-numbered versions for "classic" installation in the user's ~home filesystem according to our long-established methodology, and we use odd-numbered versions for the new "global" installation option, going into the /usr filesystem.
Recent development work had advanced the features of odd-numbered version 8.41 a tiny bit beyond the features of even-numbered version 8.40. The only purpose of this version 8.42 is to synchronize the feature set. Now, with version 8.42, those that want to install in their ~home filesystem will get exactly the same features as those that have recently installed version 8.41 into their global /usr filesystem.
If you are already using version 8.41, there is no reason to update to version 8.42.
Those upgrading from version 8.40 will see just two small changes as follows:
1 of 2: Descriptive text in some of the mission menus is a little more detailed.
2 of 2: A subtle rudder-induced roll effect enhances the flight model. You will notice this when applying full rudder because your aircraft will tend to roll a bit. This is easily and naturally overcome with gentle aileron pressure as in real aircraft.
Changes in Lac08p40
This version derives directly from Lac08p38 (bypassing Lac08p39 which has different objectives). It remains fully compatible with the prior published version. If you are happily using prior version 8.38 or 8.39, there is little reason to update to this new version. However, new users may benefit, especially if they are not using a full-size keyboard. Several small improvements were made as follows:
The cockpit's "SPEED" instrumentation has been enhanced. In addition to displaying the True Airspeed, additional controls now also display Indicated Airspeed ("IAS") and Ground Speed ("GS") when in flight.
Improved Menu references to "Peabody's Mission": LAC's previous few versions have resulted in very nice completion of "Peabody's Mission". However, the menu text describing that mission was still advertising it as "BETA TEST" and "UNFINISHED MISSION". We updated those menu references to advertise the mission's completion and stable status. We also enhanced menu text associated with that mission to more clearly define its objectives and unique aspects.
Improved commentary within the LacConfig.txt file to update and clarify certain details that have been evolving during the past several months.
Improved support for compact keyboards: Many users have been running LAC on laptop computers that lack a full-size keyboard. Because those keyboards often lack or scatter the organized cluster of six keys that LAC's standard arrangement uses for zooming the Field of View, the RADAR, and the Map in and out, use of these "simplified" keyboards has proven to be cumbersome. Furthermore, the Raspberry Pi Foundation announced availability of their new Raspberry Pi Model 400, which is becoming very popular. Like many laptops, its keyboard layout does not include the convenient rectangular cluster of six keys that we have been using for all of LAC's "zoom" functions. Several other keyboard keys are missing too, including "F11" and "F12". We want LAC to run well on that hardware.
To compensate, this version allows an easy option to "double-map" the keyboard keys for affected functions. In addition to the existing logic that maps keys to functions according to our existing online documentation, this new option hard-codes the following additional keys and functions:
Num+ = RADAR Zoom In.
Num- = RADAR Zoom Out.
NumDel = FOV Zoom In.
NumIns = FOV Zoom Out.
NumEnter = Query Forward Observer for status of selected enemy airfield.
Z = Cycle Map View Zoom.
As you can see, most of those hard-coded changes rely upon formerly unused numeric keypad keys.
We now activate all of this new logic by consulting the "64" bit of the "NetworkMode" variable as configured within the "LacConfig.txt" configuration file, according to the established pattern for other run-time configuration options. The prompting text associated with "NetworkMode" within the "LacConfig.txt" configuration file has been expanded to explain all of this. It prompts the user to use the "64 bit" of "NetworkMode" to designate use of an alternate keyboard map and guides him in the calculation of the appropriate value.
Brief online testing confirms success: Now, if the user sets the "64" bit of "NetworkMode", (s)he can use the following extra keys from the numeric keypad (in addition to any already configured for the same purposes) to zoom FOV and RADAR range in and out:
NumIns: FOV Zoom Out
NumDel: FOV Zoom In
Num-: RADAR Zoom Out
Num+: RADAR Zoom In
NumEnter: Query Forward Observer
Additionally, if the operator presses "z", (s)he can cycle Map Zoom through all available settings. Each "z" zooms Map Range in farther and farther until maximum zoom is achieved. An additional "z" resets Map Zoom out to maximum, and the cycle repeats indefinitely as the operater presses "z".
As a consequence of this new optional keyboard map, LAC players that use laptop computers, Raspberry Pi Model 400 computers or others lacking a standard, robust keyboard will still have easy access to all of LAC's important functions through formerly unused keys on the Numeric Keypad.
Alternative Makefiles: This version also includes two alternative Makefiles, for use by those that have had trouble compiling LAC with our standard Makefile. The alternative Makefiles are named "MakefileV2" and "MakefileV3". As you might well suppose, the file named "MakefileV1" is a duplicate copy of "Makefile".
Thanks to a new posting in our online forums by Daniel Barland, we have learned of improvements in LAC's Makefile that seem to help Ubuntu compilation efforts. In his post (in the "Welcome to Ubuntu" thread), he refers to our YouTube video playlist showing exactly how we downloaded, compiled, installed, and tested LAC on a brand new Ubuntu system in September of 2020. Here is the YouTube playlist to which he refers:
https://www.youtube.com/watch?v=7pgCJ5QLj6A&list=PL1IYes9MY6lLv_g8KUGIHWgpirjnzyi2i
Here is the text of Daniel's original post containing his improved PlayList:
========== BEGIN ==========
For those running Ubuntu 18.04LTS, things may be a little different from 20.04LTS as shown in the video playlist. You must still install the needed libraries, but successful compilation (Lac08p38) with 18.04LTS required a couple of tiny tweaks of the provided Makefile, as shown below. My 18.04 installation is using gcc 7.5.0, make 4.1, and glibc 2.27 on AMD64. The tweaks needed are to remove g++ PIE flag and that the linker requires libraries to be appended at the end of the compiler call.
Makefile:
OBJS=3ds.o aiobject.o audio.o cockpit.o common.o conf.o dirs.o effects.o fileloader.o FlightModel.o gl.o glland.o land.o loader_tga.o main.o mathtab.o menu.o mission.o model.o NetworkApi.o object.o objload.o pilots.o vertexarray.o
LIBS=
pkg-config --libs SDL_mixer-lglut -lGL -lGLULac08p38: $(OBJS)
g++ -o Lac08p38 $(OBJS) $(LIBS)
cp Lac08p38 bin/Release/Lac08p38
chmod +x bin/Release/Lac08p38
clean:
@rm -f *.o
@rm Lac08p38
Further information can be found in the "Compiling and installing LAC" forum here:
https://sourceforge.net/p/linuxaircombat/discussion/compilinglac/
================ END =============
Daniel's new Makefile is included herewith as "MakefileV2". If our standard Makefile doesn't work for you, replace it with MakefileV2 and give it a try (or use the "CodeBlocks" option, with which many, many people have had success). "MakefileV3" derives from Daniel's MakefileV2 but includes compiler directives for "speed at any price". It should result in better frame rates. Further information about compiling LAC with all of these options can be found in our "Compiling and Installing LAC" forum here:
https://sourceforge.net/p/linuxaircombat/discussion/compilinglac
No changes were made that affect flight. When used in any of the three classic online, multi-user, server-based missions, this version remains operationally compatible with all prior versions since Lac07p92.
Changes in Lac08p38
This version derives directly from Version 8.36 (bypassing version 8.37). Three minor bugs were fixed in "Peabody's Mission" as follows:
1 of 3: RADAR was tracking targets flying too low to be realistically detected (down in valleys, etc.)
2 of 3: Target reticles were drawn around those same targets even when flying too low to be tracked by RADAR.
3 of 3: The rotating RADAR antenna at field "RED2" was positioned a few feet to far to the West.
Note that none of these bugs affected any other missions.
We also eliminated run-time diagnostic reporting during Peabody's Mission, resulting in much quieter operation. This was done by simply "commenting out" the associated source code lines. Accordingly, Mission Developers can easily re-enable that run-time reporting should they ever want to enhance the Mission or derive some future mission from it.
We also eliminated the "TEST" label associated with Peabody's Mission in the main menu, since it is now confirmed to be of "production" quality.
We also tweaked some of the graphic detail settings in main.cpp to achieve a very very slight improvement in frame rate.
No changes were made that affect flight. When used in any of the three classic online, multi-user, server-based missions, this version remains operationally compatible with all prior versions since Lac07p92.
Changes in Lac08p36
This version derives directly from Version 8.34 (bypassing version 8.35). This version fixes two bugs in "Peabody's Mission" as follows:
1 of 2: Peabody's Mision was failing to display the RADAR antenna at secondary airfields,
2 of 2: In Peabody's Mission, the player's aircraft was prematurely destroyed whenever his secondary airfield was heavily damaged.
(Extensive online testing has recently confirmed that "Peabody's Mission" is now well-behaved and although it is still marked "TEST" in the menus, it can now be considered to be of "production" quality.
No changes were made that affect flight. When used in any of the three classic online, multi-user, server-based missions, this version remains operationally compatible with all prior versions since Lac07p92.
Last edit: bbosen 2021-02-08