Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

May 10th: Update on Maddog Updates

Featured Replies

  • Commercial Member

May 10th, 2010:As you know, Leonardo just released the Maddog 2010 which features a new panel as well as a new SP for 2008.I'll be releasing updates soon. However, I need the "dust to settle" a bit before releasing these updates as I want to ensure the 2010 and 2008 SP are stable so I don't have to keep re-releasing updates.Cheers,

May 10th, 2010:As you know, Leonardo just released the Maddog 2010 which features a new panel as well as a new SP for 2008.I'll be releasing updates soon. However, I need the "dust to settle" a bit before releasing these updates as I want to ensure the 2010 and 2008 SP are stable so I don't have to keep re-releasing updates.Cheers,
Thanks for the update on the update. Looking forward to getting the MD82 back in the air once you release it!

John Skibo

 

 

May 10th, 2010:As you know, Leonardo just released the Maddog 2010 which features a new panel as well as a new SP for 2008.I'll be releasing updates soon. However, I need the "dust to settle" a bit before releasing these updates as I want to ensure the 2010 and 2008 SP are stable so I don't have to keep re-releasing updates.Cheers,
Hello Bryan,Is what you are working on, updates for both the 2008 update and the 2010? Will these be two separate updates for you?I have downloaded both the 2010 Pro and the updates for the 2008 Pro, but I'm not installing either until I know that it won't mess up my FSCrew.Thanks,Bob

Robert Yunque

PilotEdge Ratings =   CAT-11 (2016-09-13)  I-11 (2016-10-23)  V-3 (2016-08-01)

fslabs_banner.png

  • Author
  • Commercial Member
Hello Bryan,Is what you are working on, updates for both the 2008 update and the 2010? Will these be two separate updates for you?I have downloaded both the 2010 Pro and the updates for the 2008 Pro, but I'm not installing either until I know that it won't mess up my FSCrew.Thanks,Bob
Hi Bob,I'm not totally sure yet. I'm going to have to sort out these Maddog updates.Cheers,

Bryan,The 2008 versions (aka. 3.0 and 3.0 pro) are not for sale from Leonardo anymore. These are the versions that the current version of FS2Crew works with.Patching the standard version 3.0 using the free patch brings it up to version 3.2, aka 2010 Standard. This is also what you get if you buy the Maddog Standard version from Leonardo today.Using the free patch for the pro version 3.0 brings it up to to an intermediate version which is not for sale from Leonardo. This one doesn't have an official name, I think, but should be thought of as "2008 pro SP1" (name invented by me)Purchasing the full analogue upgrade for the pro version brings it up to version 3.2, aka 2010 pro. This is what you get if you buy the Maddog Pro version from Leonardo today.That makes five versions to consider for each sim (FS9/FSX), so potentially 10 different versions to be compatible with in FS2Crew. Not pretty.

Anyone tried the updating the panel.cfg for the full analogue version (Maddog 2010) and running FS2Crew with it?The only things I can think of being a problem are the testing of the HSI and the EHSI.As FS2Crew for the Maddog doesn't rely on a fake panel, but uses the Maddog SDK this might not be a problem.Aren't we all so impatient, after all, Bryan will release a proper patch soon (very soon hopefully :( ) and we are all trying to ######ise it to make it work in the meantime.Neil

beta.gif

I have been testing the FS2Crew SP1 interaction with newest Maddog 2010, and so far I had 1 major finding, and another smaller one:- Major finding is related to the full analog panel. During the flight deck preparation, in some point FO side lost the ADI & HSI. The gauges just "disappeared". Capt side all seemed ok (I just needed to press ADI test switch to reset ADI).- The other one is related to the ABS. As it was not previously implemented in FS2crew due to known limitations, FO arms autospoilers but not ABS leading to some TO warnings.No CTDs until now, and in my case airplane has been more than flyable.Note that I only performed some random testing, without completing any full flight, so I am not sure if other issues can be found.Anyway, if someone wants to give it a try, remember it remains at your own risk.Regards,Samuli

Hi guys,I got it working with the Full Analogue version, and the only slight glitch is that you have to press the test button again to reset the ADI (as Samuli said above).It all works fine, and I'm having great fun :( Thanks to all the guys for their hard work again,Neil

beta.gif

So let me get this straight since Leonardo seem to be very vague on this (perhaps on purpose)- The Pro version of Maddog 2010 allows gives you full analogue panel in the 2D. What of the VC? Is there an analogue VC?

After yesterday's corrected Maddog version, published by Leonardo, now the problem with the FO's ADI & HSI loss is not happening anymore, at least to me.ADI must be reset, and special care must still be taken with ABS/autospoilers.For those who want to install Maddog 2010 and use FS2Crew, I will attach here modified panel.cfg files.As I cannot attach a panel.cfg file due to uploading restrictions I have to attach it as a .txt file.So what you will need to do is pretty simple:- Make a backup copy of the panel.cfg files found on these 2 folders: FS9/Aircraft/Maddog2008/Panel.full_analog and Panel.wide_full_analog folders. (it is important to keep original panel.cfg file safe somewhere just in case)- Open panel.cfg file (double click on it, chose "select a program on the list of installed programs", click ok, chose notepad and IMPORTANT uncheck "always use the selected program to open this kind of file", click ok.- delete the text, replacing it with the one you can find on the corresponding .txt file.- Save it and that's it.Note: I highly recommend you to create a backup of those files before attempting to make any change. I try to make the explanation as simple as possible, but you should have a minimum knowledge to try this operation, as it will obviously be at everyone's own risk.IMPORTANT NOTE: These panel.cfg files are only to be used with the actual Maddog2010 (uploaded on the 12.05.10) and under FS9.I have currently no FSX installed on my PC.What will these files do? They will allow you to open the FS2Crew control panels by clicking on the ADI. And it will allow you to make the ADI test as well.And obviously these files are only needed for the full analog version of the newest Maddog.Hope this helps you to enjoy new, much improved MD80 together with your favorite Copilot meanwhile waiting for a nice update for FS2Crew.Bryan, I hope this will give you a slight pressure release so you can work on a nice update :( .Happy landings,SamuliP.D.: You will need to right click on the attached files and "save target as...", otherwise you will not be able to open them with notepad.

Thanks SS,I'm still working on the Maddog update while trying to get the Jetstream beta out the door.Cheers,
Can we say multitask? :(

Robert Yunque

PilotEdge Ratings =   CAT-11 (2016-09-13)  I-11 (2016-10-23)  V-3 (2016-08-01)

fslabs_banner.png

  • 3 weeks later...

Bryan, Any news on the maddog update now that the Jetstream is out the door? JeffG

Now that I've released the Jetstream, updating the Dog is my new priority.Hopefully in a couple days I'll have a public beta out.Cheers,
You're the man Bryan!

Robert Yunque

PilotEdge Ratings =   CAT-11 (2016-09-13)  I-11 (2016-10-23)  V-3 (2016-08-01)

fslabs_banner.png

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.