I found it.Please ignore any other message that may appear here. I poked around within the PMDG Web site and found what I believe to be the correct Service update for the Beech 1900D(I had posted before that I could not find the new upload.)Thank you,

Great update, looking forward to the others.Can someone please post the "text" change to the panel.cfg to get the wing views back, the update changed the panel.cfg and I did not save the wing view text.Thanks,Carl Wilson

To PMDG Team:I installed SU1_1 for the PMDG B1900D.But like in the original release, for hear the

Hey all,From the update readme: "Updated fuselage lighting and structure"You forgot to update the engine structure though - the exhausts are still incorrect on the starboard engine.Just FYI.David

I would also like to know what changed in the panel.cfg. I have a RXP mod'd panel.cfg file, and would like to merge the changes if possible.Jason Barlow

The update for this aircraft is wonderful!! The sounds are much better and I greatly appreciate the modified exterior lighting. I do however have one problem though. Whenever another aircraft is given a traffic alert about my aircraft, ATC always says 'Beech Beech 1900'. Is there anyway to fix this so it says 'Beech 1900'?

>>ATC always says 'Beech Beech 1900'>>This is a tricky one. If you make the fix, when ATC speaks directly to you, it will only use your tail number.. not Beech #######If you prefer this.. simply open the B1900D aircraft.cfg, go to the {GENERAL} section, and find the line that says: atc_type=BEECHSimply delete the "BEECH" so the entry looks like this:atc_type=But again, when ATC speaks to you directly, they will use only your tail number. Your choice :)Best,Vin ScimonePMDGwww.precisionmanuals.comhttp://www.precisionmanuals.com/images/forum/devteam.jpg

Hi Jason,The change was very minor, and had already been made in the RXP configuration files. If you redownload the RXP panel.cfg files and install them, you wont have a problem.Best,Vin ScimonePMDGwww.precisionmanuals.comhttp://www.precisionmanuals.com/images/forum/devteam.jpg

When ATC talks directly to me such as on my test flight with the new patch my callsign was 'Orbit 27'. It's when they say: "Orbit 2586, traffic is two o'clock, 4 miles at 14,000, Beech Beech 1900, report them in sight". That's the problem.

HmmmI would say that's a problem with your AI traffic Beech not with your PMDG Beech! ;-)You need to alter whatever aircraft.cfg your AI traffic uses for that particular aircraft type.Hope it helps,

Mats,When the FS ATC gives traffic alerts to OTHER AI traffic regarding you it'll say Beech Beech 1900.e.g. G-SCOT, traffic is 3 o'clock 4000, Beech Beech 1900 report in sight. (where you are flying the offending aircraft)Hope that helps clarify :)DavidP.s. To anyone at PMDG, any word on my exhaust comment? It came up soon after the initial release and when I read that the exteriour had been changed this is what I though of.

AHHHHHHHHHHHHHHHHH!!!Of course!!!Stupid me :-knock :-rollI'll take back everything I've said and state the opposite!Cheers,

David-In Vin's repost we changed the word "structure" as it is misleading.... Lighting and Structure means hat we changed the way the lighting is set up and the format in which it operates.... We made no changes to the visual models, as the only change required was the exhaust modification as you pointed out. To make just that one small modification would require that all of the visual models get replaced in the patch process, and this pushes the patch into the 20MB range....(We could "patch" the model itself using bit by bit replacement- but this is an inherently unstable technology when dealing with MDL files... so it really isn't a good solution even though it saves space.)

Hey,Thanks for that Robert.Personally I'd like to see it fixed, 20MB is not a big file even for dial up. And going by the current results of the 2004 Avsim survey only 18% of over 4000 people still have dial up not all of which will be PMDG customers.Or an even better way of putting it. The original setup file for the 1900 was a 25Mb download. If everyone managed to get that ok why not a 20Mb patch?Not trying to start a war here, it's just if I've got a question I'll ask it :)Have a good one,David

I second the patch for the exhaust port. It's minor, but I think it'd be worthwhile. I'm a dial-up user and have dl'd packages and updates exceeding 40 megs--I set up the download, then wake up the next morning with everything done.I am curious however--the mdl file itself is not very large, along with any texture associated with the engine. Why would compilation of these into a patch result in a 20 meg download?-John