Leaderboard

The gunners were good. As you can see, they tracked my flight path across the base quite well. Speed was what saved me. They missed the parachute retarded store I dropped on the pass. (on the left) This one... Not a bad drop for going by at high speed. A little late to run now, though.

As part of your continuing training and pilot education, we have a special test for you today. As you can see, the maintainers have repainted all the gauge faces, so NONE of the numbers can be seen. It is your task, not only to remember which gauge is where, but what the information the gauge is displaying. To do this, you'll be flying a full circuit around the base. Engine start, taxi, takeoff, fly the pattern, and land. You'll taxi back to the parking slot you started from. Have a safe flight. Happy April Fools Day!!!

I'm back to the Polish-Russian war. Finally started working on some new planes - Ansaldo Ballila for the Kosciuszko squadron.

If it keeps that up then just download this file from the site and edit the weapons therein to your liking. It should contain everything you need including models, skins and data files. You can put these in your Objects\Weapons folder

I must have gotten it out of the cat files with the cat Extractor. Here is mine. Just copy it to your Objects folder. I have also included the GUNDATA.INI file. It contains the information for all the guns in the game. Put it in the Objects folder as well. WEAPONDATA.INI GUNDATA.INI

Go to the Objects folder in your install. Look for a file called WEAPONDATA.INI and make a copy of it in case you make a mistake while editing it. This contains the weapon data for the weapons included in the base install. You can search for the AA-2 by using CTRL-F. Individual weapons are overwritten by the folders in the Objects\Weapons folder. So, if there is no AA-2 folder the computer will use the data from the WEAPONDATA.INI file. It is the same data but in a long numbered list with over 100 weapons. In my WEAPONDATA.INI file the AA-2 is [WeaponData141]. Yours may vary. You can change the GuidanceType=10 or any other statement as you see fit.

I used Extract All for the CAT File extractor and it worked fine for me. It takes a while of course, but they should be in there somewhere.

Excellent, Drach nails it again, I like the way all his vids are very mater of fact, and he speaks with deep knowledge. As for the "Takao Incident" this was hushed up rather swiftly, until some wise ass Japanese thought it would be an awfully spiffing show to make "Sience'ee Fiction'ee" Documentaries on the subject of The King of the Monsters.

Happy April 1st!!

Here the libyan view: https://warisboring.com/the-libyans-describe-a-different-version-of-their-1981-battle-with-the-u-s-navy/ It comes from a book by Tom Cooper Libyan Air Wars, Volumes 1 & 2.

not to be too dramatic but I'm almost weeping with joy. Thank you so much.

If I am allowed, you may lower the Bump Maps to 5% for panels and 2% or even 1% for rivets so they can show better, I use Normal Map Generator in this case, happy to share it, if you like.

Coming soon is the A6-A late with va-196 Attack Squadron skin and decals. Screenshot by @Coupi

