Still 2.1.9936.0 in game/ Help/About LM/ and the PrepaR3D.exe in the P3D folder File Version details says 2.1.9936.0. The rar file iself is labeled 2.1.10017.0.

 

You know what. Mine too. I've tried everything I can think of...

Pilot and passenger back in the Tiger Moth... yay!

 

My build no. in sim is also 2.1.9936.0

Yes strange that same here,but all the new dll,s shows the date in the modified column as the 24.02.14 and my original saved versions show the dll,s date modified as 10.02.14 .14 days earlier and as today's date is the 28.02.14 today I presume that something has changed,

Great news, thanks for the update.

This fixed a number of issues that I was having!  

Wow, this is working great! Will be a busy weekend

 

Sent from my Mobile thing

I wouldn't worry about the build numbers. The zip file has the correct build number, but none of the files had their build number changed for some reason. Can anybody see from the file sizes which dlls were changed?

QW just advised the hotfix corrected the issues in the BAe146 and 757 as well, even the sunken wheels in the tarmac.

 

Sent from my Mobile thing

The hotfix fixed the A2A Piper Cub's propeller [the spinning animation, that was broken in P3D v.2.1 now works correctly again), and I had a nice long flight last night where my A2A Piper worked perfectly in P3D again.

 

The patch didn't totally fix my A2A C172, as the beacon light still does not work properly (I still have to reload the Cessna into my current flight a second time to get the beacon to light up ... which also worked in the pre-hotfix). There are also some issues with the landing lights and taxi lights illuminating the exterior (reloading the aircraft sometimes fixes these as well, but it may require more than one reload).

I wouldn't worry about the build numbers.

 

Im not. But the you had stated the build number changed. So lets not confuse us anymore than we already are. The way you cam tell is the extension on the end of the build number and the date of 2-14-2014. No big deal .Not to be confusing.

It looks like the GPS of the Carenado B1900D is now working correctly.

 

GREAT!

 

Patric

 

Are you sure?

 

If you increase / decrease range (Garmin) .. does it work?

 

Do you have an Engine fire alarm light on the front panel?

Are you sure?

 

If you increase / decrease range (Garmin) .. does it work?

 

Do you have an Engine fire alarm light on the front panel?

 

I have just finished my first flight with the B1900D after the installation of the hotfix. Yes, I can increase or decrease the range of the Garmin, and I've got no fire alarm on the front panel.

But I had another problem. The brightness of the Garmin GPS has changed constantly. About every five seconds the display brightness changed from bright to dark and conversely.

 

Patric

Patric,

 

That is good news.

 

Thanks for confirming.

"But I had another problem. The brightness of the Garmin GPS has changed constantly. About every five seconds the display brightness changed from bright to dark and conversely.

 

Patric"

 

Ok, I checked (daytime) .. on Map page it looks ok here.

But, if I go to another page I do see the display intensity change like you mentioned.

Everyone please keep in mind that this "hot fix" simply restored the XML parser's ability to "ignore" certain errors that otherwise kept entire sections of the XML script from executing...

 

It does not however magically fix those errors, nor any others that may prevent proper execution of all the functions, such as the "brightness fluctuation" mentioned above...

 

Developers will still have to find and fix their actual errors and fumble-fingered boo-boos in their scripts...

 

...as those errors will continue to create cumulative VAS increases!  :Whistle:

Im  very appy, never was able to fix the gps530 syntax  anyway ...