Leaderboard

Having a blast of time enjoying those cloud lighting variations, in combination with ASXP loving those thick and solid cloud decks formed near my route, superb add on. Wondering what crazy amazing stuff you have reserved for SMP v5 some day...

Kicking off a series of development updates, we will travel to the past, from when DC-3 was born to today, to understand the significance of this aircraft for the whole airline industry. Douglas Aircraft Company, after a TWA inquiry, started development of a new series of aircrafts, designated as Douglas Commercial (DC), the DC-1 in 1933, and DC-2 next year. Although DC-2 was successful, it was a bit narrow for what American Airlines wanted, which led to the development of one DST prototype. DST stands for Douglas Sleeper Transport! Yes beds in the airplane! Flew first time on December 17, 1935, the 32nd anniversary of Wright Bros first flight. The aircraft was fitted with 21 seats (instead of 14-16 sleeping berths), and designated as DC-3! Totally built, up to 1943, 607 DC-3 aircrafts. But WWII has begun and many DC-3s were put into military service. The needs for a military transport aircraft were huge, and with DC-3 fitting the bill, the C-47 Skytrain was created. It was based on DC-3 with few changes needed for the operations in the military, most notably the reinforced floor that allowed for higher gross weight, and the dual cargo doors. A total of around 10,000 C-47 aircrafts (and variations) were constructed. Many C-47s, after WWII, became available for civilian use, and even today, there are many DC-3s and C-47 in use! Later, in 1990, another variation was developed by Basler Turbo Conversions, retrofitting P&W PT-6 turboprop engines, and airframe modifications, designated as BT-67. Our Leading Edge Simulations DC-3 (v2) is based on the original, 21-seats, variants. The aircraft has a maximum gross weight (MGW) of 25,200 lbs for take off and landing, and can reach speeds up to 207 mph (180 knots). 2 Pratt and Whitney PW R-1830 Twin Wasp radial engines, providing 1,200 hp each, driving a 3-blade Hamilton Standard propeller. In the next weeks leading to the release, as development progresses, we will look into each area of the aircraft in more detail. For now, I will leave you with a few more random images. Keep in mind that everything you see here, up to the release, is work-in-progress, not final! (source: Wikipedia)

I think the new clouds lighting looks amzing, very natural and for me personally those are the best clouds I've ever seen in a simulator, including FS20 alpha (I don't like their clouds at all). Further I'm still impressed how the SMP clouds give a feel for their position, most cloud system look somehwat 'flat' like a picture but with SMP everything feels truly threedimensional for me (don't know what's the magic with SMP, no other cloud system ever gave me that feeling). Also the towering clouds seem to have improved over time, every formation now looks different it seems and I always loved those towers... :-)

Glad it´s solved now!

AFM Simulation is excited to share with you a preview of the upcoming FMOD sound pack for the M20 Collection! With new recordings, optimized FMOD, and more, this sound pack should impress! This updated sound pack is not complete and will change before final release. Features: New engine sounds New start up and shut down sounds New environmental sounds based on time of day and altitude New flap sounds New landing gear sounds New interior system sounds (avionics, fans, etc.) And a whole bunch more! Download Here: https://afms.im/zgJfR7 Installation Instructions: Download FMOD sound pack from above Open the folder: "X-Plane 11/Aircraft/X-Aviation/M20 Collection" In M20R Ovation II, M20R Ovation III, and M20TN Acclaim: delete the fmod folder In each of those three folders, paste in the new "fmod" folder from the zip Enjoy the FMOD preview! If you do not have the M20 Collection already, you can get it here now!

Can you please add an option to change the altimeter reference subscale between HPa and inHg?

Hi nopixar, This is due to the docs being currently out of sync with the release version. I will send you the beta of 1.1.0 with that feature integrated.

I doubt we'll address this for this next release. Given the various techniques of achieving "smooth braking", my preference is to opt for a PI(D) algorithm which controls "deceleration Gs'....which would be set by a slider, and IMO, feel the most natural. Accomodating braking by hardware, keystroke, commmand and accounting for separate toe braking requires a bit of forethought. Its really easy to implement one method and end up breaking (no pun intended) the implementation for another user, so i don't want to rush into it assuming its simple. We are fast focusing on final details of the upcoming release and I'm reluctant to mess with any systems programming at this point. Of course we'll work on it for the one after as it is a good idea. -tkyler

Beautiful shots, and we are happy you enjoy the update.....

YES! it’s a bug with cinema Vérité. It’s now off.

Regarding cloud color, I was also going to comment too. I'm a new user, so I don't know if color has changed, but I find that the darker parts of cumulus clouds do have an unnaturally brownish color to them during times of the (virtual) day when I wouldn't expect any color at all. I'm looking out my window now (IRL) at a sky full of similar clouds at 9am and the darker areas are distinctly colorless (gray). A relatively minor thing in the grand scheme of things, but I'm thinking cloud color may be more saturated than it needs to be.

ok, thanks for letting me know

I will try, I find screenshoting in VR very hit and miss!

Beats me. But in all seriousness though I don't think that a random person would just say that the project isn't dead if they don't know for sure if it's dead or not...I don't know, that's just my opinion. Maybe he/she is being a bit optimistic, or maybe he/she is somehow in contact with Peter and knows for sure that it isn't dead - who knows? I was simply going by the posts I saw over on the threshold forum..and that post was the latest one.

@ktomais It works by default on the IXEG. You can hide the tooltip... look inside your FlyWithLua\Scripts folder and you'll see a file called "nm_differential_brakes.ini". Open this file in your text editor and change SHOW_BRAKES_INFO=true to SHOW_BRAKES_INFO=false This is also where you can change the time it takes from activating your brakes until max brake force is achieved as well as the time from releasing your brakes until zero brake force is achieved.

I understand and actually agree with this feature...I think its a good idea. I also don't have pedals and even the 50% / 100% braking can lead to jerky motion. The idea of a command that you "hold" for progressive braking, I think is worth a look-see. Commands don't really cost anything and are easy to add. -tkyler