One more friendly public service post under this thread, regarding FlightGear. Many thanks first of all to Emmanuel Baranger for pointing me in the right direction for how to enable photo/ortho-scenery in this fine, open-source simulator. Most of the important details regarding photo-scenery and proper installation of packages, programs, etc., in order to have everything function properly - are available under the "Julia Photoscenery Generator" tutorial. Thank you "abassign" for the original instructions, coding, and tutorial. Also many thanks to Manuel who has done a video run-through of the main components of that tutorial. I wish, however, to draw attention to a few peculiarities that are likely relevant only to Intel-era Macs and/or to specific "Wintosh" combinations such as I am running, and perhaps others are running too. Tips and directions below are for the stable ver. 2020.3.19 of FlightGear, by the way. Five important things to keep in mind: a) when downloading necessary applications to enable photoscenery, as indicated in the tutorial, such as the "Photoscenary" files, the Julia compiler, and the ImageMagick application that converts images to the DDS format, make sure to download the *actual installer* for ImageMagick (indicated with an .exe extension) - it is fine to download the portable version of the Julia compiler, but do *not* download the portable version of ImageMagick; the full installer for the latter is necessary; furthermore, while installing ImageMagick, make sure to select the two options for "set system path to files/program installed," as well as for "legacy converters"; also important is to install the Visual C++ Redistributable Package that is linked to near the bottom of the main ImageMagick website - only with all of those details followed does ImageMagick work properly on an Intel Mac b) once all of the necessary programs and files are installed, go into the "Photoscenary" folder, open the two text files titled "conn" and "args" - delete the contents of both - and paste in *either* of the following two sets of commands into *both* files (don't forget to save once the information is entered): option one, for great photo-imagery quality and decent FPS, even if flying in multiplayer: --connect 127.0.0.1:5000 -s 5 -r 30 --attemps 3 --over 1 --sdwn 2 option two, once again for fine photo-scenery quality and good FPS, even in multiplayer (but perhaps slightly better for lower-end rigs): --connect 127.0.0.1:5000 -s 4 -r 40 --attemps 3 --over 1 --sdwn 1 c) while still inside the "Photoscenary" folder, right-click on the "photoscenary.jl" application and select the option to open it with Notepad; once the application is opened in Notepad, scroll to the following code: julia -t 10 -p 2 photoscenary.jl and change, for example, to: julia -t 5 -p 2 photoscenary.jl (the suggested change reduces noticeably the no. of threads that the "photoscenary" application uses to download satellite imagery for FlightGear; the general rule of thumb is to set the no. of threads to 50% or slightly less of your total no. of processor threads available; furthermore, the "-p 2" command references the no. of processor cores to dedicate to photo-imagery downloading; a sensible no. for the cores is no more than 50% of the total cores that you have -- anything higher than such percentages devoted to ortho/photo-siphoning is excessive and will not improve tile-download smoothness or overall FPS in FlightGear -- from my tests, I have noticed that I am getting very good results either with 6 threads and 3 cores, or 5 threads and 2 cores, devoted to the tile siphoning/download process; the total no. of threads on my system is 12, and the total no. of cores is 6, by the way) d) make sure, before running the "photoscenary.jl" application (i.e., before double-clicking it so that it begins to fetch photo-scenery for FlightGear), to unselect any custom scenery that you might have installed in FlightGear and that is visible under the "Add-ons" menu; then run "photoscenary.jl" and it will proceed to set up a default "Orthophotos" folder at the following directory path - \FlightGear\Downloads\TerraSync\Orthophotos e) last, it is vital directly to select the created "Orthophotos" folder as your custom scenery folder in FG's "Add-ons" menu; otherwise, photo-scenery will not be visible while flying in FlightGear; if you have other custom terrain folders, you may re-select them at this point, but make sure that the "Orthophotos" folder is always at the top of the hierarchy (see illustrative pic. below) NOTE 1: "photoscenary.jl" will on its next run set up another "Orthophotos" folder within the one that we have already locked to FlightGear, but that is fine; allow the directory structure to exist as \TerraSync\Orthophotos\Orthophotos (and feel free to delete any other folders that may have been created in the meantime in the first "Orthophotos" folder of the directory path, right after "TerraSync") NOTE 2: if running the application OSArmor (or the older variant "NoVirusThanks OSArmor"), make sure to *disable protection* before running "photoscenary.jl"; otherwise, blocked process warnings will pop up with every photo-scenery download and will likely disrupt operation of the whole photo-scenery fetching mechanism Below follow several representative pics. of photo-scenery functioning properly in ver. 2020.3.19 of FlightGear on an Intel Mac. I have not noticed any drop in FPS with photo-scenery enabled; on the contrary, my overall FPS seems to have improved by a few frames when compared with flight over stock TerraSync terrains in FG. While there are so many wonderful things about photo-scenery, one of the details worth mentioning is that the terrain now overlaps very closely with what is seen on the "mpmap" if you enjoy tracking your flight's progress that way too. Take note, for example, of the subtle depression in the grass where the Piper PA-28 B Model has been parked, and also of the location where it sits on the Google maps pic. (great stuff). As well please find included, below the pics., a small attachment that includes a few ALS shader tweaks for FlightGear, to improve graphics crispness and/or to stabilize FPS further on AMD-vid rigs. FlightGear_ALSshaderTweaks_VonS.zip Good flying to you,

My fav modeler is back! With a new toy! A plane must needed.

X-31

cool, but available where? dunno why but the Stealth Hawk made me think of a SF2 porting of this for now i'll just settle for whatever TC can wrangle up.....

Awesome Ansaldo! It's great to see you back Stephen.

Looking forward to some Austro-Hungarian Oeffag Albatros for the polish!

Nice to see you back buddy, you have been quiet for a while, the Ballila looks nice.

Small discussion between Rebels and imperial Forces.

They are coming along nicely, what do you say?