strider

I have had the parking brake set since flight inception. I clicked the blue "ground power available" light 5 minutes ago...and have waited per the RTFM...no ground power is available. What am I doing wrong...I can't get Ground Power? Vic

Has anyone else had "fe.dll" errors when using this repaint on the FS9 LevelD 767? I get an MSFS "fe.dll" error every time I use it. I can use any other LevelD 767 repaint and it works fine. I'm just wondering if I'm the only one?

OK...found the problem with my Beacon and various other TM2 lighting. When deleting the "splashes", from the aircraft.cfg, I found a stray [LIGHTS] header...probably from my original "copy & paste" to install the splashes, in the first place. I'm back to default and everything is working. I'll give the splashes another try...without any strays!

Do the light splashes from Matthew ("splash.zip"), created several versions ago, not work with the 1.40 version? I'm having problems with my beacon and strobes but I don't know if the 2 are related. Vic

Exactly, Chuck. It's useless with detailed addon aircraft.This entire problem is a system issue. I never had the problem with my old Alienware system. This ASUS MoBo I have now is an overclockers paradise...unless you enjoy stability!! All OC is turned off at this time...and it still happens. It's as if SOME program is doing something while FS9 is paused...and causing a conflict? Like I said...there is no rhyme nor reason I can find. I'm currently trying minimization after pausing (so only the desktop shows) and making sure any ACARS programs for my various VA's are OFF. Other than that...I'm at a loss.

Nope...gave that up as it was good for nothing but system crashes...and really made no diff with FS9.

Can some really knowledgable person explain why pausing FS9 would cause a system freeze? I have been dealing with this problem for over a year, now...and I'm about to go insane. I believe it is more about my system rather than FS9 itself.Whenever I use the "Pause" function in FS9, I stand a chance of a complete system lockup. I just started a descent into KSFO, paused to go take care of business for 2 MINUTES. Came back and my system was locked up tight. I've used "FSPause" with the same result...SOMETIMES. There is no Rhyme or Reason...sometimes I can pause and others I get locked up, at some point. It NEVER happens when I push the "P" key...it's always at some point after. When using "FSPause" or "I will be back" I sometimes have no problems...but most times come back to a completely locked up system. #####? This one single issue has driven me to the edge of completely wiping out any MSFS...and moving on. Imagine flying 10 hours and having the system freeze on approach!! Just because you paused??Like I said...it never happens WHEN you pause...it happens WHILE you are paused. Sometimes 1 minute in, sometimes 20 minutes into a "pause", sometimes I have no idea...FSPause does it's thing and I come back to the system hours later...and it's locked up tight. This is my last straw, friends. If I can't figure this out I'm calling it quits for MSFS, after 15 years. I just don't need the aggravation any more. It's just no fun, anymore.

I can't even find the ISG unit. The link in the manual goes to www.fsbuild.com but I see no mention of the unit there?Anywho...was wondering about these entries you have://file=Main_igs.bmp //Main panel bitmap with square HSI face for ISG glass HSI //file_1024=Main_igs.bmp file=Main_tcas_fms.bmp //main panel bitmap with square face for ILH TCAS gauge file_1024=Main_tcas_fms.bmp //gauge05=B732ADV!vsi, 399, 774, 131, 131 //round dial VVI gauge05=ILH_TCAS!IVSIb, 393,769,142,142, pic:no //VVI/TCAS, requires all "ILH" gauges //NOT compatible with ISG TCAS I'm thinking that Lee's TCAS and the ISG are incompatible? But I don't know that. Hopefully someone who has the ISG working will come along with better info...and where to actually find it? :(

Bob, I've updated to 1.40 with no problems. I will give the ISG unit a look see.Thanks!Vic

OK, Bob...but I'm not, as yet, using the version 4.0...I'm still on 2.5 for the 'mouse. Do you think updating to 4.0 and adding some kind of GPS "switch" will still not work? Perhaps I also need to add the actual GPS to the panel before it will work (I haven't done that...just added the FS9 default 737-400 GPS-NAV switch)? I'm going to update to 4.0 anyway...just as soon as I land at LIBR in my current flight. Just wondering if 2.5 vs. 4.0 will make any difference. Anywho, ideally I would like to select between the CIVA INS and GPS...if possible in the future. If not I'll live with it...y'know?

Bob...have you had a chance to look at this thread? If so let me know if there's an answer or not. That way I'll move on and not keep waiting :( Vic

I fly at a VA which uses the 737-200 for humanitarian cargo flights all over the World. Some of these are at the edge of the 732's safe range and are very long. While I love the CIVA INS unit it is only practical when I'm actually at the computer to switch to the next ADEU card on these long flights. Yes...I admit it...I have a life and cannot spend hours upon hours waiting for the next ADEU card switch :( . So, is there some way to just use GPS navigation for long routes? I added the "NAV/GPS" switch from the default FS9 737-400 as suggested here (a long time ago) but that switch did nothing. I was in "RAD" mode...not "NAV", and selected "VOR/LOC" on the AP and switched to GPS...the aircraft just blew straight through the route and kept going straight. One thing I wonder about...this flight plan had no VOR's at the beginning...only intersections. Do I have to lock on to a VOR before I can switch to GPS mode using the added 737-400 switch...or is there more to it than that?I'm still using V1.25, BTW...just realized we were up to 1.40. :( Vic

Made a support ticket to PMDG regarding this and they got right back to me (sweet!). "Did you try renaming or deleting the FS9.cfg file? It looks like there's a funky saved panel state in there for some reason.RegardsPaul GollnickManager Customer SupportPrecision Manuals Development Group" I deleted the FS9.CFG and, while at it, I replaced the default flight (FLTSIM.FLT) with the original from the CD...just to be sure. Started FS9 to create a new FS9.cfg and all is working well in the world! I'm waiting to hear back from support regarding what part of the FS9.cfg they suspect caused the problem before doing any changes. :( :( :( Thanks for the help, PMDG support!

OK...tried all the suggestions. Uninstalled the MD-11 and made sure all files were gone. Installed the FS9 PMDG MD-11 and the version update. Did a defrag. Loaded the default FS9 Cessna flight, went to the Cockpit view and loaded the MD-11. The panel was fine, at this point. Moved to my departure airport, loaded the flightplan in FS9...and saved the flight. Exited FS9 and rebooted the system. Restarted FS9 and loaded the saved flight...and it still did not load the panel correctly...SSDD :( Anyone else have any suggestions?

As I said...this is a brand new install with no liveries added yet. The only thing added is the FS9 MD-11 update to version v1.20.0055. I can try all day...same result. I'll give the defrag a go and then try to build the flight again and see what happens.

Nope...it's still not working. I load the default Cessna, move to my departure airfield, go to the main panel view and then load the MD-11. I set Cold & Dark and at this point the panel looks like it should and used to, in the past. I then save the flight. When I reopen the saved MD-11 flight I get this:What the heck is going on here?? I've never had these kind of problems with the PMDG MD-11 before.

I believe the Subject line should read "Undocked".I decided to dust off my MD-11, it's been 6 months since I last flew it, but ran into an issue I haven't seen in this aircraft before. When I load the MD-11, either from the "Create a Flight" menu or after loading the default FS9 Cessna flight, my MD-11 panel loads with undocked windows? I did an uninstall of the MD-11, made sure everything was truly gone, and reinstalled it...no difference. In the screen shot below I have moved the 3 "undocked" panels so you can see what all is happening.I also deleted the UI Generated Flight from the Panel States folder as I read another thread here from an FSX user with the same problem. Thought I would try it even though I'm FS9. Didn't help at all. That user never found a solution (at least from the thread I read).My PMDG 747's and 737's load fine, BTW. Any ideas?Vic

See how quiet it gets when you mention those things? :(

Been there, tried that. The other thing to consider is that one thing I've learned in my 15 years simming...badmouthing a payware dev here or at the "other sim website" will get your post deleted quickly...if not your member account here outright cancelled (I speak with some experience in this matter :( ). Avsim gets a lot of support from payware developers and they get a bit touchy when you start hammering them. The other thing is that most people have moved on, so to speak. This is an FS9 addon and the general concensus with the public is "oh well"...unless you happen to be one of the unlucky slobs who bought the package. There are enough of them at the dev's website asking for things to be corrected...but like the other FS9 aircraft I bought from them..."we are no longer supporting this product". :( They are selling FSX aircraft and some disatisfied customers of older products that were never right means little to them. I tell everybody who asks for opinions on their products all about our past experiences with them. That and keeping my money away from them is about all I can do. I've heard some say that there newer products are just dandy but I refuse to reward previous bad behavior just because some say that it's all better now.

The configurator sets whether there is a VC or 2D views, the type of panel (analog or EICAS), matte or semi-gloss exterior, various effects (engine smoke, fuel dump, flares, etc.), interior lighting color, interior glass reflections, external fuel tanks (on or off) and fuel load, payload type (cargo, transport or casualties) and the sub-types of each and weight. You would need either a lot of time to figure what the tens of different models and panels in the aircraft folder are (actual aircraft model, VC or noVC, and on and on). If the .exe included an .ini that allowed you to set the "target" aircraft folder (of the 3 possibles) it might be workable...but I'm not even sure of that...at this point.

I was fairly certain that the "multiple aircraft.cfg" option was a no go...but I've made other assumptions before...and been completely wrong :( . In this case the 3 aircraft do have seperate Models and Air files...but those could have been worked with as they are selected in each aircraft entry in the aircraft.cfg. I'm reduced to trying to alter the configurator for this (no longer supported) FS9 payware, so that it will recognize and alter aircraft in 3 seperate aircraft folders...or just realizing I've been somewhat abused and remembering that for the rest of my FS buying life. The "realizing" part I got a while back...the "remembering" part is now firmly implanted into a cluster of healthy, working synapses. :( If there was competition for the "problem aircraft", I would spend the money and try the other developers entry...I have done this with the first aircraft I ever bought from "these" people...and never looked back. I do understand the decision to no longer create FS9 aircraft (don't much like it but...we've had this discussion enough)...it's all business, I understand that. But failing to fix a configurator for an FS9 aircraft you sold me just after FSX was released??? Not cool. That speaks completely of "let's get this last suckers bucks on an upgrade package and not spend another dime on any problems". Again...my bad...they repeated this similar scenario with another aircraft...the only payware one of this major model I know of. It wasn't FSX, that time...it was just..."we are done" and "we are closing our website for now". LOL! Too many complaints at that time and the new forums no longer allow help from those who could possibly "fix" the problems...or even much public discussion. I realize that many developers catch a lot of flack. So what...if you plan on being in this business you better have very thick skins. You are dealing with one of the most sophisticated entertainment software buyers in the World. This ain't "gaming". Throwing out the baby with the bath water is NOT the answer. No...you do not have to put up with ignorance or opposing business views ("I want you to make this for FS9 !). I think all of us FS9'ers get that. Most of you have made it emphatically clear why your decisions are what they are. But simply screwing people by selling a totally incomplete package and then saying, 2 days after taking my dime, we don't support it and we won't fix it?? That is wrong. Oh, sure...after enough complaints a "disclaimer" is added on the sales page...lot of good that does. Most developers at least try to support their products for a reasonable amount of time. I'm talking about those few who are obviously, by their very actions, interested in only one thing...screwing people out of their money. I'll mention no names...and I'll not spend another dime on people like this...a bit too little, too late for me, I'm afraid.

Using the program "FPconverter.exe" all my "cards" end at 7 waypoints:

Nah...I noticed it also but just figured the TM had been through so much "development" that it was one of those things that got lost...like you said.

Is it possible to have more than one "aircraft.cfg" in a single aircraft folder (aircraft.cfg, aircraft1.cfg, aircraft2.cfg, etc.) and enter a line in each aircraft entry for which CFG it uses? As an example:[fltsim.1]title=Boeing 737-400 Paint1sim=Boeing737-400cfg=aircraft2model=panel=sound=texture=1kb_checklists=Boeing737-400_checkkb_reference=Boeing737-400_refatc_id=N737Watc_airline=Landmarkatc_flight_number=1123ui_manufacturer=Boeingui_type="737-400"ui_variation="Landmark Airlines"I'm guessing not but, here's why I ask.A to be unnamed payware developer sold me an FS9 addon aircraft and a package of more addons to go with it. They did not, however, update their aircraft configuration program to look in the 2 extra aircraft folders the extra's added? And they have stated that they won't...FS9 you know..."we prefer to leave you in the lurch than fix this no longer supported FS9 stuff". How hard for them would it be? But, whatever, I'll never buy anything from them again. So, the aircraft configuration program is useless for any aircraft not in the original folder (for S&G's lets say D230, D233 and D230B are the folders...only aircraft in the D230 show up in the configurator). I have 2 options...somehow hack the configurator to change where it finds it's aircraft (no luck with that, so far) or combine all aircraft in the "D230" folder, yet retain their individual characteristics, from the "aircraft.cfg"'s. So...if option 2 is a no go...how do I find where the configurator EXE finds it's aircraft...and modify 2 copies of it?At least, if you are running FSX, you'll never have to worry about a developer abandoning you for the next version...LOL!

Are you saying it only searches the default FS9 Addon Scenery folder? If so that probably won't work for me. All of my FS9 Addon Scenery reside on their own HDD. If it also doesn't include the default FS9 "Textures" folder, it's not going to find the hundreds of default textures that many developers include in their addon scenery. What I need is a proggy that will search in folders I designate...in this case the default FS9 Texture folder and my Addon Scenery folder on it's own drive. Anything else misses the duplicates in my setup. This is why the old reliable FSManager no longer works...I've moved my Addon Scenery off of my FS9 drive. Vic